|
 



 |


A computer system that is a component of a larger machine or

system.

Embedded systems can respond to events in real time.

System designed to perform one or a few dedicated functions or a

specific task

A system containing a processor where the processor is not

generally re-programmable by the end user.

  
  
  

 
An embedded system is a special-purpose system in which the
computer is completely encapsulated by the device it controls.

Unlike a general-purpose computer, such as a personal computer, an

embedded system performs , pre-defined tasks, usually with very
specific requirements.

Since the system is dedicated to a specific task, design engineers can

optimize it, reducing the size and cost of the product.

Embedded systems are often mass-produced ,so the cost savings may
be multiplied by millions of items.
|
 | 
þ  |

   |
h. Complex Algorithms: Sophisticated and dedicated operations
2. User Interface: Multiple Menus and many options
3. Real Time: Missing deadline is not allowed
4. Multi rate: Many operations at a time (Some are slow and some
of them are at fast rate)
5. Cost: Manufacturing cost- Microprocessor used
Amount of Memory
Type of I/O
Power Cost- Battery life
Heat Dissipation
  

|
h. Hardware needed: Microprocessor Selection
Power and Hardware relation
Memory (Foot print / Swap)
I/O Peripherals
2. To meet Deadlines:Speed up hardware so that program
runs faster
System more expensive
CPU clock
3. Minimize Power Consumption:Heat Dissipation
Slow switching devices
4. Design for Upgrade ability:Versions of the product
Hardware or software changes
5. Reliability: System should work properly
Safety for critical systems
Complex testing
Limited controllability
Restricted development environment
Design Process

Requirements

Specification

Architecture

Components

System Integrity
 ã 


h. Performance: Usability of the system

Optimization
2. Cost: Manufacturing cost
Components, Assembly
Non Recurring Engineering Cost
Personal, other cost of design
3. Physical: Size, shape and weight
4. Power: Battery life (consumption)
Heat dissipation
  

h. Ambassador between Customer and Architects

2. Customer requirements should be carefully drafted
3. It should be accurately reflected for i/p to architects
4. It decides What system does?
5. Use of UML design recommended
 

h. It decides How system does it?

2. It plans overall structure
3. It gives I/p to design components
4. Use of Block diagram is recommended
5. It shows implementation details
6. It tells about both hardware as well as software
  



h. It includes Hardware and software

2. Actual implementation of Architecture
3. Use of readymade components or customer specific
components
4. Considering Power, memory and Microprocessor design
  
  

h. Putting components all together

2. Just plugging everything together
3. Resolves bugs and fixing the bugs (Testing)
4. Give ready to use product for implementation
 ]  |
h. Conceptualize different task in diagram
2. Use of Unified Modeling Language (UML)
3. Maintain levels of abstraction
4. Encourages the design to described as number of interacting
objects
5. Objects will correspond to real pieces of software or hardware
in system
6. It uses Description: Structural Description
Behavioral Description
  

h. Includes basic components

2. Classes, attributes and functions
3. Relationships / links: Association, Aggregation, composition,
generalization
4. It includes Interface
5. It implements all above points
þ  

h. It implements with state machine

2. It triggers by occurrence of event
3. It Uses Sequence diagram