The Role of Business Process Modeling in Information System Development with Disciplined Agile Delivery Approach (original) (raw)
Related papers
Software Process Models and Agile Method Applicability in Industry
International Journal of Trend in Scientific Research and Development
Software process models have been developed since 1968. When software process models are implemented in the software sector, it is considered that more suitable projects will be developed in terms of customer satisfaction and cost. In this study, the use of Agile, which is a frequently used software process model, in industry is investigated. In the research, software process models are explained and industrial sectors using Agile method are examined. It has been observed that customer satisfaction, time saving, a project success increase in sectors where Agile method is applied. Likewise, the project has also increased efficiency and competence.
Towards a Business Process Modeling Technique for Agile Development of Case Management Systems
Complex Systems Informatics and Modeling Quarterly, 2017
A modern organization needs to adapt its behavior to changes in the business environment by changing its Business Processes (BP) and corresponding Business Process Support (BPS) systems. One way of achieving such adaptability is via separation of the system code from the process description/model by applying the concept of executable process models. Furthermore, to ease introduction of changes, such process model should separate different perspectives, for example, control-flow, human resources, and data perspectives, from each other. In addition, for developing a completely new process, it should be possible to start with a reduced process model to get a BPS system quickly running, and then continue to develop it in an agile manner. This article consists of two parts, the first sets requirements on modeling techniques that could be used in the tools that supports agile development of BPs and BPS systems. The second part suggests a business process modeling technique that allows to start modeling with the data/information perspective which would be appropriate for processes supported by Case or Adaptive Case Management (CM/ACM) systems. In a model produced by this technique, called data-centric business process model, a process instance/case is defined as sequence of states in a specially designed instance database, while the process model is defined as a set of rules that set restrictions on allowed states and transitions between them. The article details the background for the project of developing the datacentric process modeling technique, presents the outline of the structure of the model, and gives formal definitions for a substantial part of the model.
AN AGILE BUSINESS PROCESS SOFTWARE DEVELOPMENT METHODOLOGY
An agile business process software development methodology is proposed, developed and tested in this research. To speed up the business process software development practices in the organization and to address the requirements more efficiently, an agile approach was adapted. Two new processes were developed using the new methodology. The improvement was assessed by utilizing nine older developments: A formula was developed in this research that estimates the development efforts for old business process software development projects. The motivation mainly was to efficiently gather desired requirements and decrease the development time. There are difficulties in applying agile practices to the domain: stakeholders of the business process software development deal with more than one project at the same time. Moreover the proposed methodology suggests a critical utilization of training that improves the gathering of quality requirements. Agile requirements gathering, periodic meetings, and incremental and iterative development are observed to be the building blocks of the proposed methodology during the studies for applying the methodology to two processes in an organization. A survey on business process software development methodologies is included. There are currently process development methodologies and limited adaptation work on agile approaches to process redesign. Such existing work does not define a specialized agile methodology for business process software development. In addition, the proposed methodology is examined based on the effort spent during the development. The examination is realized with the effort estimation formula. According to the formula, a 21% effort saving is realized with the proposed methodology compared with the traditional methodology.
Software Development Process Supported by Business Process Modeling - An Experience Report
Proceedings of the Seventh International Symposium on Business Modeling and Software Design, 2017
Understanding businesses and how they work can help software engineers build systems that really meet the corresponding business goals. For instance, methods such as the Rational Unified Process (RUP) include activities to model a business before eliciting requirements. However, during our software development practice in academic and "real-life" projects, we found problems using these artefacts with stakeholders. Here we present our experience on integrating BPMN (Business Process Modeling and Notation) diagrams with RUP, aiming to improve the elicitation of software requirements. These diagrams appeared to be easier to understand by stakeholders. The current paper discusses the challenges we faced in using RUP and the way in which we integrate conceptual maps and BPMN into the process. In addition, we illustrate the changes using models that reflect real project implementations realized by using this approach. Eliciting requirements using RUP. In RUP, business processes are analyzed using diverse artifacts: 242
Business Process Modeling for developing Process Oriented IT Systems
2004
Information system developers are challenged to develop systems that should meet the requirements of modern organizations. By promoting the enterprise-wide integration, the paradigm of Business Process Management contrasts with traditional information system development. The latter was suffered, but also crystallized, the vertical division of the enterprise activities. In addition, the paradigms of Business Process Reengineering and Improvement contrast with traditional information system development that focused on automating and supporting existing business processes. Now, enterprises should create new ways of working to survive in a competitive environment. In this context, enterprise modeling can help understanding the current business situation and establishing a vision of what the future should be like. Therefore, business process modeling becomes a prerequisite for system requirements elicitation and system development.
Business Process Modeling in Software Development
1997
This paper is structured into two parts, dealing with notational and methodological aspects, respectively. The rst part introduces a description technique for business processes which p r o vides both an intuitive, graphical notation and a textual syntax. The de nition of semantics of this description technique is related to a mathematical system model. Using this mathematical system model as a common formal basis, the relation between business process model and other models employed in software development can be precisely de ned. In the second part, a business process driven method of software development is outlined, as well as a systematic approach to business process reengineering. As software development and business process reengineering are closely related and often occur together in practice, these two approaches will be integrated into a method which systematically combines both techniques.
Software process models are integral constituents of system lifecycle models that were initially proposed to follow a structured approach to building an improved or a new system. They are the core processes of the software engineering area. This work is an attempt to study the different software process models. The advantages and disadvantages of every model have been analyzed and the performance of every model has been evaluated. The main critics to the present software systems models are that they cannot be built with mathematical certainty hence they are not empirical models. Many models like Waterfall model (sequential approach), Incremental Model (incremental approach), Spiral Model (evolutionary approach), Formal Methods Model (specialized approach), Extreme Programming Model (agile approach) and Rational Unified Process (RUP) are studied in a comparative and differentiative manner. The evolution of these development methods has been uncovered in this study.
Software process models: a review and analysis
International Journal of Engineering & Technology
Modeling of software process has been a very challenging problem and constantly debated in the software development community in the past 30+ years, largely due to the complex nature of the software development process that involves not only the technical knowledge and skills but also many other factors, such as human, management, quality assessment, and cost. Although the situations of creating software differ greatly from one case to another, there are some common themes shared by many of the situations, and hence various software process models have been emerged to address these common themes. In this paper, we present a review of the software process models commonly used in practice, from traditional to agile, and assessment of these models with metrics and case studies.