Abstract
The need to co-develop requirements and architectural artefacts, especially for innovative solutions, is widely recognised and accepted. Surprisingly, no comprehensive approach exists to structure the co-design process and to support the stakeholders, requirements engineers, and system architects in co-developing innovative requirements and architectural artefacts. In this paper, we propose a method for the co-design of requirements and architectural artefacts based on two viewpoints, the system usage viewpoint and the system architecture viewpoint. Initially, the two viewpoints are nearly decoupled. The method consists of five sub-processes that support the development of each viewpoint, the comparison of the two viewpoints, the consolidation of the viewpoints, and the definition of detailed system requirements based on the two viewpoints. The consolidation of system usage and coarse-grained system architecture is driven by the refinement of system interaction scenarios into architectural scenarios and the refinement of the associated usage goals. Preliminary results of applying our method in industry are reported.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Antón, A.I., Dempster, J., Siege, D.: Deriving Goals from a Use Case Based Requirements Specification for an Electronic Commerce System. In: Proc. 6th Int. Workshop on Requirements Engineering: Foundation for Software Quality, REFSQ’00 pp. 10-19 (2000)
Bachmann, F., Bass, L., Chastek, G., Donohoe, P., Peruzzi, F.: The Architecture Based Design Method. Tech. Report CMU/SEI-2000-TR-001, Carnegie Mellon Software Engineering Institute (2000)
Beyer, H., Holtzblatt, K.: Contextual Design: Defining Customer-Centered Systems. Morgan Kaufmann, San Fransisco (1998)
Robert Bosch GmbH: ACC Adaptive Cruise Control. The Bosch Yellow Jackets, Edition 2003; available via http://www.christiani-tvet.com
Carroll, J.M.: Making Use - Scenario-Based Design of Human-Computer Interactions. MIT Press, Cambridge (2000)
Clements, P., Kazman, R., Klein, M.: Evaluating Software Architectures: Methods and Case Studies. In: SEI Series in Software Engineering, Addison-Wesley, Boston (2001)
Davis, A.M.: Software Requirements: Objects, Functions, and States. Prentice Hall, Englewood Cliffs (1993)
Grünbacher, P., Egyed, A., Medvidovic, N.: Reconciling Software Requirements and Architectures: The CBSP Approach. In: Proc. 5th IEEE Int. Symp. on Req. Eng., RE’01, Toronto, Canada, pp. 202–211. IEEE Computer Society Press, Washington (2001)
Haumer, P., Pohl, K., Weidenhaupt, K.: Requirements Elicitation and Validation with Real World Scenes. IEEE Trans. on Softw. Eng. 24(12), 1036–1054 (1998)
Halmans, G., Pohl, K.: Communicating the Variability of a Software Product Family to Customers. Software and Systems Modeling 2(1), 15–36 (2003)
ITU-T Recommendation Z.120: Message Sequence Chart (MSC). International Telecommunication Union (2004)
Jarke, M., Pohl, K.: Establishing Visions in Context: Towards a Model of Requirements Processes. In: Proc. 14th Int. Conf. on Inf. Systems, Orlando, Florida, pp. 23–34 (1993)
Khendek, F., Bourduas, S., Vincent, D.: Stepwise Design with Message Sequence Charts. In: Proc. IFIP TC6/WG6.1 - 21st Int. Conf. on Formal Techniques For Networked and Distributed Systems, pp. 19–34. Kluwer, Dordrecht (2001)
Van Lamsweerde, A.: Goal-Oriented Requirements Engineering: A Guided Tour. In: Proc. 5th IEEE Int. Symp. on Req., pp. 249–262. IEEE Computer Society Press, Washington, DC (2001)
Maiden, N., Alexander, I. (eds.): Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle. Wiley, Chichester (2004)
Nuseibeh, B.: Weaving Together Requirements and Architectures. IEEE Computer 34(3), 115–117 (2001)
Pohl, K., Haumer, P.: Modelling Contextual Information about Scenarios. In: Proc. 3rd Int. Workshop on Requirements Engineering: Foundation for Software Quality, REFSQ’97, Barcelona, Presses Universitaires, Namur (1997)
Puschnig, A., Kolagari, R.T.: Requirements Engineering in the Development of Innovative Automotive Embedded Software Systems. In: Proc. 12th IEEE Int. Req. Eng. Conf. RE’04, Kyoto, Japan, pp. 328–333. IEEE Computer Society, Washington (2004)
Rapanotti, L., Hall, J.G., Jackson, M., Nuseibeh, B.: Architecture-driven Problem Decomposition. In: Proc. 12th IEEE Int. Req. Eng. Conf. RE’04, Kyoto, Japan, pp. 80–89. IEEE Computer Society, Washington (2004)
Rolland, C., Souveyet, C., Achour, C.B.: Guiding Goal Modeling Using Scenarios. IEEE Trans. on Softw. Eng. 24(12), 1055–1071 (1998)
Rolland, C., Grosz, G., Kla, R.: Experience with Goal-Scenario Coupling in Requirements Engineering. In: Proc. 4th IEEE Int. Symp. on Requirements Engineering, RE’99, Limerick, Ireland, pp. 74–81. IEEE Computer Society Press, Washington, DC (1999)
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 2007 Springer Berlin Heidelberg
About this paper
Cite this paper
Pohl, K., Sikora, E. (2007). Structuring the Co-design of Requirements and Architecture. In: Sawyer, P., Paech, B., Heymans, P. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2007. Lecture Notes in Computer Science, vol 4542. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-73031-6_4
Download citation
DOI: https://doi.org/10.1007/978-3-540-73031-6_4
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-73030-9
Online ISBN: 978-3-540-73031-6
eBook Packages: Computer ScienceComputer Science (R0)