Traditional requirements engineering approaches suffer from the tyranny of the dominant decomposition, with functional requirements serving as the base decomposition and non-functional requirements cutting across them. In this paper, we propose a model that decomposes requirements in a uniform fashion regardless of their functional or non-functional nature. This makes it possible to project any...

At the heart of a well-disciplined, systematic methodology that explicitly supports the use of COTS components is a clearly defined process for effectively using components that meet the needs of the system under development. In this paper, we present the CARE/SA approach which supports the iterative matching, ranking, and selection of COTS components, using a representation of COTS components ...

........................................................................................................................................ II CONTENTS ....................................................................................................................................... III

At the heart of a well-disciplined, systematic methodology that explicitly supports the use of COTS components is a clearly defined process for effectively using components that meet the needs of the system under development. In this paper, we present the CARE (COTS-Aware Requirements Engineering) Framework, a process-oriented framework which supports the iterative matching, ranking, and select...

For many years systems engineers have produced traditional system requirements specifications containing shall-statement requirements. The rapid adoption of use case modeling for capturing functional requirements in the software community has caused systems engineers to examine the utility of use case models for capturing system-level functional requirements. A transition from traditional shall...

Identification of non-functional requirements is important for successful development and deployment of the software product. The acceptance of the software product by the customer depends on the non-functional requirements which are incorporated in the software. For this, we need to identify all the non-functional requirements required by all stakeholders. In the literature not many approaches...

Top-quality software architecture should consider both functional and non-functional aspects of systems and their association. In the the existing literature, considerable efforts have been directed at functional requirement analysis and design, regardless of the non-functional aspects. This disassociation makes architecture comprehension and evolution hard. This paper proposes a strategy on ho...