150 likes | 339 Views
Incremental Commitment Spiral Model for Embedded Systems. Thammanoon Kawinfruangfukul CSSE MS, ID: 1584488782. Agenda. What is an embedded system? Hardware/Software co-design ICSM for embedded systems Summary. Agenda. What is an embedded system? Hardware/Software co-design
E N D
Incremental Commitment Spiral Modelfor Embedded Systems ThammanoonKawinfruangfukul CSSE MS, ID: 1584488782
Agenda • What is an embedded system? • Hardware/Software co-design • ICSM for embedded systems • Summary
Agenda • What is an embedded system? • Hardware/Software co-design • ICSM for embedded systems • Summary
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
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
Hardware/Software Co-design (cont.) System description HW/SW Partitioning Hardware synthesis Software synthesis Interface synthesis System integration The Codesign of Embedded Systems: A Unified Hardware/Software Representation
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
Managerial roles and activities • Roles • Product manager • Hardware manager • Software manager • Reliability manager • Activities • Detail project plan • Track and record project progress • Tools • MS Project • Effort report system
Exploration phase Life Cycle Planner Operational concept engineer Feasibility Analyst IIV&V Analyze current system operation, business workflow, environment (hardware/software) Identify responsibilities and current & required skills Verify and validate work products Identify, assess, and mitigate risks
Valuation phase IIV&V and QFP Operational concept engineer Feasibility Analyst Requirements engineer Life Cycle Planner Define operational concept Explore and evaluate alternative hw/swcomponents Identify, assess, and mitigate risks Negotiate and gather win conditions Identify responsibilities, milestones, and life cycle management approach Verify & validate work products Identify quality management strategy Explore and evaluate alternative hw/swcomponents Define and assess system requirement Merge Merge Hardware prototyper & PCB designer System architect Software prototyper Prepare development software (cross-platform) Provide project feasibility evidence Plan for project life cycle Hw& Sw trade off analysis design and assess PCB schematic/layout develop and assess hardware prototype Identify and assess interface between hw&sw Identify and assess hw/sw components to be simulated and modeled develop and assess prototype
Foundations phase Hardware prototyper/Builder & PCB designer Software prototyper/Builder Development team System architect IIV&V and QFP develop interface between hardware and software Verify and validate work product Identify CM develop and assess hardware prototype develop and assess software prototype Assess project status Construct traceability matrix Specific detail system design Simulate and model the hardware components Fix hardware components defects Fix software components defects
Development phase: Construction iteration Hardware/Software Builder Tester IIV&V Development team Life Cycle Planner Verify and validate work product Develop and integrate system Assess project status Plan and manage project Cross-platform testing Develop Transition plan Develop Support plan Develop and assess user manual
Development phase: Transition iteration Development team IV&V Trainer Provide Training Transit the system Verify and validate work product
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
References • Raj 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.