MINERVA: Model drIveN and sErvice oRiented framework for the continuous business process improVement & relAted tools
Methodological Dimension / Business Process Service Oriented Methodology (BPSOM)
This page contains the elements comprising the Business Process Service Oriented Methodology (BPSOM) which is developed as an Eclipse Process Framework Composer (EPF Composer) method plug-in. The first link allows navigating in the BPSOM Web site generated by the EPF Composer, the second link allows downloading the BPSOM method plug-in sources in EPF Composer as a zip file, to be imported into EPF Composer and added to the software base development process used in the organization for service oriented development based on business processes, finally the third link presents experimental material associated with BPSOM.
Overview
The Business Process Service Oriented Methodology (BPSOM) extends a previous defined methodology which defines a core set of disciplines: Business Modeling, Design and Implementation, activities, deliverables and roles to be added to the software development process used in the organization. Conceptually the methodology can be added as a plug-in to the base software development process used in the organization, adding the new elements to guide the service oriented development from business processes. To make this integration effective, we have developed it with the Software Process Engineering Metamodel (SPEM) (OMG, 200X) as an Eclipse Process Framework Composer (EPF Composer) (Eclipse, 200X) method plug-in to be integrated in the organization's existing software development process. In Fig. 1 the integration of BPSOM with the existing base software development process is shown.
Fig. 1 Business Process Service Oriented Methodology (BPSOM) as BPMN business process
In Fig. 2 the defined core set of disciplines: Business Modeling, Design and Implementation, its activities and execution flow are shown as a BPMN2 (OMG,2011) process model. It also shows how the methodology defines several related activities to develop service oriented systems from business processes, starting with business process modeling where the use of process patterns (van der Aalst, 2003) is recommended. It can also be noticed how the flow of BPSOM activities is integrated with the existing Requirements Discipline from the base software development process used.
Fig. 2 Business Process Service Oriented Methodology (BPSOM) as BPMN business process
BPSOM also defines input and output deliverables (i.e. Services document) and responsible and participant roles for the defined activities, as well as a detailed description of objectives and tasks to be carried out when performing the activity, which are summarized in Table 1.
Table 1. Elements defined in the methodology related to the core activities
Activity |
Objective |
Inputs/Outputs |
Roles |
Assess the target Organization (MN1) |
Obtain the organization map, its processes and technologies |
I:Meetings with clients/ O:Evaluation of the Target Organization Document |
Business Analyst, Architect, Analyst |
Identify Business Processes (MN2) |
Model business processes, flow, involved roles, associated functionalities |
I: Evaluation of the Target Organization Document, minutes of meetings with clients, O:BP Document |
Business Analyst, Architect, Analyst |
Identify and categorize services (D1) |
Define and classify the services to carry out the business processes and functionalities |
I: SW Architecture, BP, Requirements and Services Documents, O: Services Document,SWArchitecture |
Architect, Analyst, Developer |
Specify services (D2)
|
Define contract of services, operations, parameters, etc. |
I/O:Services Document
|
Architect, Analyst |
Investigate existing services (D3) |
Reuse services, components, implemented functionalities |
I/O: Services Document and Catalogue |
Architect, Analyst |
Assign services to components (D4) |
Define service implementation |
I: Services and Design Documents, O: Services and Implementation Docs. |
Architect, Developer |
Define services interaction (D5) |
Define sequences of invocation of services to carry out the business processes |
I: BP, Services and Requirements Documents, O:Services and Implementation Docs. |
Architect, Analyst, Developer |
Implement services (I1) |
Build the services as they were designed |
I: Services, Design and Implementation Docs., O: Implemented service |
Developer |
Key Publications:
Author: Andrea Delgado 2010