Unit 2

1.An embedded operating system is an operating system for embedded computer systems. These
operating systems are designed to be compact, efficient at resource usage, and reliable, forsaking
many functions that non-embedded computer operating systems provide, and which may not be
used by the specialized applications they run. They are frequently also referred to as real-time
operating systems, and the term RTOS is often used as a synonym for embedded operating system.
2. An embedded system is a computer system with a dedicated function within a larger mechanical
or electrical system, often with real-time computing constraints.[1][2] It is embedded as part of a
complete device often including hardware and mechanical parts. Embedded systems control many
devices in common use today.[3]
Properties typical of embedded computers when compared with general-purpose ones are e.g. low
power consumption, small size, rugged operating ranges and low per-unit cost. This comes at the
price of limited processing resources, which make them significantly more difficult to program and to
interface with.
3. Embedded System Design: Modeling, Synthesis and Verification introduces a model-based approach to system
level design. It presents modeling techniques for both computation and communication at different levels of
abstraction, such as specification, transaction level and cycle-accurate level. It discusses synthesis methods for
system level architectures, embedded software and hardware components. Using these methods, designers can
develop applications with high level models, which are automatically translatable to low level implementations. This
book, furthermore, describes simulation-based and formal verification methods that are essential for achieving design
confidence. The book concludes with an overview of existing tools along with a design case study outlining the
practice of embedded system design. Specifically, this book addresses the following topics in detail:
. System modeling at different abstraction levels
. Model-based system design
. Hardware/Software codesign
. Software and Hardware component synthesis
. System verification

4. Mobile Computing is "taking a computer and all necessary files and software out into the
field".[1] Mobile computing is any type of computing which use Internet or intranet and respective
communications links, as WAN, LAN, WLAN etc. Mobile computers may form a wireless personal
network or a piconet.
There are at least three different classes of mobile computing items:

portable computers, compacted lightweight units including a full character set keyboard and
primarily intended as hosts for software that may be parametrized, as laptops, notebooks,
notepads, etc.

mobile phones including a restricted key set primarily intended but not restricted to for vocal
communications, as cell phones, smart phones, phonepads, etc.

wearable computers, mostly limited to functional keys and primarily intended as incorporation
of software agents, as watches, wristbands, necklaces, keyless implants, etc.

5. Context.
Device Proliferation.
Voice, Prioritized Over Touch.
Heads-Up Interfaces.
Bigger -- And Smaller -- Touch Devices, And Adaptive UIs
Mobile Apps Become Pluggable Mobile Services.
Wearables, Connectables And Local Networks.
Hybrid Application Model
Cloud-Powered Development.
6. Two

Tier. The access and data layers for the component products are separated
onto different servers.
Two Tier Logical Architecture
In a two tier logical architecture, the data stores communicate through front-end
processes. In the case of Messaging Server, this means MMPs, MEMs, and MTAs are
residing on separate machines from the data store processes. This enables the mail
store to offload important and common tasks and focus on receiving and delivering
mail. In the case of Calendar Server, this means the HTTP service and Administration
service reside on a separate machine from the store processes. In the case of Instant
Messaging, this means the proxy service is residing on a separate machine from the
back-end processes.
There might be some level of cohabitation with other services. For example, you
could have the Calendar store and the Message Store on the same machine. Similarly,
you could have the calendar front end on the MMP machine.

In a two tier logical architecture, Directory Server is usually a complex deployment in

its own right, with multi-master and replication to a set of load-balanced consumer
directories.
Figure 4-4 represents the two tier logical architecture for Communications Services.
Figure 4-4 Two Tier Logical Architecture

In the preceding figure, end-user client programs, such as Outlook and Messenger
Express, form the User Tier. The load balancers form Tier 0. The Calendar Server,
Messaging Server, and Instant Messaging front ends form Tier 1. Finally, the
Directory Server, Calendar Server, Messaging Server, and Instant Messaging back
ends form Tier 2. This architecture enables you to deploy Tier 1 and Tier 2 elements
as separate instances, increasing overall flexibility of design. Additionally, you
enhance system security by assigning discrete functions to individual instances.
For typical deployments, place the messaging and calendar front ends within the
network Demilitarized Zone (DMZ), connecting to the main messaging and calendar
services through a firewall. This configuration enables you to scale the system
horizontally, as the Tier 1 elements can be scaled independently. Do not scale these
elements beyond the capacity of the back-end servers.

When the front-end elements have reached the capacity of the back-end servers, you
can scale the back-end Tier 2 elements to support more users. In general, the front end
should scale as a function of the traffic. The back end should be scaled as a function
of the number of users.

7. DEFAULTS

Base
Print

LAYOUT

Grid
Panel
Article
Comment
Utility
NAVIGATIONS

Nav
Navbar
Subnav
Breadcrumb
Pagination
Tab
ELEMENTS

