Modularisation and composition of aspectual requirements

Rashid, Awais; Moreira, Ana; Araújo, João

doi:10.1145/643603.643605

Cited by 291 publications

(257 citation statements)

References 23 publications

Supporting

Mentioning

240

Contrasting

Unclassified

Order By: Relevance

“…In order to construct our metamodel we investigated and benefited from several approaches which are commonly used to define and represent requirements: goal-oriented [91,67], aspect-driven [76], variability management [66], use-case [19], domain-specific [74,50], and reuse-driven techniques [60]. The main elements in the requirements metamodel are Requirement and Relationship (see Fig.…”

Section: Requirements Metamodelmentioning

confidence: 99%

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

View full text Add to dashboard Cite

a b s t r a c tContext: Following the evolution of the business needs, the requirements of software systems change continuously and new requirements emerge frequently. Requirements documents are often textual artifacts with structure not explicitly given. When a change in a requirements document is introduced, the requirements engineer may have to manually analyze all the requirements for a single change. This may result in neglecting the actual impact of a change. Consequently, the cost of implementing a change may become several times higher than expected. Objective: In this paper, we aim at improving change impact analysis in requirements by using formal semantics of requirements relations and requirements change types. Method: In our previous work we present a requirements metamodel with commonly used requirements relation types and their semantics formalized in first-order logic. In this paper the classification of requirements changes based on structure of a textual requirement is provided with formal semantics. The formalization of requirements relations and changes is used for propagating proposed changes and consistency checking of proposed changes in requirements models. The tool support for change impact analysis in requirements models is an extension of our Tool for Requirements Inferencing and Consistency Checking (TRIC). Results: The described approach for change impact analysis helps in the elimination of some false positive impacts in change propagation, and enables consistency checking of changes. Conclusion: We illustrate our approach in an example which shows that the formal semantics of requirements relations and change classification enables change alternatives to be proposed semi-automatically, the reduction of some false positive impacts and contradicting changes in requirements to be determined.

show abstract

Section: Requirements Metamodelmentioning

confidence: 99%

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…There are several commonly used approaches to define and represent requirements: goal-oriented [34,50], aspect-driven [40], variability management [33], use-case [7], domain-specific [30,38], and reuse-driven techniques [31]. Goal-oriented requirements engineering [34,50] defines a model for decomposing a system goal into requirements with goal trees, and offers some decision methods based on this decomposition.…”

Section: Requirements Metamodelmentioning

confidence: 99%

“…Goal-oriented requirements engineering [34,50] defines a model for decomposing a system goal into requirements with goal trees, and offers some decision methods based on this decomposition. The aspect-oriented approach [40] gives a requirements model for the separation of crosscutting functional and nonfunctional properties in the requirements analysis phase. The System Modeling Language (SysML) [38] is a domainspecific modeling language for system engineering.…”

Section: Requirements Metamodelmentioning

confidence: 99%

Semantics of trace relations in requirements models for consistency checking and inferencing

et al. 2009

View full text Add to dashboard Cite

Requirements traceability is the ability to relate requirements back to stakeholders and forward to corresponding design artifacts, code, and test cases. Although considerable research has been devoted to relating requirements in both forward and backward directions, less attention has been paid to relating requirements with other requirements. Relations between requirements influence a number of activities during software development such as consistency checking and change management. In most approaches and tools, there is a lack of precise definition of requirements relations. In this respect, deficient results may be produced. In this paper, we aim at formal definitions of the relation types in order to enable reasoning about requirements relations. We give a requirements metamodel with commonly used relation types. The semantics of the relations is provided with a formalization in first-order logic. We use the formalization for consistency checking of relations and for inferring new relations. A tool has been built to support both reasoning activities. We illustrate our approach in an example which shows that the formal semantics of relation types enables new relations to be inferred and contradicting relations in requirements documents to be determined.

show abstract

“…Our paper belongs to the approach that adapts use cases for modeling aspects. Araújo and Rashid et al attempt to incorporate aspects into UML elements [1,2,5]. The authors propose a general model for aspect-oriented requirements engineering, which includes three main parts: identifying cross-cutting concerns, specifying functional concerns, and composing requirements.…”

Section: Introductionmentioning

confidence: 99%

“…Accordingly, they point out that "when you identify use cases, you are indeed identifying aspects." In our paper, however, we adopt the definition of aspects used by Araujo [1,2,5] in that a requirement is viewed as an aspect only when it cross-cuts more than one base use case.…”

Section: Introductionmentioning

confidence: 99%

A Comprehensive Aspect-Oriented Use Case Method for Modeling Complex Business Requirements

Song

2008

Advances in Conceptual Modeling – Challenges and Opportunities

View full text Add to dashboard Cite

Abstract. The aspect-oriented approach separates cross-cutting concerns and models them as aspects. In this paper, we present a comprehensive aspectoriented use case approach for modeling complex business requirements. We identify four categories of aspects: high level non-functional requirements, extending or optional requirements, included or subordinate requirements, and business rules. Our aspect-oriented use-case model comprises three different templates: base use cases, aspectual use cases, and nonfunctional aspects. The proposed method offers a systematic approach for identifying different potential aspects from complex business requirements. Moreover, our method provides a comprehensive model for documenting identified aspects and their composition to the core functionalities at an early stage of software development. The contributions of our paper include identifying and utilizing the four types of aspects and proposing the templates to document them.

show abstract

Modularisation and composition of aspectual requirements

Cited by 291 publications

References 23 publications

Change impact analysis for requirements: A metamodeling approach

Change impact analysis for requirements: A metamodeling approach

Semantics of trace relations in requirements models for consistency checking and inferencing

A Comprehensive Aspect-Oriented Use Case Method for Modeling Complex Business Requirements

Contact Info

Product

Resources

About