Development Process of Embedded Systems. Unlike the design process of software on a typical platform, the embedded system design implies that both hardware and software are being designed similarly Although this isn't continuously the case, it is a truth for many designs currently.

1. CONFIDENTIAL TRUNEXA INFOWAYS

2. EMBEDDED SYSTEM DEVELOPMENT PROCESS
Presented by
Pallavi Joshi
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 2

3. EMBEDDED SYSTEM DEVELOPMENT PROCESS
It is a programmed controlling & operating system Doing an activity in
with a dedicated function within a mechanical a systematic way.
or electrical system in real time computing.
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 3

4. Why process?
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 4
ES
SYSTEM
TEAM
HARDWARE
TEAM
SOFTWARE
TEAM
MECHANICAL
TEAM
USER
PROCESS
Step by Step procedure for
• Collaboration among teams
• Requirements Sharing
• Interpretations

5. Embedded system development phases
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 5
SYSTEM TEAM H/W TEAM S/W TEAM
REQ.DESIGNIMP.TESTING
System requirements
PHA,HA,RAMS
System architecture
Sub-system requirements
 H/W design S/W design Mechanical design
implementation implementation implementation
Sub-system interface
testing
System testing
MECHANICAL TEAM

6. System development models
• Waterfall Model
•V-Model
•AGILE Model
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 6

7. Waterfall Model
Requirements are very clear and frozen.
Architecture into sub-systems
Allocation of system to sub-system requirements
Each sub-system design
Sub-system testing , interface testing ,
functional testing
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 7
System
requirement
System architecture
Sub-system
requirement
System implementation
System testing

8. V-MODEL
•It is used where all requirements are not
available or requirements are going to be
changed.
•In this model ambiguous requirements are
cleaned up at design phase.
•Rework effort is less.
Advantage:
At every phase testability is checked and
requirements are made clear in terms of
measurability and ambiguity.
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 8
System requirement System testing
System
architecture
Sub-system
requirements Sub-system testing
Interface testing
System Implementation
System Team

9. AGILE Model
• Iterative & incremental
•Based on business value, requirements are
prioritized
•Care has to be taken to make sure that designed
platform or framework supports future
requirements.
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 9
Planning
Req. AnalysisTesting
DesigningImplementing

10. Embedded System development phases
• Requirement Phase
• Design Phase
• implementation Phase
• Testing phase
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 10

11. System Requirement Phase
Inputs Activity Outputs
Stakeholder System requirement analysis System requirement specification
Functional
Interface Hazard analysis HA specification
Performance (Preliminary & Detailed analysis)
Mechanical Catastrophic
Qualification Major
Business Minor
Operational RAMS RAMS specification
Maintenance
Disposal System safety analysis Safety specification
Compliance/Regularity and Safety integrity level
Safety & Security
Thermal
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 11

12. System design Phase
Inputs Activity Outputs
System req. specification System decomposition System
(Sub-systems) Architecture
HA specification System requirement Sub-system
Allocation to interface control
sub-system document
RAMS specification Compliance/traceability Sub-system
to RAMS & Safety specification
Safety specification Sub-system safety Traceability
integration level
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 12

13. System Implementation Phase
Inputs Activity Outputs
Sub-system specification Mechanical design Mechanical
H/W and S/W design design
Interface control Safety integrity level lifecycle documents
document H/W & S/W design
lifecycle documents
Traceability Traceability to RAMS & Safety Qualification testing
qualification testing documents
functional testing Functional testing
documents
Traceability docs.
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 13

14. System testing phase
Inputs Activity Outputs
Sub-system specification sub-system test cases Test cases &
results w.r.t sub-system
Sub-system interface doc. Sub-system testing
System specification doc. Sub-system interface test cases
System interface doc. Sub-system interface testing
System functional testing
System interface testing
System qualification testing
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 14

15. Conclusion
• To develop any embedded system a systematic way of activity is required. Each stakeholder
plays a crucial role in the success of product.
• Product success rate is also dependent on the development models we are choosing to develop
any ES.
• For product completion all the System development phases are required.
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 15

16. Thanks…
12/03/2018 CONFIDENTIAL TRUNEXA INFOWAYS 16

17. 10/23/2018 CONFIDENTIAL TRUNEXA TECHNOLOGIES 17
Haware Infotech Park, 1709,
Sector 30A, Vashi, Navi Mumbai,
Maharashtra 400703
contact@trunexa.com
sales@trunexa.com