Requirements Engineering Practices in UUMIT Centre: An Assessment Based on the Perceptions of In-House Software Developers
Keywords:
Requirements Engineering Practices, Requirements Description, Development and ManagementAbstract
Requirements Engineering (RE) is a systematic procedure that entails and encompasses the elicitation, elaboration, documentation, negotiation, validation and management of the system’s requirements in a software engineering project. Universiti Utara Malaysia (UUM) is been supported by several systems, engineered by the UUM Information Technology (UUMIT) Centre. The objective of this paper was to investigate the requirements engineering practices at UUMIT Centre. The major issue that led to this study was the absence of studies that support software development efforts at the UUMIT Centre. This research is aimed at assisting UUMIT Centre in developing quality, and as well, time and cost saving software systems through the employment of state of the art requirements engineering practices. Furthermore, the paper, as a contribution to UUM, identifies the activities that are needed for software construction to enable the University management allocate budget for the provision of adequate and cutting edge training for the in-house software developers. Three variables were assessed: Requirement Description, Requirements Development (consisting of: Requirements Elicitation, Requirements Analysis and Negotiation, Requirements Validation), and Requirement Management. The results from this research revealed that the current practices of requirement engineering in UUMIT is good and commendable, however there is need and room for more improvement in a few RE practices that were rarely practiced. In addition, recommendations were also proffered for effective training programs for UUMIT staff on RE practices to build the capacity of in-house developers and other associated staff. The training will increase their understanding on system requirements using RE practices to enable them develops better systems for the university. Further investigation is required in the future to understand the effect of RE practices on software development. In addition, also as a future work, the researchers aim to extend the scope of this study to other government and non-educational organizationsReferences
Cheng, B.H.C. and Atlee, J.M. “Current and future research directions in requirements engineering”. Design Requirements Engineering: A TenYear Perspective 2009. Springer.
Khan, H.H., and Naz’ri bin Mahrin, M. “Generating Risks during Requirement Eng. Process in Global Software Development
Environment”. International Journal of Digital Information & Wireless
Communication (IJDIWC). Vol. 4(1), pp. 63-78, 2014.
Wiegers, K. Creating a Software Engineering Culture. Addison-Wesley, 2013.
Sheikh, J.A., Dar, H.S., and Sheikh, F.J. Usability Guidelines for Designing Knowledge Base in Rural Areas Design, User Experience, and Usability. User Experience Design for Everyday Life Applications and Services. Springer, 2014.
Asghar, S. and Umar, M. “Requirement engineering challenges in development of software applications and selection of customer-off-theshelf (COTS) components”. International Journal of Software Engineering. Vol. 1(1), pp. 32-50, 2010.
Shah, T. and Patel, V.S. “A Review of Requirement Engineering Issues and Challenges in Various Software Development Methods”.
International Journal of Computer Applications. 99(15): 36-45, 2014.[7] Young, R.R. “The requirements engineering handbook. Artech House,
Sankhwar, S., Singh, V. and Pandey, D. “Requirement Engineering Paradigm”. Global Journal of Multidisciplinary Studies. pp. 3(3), 2014.
Kavitha, C.R. and Thomas, S.M. “Requirement gathering for small projects using agile methods”. IJCA Special Issue on Computational Science-New Dimensions & Perspectives. vol. 3, pp.122-128, 2011.
Nilofer, M. and Sheetal, G. “Comparison of Various Elicitation Techniques & Requirement Prioritization Techniques". International
Journal of Engineering Research & Technology. Vol. 1(3), pp. 1-8, 2012.
Liu, J.Y.C., Hun-Gee, C.C.C. and Sheu, T.S. “Relationships among interpersonal conflict, requirements uncertainty, and software project performance”. International Journal of Project Management. Vol. 29(5), pp. 547-556, 2011.
Bashir, M.S. and Qureshi, M.R.J. “Hybrid Software Development Approach for Small to Medium Scale Projects: Rup, Xp & Scrum. Cell. 966, 536474921, 2012.
Cerpa, N. and Verner, J.M. “Why did your project fail?” Communications of the ACM 2009. Vol. 52(12), pp. 130-134, 2009.
Lindquist, C. 2005. Fixing the requirements mess. CIO Magazine, 2005, pp. 52-60.
Ramingwong, L. “A Review of Requirements Engineering Processes, Problems & Models”. International Journal of Engineering Science & Technology. Vol. 4(6), 2012.
Kumar, S.A. and Kumar, T.A. “Study the Impact of Requirements Management Characteristics in Global Software Development Project: An Ontology Based Approach”. International Journal of Software Engineering and Application. Vol. 2(4), 2011.
Iqbal, J., Ahmad, R., Nizam, M.H., Nasir, M.D. and Noor, M.A. “Significant Requirements Engineering Practices for Software
Development Outsourcing”. Software Engineering Conf. (ASWEC)Australia, 2013.
Pfleeger, S.L. and Atlee, J.M. “Software Engineering: Theory andPractice”. 2006, India: Pearson.
Zave, P. and Jackson, M. “Four dark corners of requirements
engineering”. ACM Transaction on Software Engineering and Method.
Vol. 6(1), pp. 1-30, 1997.
Brooks, F.P. and Bullet, S. “Essence & accidents of software
engineering”. IEEE Computers. Vol. 20(4), pp. 10-19, 1987.
Leffingwell, D. and Widrig, D. Managing software requirements: a use case approach. Pearson, 2003.
Gause, D.C. and Weinberg, G.M. "Exploring requirements: quality before design. 1989, New York: Dorset House.
Boehm, W.B. and Papaccio, N.P. “Understanding and Controlling Software Cost”. IEEE Transaction on Software Engineering. pp. 1462–1476, 1988.
Leffingwell, D. “Calculating your return on investment from more effective requirements management”. American Programmer. Vol. 10(4), pp. 13-16, 1997.
Quispe, A., Marques, M., Silvestre, L., Ochoa, S.F. and Robbes, R. “Requirements engineering practices in very small software enterprises: A diagnostic study”. International Conference of the Chilean Computer Science Society (SCCC) 2010.
Leffingwell, D. and Widrig, D. Managing software requirements: a unified approach. Addison-Wesley Professional. 2000.
Bell, D., Morrey, I. and Pugh, J. The essence of program design. India: Pearson Education, 1997.
Pressman, R.S. Software Eng.: A Practitioner's Approach, 7/e, 2010, Pressman & Associates, 2010.
Wiegers, K.E. Software Requirements: Practical techniques for gathering & managing requirement through the product development cycle. Microsoft Corporation. 2003.
Damian, D., Zowghi, D., Vaidyanathasamy, L. and Pal, Y. “An industrial case study of immediate benefits of requirements engineering process improvement at the Australian Center for Unisys Software”. Empirical Software Engineering. vol. 9(1-2), pp. 45-75, 2004.
Niazi, M. and Babar, M.A. De-motivators of software process
improvement: An analysis Product of Vietnamese-Focused Software
Process Improvement. Springer, 2007.
Hickey, A.M. and Davis, A.M. “Requirements elicitation and elicitation technique selection: model for two knowledge-intensive software development processes”. International Conference on System Sciences 2003. Hawaii. 2003.
Sim, S.E., Alspaugh, T.A. and Al-Ani, B. “Marginal notes on a methodical requirements engineering: what experts learned from experience”. IEEE International Requirements Engineering Conference, 2008.
Liu, L., Li T. and Peng, F. “Why requirements engineering fails: A survey report from china”. IEEE International Requirements EngineeringConference 2010. 2010.
Rahman, A.A., Haron, A., Sahibuddin, S. and Mazlan, M.H. “An Empirical Study of the Software Project Requirements Engineering Practice in Malaysia Public Sector–A Perspective from the InternationalStakeholders”. Journal of Computer Theory and Engineering. vol. 6(1), 2014.
Khankaew, S. and Riddle, S. “A review of practice and problems in requirements engineering in small and medium software enterprises in Thailand. IEEE 4th International Workshop on Empirical Requirement Engineering (EmpiRE) 2014. 2014.
Zainol, A. and Mansoor, S. “Investigation into requirements management practices in the Malaysian software industry”. International Conference on Computer Science and Software Engineering 2008, 2008.
Hussain, A., Mkpojiogu, E.O.C. and Kamal, F.M. “Eliciting user
satisfying requirements for an e-health awareness system using kano model”. International Conference on Computer and Computational Science (WSEAS) 2015. Kuala Lumpur. pp. 156-165, 2015.
Mkpojiogu, E.O.C. and Hashim, N.L. “Understanding the relationship between Kano model’s customer satisfaction scores and self-stated requirements importance”. SpringerPlus. Vol. 5(1), pp. 1-22, 2016.
Mkpojiogu, E.O.C. and Hashim, N.L. “Quality-based prioritization: An approach for prioritizing software requirements”. Advancement on Information Technology International Conference (ADVCIT’15) 2015. Krabi, Thailand. 3-5 December 2015.
Hussain, A. and Mkpojiogu, E.O.C. “An application of Kano method in the elicitation of stakeholder satisfying requirements for an e-Ebola awareness system”. International Journal of Systems Applications, Engineering and Development. Vol. 10, pp. 169-178, 2016.
Hussain, A. and Mkpojiogu, E.O.C. “Requirements model for an e-health awareness portal”. International Soft Science Conference (ISSC) 2016. Langkawi, Malaysia, 11-13 April 2016.
Hussain, A. and Mkpojiogu, E.O.C. “Predicting the perceived worth of software products requirements with customer satisfaction”. Advanced Research in Engineering and Information Technology International Conference (AREITIC’16). Bandung, Indonesia. 31 May- 2 June 2016.
Hussain, A., Mkpojiogu, E.O.C. and Hassan, F. “Assessing the influence of self-reported requirements importance on the perceived quality of proposed software products”. International Conference on Information and Communication Technology for Transformation (IC-ICT4T’16). Sabah, Malaysia. 5-7 April 2016.
Hussain, A., Mkpojiogu, E.O.C. and Husin, Z. “Requirements: Towards an understanding on why software projects fail”, 1st
Int’l Soft Science Conference (ISSC’16), Langkawi Island, Malaysia, 11-13 April 2016.
Hussain, A., and Mkpojiogu, E.O.C. “The effects of proposed software product’s features on the satisfaction and dissatisfaction of potential customers”. International Conference on Applied Science and Technology (ICAST’16). Sintok, Malaysia. 17 May 2016.
Downloads
Published
How to Cite
Issue
Section
License
TRANSFER OF COPYRIGHT AGREEMENT
The manuscript is herewith submitted for publication in the Journal of Telecommunication, Electronic and Computer Engineering (JTEC). It has not been published before, and it is not under consideration for publication in any other journals. It contains no material that is scandalous, obscene, libelous or otherwise contrary to law. When the manuscript is accepted for publication, I, as the author, hereby agree to transfer to JTEC, all rights including those pertaining to electronic forms and transmissions, under existing copyright laws, except for the following, which the author(s) specifically retain(s):
- All proprietary right other than copyright, such as patent rights
- The right to make further copies of all or part of the published article for my use in classroom teaching
- The right to reuse all or part of this manuscript in a compilation of my own works or in a textbook of which I am the author; and
- The right to make copies of the published work for internal distribution within the institution that employs me
I agree that copies made under these circumstances will continue to carry the copyright notice that appears in the original published work. I agree to inform my co-authors, if any, of the above terms. I certify that I have obtained written permission for the use of text, tables, and/or illustrations from any copyrighted source(s), and I agree to supply such written permission(s) to JTEC upon request.
