- Author:
- Hoh In
A critical success factor in requirements engineering involves determining and resolving conflicts among candidate system requirements proposed by multiple stakeholders. Many software projects have failed due to requirements conflicts among the stakeholders.
The WinWin system developed at USC provides an approach for resolving requirements conflicts among the stakeholders. The Winwin system provides a framework for negotiation between the stakeholders to identify and resolve these conflicts. However, such systems do not scale well for large software projects containing many requirements.
Based on an analysis of the options for addressing this problem, I have focused on semiautomated tools and techniques for identifying and resolving conflicts among software quality attributes. I have developed two prototype support tools, QARCC and S-COST, which expand the capabilities of the WinWin system. QARCC focuses on software architecture strategies for achieving quality attribute objectives. S-COST focuses on tradeoffs among software cost, functionality, and other quality attributes. I have also developed portions of underlying theories and models which serve as the basis for the prototype tools.
Finally, I evaluated the theories, models, and tools with the results of WinWin negotiations, such as the CS577 15-project samples.
Cited By
- Mejbri Y, Khemaja M and Raies K Analysis of pervasive games based learning systems requirements using game theory Proceedings of the Fourth International Conference on Technological Ecosystems for Enhancing Multiculturality, (1019-1024)
- Mairiza D, Zowghi D and Nurmuliani N An investigation into the notion of non-functional requirements Proceedings of the 2010 ACM Symposium on Applied Computing, (311-317)
Recommendations
Conflict of requirements: a pattern for the treatment of conflicting non-functional requirements
SugarLoafPLoP '12: Proceedings of the 9th Latin-American Conference on Pattern Languages of ProgrammingSoftware development is an activity that works several aspects of Software Engineering. One of them is requirements elicitation and its writing in an understandable notation for software developers. Non-Functional Requirements are those associated to ...
Requirements in Conflict: Player vs. Designer vs. Cheater
MERE '08: Proceedings of the 2008 Third International Workshop on Multimedia and Enjoyable Requirements Engineering - Beyond Mere Descriptions and with More Fun and GamesThere are significant interactions between video game stakeholder emotional requirements and security require- ments. Counter-intuitively, some traditional security requirements are not necessarily met by the game implementation some forms of security ...
Slr on Identification & Classification of Non-Functional Requirements Attributes, and Its Representation in Functional Requirements
CSAI '18: Proceedings of the 2018 2nd International Conference on Computer Science and Artificial IntelligenceSoftware requirements are crucial. Tight relationship between functional and non-functional will determine the quality of requirements, in which ultimately determines the quality of the software being built. Non-Functional Requirements (NFR) often get ...