A decision model for managing and communicating resource restrictions in embedded systems design

Requirements and requirement traceability play a key role in ensuring that embedded systems meet their goals. This article deals with improving requirements and requirement traceability to design artifacts in the context of embedded design. We identify a way for capturing decisions concerning limited resources in embedded systems. This approach directly integrates decision-related information with other traceability information gathered during requirements engineering. It relies on the concept of quantifiable budgets for structuring the decision information (decision model). Upon this model the prototype of a requirements traceability management tool has been developed reduces redundancies and inconsistencies in requirements management and lays the ground for improved collaboration and sharing of project knowledge between project members.

[1]  Philippe Kruchten,et al.  Architecture blueprints—the “4+1” view model of software architecture , 1995, TRI-Ada '95.

[2]  H. Heiser.  Budgetierung: Grundsätze und Praxis der betriebswirtschaftlichen Planung , 1964 .

[3]  Christian Wolff,et al.  Ein Entscheidungsmodell für das Tracing von Anforderungen , 2007, Software Engineering.

[4]  Ralf Kneuper,et al.  CMMI - Verbesserung von Softwareprozessen mit Capability Maturity Model Integration (2. Aufl.) , 2003 .

[5]  G. J. Muller,et al.  CAFCR: A Multi-view Method for Embedded Systems Architecting. Balancing Genericity and Specificity , 2004 .

[6]  Ankur Srivastava,et al.  Budget Management with Applications , 2002, Algorithmica.

[7]  Raymond McCall,et al.  Rationale Management in Software Engineering , 2006 .

[8]  Markus Kucera,et al.  An Integrated Decision Model For Efficient Requirement Traceability In SPICE Compliant Development , 2007, 2007 Fifth Workshop on Intelligent Solutions in Embedded Systems.

[9]  R. B. Hunter,et al.  Processes for software in safety critical systems , 2001, Softw. Process. Improv. Pract..

[10]  Kurt Schneider.  Rationale as a By-Product , 2006 .

[11]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[12]  Philippe Krutchen,et al.  Architectural blueprints--the '4+1' view model of software architecture , 1995 .

[13]  Julio Cesar Sampaio do Prado Leite,et al.  Perspectives on Software Requirements (Kluwer Internation Series in Engineering and Computer Science, 753) , 2004 .

[14]  Cristina Silvano,et al.  Power estimation of embedded systems: a hardware/software codesign approach , 1998, IEEE Trans. Very Large Scale Integr. Syst..

[15]  Richard Stevens,et al.  Requirements Traceability , 1997, RE.

[16]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[17]  Bruce Powell Douglass,et al.  Real-Time Design Patterns: Robust Scalable Architecture for Real-Time Systems , 2002 .

[18]  Si Qing Zheng.  Proceedings of the 18th IASTED International Conference on Parallel and Distributed Computing and Systems, November 13-15, 2006, Dallas, Texas, USA , 2006 .

[19]  Michael E. Atwood,et al.  Effective Design Rationale: Understanding the Barriers , 2006 .

[20]  Sébastien Gérard,et al.  Annotating UML Models with Non-functional Properties for Quantitative Analysis , 2005, MoDELS Satellite Events.

[21]  Herbert Hanselmann,et al.  Challenges in automotive software engineering , 2008, ICSE Companion '08.

[22]  John B. Shoven,et al.  I , Edinburgh Medical and Surgical Journal.

[23]  Majid Sarrafzadeh,et al.  Incremental Timing Budget Management in Programmable Systems , 2004, ERSA.

[24]  Giovanni De Micheli,et al.  Readings in hardware / software co-design , 2001 .

[25]  Manfred Broy,et al.  Requirements Engineering für eingebettete Systeme , 1999, Informationstechnik Tech. Inform..

[26]  Barbara Paech,et al.  An Experience-Based Approach for Integrating Architecture and Requirements Engineering , 2003, STRAW.