From Requirements to Architectural Design –Using Goals and Scenarios

作者: Lin Liu , Eric Yu

DOI:

关键词: ArchitectureRealization (linguistics)Computer scienceArchitectural patternNotationDomain (software engineering)Software engineeringSystems engineeringFocus (computing)OperationalizationNon-functional requirement

摘要: To strengthen the connection between requirements and design during early stages of architectural design, a designer would like to have notations help visualize incremental refinement an architecture from initially abstract descriptions increasingly concrete components interactions, all while maintaining clear focus on relevant at each step. We propose combined use goal-oriented language GRL scenarios-oriented notation UCM. Goals are used in functional non-functional requirements, exploration alternatives, their operationalization into constructs. The scenario is depict elaboration realization design. approach illustrated with example telecom domain.

参考文章(8)
Eric S. K. Yu, John Mylopoulos, Why Goal-Oriented Requirements Engineering. requirements engineering: foundation for software quality. pp. 15- 22 ,(1998)
R. S. Casselman, R. J. A. Buhr, Use Case Maps for Object-Oriented Systems ,(1995)
C. Rolland, G. Grosz, R. Kla, Experience with goal-scenario coupling in requirements engineering Requirements Engineering. pp. 74- 81 ,(1999) , 10.1109/ISRE.1999.777987
Lawrence Chung, Julio Cesar Sampaio do Prado Leite, On Non-Functional Requirements in Software Engineering Conceptual Modeling: Foundations and Applications. pp. 363- 379 ,(2009) , 10.1007/978-3-642-02463-4_19
A. van Lamsweerde, L. Willemet, Inferring declarative requirements specifications from operational scenarios IEEE Transactions on Software Engineering. ,vol. 24, pp. 1089- 1114 ,(1998) , 10.1109/32.738341
P.B. Kruchten, The 4+1 View Model of architecture IEEE Software. ,vol. 12, pp. 42- 50 ,(1995) , 10.1109/52.469759
G. Abowd, R. Kazman, L. Bass, M. Webb, SAAM: a method for analyzing the properties of software architectures international conference on software engineering. pp. 81- 90 ,(1994) , 10.5555/257734.257746