No abstract

Abstract

Architecture design plays a significant role in the evolution of software systems, as it provides the prime realization of the driving requirements and their inter-dependencies. With the increasing volatility of software requirements nowadays, it is necessary to understand the correlation between evolving classical requirements dependencies and their impact on the architectural decomposition. In the context of this analysis, two questions arise: (i) what are the conventional categories of requirements dependencies that are more architecturally significant in terms of change impact? and (ii) to what extent those evolving dependencies tend to generate ripple effects through architectural modules and interfaces. In order to address these two questions, this paper first presents an analysis model that categorizes requirements dependencies. Second, we have performed an exploratory study, based on the change history analysis of a real-life Web-based information system, in order to gather the most architecturally-significant requirements dependencies from our model. We have systematically analyzed ten system releases, based on some qualitative and quantitative indicators, with respect to how the requirementsarchitecture dependencies and compositions evolved.

No abstract

Aspect oriented paradigmn butilds on the concept of separation of crossclutting concerns. The systematic activities of Separation of Concerns (SoC) are -identification of concerns, separation of concerns, representation of concerns, and composition of concerns. Few Aspect Oriented Requirem7zent Engineering (AORE) models provice validation of elicited aspects by walkthroughs, inspections, or formalized proceclures. In this paper, we have extended an already proposed framework to provide two levels of validation, which validates correct elicitation of concerns (aspect) from requirements. The proposed nmodel validates the elicited aspects by graph validlation.