Developing a Requirements Model for Software Projects
Main Article Content
Abstract
Requirements elicitation is recognized as one of the most critical activities in the software development process as it has an impact on its success. Studies such as the CHAOS Report, a study based on The [Standish Group]'s CHAOS Research Project on IT project success rates and project management best practices report, indicate that about half of the factors associated with project success are related to requirements. Previous studies showed several problems related to requirements elicitation. This paper tried to find out the existing requirements models for software projects and how to develop a new requirements model for software projects. The requirements system was developed by Visual Studio 2019. Online model verification was conducted with 6 experts from the IT industry. After the system was developed, it was validated by three developers/programmers from the same industry (functional test/white-box testing) and eleven developers (non-functional test/black-box testing). The results of the model verification supported the model of requirements. Additionally, the requirements system was validated by non-functional test/black-box testing and functional test/white-box testing
Article Details
This work is licensed under a Creative Commons Attribution 4.0 International License.
licenseTermsHow to Cite
Publication Dates
Received
Accepted
Published Online First
References
Maznevski, M.L.; Chui, C. Leading global teams. In Global leadership; Routledge. 2017, 273-301. https://doi.org/10.4324/9781315232904.
Marchewka, J.T. Information technology project management: Providing measurable organizational value; John Wiley & Sons. 2016, ISBN 13:978-1118911013.
Boehm, B.; Grunbacher, P.; Briggs, R.O. Developing groupware for requirements negotiation: lessons learned. IEEE Software. 2001, 18(3), 46-55. https://doi.org/10.1109/52.922725.
Hussain, A.; Mkpojiogu, E.O.; Kamal, F.M. The role of requirements in the success or failure of software projects. International Review of Management and Marketing. 2016, 6(7), 306-311. https://doi.org/306 - 311, 01.08.2016.
Savolainen, P.; Ahonen, J.J.; Richardson, I. Software development project success and failure from the supplier's perspective: A systematic literature review. International Journal of Project Management. 2012, 30(4), 458-469. https://doi.org/10.1016/j.ijproman.2011.07.002.
Sedelmaier, Y.; Landes, D. Software engineering body of skills (SWEBOS). In Proceedings of the 2014 IEEE Global Engineering Education Conference (EDUCON). 2014, 395-401. https://doi.org/10.1109/EDUCON.2014.6826125.
Gillani, M.; Niaz, H.A.; Ullah, A. Integration of software architecture in requirements elicitation for rapid software development. IEEE Access 2022, 10, 56158-56178. https://doi.org/10.1109/ACCESS.2022.3177659.
Kasauli, R.; Knauss, E.; Horkoff, J.; Liebel, G.; de Oliveira Neto, F.G. Requirements engineering challenges and practices in large-scale agile system development. Journal of Systems and Software. 2021, 172, 110851. https://doi.org/10.1016/j.jss.2020.110851.
Nuseibeh, B.; Easterbrook, S. Requirements engineering: a roadmap. In Proceedings of the Proceedings of the Conference on the Future of Software Engineering. 2000, 35-46. https://doi.org/10.1145/336512.336523.
Loucopoulos, P.; Karakostas, V. System requirements engineering; McGraw-Hill, Inc. 1995; ISBN 978-0-07-707843-0.
Coplien, J.O. Borland software craftsmanship: A new look at process, quality and productivity. In Proceedings of the 5th Annual Borland International Conference. 1994, 5.
Abran, A.; Moore, J.W.; Bourque, P.; Dupuis, R.; Tripp, L. Software engineering body of knowledge. IEEE Computer Society, Angela Burgess. 2004, 25, 1235, ISBN 0-7695-2330-7.
Pohl, K. Requirements engineering fundamentals: a study guide for the certified professional for requirements engineering exam-foundation level-IREB compliant; Rocky Nook, Inc. 2016, ISBN 978-1-937538-77-4.
Mulla, N.; Girase, S. A new approach to requirement elicitation based on stakeholder recommendation and collaborative filtering. International Journal of Software Engineering & Applications. 2012, 3(3), 51. https://doi.org/10.5121/ijsea.2012.3305.
Wahono, R.S. Analyzing requirements engineering problems. In Proceedings of the IECI Japan Workshop, 2003.
Frefer, A.; Mahmoud, M.; Haleema, H.; Almamlook, R. Overview success criteria and critical success factors in project management. Industrial engineering & management. 2018, 7(1), 1-6. https://doi.org/10.4172/2169-0316.1000244.
Laporti, V.; Borges, M.R.; Braganholo, V. Athena: A collaborative approach to requirements elicitation. Computers in Industry. 2009, 60(6), 367-380. https://doi.org/10.1109/CSCWD.2007.4281527.
Sommerville, I. Software Engineering, 9/E; Pearson Education India 2011.
Zhang, Y.; Harman, M.; Finkelstein, A.; Mansouri, S.A. Comparing the performance of metaheuristics for the analysis of multi-stakeholder tradeoffs in requirements optimisation. Information and software technology. 2011, 53(7), 761-773. https://doi.org/10.1016/j.infsof.2011.02.001.
Krane, H.P.; Rolstadås, A.; Olsson, N.O. Categorizing risks in seven large projects—Which risks do the projects focus on? Project management journal. 2010, 41(1), 81-86. https://doi.org/10.1002/pmj.20154.
Atladottir, G.; Hvannberg, E.T.; Gunnarsdottir, S. Comparing task practicing and prototype fidelities when applying scenario acting to elicit requirements. Requirements Engineering. 2012, 17, 157-170. https://doi.org/10.1007/s00766-011-0131-2.
Meth, H.; Brhel, M.; Maedche, A. The state of the art in automated requirements elicitation. Information and Software Technology. 2013, 55(10), 1695-1709. https://doi.org/10.1016/j.infsof.2013.03.008.
Pacheco, C.; Garcia, I. A systematic literature review of stakeholder identification methods in requirements elicitation. Journal of Systems and Software. 2012, 85(9), 2171-2181. https://doi.org/10.1016/j.jss.2012.04.075.
De Gea, J.M.C.; Nicolás, J.; Alemán, J.L.F.; Toval, A.; Ebert, C.; Vizcaíno, A. Requirements engineering tools: Capabilities, survey and assessment. Information and Software Technology. 2012, 54(10), 1142-1157. https://doi.org/10.1016/j.infsof.2012.04.005.
Asarani, N.A.M.; Ab Rahim, N.Z. Preliminary study of online training implementation from multiple perspectives in malaysian public sectors. Journal of Theoretical and Applied Information Technology 2016, 90(1), 77.
Albert, B.; Tullis, T. Measuring the user experience: collecting, analyzing, and presenting usability metrics; Newnes: 2013, ISBN 978-0124157811.
Gheni, A.Y.; Yousif, H.A.; Jusoh, Y.Y. Online medical consultation: covid-19 system using software object-oriented approach. Bulletin of Electrical Engineering and Informatics. 2021, 10(6), 3471-3480. https://doi.org/10.11591/eei.v10i6.3189.
Harrati, N.; Bouchrika, I.; Tari, A.; Ladjailia, A. Exploring user satisfaction for e-learning systems via usage-based metrics and system usability scale analysis. Computers in Human Behavior. 2016, 61, 463-471. https://doi.org/10.1016/j.chb.2016.03.051.
Brooke, J. SUS-A quick and dirty usability scale. Usability evaluation in industry. 1996, 189-194, 4-7, ISBN 9780429157011.
Lano, K. Advanced systems design with Java, UML and MDA; Elsevier: 2005; ISBN 9780080456911.
Gemino, A.; Parker, D. Use case diagrams in support of use case modeling: Deriving understanding from the picture. Journal of Database Management (JDM). 2009, 20(1), 1-24. https://doi.org/10.4018/jdm.2009010101.