0% found this document useful (0 votes)
142 views27 pages

Lecture 4 CHaracteristics and Quality Attributes of Embedded Systems

The document discusses the characteristics and quality attributes of embedded systems. It describes six key characteristics: 1) application and domain specific, 2) reactive and real-time, 3) operates in harsh environments, 4) distributed, 5) small size and weight, and 6) power concerns. It also outlines two categories of quality attributes: operational (response, throughput, reliability, maintainability, security, safety) and non-operational (testability, evolvability, portability, time to market, cost). The document provides details and examples for each characteristic and quality attribute.

Uploaded by

Saikrishna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
142 views27 pages

Lecture 4 CHaracteristics and Quality Attributes of Embedded Systems

The document discusses the characteristics and quality attributes of embedded systems. It describes six key characteristics: 1) application and domain specific, 2) reactive and real-time, 3) operates in harsh environments, 4) distributed, 5) small size and weight, and 6) power concerns. It also outlines two categories of quality attributes: operational (response, throughput, reliability, maintainability, security, safety) and non-operational (testability, evolvability, portability, time to market, cost). The document provides details and examples for each characteristic and quality attribute.

Uploaded by

Saikrishna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 27

Lecture 4: Characteristics and Quality

attributes of Embedded systems


Presentation Outline
2

Characteristics Quality
of ES attributes of ES

Operational Non-Operational
quality quality
attributes attributes
INTRODUCTION
3

 No matter whether it is an embedded system in non-embedded


system there will be a set of characteristics describing the system.

 The non functional aspects that need to be addressed in embedded


system design are commonly referred as quality attributes.

 Whenever you design an embedded system, the design should take


into consideration for both
 Functional and non functional aspects
4

Characteristics of ES
Embedded Systems Characteristics
5

 Embedded systems process certain specific characteristics and these characteristics


unique to each embedded system.
 Some of the important characteristics of an embedded system are:
1. Application and domain specific
2. Reactive and Real Time
3. Operates in harsh environments
4. Distributed
5. Small size and weight
6. Power concerns
1. Application and Domain specific
6

 An embedded system is designed for a specific purpose only.

 It will not do any other task.

◼ Ex. A washing machine can only wash, it cannot cook.

 Certain embedded systems are specific to a domain:

◼ Ex. A hearing aid is an application that belongs to the domain of signal

processing.
2. Reactive and Real time
7

 Certain Embedded systems are designed to react to the events that occur in the nearby
environment. These events also occur real-time.
 Ex. An air conditioner adjusts its mechanical parts as soon as it gets a signal from its sensors to increase or
decrease the temperature when the user operates it using a remote control.
 An embedded system uses Sensors to take inputs and has actuators to bring out the required
functionality.
3. Operation in harsh environment
8

 Certain embedded systems are


designed to operate in harsh
environments.
 Very
high temperature of the deserts
or very low temperature of the
mountains or extreme rains.
 These embedded systems have to
be capable of sustaining the
environmental conditions it is
designed to operate in.
4. Distributed
9

 Certain embedded systems are part of a larger


system and thus form components of a distributed
system.
 These components are independent of each other
but have to work together for the larger system to
function properly.
 Ex. A car has many embedded systems controlled to its
dash board.

 Each one is an independent embedded system yet


the entire car can be said to function properly only if
all the systems work together.
5. Small size and weight
10

 An embedded system that is compact in size


and has light weight will be desirable or
more popular than one that is bulky and
heavy.
 Ex. Currently available cell phones. The cell
phones that have the maximum features are
popular but also their size and weight is an
important characteristic.

 For convenience users prefer mobile phones


than phablets. (phone + tablet pc)
6. Power concerns
11

 It is desirable that the power utilization and


heat dissipation of any embedded system be
low.
 If more heat is dissipated then additional units
like heat sinks or cooling fans need to be
added to the circuit.
 If more power is required then a battery of
higher power or more batteries need to be
accommodated in the embedded system.
QUALITY ATTRIBUTES OF EMBEDDED SYSTEM
12

 Quality attributes on non functional requirements that need to be


documented properly in any system design.
 If the quality attributes are more concrete and measurable it will
be a positive impact on the system development process and the
end product.
 The various quality attributes that need to be addressed in any
embedded system development or broadly classified into two
1. Operational Quality Attributes
2. Non-Operational Quality Attributes
Types of quality attributes
13

1. Operational Quality Attributes.


 These attributes are related to operation or functioning of an
