scispace - formally typeset
Search or ask a question
Topic

Business Process Model and Notation

About: Business Process Model and Notation is a research topic. Over the lifetime, 9038 publications have been published within this topic receiving 190712 citations. The topic is also known as: Business Process Modeling Notation & BPMN.


Papers
More filters
Patent
31 Mar 2005
TL;DR: In this article, the authors present a model processing module that can be used to compare and contrast models of business models, similar to the one presented in this paper, by using a compare operator and a contrast operator.
Abstract: The present invention extends to comparing and contrasting models of business Model processing modules implement formal operators that can be used to manipulate models of business A compare operator can be used to compare similarly typed models of business A contrast operator can be used to contrast differ types of business models A constraint operator can be used to check business models for compliance with constraints A refinement operator can be used to refine business models based on industry (or otherwise more) specific data A compose operator can be used to compose new business models from portions of other business models

43 citations

Book
Paul Allen1
25 Oct 2000
TL;DR: This chapter discusses the role of CRM in e-business process improvement planning, and the importance of business specification standards in the development of component architecture.
Abstract: Table of Contents 1. Introduction. The internet age: An era of change. The challenge of change. Technology soup. The adaptive enterprise. e-Business in brief. e-Commerce versus e-business. The internet spectrum. The challenges of e-business. Components in brief. Component anatomy. Separation of concerns. Toward object maturity: How components help. Business components. Component-based development. A word on modeling. Meeting the challenges of e-business. Top-down: Process and architecture Bottom-up: Integration. Summary. References. 2. Business-IT alignment. Introduction. e-Business process improvement. The concept of e-business process improvement. e-Business process improvement planning. Business process modeling (BPM). The business case for CBD. Identifying business drivers. Assessing architecture. Assessing process. Assessing organization. Balancing strategy and delivery. Summary. References. 3. Component architecture. Introduction. An interface-based approach. The separation of interface and implementation. Interface-based design. Integrating business processes and components. The service-oriented view. The criticality of architecture. Structuring the business process model. Value-added versus commodity components. Architecture and e-business. Dimensions of component architecture. Level of abstraction. Project versus enterprise architectures. Architecture as integration model. Forms of a component. Specification versus implementation. Architecture layering. The main sequence. Summary. References. 4. Process guidelines. Introduction. CBD process framework. A track-based pattern. Deliverables. Integration. Organizing deliverables within the track-based pattern. Reuse checkpoints. CBD process themes. Iterative and incremental integration. Hybrid integration. Gap analysis. Techniques versus deliverables. Technique overview. Summary. References. 5. Migrating to e-business. Introduction. Legacy renewal and EAI. First generation e-business. Legacy renewal. Exploiting legacy systems. Exploiting software packages. Enterprise application integration. Approaches to integration. Architecture for integration. Strategic versus tactical integration. Example: migrating to e-business e-Business process improvement planning. Scoping software requirements. Building an enterprise component architecture. First increment: Rapid delivery. Second increment: e-Business solution. Summary. References. 6. Realizing e-business. Introduction. Welcome back to Harry's. e-Business process improvement planning. Third increment: Personalization Fourth increment improving the customer's experience. Business transformation. Adaptability. Business process integration. The role of CRM. External service integration. Summary. 6.5 References. 7. Provisioning strategies. Introduction. Gap analysis. A world of choice. Revisiting the CBD process. Applying gap analysis. Component provisioning keynotes. The importance of business specification standards. Visualizing provisioning strategy. Component granularity. Routes to component provision. Purchasing components. Outsourcing design and implementation. Wrapping. Adapting. Extending interfaces. Subscribing to virtual services. Outsourcing using ASPs. Summary. References. 8. CBD funding strategies. Introduction. Funding challenges. Cultural challenges. Funding models. Project funding. Corporate funding. Charging for components. Choosing the right funding model. 'Components in advance'. 'Components as you go'. 'Components by opportunity'. Examples of funding and charging. Metrics. Some rules of thumb. Component cost-benefit factors. CBD cost factors. Identifying IT benefit factors. Identifying business benefit factors. Summary. References. 9. e-Business team organization. Introduction. Team roles in context. Basic definitions. The significance of team roles. Traditional teams versus e-business teams. Leadership. Shedding IT's anorak. Further team attributes. Types of e-business teams. e-Business solution-oriented roles. Executive sponsor. Visionary. Ambassador user. Adviser user. Solution designer. Project manager. Team leader. E-challenger. Web master. e-Business integrator. Component-oriented roles. Component sponsor. Business component architect. Technical component architect. Component assessor. Reuse manager. Business component analyst. Business component designer. Technical component designer. Legacy expert. Component librarian. Component certifier. Component tester. Business-IT alignment roles. E-vangelist. Provisioning strategy manager. Business process coordinator. Component funding manager. Organizational models. Brief historical observations. Customization. Using the track-based pattern. Summary. References. APPENDICES. A. Component-oriented technologies. Component and internet standards. Component execution environments. Microsoft's COM+. CORBA. EJB. EJB and the CORBA component model. XML. Physical architecture. Server-based architecture. EAI tools. References. B. Techniques at a glance. Introduction. Business modeling. Business modeling concepts. Business modeling notation. Business modeling quick guide. Business modeling tips and hints. Business type modeling. Business type modeling concepts. Business type modeling notation. Business type modeling quick guide. Business type modeling tips and hints. Use case modeling. Use case modeling concepts. Use case modeling notation. Use case modeling quick guide. Use case modeling tips and hints. Component architecture modeling. Component architecture modeling concepts. Component architecture modeling notation. Component architecture modeling quick guide. Component architecture modeling tips and hints. Interaction modeling. Interaction modeling concepts. Interaction modeling notation. Interaction modeling quick guide. Interaction modeling tips and hints. Interface specification modeling. Interface specification modeling concepts. Interface specification modeling notation. Interface specification modeling quick guide. Interface specification modeling tips and hints. References. Bibliography. Index.

