Abstract
Requirements prioritization is ranking of software requirements in particular order. Prioritize requirements are easy to manage and implement while un-prioritized requirements are costly and consume much time as total estimation time of project can exceed. Because all requirements are depended on each other so total estimation time exceed when requirements wait for pre-requisite requirements. Priority of requirement also increases when other requirements wait for it but assigning low priority to needed requirements will delaying the project. Iteration model is software engineering (SE) process model in which all requirements are not developed at one time but are developed in phases. Only sufficient information or sub-requirements of particular user requirement (UR) can be needed for other user requirements (URs) so by implementing only the sufficient requirements in first phase will reduce waiting time. Hence total estimation time of the project will also reduce. In this research work, iteration model approach is used during prioritization to reduce total estimation time of project and to assure timely delivery of project. From the results it is concluded that not all sub-requirements of particular UR get same priority, but there are only few requirements that are important and should be given more priority.
Highlights
Software requirements gathering and management is not an easy task and needs systematic approaches [14][21]
In order to validate the significance of iteration model during requirements implementation, experiment was conducted on requirements of mobile phones inventory management system
Twenty seven user requirement (UR) were collected from mobile shop using background study and interview as elicitation technique
Summary
Software requirements gathering and management is not an easy task and needs systematic approaches [14][21]. RP is not an easy task, many authors have worked on prioritization and suggested several techniques. Business requirements (BRs) deals with benefits and cost issues of requirements. FRs are the base of URs. FRs are requirements that system must do and must consist of while non-functional (NFRs) are supportive requirements that helps in better implementation of FRs. Techniques like „Cost value ranking‟, „Attribute goal oriented‟, „Value oriented‟ are suggested for prioritizing BRs [2][3]. If the number of requirements are ten, AHP will perform forty-five times comparisons of the requirements. Because the technique is time consuming, it is not scalable for big requirements due to the pairwise comparisons for every requirement [12]. The requirement with high polls receive high priority [15]
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Advanced Computer Science and Applications
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