List
Description list
Table
Form
COMMON

Button
Icon
Close
Badge
Alert
Thumbnail
Overlay
Progress
Text
Animation

JAVASCRIPT

Dropdown
Modal
Off-canvas
Switcher
Toggle
Tooltip
Scrollspy
Smooth scroll

12. Swype is a virtual keyboard for touchscreen smartphones and tablets originally developed by
Swype Inc.[2] where the user enters words by sliding a finger or stylus from the first letter of a word to
its last letter, lifting only between words.[3] It uses error-correction algorithms and a language model
to guess the intended word. It also includes a predictive text system, handwriting and speech
recognition support. Swype was first commercially available on theSamsung Omnia II running
Windows Mobile,[4] and was originally pre-loaded on specific devices.
15. How do you define a good Exception Management for an N-Tier ASP.NET application?"
Pretty simple question, but not that simple to answer.
We are good at making things. But, may be, we are not equally good at designing a system which
properly handles errors with gracefulness, provides user with a polite message about the error and
doesn't leave him/her in a dead-end, and internally, notifies the system developers with enough
details so that the poor developers don't feel like they need to learn some rocket science to fix those
errors.
So, if you ask me the same question, I would tell you the following:
Your system has a good exception management if:

It doesn't show unnecessary technical error descriptions when an error occurs, rather, apologize to
user with a screen that something went wrong and let him/her go back to the system.
When an error occurs, it immediately notifies technical teams with detailed information for
troubleshooting, along with logging error details.
It has exception management done in a central and manageable manner without
unnecessarytry..catch...throw spread across the overall code base.
So, if we want to ensure a good exception management in our ASP.NET application, we need to meet
these three high level objectives.

16. In marketing, customer lifetime value (CLV) (or often CLTV), lifetime customer value (LCV),
or user lifetime value(LTV) is a prediction of the net profit attributed to the entire future relationship

with a customer. The prediction model can have varying levels of sophistication and accuracy,
ranging from a crude heuristic to the use of complex predictive analyticstechniques.

At Apsalar, were focused on providing the most powerful set of actionable

analytics to increase user engagement for mobile app publishers. Our
mission is to help you improve retention and increase monetization from
engaged users. We recently launched an educational blog series to help
developers understand the various types of analyses available to better
understand user behavior and increase user engagement. Catch up by
starting here.
17.

Improved Retention: Are users more likely to come back to the app?
Better Engagement: Are users more active within the app?
Increased Monetization: Are users spending more money?
Cohorting event
o Event: Launched App (for the first time, by week)
o This allows you to draw distinctions between users that launched the app for the first
time in the week immediately prior to your app update.
Retention indicator event
o Event: Relaunched App
o Because there is no overlap in the different cohorts, well be able to see whether the
update increased retention by comparing the different weeks.

18. The Data Quality Constraints Library provides generic SPARQL query
templates that may be used to identify different types of data quality problems.
The query templates are designed based on the SPARQL Inferencing
framework (SPIN) [1]. The query templates can easily be adjusted to any
Semantic Web data set and are immediately available to detect data quality
problems in the data. The constraints library may also be used for relational
data in conjunction with wrapping technologies such as D2RQ.
The Data Quality Constraints Library is of interest for data publishers and data
consumers. Data publishers may use the constraints to assure the published
data is of high quality. Data consumers may use the constraints to check the
quality state of the data before relying on it. The broad application of data
quality constraints may, moreover, help to achieve trust in Semantic Web
data.
19.The Open Web Application Security Project (OWASP) is a 501(c)(3) worldwide not-for-profit
charitable organization focused on improving the security of software. Our mission is to make
software security visible, so that individuals and organizations worldwide can make informed
decisions about true software security risks.

Everyone is free to participate in OWASP and all of our materialsare available under a free and open
software license. You'll find everything about OWASP here on or linked from our wiki and current
information on our OWASP Blog. OWASP does not endorse or recommend commercial
products or services, allowing our community to remain vendor neutral with the collective wisdom
of the best minds in software security worldwide. We ask that the community look out
for inappropriate uses of the OWASP brand including use of our name, logos, project names and
other trademark issues.
20. 1.Law: Illegal or improper alteration of, or interference with, a document or evidence; or meddling or negotiating with
a witness to influence his or her testimony.
2.Quality control: Continually adjusting a process to compensate for variations in its output. If the variations are within
the control limits of a stable system (and all stable systems have variations) then tampering invariably makes things
worse. Only a change in the system itself (and not any ad hoc adjustment) can reduce variation and improve quality. Urge
to temper (trying to do 'one's best,' but actually messing around) springs from the nave desire to do something anything
to improve results without sufficiently understanding the system, and ruins an otherwise working process. Tampering and
its effects are demonstrated with the help of funnel experiment. Not to be confused with tempering.