The importance of business process modeling in software systems design

Barjis, Joseph

doi:10.1016/j.scico.2008.01.002

Cited by 106 publications

(46 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This leads to use of models that allow all the elements mentioned to interact. Business process modeling role in informatics systems (software) construction has a great importance due to these systems grow in scale and complexity, Barjis (2008). An example of business process modeling is based in theoretical concepts of the DEMO methodology, which is built upon graphical notations using Petri Networks.…”

Section: A Literature Reviewmentioning

confidence: 99%

The Role of the Collaborative Integrated Model (MDSIC) in Agile Software Development - Case Study and Practical Advice

Valdez¹,

Contreras²,

Medina³

et al. 2018

ESJ

View full text Add to dashboard Cite

This research aims to determine the importance of the generation and application of models in the software development area, performing a comparison of existing models and their applicability. One of these models is the collaborative integrated software development model (MDSIC). There are several methodologies and models that help in software development, but most of them have processes in place that make the development more complex instead of agile. The MDSIC proposes five levels of better practices that should be followed in software development projects. Also, the model supports the main areas of knowledge proposed by the Project Management Institute (PMI), thereby generating software in line with the objectives of the organizations. The MDSIC is supported by an internet platform (MDSIC v1.0), which has been developed using Java Server Pages technology and responsive web design. This platform has generated a knowledge base using social business, thus generating an information bank helpful in obtaining the experiences of specialists, proposing best practices in building agile software European Scientific Journal February 2018 /SPECIAL/ edition ISSN: 1857 -7881 (Print) e -ISSN 1857-7431 2 projects. Therefore, this article also aims to show matching indicators and results of implementating MDSIC in software projects, evaluating the needed parameters to generate good quality software, and thus align technology with the goals of the organizations.

show abstract

Section: A Literature Reviewmentioning

confidence: 99%

The Role of the Collaborative Integrated Model (MDSIC) in Agile Software Development - Case Study and Practical Advice

Valdez¹,

Contreras²,

Medina³

et al. 2018

ESJ

View full text Add to dashboard Cite

show abstract

“…• how to apply simulations already on the level of the DEMO CM to support evaluating several implementation alternatives -as has been done already on the more detailed level of processes [3]; • how to support making first order estimations of (business-and ICT-) performance, exploitation costs and risks of implementation alternatives already on the level of the DEMO CM; • how to support making first order estimations of transformation costs and risks of implementation alternatives already on the level of the DEMO CM; • how could the other three DEMO aspect models (PM, SM, AM) contribute to supporting transformations? • what VSM-subsystems do benefit most from applying DEMO?…”

Section: Conclusion and Further Researchmentioning

confidence: 99%

Benefits of Enterprise Ontology in Governing Complex Enterprise Transformations

Land

Dietz

2012

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. Enterprises increasingly execute complex transformations, such as mergers and splits, chain redesign, sharing and sourcing, and the rationalization of products, processes and applications. Its consequences are seldom sufficiently timely and completely discerned, while this is essential for governing such a transformation. Already in a small example we can see why Enterprise Ontology, as defined in DEMO (Design & Engineering Methodology for Organizations) delivers a clear and valuable instrument for transformation governance. Especially DEMO's Construction Model, which is the most abstract ontological aspect model, combines high expressiveness with a high Return On Modeling Effort (ROME).Keywords: Enterprise Transformation, Governance, Enterprise Ontology, DEMO, Enterprise Engineering, ROME. IntroductionHeraclitus' saying "The only constant is change" (500 BC) [13] certainly applies to enterprises 1 . We observe an increasing need to perform better in "profit -peopleplanet", especially in the recent economic crisis. Enterprise activities are shared, insourced, out-sourced, off-shored and back-sourced again. They split up and merge. After giving room for regional autonomy, application portfolio rationalization programs are executed. All these attempt to save costs, improve quality and increase agility, which should ultimately lead to unique advantages in customer intimacy, product leadership and operational excellence [31].The impact of such change-decisions is generally complex and large. Many stakeholders have to be reckoned with, the constraints and opportunities of laws and regulations have to be taken into account, and relevant parties in the chain need to be actively involved. The changes will not only affect products, processes and ICT 2 applications, but also the enterprises' economy and organization. Therefore, such changes call for a well-governed enterprise transformation. To this end, a fundamental 1 We use the term "enterprise" for any goal-oriented cooperative of people. 2 ICT stands for Information and Communication Technology.The original publication is available at www.springerlink.com Enterprise Ontology, as adopted in DEMO 3 [11], reveals the essential, deep structure of an organization. A series of case studies [e.g., 16, 22, 23] of real-life reorganizations, organizational splits, post-merger integration and application portfolio rationalization has been published, in which DEMO is the core modeling method to support decision-making. These studies also report a tremendous ROME (Return On Modeling Effort). We found particularly that DEMO's systematic and reproducible abstractions from the realization and implementation of organizations are beneficial. Taking OMG's EU-Rent Case [20, 18] as an example, we will illustrate the identified benefits and make plausible that applying DEMO provides the required understanding for intellectually manage enterprise transformations, and to do this in 10% of the time commonly used.The remainder of this paper is structured as follows. Section 2 categ...

show abstract

“…With regard to the use of simulation as a preliminary step for the subsequent implementation of a WfMS we are only aware of the work described in [13]. Related to this is [3], in which a business process model is constructed for requirements specification, animation, and validation of a complex software system to be built. Other than that, we are not aware of any approach which uses the same model for specifying, developing, testing, and validating the operational performance of the resultant system.…”

Section: Related Workmentioning

confidence: 99%

Process-Aware Information System Development for the Healthcare Domain - Consistency, Reliability, and Effectiveness

Mans

Aalst

Russell

et al. 2010

Business Process Management Workshops

View full text Add to dashboard Cite

Process-aware information system development for the healthcare domain : consistency, reliability and effectiveness Mans, R.S.; van der Aalst, W.M.P.; Russell, N.C.; Bakker, P.J.M.; Moleman, A.J. Document VersionPublisher's PDF, also known as Version of Record (includes final page, issue and volume numbers)Please check the document version of this publication:• A submitted manuscript is the author's version of the article upon submission and before peer-review. There can be important differences between the submitted version and the official published version of record. People interested in the research are advised to contact the author for the final version of the publication, or visit the DOI to the publisher's website.• The final author version and the galley proof are versions of the publication after peer review.• The final published version features the final layout of the paper including the volume, issue and page numbers. Link to publication General rightsCopyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights.• Users may download and print one copy of any publication from the public portal for the purpose of private study or research.• You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal ? Take down policyIf you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. {p.j.bakker,a.j.moleman}@amc.uva.nl Abstract. Optimal support for complex healthcare processes cannot be provided by a single out-of-the-box Process-Aware Information System and necessitates the construction of customized applications based on these systems. In order to allow for the seamless integration of the new technology into the existing operational processes of a healthcare organization, ensuring the correct operation and reliability of the developed system are of the utmost importance. This paper proposes an approach in which the same model is used for specifying, developing, testing and validating the operational performance of a new system. The benefits of using the same model for different purposes are decreased potential for loss of user requirements and increased confidence in reliability and correct operation of the resultant system before its deployment. This approach has been applied to a schedule-based workflow system developed for the AMC hospital in Amsterdam.

show abstract

The importance of business process modeling in software systems design

Cited by 106 publications

References 19 publications

The Role of the Collaborative Integrated Model (MDSIC) in Agile Software Development - Case Study and Practical Advice

The Role of the Collaborative Integrated Model (MDSIC) in Agile Software Development - Case Study and Practical Advice

Benefits of Enterprise Ontology in Governing Complex Enterprise Transformations

Process-Aware Information System Development for the Healthcare Domain - Consistency, Reliability, and Effectiveness

Contact Info

Product

Resources

About