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

-- JasonKealey - 12 Oct 2005


  • Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.

FormForVirtualLibrary edit

Title From Requirements to Architectural Design - Using Goals and Scenarios
Authors L. Liu and E. Yu
Type Conference
Conference/Journal Title From Software Requirements to Architectures Workshop (STRAW 2001)
Month May
Year 2001
Pages 9
Keywords goal-oriented requirements language, GRL, scenarios-oriented, use case maps, iterative development
Topic attachments
I Attachment Action Size Date Who Comment
straw01.pdfpdf straw01.pdf manage 293 K 12 Oct 2005 - 19:20 JasonKealey STRAW2001
Topic revision: r2 - 09 Aug 2006, DanielAmyot
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback