1. UNIT 5 EMBEDDED SYSTEM DEVELOPMENT

2. INTRODUCTION Design issues and techniques. Case studies
INTRODUCTION Design issues and techniques. Case studies . Complete design of examples embedded systems

3. 3 GOALS OF DESIGN PROCESS *Time to market. * Design. * Quality.

4. TIME TO MARKET :
Customer always want new features.
The product that comes first that wins the market..
Even the customer preferences for the feature generations of the product.
The PROFITABLE MARKET LIFE OF some products is 3 to 6 months..
If we get delay for release for the product then we can never make the money for ever.
Example : calculators and school bags . Which always should sale in the correct season to grab the money .if we fail we cannot get money so we want to wait for the another season.

5. DESIGN COST:
Consumer products are cost sensitive.
Industrial buyers are more concerned about the COST.
Designing cost differs from the manufacturing cost- deals about the cost of engineers salaries,computers used in design.
Only one or a few copies of embedded system can be build.
So design cost can be DOMINATE the MANUFACTURING COSTS.
MANUFACTURING COSTS: it tells about the higher volume consumer devices based on the time to market pressures.

6. QUALITY:
Customer not only want their products fast and cheap they also want them to be right.
During the design of the product to obtain the high quality product at the end it should have the correctness and reliability and usability

7. Process change over time .
They change due to external and internal forces .
Customer may change , requirements change,products change, available components change.
People learn to do things better ,they move on to other projects and others comes in and also the companies are brought .
Software engineers have spent a lot of time on thinking about the software design processes.
Much of this thinking has been motivated by the mainframe computers such as databases.
But embedded applications inspired about the software design processes.

8. Design flow is the sequence of steps to be followed during a design.
DESIGN FLOWS:
Design flow is the sequence of steps to be followed during a design.
Some of the design steps can be performed by tools such as COMPILERS or CAD systems.
Other steps can be performed by hand.
May be partially or fully automated.
Use tools to transform, verify design.
Design flow is one component of methodology. Methodology also includes management organization, etc.

9. WATER FALL MODEL
Early model for software development.
The first model proposed for the software development process .
Introduced by ROYCE.

10. Major phases of water fall model.
requirements
architecture
coding
testing
maintenance

11. Waterfall model steps
Requirements: determine basic characteristics.
Architecture: decompose into basic modules.
Coding: implement and integrate.
Testing: exercise and uncover bugs.
Maintenance: deploy, fix bugs, upgrade.

12. Water fall model represents the one way flow of work and the information from the higher level of abstraction.
With the limited amount of feed back to the next higher level of abstraction.
Top down design is ideal because it employs the good fore knowledge of implementation during the early design phases.
It requires an bottom up feed back for most of the design projects.
As a result , the waterfall model is today considered as the unrealistic design process.

13. Waterfall model critique
Only local feedback---may need iterations between coding and requirements, for example.
Doesn’t integrate top-down and bottom-up design.
Assumes hardware is given.

14. SPIRAL MODEL: system feasibility specification prototype
initial system
enhanced system
requirements
design
test

15. An alternative model of software development called the spiral model.
While the waterfall model assumes that the system is built once in its entirety .
The spiral model assumes that the several versions of the systems will be built .
Early systems will be simple mock ups .
As the design progresses , more complex systems will be constructed.
At each level of design ,the designers go through the requirements,construction and testing phases.
At the later stages when more complete versions of the systems are constructed.

16. Each phase requires more work, widening the design spiral .
This successive refinement approach helps the designers understand the system they are working on through the series of the design cycles.
The cycles at the top of the spiral are very small and short .
While the final cycles at the bottom add detail learned from the earlier cycles of the spiral .
The spiral model is more realistic than the waterfall model because of MULTIPLE ITERATIONS are often necessary to add enough detail to complete a design .
However in spiral model having too much long of spiral takes more time to design with the major requirement.

17. SUCCESSIVE REFINEMENT MODEL :
specify
specify
architect
architect
design
design
build
build
test
test
initial system
refined system
Overheads for Computers as Components 2nd ed.

18. HARDWARE/SOFTWARE DESIGN FLOW
requirements and
specification
architecture
software design
hardware design
integration
testing
© 2008 Wayne Wolf
Overheads for Computers as Components 2nd ed.

19. Embedded computing systems often involve the design of the hardware as well as software .
The above diagram shows the design methodology for a combined hardware/software project.
Front end activities such as specifications and architecture simultaneously consider hardware and the software aspects.
Back end integration and testing consider the entire systems .
In the middle ,however ,development of the hardware and software components can go on independently.

20. CONCURRENT ENGINEERING:
when designing the large systems people may lose track of complete design flow and have each designers take a narrow view of his /her role in the design flow.
CONCURRENT ENGINEERING attempts to broader approach and optimize the total flow.
REDUCED DESIGN TIME is an important goal for an concurrent engineering.
It tries to eliminate the “over-the-wall “design steps in which one designer performs an isolated task and then throws the result over the wall to the next designer ,with the little interaction between the two .
Concurrent engineering requires eliminating the wall between the design and manufacturing.

21. CONCURRENT ENGINEERING ELEMENTS :
CROSS FUNCTIONAL TEAMS:
It includes members from various disciplines involved in the process, including manufacturing,hardware and software design ,marketing and so on.
CONCURRENT PRODUCT REALIZATION :
Doing several things at once,such as designing various subsystems simultaneously .It is critical to reducing the design time.
INCREMENTAL INFORMATION SHARING:
As soon as new information is available about the new product it is shared and integrated into the design .They are important to the effective sharing of information in the timely fashion.

22. INTEGRATED PROJECT MANAGEMENT:
It ensures that someone is responsible for the entire project.
EARLY AND CONTINUAL SUPPLIER INVOLVEMENT:
It makes the best use of suppliers capabilities.
EARLY AND CONTINUAL CUSTOMER FOCUS:
It ensures that the product best meets the customer’s needs.