Executive Summary: As organizations are moving to an abstract level of software development, IT managers generally find their software development tool base difficult to change. Often, there are multiple, purpose-specific tools, which are not integrated with each other well. Hence, substituting tools is not an easy venture and usually results in retraining of software development staff.
The Business Process Management Ontology (BPMO): Today’s business integration landscape suffers from many deficiencies. For example, business process execution languages only standardize the technical aspects of process integration. They ignore the business semantics, such as which data elements are required in a purchase order. Similarly, there is no answer to the question what constitutes a binding business transaction. The list could go on and on. As a result, semantic differences remain the primary roadblock to smooth integration. Ontologies are a way to solve these issues. Click here to read more…
Related Case Studies:
- Case Study for Applying Business Process Management Systems Abstract: Business Process Management Systems aim to support the Business...
- A Case Study on Business Process Modelling and Execution Overview: Business Process Management (BPM) has recently gained prominence and...
- A Case Study for Understanding Business Process Modeling Business process modeling is a discipline in and of itself....
- A Case Study on Business Process Management A medical association creates a manageable roadmap for the future...
- Learning Business Process Models: A case study Abstract: Learning how to improve business processes is an evolutionary...