43 citations

Book ChapterDOI
12 Sep 2012
TL;DR: This paper mainly focuses on the part related to the elicitation and definition of data quality requirements and presents an extension of BPMN suitable to include them at a business process modeling level.
Abstract: BPMN is a notation for business process modeling through which it is possible to represent multiple characteristics of the analyzed business processes. However, although in a business process data play a fundamental role, it is still not possible to model data quality issues using BPMN due mainly to the lack of a specific notation. Since data quality is one of the main elements for achieving the business process goals, we aim to develop a comprehensive framework that supports the design of data quality-aware business processes. In this paper, we mainly focus on the part related to the elicitation and definition of data quality requirements and we present an extension of BPMN suitable to include them at a business process modeling level.

43 citations

Book ChapterDOI
11 Nov 2013
TL;DR: This paper provides an approach that extends visual compliance rule languages with the ability to consider data, time, resources, and partner interactions when modeling business process compliance rules.
Abstract: A fundamental challenge for any process-aware information system is to ensure compliance of modeled and executed business processes with imposed compliance rules stemming from guidelines, standards and laws. Such compliance rules usually refer to multiple process perspectives including control flow, time, resources, data, and interactions with business partners. On one hand, compliance rules should be comprehensible for domain experts who must define and apply them. On the other, they should have a precise semantics such that they can be automatically processed. In this context, providing a visual compliance rule language seems promising as it allows hiding formal details and offers an intuitive way of modeling. So far, visual compliance rule languages have focused on the control flow perspective, but lack adequate support for the other perspectives. To remedy this drawback, this paper provides an approach that extends visual compliance rule languages with the ability to consider data, time, resources, and partner interactions when modeling business process compliance rules. Overall, this extension will foster business process compliance support in practice.

43 citations


Network Information
Related Topics (5)
Web service
57.6K papers, 989K citations
88% related
Software development
73.8K papers, 1.4M citations
88% related
Software system
50.7K papers, 935K citations
86% related
Ontology (information science)
57K papers, 869.1K citations
85% related
Software construction
36.2K papers, 743.8K citations
84% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
202383
2022208
2021122
2020164
2019211
2018242