From Non-Functional Requirements to Design through Patterns

Groß, Daniel; Yu, Eric

doi:10.1007/s007660170013

Cited by 170 publications

(98 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The source and target languages are respectively the i* modeling language and Acme architectural description language [21]. Gross and Yu [14] proposed a systematic treatment of NFRs in descriptions of patterns and when applying patterns during design. The approach organizes, analyzes and refines non-functional requirements, and provides guidance and reasoning support when applying patterns during the design of a software system.…”

Section: Requirements To Architectural Designmentioning

confidence: 99%

From i* Models to Service Oriented Architecture Models

Castro¹,

Franch²,

Astudillo³

2010

Proceedings of the 4th International Workshop on Architectures, Concepts and Technologies for Service Oriented Computing

View full text Add to dashboard Cite

Abstract. Requirements engineering and architectural design are key activities for successful development of software systems. Specifically in the service-oriented development systems there is a gap between the requirements description and architecture design and assessment. This article presents a systematic process for systematically deriving service-oriented architecture from goal-oriented models. This process allows generate candidate architectures based on i* models and helps architects to select a solution using services oriented patterns for both services and components levels. The process is exemplified by applying it in a synthesis metadata and assembly learning objects system.

show abstract

Section: Requirements To Architectural Designmentioning

confidence: 99%

From i* Models to Service Oriented Architecture Models

Castro¹,

Franch²,

Astudillo³

2010

Proceedings of the 4th International Workshop on Architectures, Concepts and Technologies for Service Oriented Computing

View full text Add to dashboard Cite

show abstract

“…Many efforts for bridging the gap between the requirements and architecture have considered a goal-oriented approach (e.g. [Gro01,Liu01,Bra01,Cas02]). Among them, [Lam03] and [Jan05] describe two different processes for deriving architectural designs form goal-oriented requirements models expressed in KAOS.…”

Section: Related Workmentioning

confidence: 99%

Deriving event-based transition systems from goal-oriented requirements models

et al. 2008

View full text Add to dashboard Cite

show abstract

“…E.g. safety, security, reliability, usability, maintainability, cost and development time (Gross and Yu 2001). High level nonfunctional requirements often decompose into functional requirements they are not specifically concerned with the functionality of a system, placing restrictions of the product being developed and the development process.…”

Section: Requirementsmentioning

confidence: 99%