scholarly journals Toward a Well-structured Development Methodology for Business Process-oriented Software Systems based on Services

2013 ◽  
Vol 9 ◽  
pp. 351-360 ◽  
Author(s):  
Margarita Mondragón ◽  
Manuel Mora ◽  
Laura Garza ◽  
Francisco Álvarez ◽  
Laura Rodríguez ◽  
...  
2009 ◽  
Vol 19 (1) ◽  
pp. 1-37 ◽  
Author(s):  
Chun Ouyang ◽  
Marlon Dumas ◽  
Wil M. P. Van Der Aalst ◽  
Arthur H. M. Ter Hofstede ◽  
Jan Mendling

Author(s):  
Daniel Lübke ◽  
Maike Ahrens ◽  
Kurt Schneider

AbstractBusiness process modeling is an important activity for developing software systems—especially within digitization projects and when realizing digital business models. Specifying requirements and building executable workflows is often done by using BPMN 2.0 process models. Although there are several style guides available for BPMN, e.g., by Silver and Richard (BPMN method and style, vol 2, Cody-Cassidy Press, Aptos, 2009), there has not been much empirical research done into the consequences of the diagram layout. In particular, layouts that require scrolling have not been investigated yet. The aim of this research is to establish layout guidelines for business process modeling that help business process modelers to create more understandable business process diagrams. For establishing benefits and penalties of different layouts, a controlled eye tracking experiment was conducted, in which data of 21 professional software developers was used. Our results show that horizontal layouts are less demanding and that as many diagram elements as possible should be put on the initially visible screen area because such diagram elements are viewed more often and longer. Additionally, diagram elements related to the reader’s task are read more often than those not relevant to the task. BPMN modelers should favor a horizontal layout and use a more complex snake or multi-line layout whenever the diagrams are too large to fit on one page in order to support BPMN model comprehension.


2003 ◽  
Vol 3 (2) ◽  
pp. 137-154
Author(s):  
Kostas Chalikias ◽  
George Valiris ◽  
Panagiotis Chytas

2018 ◽  
Vol 7 (4.12) ◽  
pp. 52
Author(s):  
Mohit Arora ◽  
Dr. Sahil Verma ◽  
Dr. Kavita

Software Process Models from its inception instill standardization and creates a generic culture of developing software for various IT industries. A great paradigm shift has been observed in terms of embracing Agile Development methodology as a viable development methodology in cross key business units. There is a buffet of agile methodologies comes under the umbrella of ASD, out of which Scrum got the highest popularity and acceptability index.  Agile based software development is the need of immediate environment. There is an increasing demand for significant changes to software systems to meet ever-changing user requirements and specifications. As Agile is volatile, so effort estimation is challenging and still striving for perfection to decide size, effort, cost, duration and schedule of projects with minimum error. This cause sensitizes potential researchers all across the globe to start working on addressing the issue of inaccurate predication of efforts. The gap between estimated and actual effort is because of limited or no inclusion of various estimation factors like people and project related factors, inappropriate use of size metric and cost drivers, ignorance of testing effort, team member’s inability to understand user story size and complexity etc. This paper attempts to bridge the gap of estimated and actual effort by the use of soft computing techniques thus taking the research to advance frontier area in terms of estimation. 


Author(s):  
Sven Feja ◽  
Sören Witt ◽  
Andreas Speck

Business process models (BPM) are widely used for specification of software systems, as the basis for model driven software development. Hence, it is crucial to ensure that these BPMs fulfill the requirements they have to comply with. These requirements may originate from various domains. Many may be considered non-functional requirements. They are affecting privacy, security, as well as compliance or economic aspects. In order to avoid error-prone manual checking, automated checking techniques should be applied wherever possible. This requires expressing requirements in a formal manner. The common textual representations for such formal requirements are not well accepted in the modeling domain, since they are settled on a lower level of abstraction, compared to BPMs. In this chapter, the authors present the Business Application Modeler (BAM), which integrates formal requirement specification and automated checking with process modeling. On the one hand BAM supports different notations for process modeling. On the other hand a graphical notation, called G-CTL, for the formal specification of requirements is provided. G-CTL is based on temporal logic, and statements are expressed on the level of abstraction of the graphical process models. Furthermore BAM provides the ability to define selective views on process models. This allows complex domain specific annotations of processes as well as the assignment of responsibilities regarding functional domains. Moreover, BAM integrates into common requirements engineering processes.


Author(s):  
Lerina Aversano ◽  
Raffaele Esposito ◽  
Teresa Mallardo ◽  
Maria Tortorella

In e-business, addressing the technical issues alone is not enough to drive the evolution of existing legacy applications, but it is necessary to consider problems concerning the strict relationship that exists between the evolution of the legacy system and the evolution of the e-business process. To fulfill this purpose, this chapter proposes a strategy for extracting the requirements for a legacy system evolution from the requirements of the e-business process evolution. The strategy includes a toolkit composed of a set of decision tables and a measurement framework, both referring to the organization, business processes, and legacy software systems. The decision tables allow the identification of the processes to be evolved, the actions to be performed on them and their activities, and the strategies to be adopted for evolving the information systems. The measurement framework aims at achieving a greater understanding of the processes and related problems, taking into account organizational and technological issues.


Author(s):  
Eberhard Stickel ◽  
Jens Hunstock ◽  
Anke Ortmann ◽  
Jan Ortmann

Sign in / Sign up

Export Citation Format

Share Document