We compare the success of university students in interpreting business process descriptions, for an established graphical notation (BPMN) and for an alternative textual notation (based on written use-cases).
However, traditional workflow definition languages, such as extended XPDL and service-oriented BPEL4WS, have become insufficient to specify business process semantics, especially the descriptions of inputs, outputs, preconditions and effects.
The overall context is represented by the description of the overarching business process, scenarios, scenes, and steps.
To keep records of their business process architecture enterprises use informal and as well formal process descriptions.
The process description languages, which are used in business, may be useful in logistics processes.
In this paper, we focus on business process support analysis using information derived from enterprise architecture description.
These enhanced descriptions focus on organizational-specific information, which makes it easier for business process experts to understand the capabilities of services in their organizational context.
WS allows the implementation of SOA recommendations, it supports Web Services Description Language WSDLL) as a description language, communication APIs like Simple Object Access Protocol (SOAP and Representational State TransferRESTEST), and coordination of services through Business Process Execution Language (BPEL) [13].
In our work, we propose an automated solution that relies on Description Logics and automated reasoners for validating mappings that describe the realization of goals by activities in business process models.
Written Process Description.
6.11.2 Process Description.
