A. Sapunkov
ABSTRACT
This paper describes the system for automating the user requirements prioritization URPCalc. A key feature is the presentation of user requirements as an estimation of priorities based on key characteristics of users and changes in these ratings over time. This approach allows us to estimate the change in the relevance of user requirements and forecast it for the near future. The proposed approach focuses on ensuring quality and reducing labor costs for a product manager by developing software for analyzing and prioritizing user requirements. The article presents and discusses the algorithms and architecture of the URPCalc system.
- Yadav M., Goyal N. and Yadav. J. 2015. Agile Methodology over iterative approach of Software Development. In Proceedings 2nd International Conference on Computing for Sustainable Global Development (May 2015), 542--547.Google Scholar
- Wingo R. and Tanik. M. 2015. Using an agile software development methodology for a complex problem domain. In Proceedings SoutheastCon 2015 (June 2015), 1--8.Google ScholarCross Ref
- Rizwan M. and Qureshi. J. 2012. Agile software development methodology for medium and large projects, IET Software, vol. 6 (Aug. 2012), 358--363.Google Scholar
- Rover D., Ullerich C., Scheel R., Wegter J. and Whipple C. 2015. Advantages of agile methodologies for software and product development in a capstone design project. In Proceedingseedings Frontiers in Education Conference (February 2015), 1--9.Google Scholar
- Benefield R. 2009. Agile Deployment: Lean Service Management and Deployment Strategies for the SaaS Enterprise. In Proceedings 42nd Hawaii International Conference on System Sciences (January 2009), 1--5. Google ScholarDigital Library
- McLaughlin M. 2018. 'What Is Agile Methodology?', VersionOne{Online}. Available: https://www.versionone.com/agile-101/agile-methodologies/ URL. {Accessed: 10-May-2018}.Google Scholar
- Sutherland M. and Schwaber M. 2018. The Definitive Guide to Scrum:The Rules of the Game. The Scrum Guide, 2018 {Online}. Available: https://www.scrumguides.org/ URL. {Accessed: 10-May-2018}Google Scholar
- ISO/IEC/IEEE 29119-1:2013. Standards catalogue. International Organization for Standardization. September 2013. Retrieved 05 November 2018.Google Scholar
- Farris P., Bendle N., Pfeifer P. and Reibstein D. 2015. Marketing Metrics: The Definitive Guide to Measuring Marketing Performance. Upper Saddle River, New Jersey: Pearson Education (August 2015), 55--59. Google ScholarDigital Library
- Gunning M., Kelley J., Khandker N., Kornienko I., Richer P., Sneden J. and Stephen K. 2007. Systems and Methods for Project Management Task Prioritization, 2007, US20090133027A1.Google Scholar
- Lober R., Padois V. and Sigaud O. 2015. Variance modulated task prioritization in Whole-Body Control. In Proceedings. IEEE/RSJ International Conference on Intelligent Robots and Systems (October 2015), 3944--3949.Google Scholar
- Xu Y., Li K., Hu J. and Li K. 2014. A genetic algorithm for task scheduling on heterogeneous computing systems using multiple priority queues. In Proceedings Information Sciences, Elsevier Inc (February 2014), 255--287.Google Scholar
- Kano N., Seraku N., Takahashi F. and Tsuji S. 1984. Attractive Quality and Must-be Quality. The Journal of the Japanese Society for Quality Control (1984), 39--44.Google Scholar
- Hohmann L. 2006. Innovation Games: Creating Breakthrough Products Through Collaborative Play. Pearson Education (August 2006). Google ScholarDigital Library
- Wiegers K. 1999. First Things First: Prioritizing Requirements. Software Development (September 1999). Google ScholarDigital Library
- Hudda S., Mahajan R., Chopra S. 2016. Prioritization of User-Stories in Agile Environment. Indian Journal of Science and Technology, vol. 9 (December 2016), 1--23.Google ScholarCross Ref
- Popli R., Chauhan N. and Sharma H. 2014. Prioritising user stories in agile environment. 2014 International Conference on Issues and Challenges in Intelligent Computing Techniques (February 2014), 515--519.Google Scholar
- Ecar M., Kepler F. and Pablo S. 2018. Cosmic User Story Standard. Lecture Notes in Business Information In Proceedingsessing, val. 314 (May 2018), 3--18.Google Scholar
- Nuseibeh B. and Easterbrook S. 2000. Requirements engineering: a roadmap. In Proceedingseedings of the conference on the future of Software engineering, ACM New York (June 2000), 35--46. Google ScholarDigital Library
- Gotel O. and Finkelstein A. 2002. An Analysis of the Requirements Traceability Problem. In Proceedings. In Proceedingseedings of IEEE International Conference on Requirements Engineering, (August 2002), 94--101.Google Scholar
- Afanasieva T. and Sapunkov A. 2018. Calculating the priorities of user problems in software development. In Proceedings. 12th International Conference on Application of Information and Communication Technologies (October 2018), 234--240.Google Scholar
- Afanasieva T., Yarushkina N., Toneryan M., Zavarzin D., Sapunkov A. and Sibirev I. 2015. Time series forecasting using fuzzy techniques. In Proceedings. International Joint Conferece IFSA-EUSFLAT 15 (July 2015), 1068--1075.Google Scholar
- Afanasieva T. and Sapunkov A. 2015. Selection of time series forecasting model, using a combination of linguistic and numerical criteria. In Proceedings. 10th International Conference on Application of Information and Communication Technologies (October 2016), 341--346.Google Scholar
- B2B Family {Online}. Available: https://b2bfamily.com URL. {Accessed: 1- December-2018}Google Scholar
- OmniDesk {Online}. Available: https://omnidesk.ru URL. {Accessed: 1- December-2018}Google Scholar
- Trello {Online}. Available: http://trello.com URL. {Accessed: 1- December-2018}.Google Scholar
Recommendations
An Approach for Eliciting Software Requirements and its Prioritization Using Analytic Hierarchy Process
ARTCOM '09: Proceedings of the 2009 International Conference on Advances in Recent Technologies in Communication and ComputingMost software engineering methods presume that requirements are explicitly and completely stated; however, experience shows that requirements are rarely complete and usually contain implicit requirements. The failure or success of a software system ...
User Requirements and System Requirements
Stakeholders, analysts, and designers often fail to differentiate the roles of user and system requirements. Unfortunately, treating them as the same thing can create problems for projects. Here are three strategies for managing user and system ...
A systematic literature review of software requirements prioritization research
Context: During requirements engineering, prioritization is performed to grade or rank requirements in their order of importance and subsequent implementation releases. It is a major step taken in making crucial decisions so as to increase the economic ...
Comments