pab's picture

In the initial article of the EBPM blog series Thomas Stoesser explained, that Model-to-Execute (M2E) resembles a methodology focused on process automation that is driven by requirements and definitions coming from process transformation efforts.

But how will these business requirements be communicated to IT? To answer this question I’d like to categorize requirements in the context of M2E into 2 different groups:

  1. Requirements for the process itself
  2. Requirements for software services needed to execute the process

In this blog post I’d like to specifically address requirements for software services.

ARIS provides a service browser which is able to access CentraSite (CS). With the help of this service browser existing software services and service operations can be imported into ARIS and connected with appropriate business services. In fact a software service represents the technical realization of a business service. Once imported into ARIS, all software services will be synchronized automatically between ARIS and CentraSite.

When designing a business process, business services are used to document the service support for the individual process step (you will learn more about that approach in the next EBPM blog post which is addressing business and requirements modeling for process automation). It is either possible to use the existing business services which are already connected to CS-managed software services or to create new business services. Actually the new created artifacts are the starting point to request the development of a new software service.

The integration between ARIS and CentraSite provides a governance process for service development which allows the different stakeholders from business and IT to work within a common workflow. The governance process includes the creation of a requirements document based on the description of the business service in ARIS. The content of the requirements document is configurable to the needs of the requester and service developer. With this, the business context of the request for service development is communicated crisp and clearly to the developer respective IT.

The service synchronization and connection between ARIS and CentraSite is also the foundation for SOA Portfolio Management. Read more about that topic in my blog post: “SOA Portfolio Management with ARIS and CentraSite  – Demonstrate the Value of IT to the Business”.

Service synchronization between ARIS and CentraSite:

Business can request service development based on Business Process Analysis:

Tags: ARIS