• Corpus ID: 15507001

Approach for Change Impact Analysis of Aspectual Requirements

@inproceedings{Chitchyan2008ApproachFC,
  title={Approach for Change Impact Analysis of Aspectual Requirements},
  author={Ruzanna Chitchyan and Awais Rashid and Raffi Khatchadourian},
  year={2008}
}
The initial model for change impact analysis of requirements focuses on identification of requirement level dependencies, which helps in predicting the scope (intensity and depth) of change impact. The change impact analysis model is a multidimensional concern-slicing approach that facilitates understanding of requirements dependencies and impact of requirements change. The concerns are sliced as temporal, conditional, task-oriented, and business rules. Based on stakeholders’ preferences and… 
2 Citations

Figures and Tables from this paper

Traceability Framework : From Requirements Through Architecture and Design
The ability to follow and examine (i.e., trace) the life of a artifact throughout software evolution can greatly improve overall system comprehension. In this deliverable, we present material

References

SHOWING 1-10 OF 17 REFERENCES
A tool suite for aspect-oriented requirements engineering
TLDR
A tool suite to support AORE in a scalable fashion is presented and it is shown that its output is comparable to that of a requirements engineer carrying out the same tasks manually.
Change impact analysis for aspect-oriented software evolution
TLDR
The main feature of this approach is to assess the effect of changes in an aspect-oriented program by analyzing its source code, and therefore, the process of change impact analysis can be automated completely.
Concern graphs: finding and describing concerns using structural program dependencies
  • M. Robillard, G. Murphy
  • Computer Science
    Proceedings of the 24th International Conference on Software Engineering. ICSE 2002
  • 2002
TLDR
The concern graph representation, a representation that abstracts the implementation details of a concern and makes explicit the relationships between different parts of the concern, is introduced and the results indicate that concern graphs can be used to document a concern for change, that developers unfamiliar with concern graph can use them effectively, and that the underlying technology scales to industrial-sized programs.
Mining Aspects in Requirements
The early identification and documentation of crosscutting concerns enables better change management and traceability of requirements. Moreover, this also improves the early identification of
Constructing formal specifications from informal requirements
  • R. Clark, A. Moreira
  • Computer Science
    Proceedings Eighth IEEE International Workshop on Software Technology and Engineering Practice incorporating Computer Aided Software Engineering
  • 1997
TLDR
A user-centred model will give very early feedback to the requirements capture process and can be used as a step in the construction of the ROOA model, a formal and executable model which specifies behaviour in terms of what the environment expects from the system should be constructed initially.
From Requirements Documents to Feature Models for Aspect Oriented Product Line Implementation
TLDR
The approach, NAPLES, which uses natural language processing and aspect-oriented techniques to facilitate requirements analysis, commonality and variability analysis, concern identification to derive suitable feature oriented models for implementation is described.
COMPASS: Composition-Centric Mapping of Aspectual Requirements to Architecture
Currently there are several approaches available for aspect-oriented requirements engineering and architecture design. However, the relationship between aspectual requirements and architectural
A Multi-Dimensional, Model-Driven Approach to Concern Identification and Traceability
TLDR
The approach employs model-driven techniques to map a problem description to recurring concern patterns as well as maintain the traceability of the concerns thus identified through to implementation, based on the multi-dimensional concern model for requirements engineering presented in [6].
Semantics-based composition for aspect-oriented requirements engineering
TLDR
A requirements description language (RDL) that enriches the existing natural language requirements specification with semantic information derived from the semantics of the natural language itself, hence providing improved means for expressing the intentionality of the composition, in turn facilitating semantics-based reasoning about aspect influences and trade-offs.
Using Program Slicing in Software Maintenance
TLDR
Using the lattice of single variable decomposition slices ordered by set inclusion, it is shown how a slice-based decomposition for programs can be formed and how to delineate the effects of a proposed change by isolating those effects in a single component of the decomposition.
...
1
2
...