No abstract

Abstract. This paper presents an initial ontology for reasoning about a system's System Qualities (SQs), ilities, or non-functional requirements (reliability, usability, affordability, etc.). The need for such an ontology is based primarily on two factors. One is the importance of getting the SQs sufficiently well defined that the system's definition, development and evolution result in a satisfactory balance of SQ values for the system's success-critical stakeholders, given the frequent system shortfalls and overruns that occur when this balance is not achieved. The other is that current system acquisition and evolution guidance descriptions have numerous deficiencies and inconsistencies in their coverage of SQ considerations. This situation is becoming more serious as systems and their stakeholders become increasingly complex, dynamic, and diverse. This paper provides an elaboration of the needs, a set of initial SQ ontology elements and definitions, examples of their application to some key SQs and their relationships, and an identification of further research and development needed to make the ontology fully useful and evolvable.

No abstract

This paper presents an initial ontology for reasoning about a system's System Qualities (SQs), ilities, or non‐functional requirements (reliability, usability, affordability, and more). The need for such ontology is based primarily on two factors. One is the importance of getting the SQs sufficiently well defined such that the system's definition, development, and evolution result in a satisfactory balance of SQ values for the system's success‐critical stakeholders, given the frequent system shortfalls and overruns that occur when the system does not achieve this balance. The other is that current system acquisition and evolution guidance descriptions have numerous deficiencies and inconsistencies in their coverage of SQ considerations. This situation is becoming more serious as systems and their stakeholders become increasingly complex, dynamic, and diverse. This paper provides an elaboration of the needs, a set of initial SQ ontology elements and definitions, examples of their application to some key SQs and their relationships, and an identification of further research and development needed to make the ontology fully useful and evolvable.

No abstract

Budget and schedule constraints limit the number of requirements that can be worked on for a software system and is thus necessary to select the most valuable requirements for implementation. However, selecting from a large number of requirements is a decision problem that requires negotiating with multiple stakeholders and satisficing their value propositions. In this paper I present a two-step value-based requirements prioritization approach based on TOPSIS, a decision analysis framework that tightly integrates decision theory with the process of requirements prioritization. In this two-step approach the software system is initially decomposed into high-level Minimal Marketable Features (MMFs) which the business stakeholders prioritize against business goals. Each individual MMF is further decomposed into low-level requirements/features that are primarily prioritized by the technical stakeholders. The priorities of the low-level requirements are influenced by the MMFs they belong to. This approach has been integrated intoWinbook, a social-networking influenced collaborative requirements management framework and deployed for use by 10 real-client project teams for the Software Engineering project course at the University of Southern California in Fall 2012. This model allowed the clients and project teams to effectively gauge the importance of each MMF and low-level requirement and perform various sensitivity analyses and take value-informed decisions when selecting requirements for implementation.

No abstract

No abstract