Prioritizing software development productivity factors using the analytic hierarchy process
Journal of Systems and Software
Viewpoints for requirements definition
Software Engineering Journal
An analytic framework for specifying and analyzing imprecise requirements
Proceedings of the 18th international conference on Software engineering
A quantitative approach for assessing the priorities of software quality requirements
Journal of Systems and Software - Special issue on software engineering and knowledge engineering
Software Requirements
Identifying Quality-Requirement Conflicts
IEEE Software
A Cost-Value Approach for Prioritizing Requirements
IEEE Software
Supporting Distributed Collaborative Prioritization
APSEC '99 Proceedings of the Sixth Asia Pacific Software Engineering Conference
Prioritisation mechanisms to support incremental development of agent systems
International Journal of Agent-Oriented Software Engineering
Requirements engineering for home care technology
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
An integrated approach to supporting interaction evolution in home care systems
Proceedings of the 1st international conference on PErvasive Technologies Related to Assistive Environments
A simulation-based fuzzy multi-attribute decision making for prioritizing software requirements
Proceedings of the 1st Annual conference on Research in information technology
Multi-person decision-making for requirements prioritization using fuzzy AHP
ACM SIGSOFT Software Engineering Notes
A systematic literature review of software requirements prioritization research
Information and Software Technology
Hi-index | 0.00 |
The development of complex software systems involves collecting software requirements from various stakeholders. Often stakeholder perceptions conflict during the requirements elicitation phase. An effective technique for to resolve such a conflict is needed. In this paper, we presented a framework that prioritizes software requirements gathered from multiple stakeholders by incorporating inter-perspective relationships, which is not addressed by existing priority assessment techniques. We use a relationship matrix to analyze the impact between requirements and facilitate the integration process which assesses their priorities based on their relationships from multiple perspectives. It allows the development team to resolve conflicts effectively and concentrate their valuable time and resources on the critical few requirements from multiple perspectives that directly contribute to high customer satisfaction.