Search

The article discusses ways to identify and capture early aspects in requirements and architecture activities related to computer softwares. Early aspects are concerns that crosscut an artifact's dominant decomposition or base modules derived from the dominant separation-of-concerns criterion, in the early stages of the software life cycle. Identifying and managing early aspects helps in improving modularity in the requirements and architecture design and to detect conflicting concerns early, thus resolving trade-offs. Besides, identifying aspects at one stage provides benefits downstream. Knowledge of requirements-level aspects helps architects in designing a better systems. Similarly, knowing architecture-level aspects helps produce a better implementation. Early aspects can measure development activities and many find their way into the code as traditional implementation aspects. Identifying early aspects across phases can increase the consistency of requirements and architecture designs with each other and provides a rationale and traceability for aspects across life-cycle activities. INSET: Dominant Decomposition in Early Software Development..