scholarly journals Software Development Process Supported by Business Process Modeling - An Experience Report

Author(s):  
Olga Lucero Vega Márquez ◽  
Jaime Chavarriaga ◽  
Helga Duarte
2019 ◽  
Vol 26 (2) ◽  
pp. 655-674 ◽  
Author(s):  
Laura P. Lopez-Arredondo ◽  
Cynthia B. Perez ◽  
Jesus Villavicencio-Navarro ◽  
Kathya E. Mercado ◽  
Martin Encinas ◽  
...  

Purpose The purpose of this paper is to address the need of a reengineering of the software development process in a Mexican technology services company. In general, the main risk faced by small- and medium-sized software developers (SMEs) is the inability to meet delivery times or to adjust to project requirements, whether through lack of follow-up on the critical activities of the development process or through an inadequate distribution of workloads among members of the project team. Design/methodology/approach The methodology used to carry out the reengineering of the software development process is Hammer and Champy, which consists of six stages: introduction to the current situation of the company and the need for change; identification of the business processes; selection of the business process to be redesigned; understanding of the process selected; proposal for reengineering the business process selected; and the results of the comparison between the current situation of the process and the proposed reengineering of the process through the use of Business Process Model and Notation (BPMN 2.0). Findings Based on the results, the paper shows the importance of the analysis and implementation of the reengineering in a software development company. It describes step-by-step how to apply the methodology of Hammer and Champy in a business process through simulated scenarios, using BPMN 2.0. By carrying out the implementation of the proposed reengineering, the company would therefore save 45.12 percent of costs, 41.17 percent of time, and a better distribution of resources, at the same time guaranteeing the satisfaction of its clients. Originality/value The study addresses the current needs of small- and medium-sized software developers, providing a step-by-step guide to the implementation of a process reengineering methodology, performing an analysis and modeling of processes in BPMN 2.0 and providing results through a simulation of the critical process, with the aim to observe the flow of activities and the significant improvements that would be achieved by implementing the reengineering proposal. This simulation schema allows business owners to observe the potential of the changes and to verify the positive impact they would have on the company before beginning to make operational changes in the organization.


Author(s):  
Harry S. Delugach

Automated tools are often used to support software development workflows. Many of these tools are aimed toward a development workflow that relies implicitly on particular supported roles and activities. Developers may already understand how a tool operates; however, developers do not always understand or adhere to a development process supported (or implied) by the tools, nor adhere to prescribed processes when they are explicit. This chapter is aimed at helping both developers and their managers understand and manage workflows by describing a preliminary formal model of roles and activities in software development. Using this purely descriptive model as a starting point, the authors evaluate some existing tools with respect to their description of roles in their processes, and finally show one application where process modeling was helpful to managers. We also introduce an extended model of problem status as an example of how formal models can enrich understanding of the software development process, based on the analysis of process roles


Sign in / Sign up

Export Citation Format

Share Document