Institutional review boards (IRB) are established by institutions to protect (human) research subjects from abuse. Researchers are thus required to apply and obtain IRB ap- proval for any research initiative that involves human subjects. Currently, most USA institutions use paper-based or partially automated approaches for IRB application, review, and approval processes. This can be cumbersome, error-prone and usually add unnecessary workloads to researchers. Moreover, paper- based approaches can delay or reduce research output, especially during collaborative research projects if researchers are from different institutions. Web-based information systems can be developed and used to streamline IRB application and approval processes. Before such web-based systems can be developed, the requirements of the system have to be analyzed and designed. However, requirements analysis and design are usually very tedious and expensive project, which may discourage some institutions from implementing systems to support IRB processes. The aim of this paper is to contribute a set of requirements and systems models that can be customized and re-used, by other institutions, to develop IRB Systems. Accordingly, we provide the following models, use case, feature tree model, and network diagram. In addition, we discussed our experiences and systems analysis principles we adopt to make this project a success. We believe that the experiences we share and the models we provide in this paper can inform practice and advance the knowledge of web-based information systems development. Re-using existing requirements and designs can also help to reduce the amount of time and cost required to develop similar systems.
| Published in | American Journal of Operations Management and Information Systems (Volume 6, Issue 4) |
| DOI | 10.11648/j.ajomis.20210604.12 |
| Page(s) | 75-85 |
| Creative Commons |
This is an Open Access article, distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution and reproduction in any medium or format, provided the original work is properly cited. |
| Copyright |
Copyright © The Author(s), 2024. Published by Science Publishing Group |
Functional Requirements, Feature Tree Model, IRB, Web-based System, Information Systems and Technologies, Design Models
| [1] | M. Bertocco, F. Ferraris, C. Offelli, and M. Parvis. A client-server architecture for distributed measurement systems. IEEE Transactions on Instrumentation and Measurement, 47 (5): 1143–1148, Oct 1998. |
| [2] | Jiang Bian, Mengjun Xie, William Hogan, Laura Hutchins, Umit Topaloglu, Cheryl Lane, Jennifer Holland, Thomas Wells, Yu Fan, Matt Baker, et al. Clara: an integrated clinical research administration system. Journal of the American Medical Informatics Association, 21 (e2): e369–e373, 2014. |
| [3] | O. Brill and E. Knauss. Structured and unobtrusive observation of anonymous users and their context for requirements elicitation. In 2011 IEEE 19th International Requirements Engineering Conference, pages 175–184, Aug 2011. |
| [4] | Ya-Ling Chen, Hsueh-Lin Chen, Chia-I Lin, Bo-Chao Cheng, Guo-Tan Liao, Ting-Chun Yin, and Kuo-Yang Hung. ipat: Intelligent privacy- preserving administration tool for irb applications. In 2012 IEEE 14th International Conference on e-Health Networking, Applications and Services (Healthcom), pages 494–497, Oct 2012. |
| [5] | Raymond G. De Vries and Carl P. Forsberg. What do irbs look like? what kind of support do they receive?. Accountability in Research: Policies & Quality Assurance, 9 (3/4): 199, 2002. |
| [6] | Kathleen Dziak, Roger Anderson, Mary Ann Sevick, Carol S Weisman, Douglas W Levine, and Sarah Hudson Scholle. Variations among institutional review board reviews in a multisite health services research study. Health services research, 40 (1): 279–290, 2005. |
| [7] | Stefan Ferber, Jurgen Haag, and Juha Savolainen. Feature interaction and dependencies: Modeling features for reengineering a legacy product line. In International Conference on Software Product Lines, pages 235–256. Springer, 2002. |
| [8] | Nancy Friedman, Lin Drury, and Brian Evans. Pace universitys web- based irb application processing system. |
| [9] | Ravindra Ghooi. Institutional review boards: Challenges and opportu- nities. Perspectives in Clinical Research, 5 (2), Apr 2014. Copyright - Copyright Medknow Publications & Media Pvt Ltd Apr-Jun 2014; Last updated - 2015-11-02. |
| [10] | K. D. Gill, A. M. Zaidi, and M. M. Kiani. Eliciting futuristic end- user requirements through contributory appreciative inquiry. In 2014 National Software Engineering Conference, pages 49–54, Nov 2014. |
| [11] | Christine Grady. Institutional review boards: Purpose and challenges. Chest, 148 (5): 1148 – 1155, 2015. |
| [12] | Shan He, Scott P. Narus, Julio C. Facelli, Lee Min Lau, Jefferey R. Botkin, and John F. Hurdle. A domain analysis model for eirb systems: Addressing the weak link in clinical research informatics. Journal of Biomedical Informatics, 52: 121 – 129, 2014. Special Section: Methods in Clinical Research Informatics. |
| [13] | A. M. Hickey and A. M. Davis. Elicitation technique selection: how do experts do it? In Proceedings. 11th IEEE International Requirements Engineering Conference, 2003., pages 169–178, Sept 2003. |
| [14] | A. M. Hickey and A. M. Davis. Requirements elicitation and elicitation technique selection: model for two knowledge-intensive software devel- opment processes. In 36th Annual Hawaii International Conference on System Sciences, 2003. Proceedings of the, pages 10 pp.–, Jan 2003. |
| [15] | Jon Mark Hirshon, Scott D Krugman, Michael D Witting, Jon P Furuno, M Rhona Limcangco, Andre R Perisse, and Elizabeth K Rasch. Variability in institutional review board assessment of minimal-risk research. Acad Emerg Med, 9 (12): 1417–1420, 2002. |
| [16] | Y. Kaeri, K. Sugawara, Y. Manabe, and C. Moulin. A support system for remote brainstorming sessions. In 2015 IEEE 14th International Conference on Cognitive Informatics Cognitive Computing (ICCI*CC), pages 303–308, July 2015. |
| [17] | Kyo C Kang, Jaejoon Lee, and Patrick Donohoe. Feature-oriented product line engineering. IEEE software, 19 (4): 58–65, 2002. |
| [18] | Elaine Larson, Tiffany Bratts, Jack Zwanziger, and Patricia Stone. A survey of irb process in 68 u.s. hospitals. Journal of Nursing Scholarship, 36 (3): 260–4, Third 2004. Copyright - Copyright Sigma Theta Tau International, Inc., Honor Society of Nursing Third Quarter 2004; Last updated - 2014-06-28; CODEN - IMNSEP. |
| [19] | Yvonna S Lincoln and William G Tierney. Qualitative research and institutional review boards. Qualitative inquiry, 10 (2): 219–234, 2004. |
| [20] | Jonathan Mansbach, Uchechi Acholonu, Sunday Clark, and Carlos A Camargo. Variation in institutional review board responses to a stan- dard, observational, pediatric research protocol. Academic Emergency Medicine, 14 (4): 377–380, 2007. |
| [21] | J. C. Nwokeji, T. Clark, B. Barn, V. Kulkarni, and S. O. Anum. A data-centric approach to change management. In 2015 IEEE 19th In- ternational Enterprise Distributed Object Computing Conference, pages 185–190, Sept 2015. |
| [22] | J. C. Nwokeji, T. Clark, and B. S. Barn. Towards a comprehensive meta- model for kaos. In 2013 3rd International Workshop on Model-Driven Requirements Engineering (MoDRE), pages 30–39, July 2013. |
| [23] | Joshua C. Nwokeji, Tony Clark, and Balbir S. Barn. A proposal for consolidated intentional modeling language. In Proceedings of the Second Workshop on Graphical Modeling Language Development, GMLD ’13, pages 12–22, New York, NY, USA, 2013. ACM. |
| [24] | Carla Pacheco and Ivan Garcia. A systematic literature review of stakeholder identification methods in requirements elicitation. Journal of Systems and Software, 85 (9): 2171–2181, 2012. |
| [25] | C. Putnam and J. Cheng. Therapist-centered requirements: A multi- method approach of requirement gathering to support rehabilitation gaming. In 2014 IEEE 22nd International Requirements Engineering Conference (RE), pages 13–22, Aug 2014. |
| [26] | Matthias Riebisch, Kai Bollert, Detlef Streitferdt, and Ilka Philippow. Extending feature diagrams with uml multiplicities. In 6th World Conference on Integrated Design & Process Technology (IDPT2002), volume 23, 2002. |
| [27] | GEORGE SILBERMAN and KATHERINE L. KAHN. Burdens on research imposed by institutional review boards: The state of the evidence and its implications for regulatory reform. Milbank Quarterly, 89 (4): 599 – 627, 2011. |
| [28] | Thomas O Stair, Caitlin R Reed, Michael S Radeos, Greg Koski, and Carlos A Camargo. Variation in institutional review board responses to a standard protocol for a multicenter clinical trial. Academic Emergency Medicine, 8 (6): 636–641, 2001. |
| [29] | A. Sutcliffe and P. Sawyer. Requirements elicitation: Towards the unknown unknowns. In 2013 21st IEEE International Requirements Engineering Conference (RE), pages 92–104, July 2013. |
| [30] | Simon N Whitney, Kirsten Alcser, Carl E Schneider, Laurence B McCullough, Amy L McGuire, and Robert J Volk. Principal investigator views of the irb system. Int J Med Sci, 5 (2): 68–72, 2008. |
| [31] | Karl Wiegers and Joy Beatty. Software requirements. Pearson Education, 2013. |
| [32] | Nwokeji, Joshua C., Ayodele Olagunju, Anugu Apoorva, Steve Frezza, and M. M. Tang. "Requirements Model for an Integrated Attendance Monitoring System (IAMS)." In Future Technologies Conference (FTC), pp. 29-30. 2017. |
| [33] | Nwokeji, Joshua, Faisal Aqlan, Jorge Martinez, Terry Holmes, Stephen Frezza, and Rita Orji. "Panel: Integrating Requirements Engineering Education into Core Engineering Disciplines." In 2018 IEEE Frontiers in Education Conference (FIE), pp. 1-3. IEEE, 2018. |
APA Style
Joshua Nwokeji, Walter Iwanenko. (2021). Requirements Analysis and Design of IRB System. American Journal of Operations Management and Information Systems, 6(4), 75-85. https://doi.org/10.11648/j.ajomis.20210604.12
ACS Style
Joshua Nwokeji; Walter Iwanenko. Requirements Analysis and Design of IRB System. Am. J. Oper. Manag. Inf. Syst. 2021, 6(4), 75-85. doi: 10.11648/j.ajomis.20210604.12
AMA Style
Joshua Nwokeji, Walter Iwanenko. Requirements Analysis and Design of IRB System. Am J Oper Manag Inf Syst. 2021;6(4):75-85. doi: 10.11648/j.ajomis.20210604.12
Share This Article
Twitter
Linked In
Facebook
Copy
Download@article{10.11648/j.ajomis.20210604.12,
author = {Joshua Nwokeji and Walter Iwanenko},
title = {Requirements Analysis and Design of IRB System},
journal = {American Journal of Operations Management and Information Systems},
volume = {6},
number = {4},
pages = {75-85},
doi = {10.11648/j.ajomis.20210604.12},
url = {https://doi.org/10.11648/j.ajomis.20210604.12},
eprint = {https://article.sciencepublishinggroup.com/pdf/10.11648.j.ajomis.20210604.12},
abstract = {Institutional review boards (IRB) are established by institutions to protect (human) research subjects from abuse. Researchers are thus required to apply and obtain IRB ap- proval for any research initiative that involves human subjects. Currently, most USA institutions use paper-based or partially automated approaches for IRB application, review, and approval processes. This can be cumbersome, error-prone and usually add unnecessary workloads to researchers. Moreover, paper- based approaches can delay or reduce research output, especially during collaborative research projects if researchers are from different institutions. Web-based information systems can be developed and used to streamline IRB application and approval processes. Before such web-based systems can be developed, the requirements of the system have to be analyzed and designed. However, requirements analysis and design are usually very tedious and expensive project, which may discourage some institutions from implementing systems to support IRB processes. The aim of this paper is to contribute a set of requirements and systems models that can be customized and re-used, by other institutions, to develop IRB Systems. Accordingly, we provide the following models, use case, feature tree model, and network diagram. In addition, we discussed our experiences and systems analysis principles we adopt to make this project a success. We believe that the experiences we share and the models we provide in this paper can inform practice and advance the knowledge of web-based information systems development. Re-using existing requirements and designs can also help to reduce the amount of time and cost required to develop similar systems.},
year = {2021}
}
TY - JOUR T1 - Requirements Analysis and Design of IRB System AU - Joshua Nwokeji AU - Walter Iwanenko Y1 - 2021/12/24 PY - 2021 N1 - https://doi.org/10.11648/j.ajomis.20210604.12 DO - 10.11648/j.ajomis.20210604.12 T2 - American Journal of Operations Management and Information Systems JF - American Journal of Operations Management and Information Systems JO - American Journal of Operations Management and Information Systems SP - 75 EP - 85 PB - Science Publishing Group SN - 2578-8310 UR - https://doi.org/10.11648/j.ajomis.20210604.12 AB - Institutional review boards (IRB) are established by institutions to protect (human) research subjects from abuse. Researchers are thus required to apply and obtain IRB ap- proval for any research initiative that involves human subjects. Currently, most USA institutions use paper-based or partially automated approaches for IRB application, review, and approval processes. This can be cumbersome, error-prone and usually add unnecessary workloads to researchers. Moreover, paper- based approaches can delay or reduce research output, especially during collaborative research projects if researchers are from different institutions. Web-based information systems can be developed and used to streamline IRB application and approval processes. Before such web-based systems can be developed, the requirements of the system have to be analyzed and designed. However, requirements analysis and design are usually very tedious and expensive project, which may discourage some institutions from implementing systems to support IRB processes. The aim of this paper is to contribute a set of requirements and systems models that can be customized and re-used, by other institutions, to develop IRB Systems. Accordingly, we provide the following models, use case, feature tree model, and network diagram. In addition, we discussed our experiences and systems analysis principles we adopt to make this project a success. We believe that the experiences we share and the models we provide in this paper can inform practice and advance the knowledge of web-based information systems development. Re-using existing requirements and designs can also help to reduce the amount of time and cost required to develop similar systems. VL - 6 IS - 4 ER -
Email: