Quarterly Journal of Information and Communication Technology ​

Workflow Checklist Package for Software System Development

Document Type : Original Research Article

Author

Department of Computer Engineering, Khodabandeh Branch, Islamic Azad University, Zanjan, Iran

10.22034/apj.2023.706762
Abstract
In today's technology-oriented world, a wide range of commercial and administrative services are provided through the use of software systems. Due to the importance of a comprehensive and structured process in the development of a software systems and in this regard, in this paper proposes a useful management checklist cluster, called software system development workflow checklist. The proposed checklist is actually a package containing a subset of more detailed monitoring checklists in the software system development process. The suggested checklist is a tool to create a comprehensive management routine to evaluate the performance of tasks and structured workflow in the development of software systems. In addition to explaining the system workflow and clarifying the monitoring of software system development, the proposed workflow checklist package is proposed as a resource for working team members to evaluate and resolve differences of opinion and align executive tasks and also to avoid and prevent common management mistakes. It should be noted that based on the proposed checklist package, in the software system development workflow management process, project managers could monitor the system development with both a top-down and middle-out approach. This means that first, with a top-down view of each phase of the software life cycle, could receive the progress report and with the middle-out management view, evaluate and control items of the proposed checklist package. From our point of view, having such a workflow checklist package is one of the most essential activities in order to facilitate the management and auditing of the software development life cycle, which is needed for the integrated implementation of organizational projects and their structured and comprehensive management.

Keywords


          Molléri JS, Petersen K, Mendes E. Survey guidelines in software engineering: An annotated review. InProceedings of the 10th ACM/IEEE international symposium on empirical software engineering and measurement 2016 Sep 8 (pp. 1-6).
     [2]          Zhang L, Tian JH, Jiang J, Liu YJ, Pu MY, Yue T. Empirical research in software engineering—a literature survey. Journal of Computer Science and Technology. 2018 Sep;33:876-99.
     [3]          Bhuvaneswari T, Prabaharan S. A survey on software development life cycle models. International Journal of Computer Science and Mobile Computing. 2013 May;2(5):262-7.
     [4]          Sarker IH, Faruque F, Hossen U, Rahman A. A survey of software development process models in software engineering. International Journal of Software Engineering and Its Applications. 2015 Nov;9(11):55-70.
     [5]          Suleiman H, Adepetu A, Arnautovic E, Svetinovic D. Comprehensive integrated checklists for requirements engineering and software project management. In2013 International Conference on Information Science and Applications (ICISA) 2013 Jun 24 (pp. 1-4). IEEE.
     [6]          Brace W, Ekman K. CORAMOD: a checklist-oriented model-based requirements analysis approach. Requirements Engineering. 2014 Mar;19:1-26.
     [7]          Morschheuser B, Hassan L, Werder K, Hamari J. How to design gamification? A method for engineering gamified software. Information and Software Technology. 2018 Mar 1;95:219-37.
     [8]          Kanewala U, Bieman JM. Testing scientific software: A systematic literature review. Information and software technology. 2014 Oct 1;56(10):1219-32.
     [9]          Houston D. The value of a good checklist. Software Quality Professional. 2004 Mar 1;6(2):17.
  [10]          Tausworthe RC. The work breakdown structure in software project management. Journal of Systems and Software. 1979 Jan 1;1:181-6.
  [11]          Li L. The impact of risk checklists on project manager's risk perception and decision-making process.
  [12]          Marcelino-Sádaba S, Pérez-Ezcurdia A, Lazcano AM, Villanueva P. Project risk management methodology for small firms. International journal of project management. 2014 Feb 1;32(2):327-40.
  [13]          Parmenter D. Key performance indicators: developing, implementing, and using winning KPIs. John Wiley & Sons; 2015 Apr 13.
  [14]          Kuhrmann M, Diebold P, Münch J, Tell P, Garousi V, Felderer M, Trektere K, McCaffery F, Linssen O, Hanser E, Prause CR. Hybrid software and system development in practice: waterfall, scrum, and beyond. InProceedings of the 2017 international conference on software and system process 2017 Jul 5 (pp. 30-39).
  [15]          Madaio MA, Stark L, Wortman Vaughan J, Wallach H. Co-designing checklists to understand organizational challenges and opportunities around fairness in AI. InProceedings of the 2020 CHI conference on human factors in computing systems 2020 Apr 21 (pp. 1-14).
  [16]          Lewis WE. Software testing and continuous quality improvement. CRC press; 2017 Jun 1.
  [17]          Kupiainen E, Mäntylä MV, Itkonen J. Using metrics in Agile and Lean Software Development–A systematic literature review of industrial studies. Information and software technology. 2015 Jun 1;62:143-63.
  [18]          Wieringa RJ. Design science methodology for information systems and software engineering. Springer; 2014 Nov 19.
  [19]          Wagner S, Ruhe M. A systematic review of productivity factors in software development. arXiv preprint arXiv:1801.06475. 2018 Jan 19.
  [20]          Blank S, Dorf B. The startup owner's manual: The step-by-step guide for building a great company. John Wiley & Sons; 2020 Mar 17.
  [21]          Braude EJ, Bernstein ME. Software engineering: modern approaches. Waveland Press; 2016 Mar 9.
  [22]          Dennis A, Wixom B, Tegarden D. Systems analysis and design: An object-oriented approach with UML. John wiley & sons; 2015 Mar 2.
  [23]          Ghobadi S. What drives knowledge sharing in software development teams: A literature review and classification framework. Information & Management. 2015 Jan 1;52(1):82-97.
  [24]          Mayring P. Qualitative content analysis: theoretical foundation, basic procedures and software solution.
  [25]          Ilyas M, Khan SU, Rashid N. Empirical validation of software integration practices in global software development. SN Computer Science. 2020 May;1:1-23.
  [26]          Lasso A, Kazanzides P. System integration. InHandbook of Medical Image Computing and Computer Assisted Intervention 2020 Jan 1 (pp. 861-891). Academic Press.
  [27]          Kotha S, Gopal TV. Formal methods for enterprise application integration. Complex Control System. 2021;3(1):9-24.
  [28]          Aghajani E, Nagy C, Vega-Márquez OL, Linares-Vásquez M, Moreno L, Bavota G, Lanza M. Software documentation issues unveiled. In2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE) 2019 May 25 (pp. 1199-1210). IEEE.
  [29]          Al-Saqqa S, Sawalha S, AbdelNabi H. Agile software development: Methodologies and trends. International Journal of Interactive Mobile Technologies. 2020 Nov 1;14(11).