Thammanoon Kawinfruangfukul

CSSE MS, ID: 1584488782

Incremental Commitment Spiral Modelfor Embedded Systems

2

Agenda What is an embedded system? Hardware/Software co-design ICSM for embedded systems Summary

3

Agenda What is an embedded system? Hardware/Software co-design ICSM for embedded systems Summary

4

What is an embedded system?

a system consists of hardware and software designed and implemented for a particular application.

Characteristics Special-purpose• Multiple functions

Resource-constrained• Memory, Processor speed

Reactive

Hardware and Software co-exist• Using software is more flexible

and extendable Intel Embedded Community

5

Hardware/Software Co-design

Concurrent and cooperative design

Hardware/Software Trade-offs• Performance Vs. Cost

Similarities and differences between Software and Hardware Similarities: modules and reusable elements Differences: hardware (physical characteristics)

ICSM Principles: Concurrent hardware-peopleware-software system definition and development

6

Hardware/Software Co-design (cont.)

System description

HW/SW Partitioning

Software synthesis

Interface synthesis

Hardware synthesis

System integration

The Codesign of Embedded Systems: A Unified Hardware/Software Representation

7

ICSM for embedded systems Adopt and extend ICSM for Architected Agile Process

Apply Hardware/Software Co-design

Focus on embedded software development• Identify project roles, activities, and tools• Excluding operation phase

ICSM for Architected Agile Process ICSM for embedded systems

Project managerOperational concept engineerFeasibility AnalystLife Cycle PlannerDevelopment teamRequirements engineerQuality Focal PointIIV&VSoftware architectPrototyperBuilderTesterTrainer

ManagersOperational concept engineerFeasibility AnalystLife Cycle PlannerDevelopment teamRequirements engineerQuality Focal PointIIV&VSystem architectHardware/Software prototypersHardware/Software buildersPCB DesignerTesterTrainer

8

Managerial roles and activitiesRoles Product manager Hardware manager Software manager Reliability manager

Activities Detail project plan Track and record project progress

Tools MS Project Effort report system

9

Exploration phase

Operational concept engineer Feasibility Analyst Life Cycle Planner

Analyze current system operation, business

workflow, environment (hardware/software)

Identify, assess, and mitigate risks

Identify responsibilities and current & required

skills

IIV&V

Verify and validate work products

10

Valuation phaseOperational concept engineer

Define operational

concept

Explore and

evaluate alternative

hw /sw components

Feasibility Analyst

Identify, assess,

and mitigate

risks

Explore and

evaluate alternative

hw /sw components

Requirements engineer Life Cycle Planner IIV&V and QFP

Merge

Define and assess system

requirement

Negotiate and

gather win

conditions

Plan for project

life cycle

Identify responsibilities,

milestones, and life cycle management

approach

Identify quality

management strategy

Verify & validate

work products

Merge

System architectHardware prototyper

& PCB designer

Identify and

assess interface between hw&sw

Identify and assess

hw/sw components

to be simulated

and modeled

Hw& Sw trade off analysis

Software prototyper

Provide project

feasibility evidence

design and assess PCB

schematic/layout

develop and assess hardware prototype

Prepare development

software (cross-

platform)

develop and assess prototype

11

Foundations phase

Development team System architect Hardware prototyper/Builder & PCB designer

Assess project status

Specific detail system design

IIV&V and QFPSoftware prototyper/Builder

Construct traceability

matrix

Fix hardware

components defects

Simulate and model

the hardware

components

develop and assess hardware prototype

Fix software

components defects

develop interface between

hardware and

software

develop and assess software

prototype

Identify CM

Verify and

validate work

product

12

Development team Life Cycle PlannerHardware/Software

Builder

Assess project status

IIV&VTester

Plan and manage project

Develop Transition

plan

Cross-platform testing

Develop and integrate system

Verify and validate

work product

Development phase: Construction iteration

Develop and assess user

manual

Develop Support

plan

13

Development phase: Transition iteration

Development team Trainer IV&V

Transit the system

Provide Training

Verify and validate

work product

14

Summary

Embedded systems ICSM for embedded systems• Exploration phase• Valuation phase• Foundation phase (co-design)• Development phase (co-verification and validation)

Construction Iteration Transition Iteration

Contribution to CSCI 577ab

15

ReferencesRaj Kamal, Embedded Systems, Architecture, Programming and Design, Tata McGraw-Hill, 2003.

S. Kumar, S. Klumar, “The Codesign of Embedded Systems: A Unified Hardware/Software Representation”, Kluwer Academic Publishers, 1995.

Incremental Commitment Spiral Model - Electronic Process Guidelines http://greenbay.usc.edu/IICMSw/ accessed on March 5, 2012

Boehm, B., Lane, J., Koolmanojwong, S.:A Risk-Driven Process Decision Table to Guide System Development Rigor. In: Proceedings of the 19th International Conference on Systems Engineering, Singapore, July, (2009).

Qian, K., Den Haring, D., Cao, L.: Embedded software development with c, Springer US (2009).

Zurawski, Richard. Embedded systems handbook : embedded systems design and verification. CRC Press, 01 Jun 2009.