We apologize for a recent technical issue with our email system, which temporarily affected account activations. Accounts have now been activated. Authors may proceed with paper submissions. PhDFocusTM
CFP last date
20 December 2024
Reseach Article

Framework for Enhancing Requirements Engineering Processes: A Conceptual view of Health Information System

by Ishaya Gambo, Abimbola Soriyan, Rhoda Ikono
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 93 - Number 2
Year of Publication: 2014
Authors: Ishaya Gambo, Abimbola Soriyan, Rhoda Ikono
10.5120/16188-5284

Ishaya Gambo, Abimbola Soriyan, Rhoda Ikono . Framework for Enhancing Requirements Engineering Processes: A Conceptual view of Health Information System. International Journal of Computer Applications. 93, 2 ( May 2014), 19-26. DOI=10.5120/16188-5284

@article{ 10.5120/16188-5284,
author = { Ishaya Gambo, Abimbola Soriyan, Rhoda Ikono },
title = { Framework for Enhancing Requirements Engineering Processes: A Conceptual view of Health Information System },
journal = { International Journal of Computer Applications },
issue_date = { May 2014 },
volume = { 93 },
number = { 2 },
month = { May },
year = { 2014 },
issn = { 0975-8887 },
pages = { 19-26 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume93/number2/16188-5284/ },
doi = { 10.5120/16188-5284 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T22:14:47.001794+05:30
%A Ishaya Gambo
%A Abimbola Soriyan
%A Rhoda Ikono
%T Framework for Enhancing Requirements Engineering Processes: A Conceptual view of Health Information System
%J International Journal of Computer Applications
%@ 0975-8887
%V 93
%N 2
%P 19-26
%D 2014
%I Foundation of Computer Science (FCS), NY, USA
Abstract

Requirements engineering (RE) involves understanding the needs of stakeholders, the contexts in which the to-be-developed software will be used; analysing, negotiating, and documenting the stakeholders' requirements; and managing requirement evolution. This is achieved through a process called requirement engineering process. Therefore, the ability to improve software products in order to meet the needs of these stakeholders within today's challenging and fast-paced environment is a great concern in the software development industries. This paper is aimed at presenting an enhanced framework for reasoning about RE process in terms of skill enhancement within the scope of software engineering (SE) and information system development (ISD) using the health information system (HIS) as an example to conceptualize the idea. The paper justifies requirement engineering as a process like all other SE and ISD activities to be adapted to the needs of the processes, the products, the projects and the people doing the work in a conceptual framework for quality improvement. The paper conceptualized this by considering the university as the domain where information system, software system, and healthcare research is carried out for knowledge acquisition that proffers solutions to the software organisations where skills are enhanced. This is with the view to improve the customer organisations where the products, processes and services are used. The framework strive to suggest the enhancement of RE process skills to what the stakeholders wants, which serve to establish a solid foundation for the design and construction of what the stakeholders' gets. As such, a framework to enhance the ability to develop software products for the healthcare domain with the aim of meeting the needs of all system stakeholders and to ensure that the development process is going on the right tract is very important.

References
  1. Cheng, B. H. , & Atlee, J. M. (2009). Current and future research directions in requirements engineering. In Design Requirements Engineering: A Ten-Year Perspective (pp. 11-43). Springer Berlin Heidelberg.
  2. Luukkonen, I. , Toivanen, M. , Mursu, A. , Saranto, K. and Korpela, M. (2013). Researching Activity-Driven Approach for Information Systems Development. In Cruz-Cunha MM, Miranda IM, and Gonçalves P. (eds. ) Handbook of Research on ICTs and Management Systems for Improving Efficiency in Healthcare and Social Care. IGI Global.
  3. Kavakli, E. (1999). Goal-driven requirements engineering: modeling and guidance (Doctoral dissertation, the University of Manchester).
  4. Zave, P. (1997). Classification of research efforts in requirements engineering. ACM Computing Surveys (CSUR), 29(4), 315-321.
  5. Rolland, C. (2006). From conceptual modeling to requirements engineering. In Conceptual Modeling-ER 2006 (pp. 5-11). Springer Berlin Heidelberg.
  6. Maalej, W. , & Thurimella, A. K. (2009, September). Towards a research agenda for recommendation systems in requirements engineering. In Managing Requirements Knowledge (MARK), 2009 Second International Workshop on (pp. 32-39). IEEE.
  7. Castro-Herrera, C. , & Cleland-Huang, J. (2010, May). Utilising recommender systems to support software requirements elicitation. In Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering (pp. 6-10). ACM.
  8. Broy, M. (2006). Requirements engineering as a key to holistic software quality. In Computer and Information Sciences–ISCIS 2006 (pp. 24-34). Springer Berlin Heidelberg.
  9. Nuseibeh, B. , & Easterbrook, S. (2000, May). Requirements engineering: a roadmap. In Proceedings of the Conference on the Future of Software Engineering (pp. 35-46). ACM.
  10. Korpela M, Soriyan HA, Olufokunbi KC. (2000) Activity analysis as a method for information systems development: general introduction and experiments from Nigeria and Finland. Scand J Inf Syst 12(1):191-210.
  11. Luukkonen, I. (2012): Activity-Driven Needs Analysis and Modeling in Information Systems Development. Publications of the University of Eastern Finland, Dissertations in Forestry and Natural Sciences, No 74. Academic Dissertation.
  12. Sommerville I. , Sawyer P. and Viller S. (1997) Requirements Process Improvement through the Phased Introduction of Good Practice, Software Process-Improvement and Practice, 3, 19-34.
  13. Robertson, S. and Robertson, J. (1999). Mastering the Requirements Process. Addison-Wesley, Harlow.
  14. Bray, I. K. (2002). An Introduction to Requirements Engineering, Addison-Wessley.
  15. Yourdon, E. (1989). Modern Structured Analysis, Prentice-Hall, New Jersey, 1989.
  16. Rumbaugh, J. , Jacobson, I. and Booch, G. (1999). The Unified Modelling Language Reference Manual, Addison-Wesley.
  17. Van Lamsweerde, A. (2000, June). Requirements engineering in the year 00: A research perspective. In Proceedings of the 22nd international conference on Software engineering (pp. 5-19). ACM.
  18. Dhirendra, P. (2013). Requirement Engineering Research, International Journal of Computer Science & Engineering Technology (IJCSET), Vol. 4 No. 04, pp. 447-450, ISSN: 2229-3345.
  19. Watson, A. (2008, September). Reflections on Requirements Engineering. In EDOC, pp. xxxiii – xxxiii, ISBN: 978-0-7695-3373-5, IEEE.
  20. Yen, J. , & Tiao, W. A. (1997, January). A systematic tradeoff analysis for conflicting imprecise requirements. In Requirements Engineering, 1997, Proceedings of the Third IEEE International Symposium on (pp. 87-96). IEEE.
  21. Ijadunola KT, Bello MO, Korpela M, and Koskivirta M. (1998). A strategy for the use of information systems to support community-oriented primary healthcare in a deprived economy: A case study of Ife Central LGA, Nigeria. In: Richards B, ed. Current Perspectives in Healthcare Computing 1998, Conference Proceedings. Weybridge, BJHC Books, pp 3-9.
  22. Hannola, L. (2009). Challenges and means for the front end activities of software development. Academic dissertation, Lappeenranta University of Technology, Digipaino.
  23. Dorn, J. , Grun, C. , Werthner, H. and Zapletal, M. (2007). A Survey of B2B Methodologies and Technologies: From Business Models towards Deployment Artifacts. In Proceedings of the 40th Annual Hawaii International Conference on System Sciences (HICSS'07). p. 143. IEEE Computer Society Washington, DC, USA.
  24. Soriyan H. A. ,Afolabi A. O. ,Fatusi O. , Mursu A. ,Korpela M. J. Akinde A. D(2005). Development of a computer based Primary health care Information System: Towards a holistic system. In: Abiodun O. Bada and Adekunle Okunoye, eds. Enhancing Human Resource Development Through ICT: In Research-In-Progress Papers[CD-ROM]. Procceedings of the 8th International Working Conference of IFIP WG 9. 4 26-28 May, 2005, Abuja, Nigeria
  25. Jarke, M. , Loucopoulos, P. , Lyytinen, K. , Mylopoulos, J. , & Robinson, W. (2010, January). The brave new world of design requirements: four key principles. In Advanced Information Systems Engineering (pp. 470-482). Springer Berlin Heidelberg.
  26. Ernst, N. A. (2012). Software Evolution: a Requirements Engineering Approach (Doctoral dissertation, University of Toronto).
  27. Zave, P. , & Jackson, M. (1997). Four dark corners of requirements engineering. ACM Transactions on Software Engineering and Methodology (TOSEM), 6(1), 1-30.
  28. Gambo, I. , Soriyan, A. , & Achimugu, P. (2012). Software Performance Quality Evaluation of MINPHIS Architecture using ATAM. International Journal of Computer Applications, 46.
  29. Groen, P. ; Soriyan A. , and Nyamai-Kisia, C. (2005) "MINPHIS: Nigeria's experience using VistA, MUSTI, and other technologies in building their own national health information system", in the Virtual Medical World, a monthly news service for virtual medical community,http://www. hoise. com/vmw/05/articles/vmw/LV-VM-10-05-19. html (Accessed 05/01/2006)
  30. Damian, D. E. H. (2003) "Challenges in Requirements Engineering," Requirements E, Springer, Springer, vol. 8, no. 3, pp. 149-160.
  31. Berry, D. M. and Lawrence, B. (1998): Requirements Engineering, IEEE Software, Vol. 15, No. 2, pp. 26-29.
  32. Leite, J. C. (1987): A Survey on Requirements Analysis, Advanced Software Engineering Project Technical Report RTP-071, University of California at Irvine, Department of Information and Computer Science.
  33. Damian, D. , Izquierdo, L. Singer, J. and Kwan, I. (2007). Awareness in the wild: Why communication breakdowns occur. In Second IEEE International Conference on Global Software Engineering, 2007. ICGSE 2007, pages 81-90.
  34. Kwan, I. and Damian, D. (2011). The hidden experts in software-engineering communication (NIER track). In Proceedings of the 33rd International Conference on Software Engineering, ICSE '11, pages 800-803, New York, NY, USA, ACM.
  35. McAllister, C. A. (2006). Requirements determination of information systems: User and developer perceptions of factors contributing to misunderstandings. ProQuest.
  36. Firesmith, D. (2007, May). Engineering Safety and Security Related Requirements for Software Intensive Systems. In ICSE Companion (p. 169).
  37. Sawyer, P. , Gervasi, V. , & Nuseibeh, B. (2011, August). Unknown knowns: Tacit knowledge in requirements engineering. In Requirements Engineering Conference (RE), 2011 19th IEEE International (pp. 329-329). IEEE.
  38. El Emam, K. , & Madhavji, N. H. (1995, March). A field study of requirements engineering practices in information systems development. In Requirements Engineering, 1995. , Proceedings of the Second IEEE International Symposium on (pp. 68-80). IEEE.
  39. Sommerville I. (1996) Software Engineering Fifth Edition, Addison-Wesley.
  40. Schrodl, H. , and Wind, S. (2011). Requirements Engineering for Cloud Computing, Journal of Communications and Computers, Vol. 8, pp. 707-715.
  41. Standish Group, CHAOS Report, available online http://www. standishgroup. com, 2010.
  42. Rouibah, K. , and Al-Rafee, S. (2009). Requirement engineering elicitation methods: A Kuwaiti empirical study about familiarity, usage and perceived value, Information Management & Computer Security, Vol. 17, No. 3, pp. 192-217.
  43. Aurum, A. , & Wohlin, C. (Eds. ). (2005). Engineering and managing software requirements. Springer Verlag, Berlin.
  44. Beecham, S. , Hall, T. , & Rainer, A. (2003). Software process improvement problems in twelve software companies: An empirical analysis. Empirical software engineering, 8(1), 7-42.
  45. Leffingwell, D. (1997). Calculating the Return on Investment from More Effective Requirements Management, American Programmer, Vol. 10, No. 4, pp. 13–16.
  46. Grady, R. (1999). An Economic Release Decision Model: Insights into Software Project Management. In Proceedings of the Applications of Software Measurement Conference, Orange Park, FL, pp. 227–239.
  47. Gilb, T. (2010). What's Wrong with Requirements Specification? An Analysis of the Fundamental Failings of Conventional Thinking about Software Requirements, and Some Suggestions for Getting it Right. JSEA, 3(9), 827-838.
  48. Sadraei, E. , Aurum, A. , Beydoun, G. , and Peach, B. (2007). A field study of the requirements practice in Australian software industry, Requirements Engineering, Vol. 12, pp. 145-162.
  49. Hall, T. , Beecham, S. , and Rainer, A. (2002). Requirements problems in twelve software companies: an empirical analysis, IEEE Proceedings Software 149, pp. 153-160.
  50. Soriyan H. A. (2004) A conceptual Framework for Information System Development Methodology for Educational and Industrial Sectors in Nigeria. PhD Thesis. Obafemi Awolowo University, Ile-Ife Nigeria.
Index Terms

Computer Science
Information Sciences

Keywords

Requirements Requirements Engineering Process Health Information System MINPHIS.