A model-based development process for embedded systems

Tagungsband - Dagstuhl-Workshop MBEES: Modellbasierte Entwicklung eingebetteter Systeme, MBEES 2005

Volumn , Issue , 2005, Pages 191-202

  Heisel, Maritta ^a   Hatebur, Denis ^a,b  

^a UNIVERSITY OF DUISBURG ESSEN   (Germany)

^b Institut für Technische Systeme GmbH   (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

DEVELOPMENT PROCESS; EMBEDDED SOFTWARE COMPONENTS; HARDWARE AND SOFTWARE COMPONENTS; INDUSTRIAL PRACTICES; MODEL BASED DEVELOPMENT;

EMBEDDED SYSTEMS;

EID: 84873467676     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (11)

1. Ramesh Bharadwaj and Constance Heitmeyer. Hardware/Software Co-Design and Co-Validation using the SCR Method. In Proceedings IEEE International High-Level Design Validation and Test Workshop (HLDV 99), 1999.
2. Manfred Broy and Wolfgang Pree. Ein Wegweiser für Forschung und Lehre im Software-Engineering eingebetteter Systeme. Informatik Spektrum, 18:3-7, Februar 2003.
3. Common Criteria for Information Technology Security Evaluation, 1999. aligns to ISO/IEC 14508:1999, see http://www.commoncriteria.org.
4. J. Madey D. L. Parnas. Functional documents for computer systems. In Science of Computer programming, volume 25, pages 41-61, 1995.
5. M. Heisel. Agendas. A Concept to Guide Software Development Activites. In R. N. Horspool, editor, Proc. Systems Implementation 2000, pages 19-32. Chapman & Hall London, 1998.
6. M. Heisel and J. Souquières. A Method for Requirements Elicitation and Formal Specification. In J. Akoka, M. Bouzeghoub, I. Comyn-Wattiau, and E. Métais, editors, Proceedings 18th International Conference on Conceptual Modeling, ER'99, LNCS 1728, pages 309-324. Springer-Verlag, 1999.
7. International Electrotechnical Commission. Functional safety of electrical/electronic/programmable electronic safty-relevan systems - Part 1: General Requrements, 1998.
8. M. Jackson. Problem Frames. Analyzing and structuring software development problems. Addison-Wesley, 2001.
9. M. Jackson and P. Zave. Deriving Specifications from Requirements: an Example. In Proceedings 17th Int. Conf. on Software Engineering, Seattle, USA, pages 15-24. ACM Press, 1995.
10. Object Management Group OMG. UML 2.0 Infrastructure Specification, 2003.
11. P. Zave and M. Jackson. Four dark corners for requirements engineering. ACM Transactions on Software Engineering and Methodology, 6(1):1-30, January 1997. Also availble under http://www.research.att.com/.pamela/ori.html#fre.