embedded system. The way an embedded system operates affects its
overall quality.
2. Non-Operational Quality Attributes.
 These attributes are not related to operation or functioning of an
embedded system. The way an embedded system operates affects its
overall quality.
 These are the attributes that are associated with the embedded system
before it can be put in operation.
1. Operational QUALITY Attributes
14

 The important quality attributes coming under this category are listed
below:
1. Response
2. Throughput
3. Reliability
4. Maintainability
5. Security
6. Safety
1. Response and
15
2. Throughput
1. Response
 Response is a measure of quickness of the system.
 It gives you an idea about how fast your system is tracking the input variables.
 Most of the embedded system demand fast response which should be real-time.
2. Throughput
 Throughput deals with the efficiency of system.
 It can be defined as rate of production or process of a defined process over a stated period of time.
 In case of card reader like the ones used in buses,
 Throughput means how much transaction the reader can perform in a minute or hour or day.
3. Reliability
16

3. Reliability
 Reliability is a measure of how much percentage you rely upon the proper
functioning of the system .
 Mean Time Between Failures (MTBF) and Mean Time To Repair (MTTR) are
terms used in defining system reliability.
 Mean Time between failures
◼ The average time the system is functioning before a failure occurs.

 Mean Time To Repair


◼ The average time the system has spent in repairs.
4. Maintainability
17

 Maintainability deals with support and maintenance to the


end user or a client in case of technical issues and product
failures or based on a routine system check up
 It can be classified into two types:-
1. Scheduled or Periodic Maintenance (Preventive
maintenance)
◼ This maintenance is required regularly after a periodic time interval.
◼ Example : Periodic Cleaning of Air Conditioners
◼ Refilling of printer cartridges.
2. Maintenance to unexpected failure (corrective
maintenance)
◼ This involves the maintenance due to a sudden breakdown in the
functioning of the system.
◼ Example: Air conditioner not powering on
◼ Printer not taking paper in spite of a full paper stack
5. Security
18

 Confidentiality, Integrity and Availability are three corner stones of informatio


security.
 Confidentiality deals with protecting data from unauthorized disclosure.
 Integrity gives protection from unauthorized modification.
 Availability gives protection from unauthorized user
 Certain Embedded systems have to make sure they conform to the security measures
 Ex. An Electronic Safety Deposit Locker can be used only with a pin number like a password.
6. Safety
19

 Safety deals with the possible damage that can happen to the operating person and
environment due to the breakdown of an embedded system or due to the emission of
hazardous materials from the embedded products.
 A safety analysis is necessary in product engineering to evaluate the anticipated damage
and determine the best course of action to bring down the consequence of damages to an
acceptable level.
2. Non-Operational quality Attributes
20

 The important quality attributes coming under this category are


listed below.
1. Testability & Debug-ability

2. Evolvability

3. Portability

4. Time to prototype and market

5. Per unit and total cost.


1. Testability and Debug-ability
21

 It deals with how easily one can test his/her design, application and by which mean he/she can
test it.
 In hardware testing the peripherals and total hardware design functioning.
 Firmware testing is functioning in expected way
 Debug-ability is means of debugging the product as such for figuring out the probable sources
that create unexpected behavior in the total system
2. Evolvability
22

 For embedded system, the qualitative attribute “Evaluability”


refer to ease with which the embedded product can be modified
to take advantage of new firmware or hardware technology.
3. Portability
23

 Portability is measured of “system Independence”.


 An embedded product can be called portable if it is capable of performing its operation
as it is intended to do in various environments irrespective of different
 processor
 or controller and
 embedded operating systems.
4. Time to prototype and market
24

 Time to Market is the time elapsed between the conceptualization of a product and time at
which the product is ready for selling or use
 Product prototyping help in reducing time to market.
 Prototyping is an informal kind of rapid product development in which important feature
of the under consider are develop.
 In order to shorten the time to prototype, make use of all possible option like use of reuse,
off the self-component etc.
5. Per unit and total cost
25

 Cost is an important factor, which needs to be carefully


monitored.

 Proper market study and cost benefit analysis should be


carried out before taking decision on the per unit cost of the
embedded product.

 When the product is introduced in the market, for the initial


period the sales and revenue will be low.

 There will not be much competition when the product sales


and revenue increase.

 During the maturing phase, the growth will be steady, revenue


reaches highest point, and at retirement, time there will be a
drop in sales volume.
26
GKK Rayudu

You might also like