## 3 Related Work
### Business Process Mapping to Software Design  
[PERSON] et al. [41] systematically analyze the relationship between business requirements, processes and software systems that support them. [PERSON] et al. [42] consider business process model from goals, context, structure and information technology application aspects. Recently, the use of IT solutions to support business processes is monitored by using process mining tools and algorithms [20]. To enable automation, business process models are transformed to particular BPm notations, such as XPDL [43], event-driven process chains [31], derivation of IDEF0 to BPEL4 WS [44], communicative event diagram to state machines [45] and BPEL to BPMN [46]. To support appropriate software design and development, business process models are transformed into other types of models, such as data models [47], class diagrams [48] and use cases [49]. Business process models could be the basis for software user interface [50] or user interface flow model derivation [51]. BPM can be used in combination with other types of models (use cases) to enable software development and workflow automation [52]. [PERSON] [5] compare Data Flow Diagrams (DFD) and UML use case diagrams to represent data flow within information systems development. [PERSON] and [PERSON] [53] proposed a method for deriving user requirements for processes automation from BPM. Similarly, a business process model could be derived from early requirements analysis and created to adjust to information technology support, such as service-oriented software implementation [54]. Further efforts were made towards automated derivation of software services and web services from business process model repositories [55] with the use of semantic technology [56; 57], such as in the case of Fun  
Figure 2: (**a**) Abstract Data Flow Diagram with the context diagram and the first level of decomposition; (**b**) Abstract business process diagram (similar to BPMN). damental Business Process Modeling Language (FBPML) mapping to the Web Services Ontology (OWL-S) [58]. Since there are different BPM notations, a meta-model has been developed in [59], to represent a basis for derivation of web services that support grid-based service-oriented architectures. Business process and activities mapping to software solutions could be considered at the architecture level [60], with business domain aligned to software components [61; 62]. [PERSON] et al. [27] propose a framework for mapping enterprise process models into ERP software system layers: (1) Front-end layer (user-oriented graphical representation), (2) Back-end layer (formal representation of business processes automation support, with Petri nets). Trends in business process mapping to software design could be presented as directions toward mapping business architecture to a component-based software architecture [63] and service-oriented computing with web services [64]. Orchestration and choreography could be utilized by using Business Process Execution Language for Web Services (BPEL4 WS) [65]. [PERSON] et al. [27] consider aspects of process improvements with business process reengineering [66] and technology advancements. Having business processes variability [67] considered, [PERSON] et al. [42] explore business process flexibility and context awareness. [PERSON] et al. [68] elaborate business process flexibility in the context of software systems perspective, while [PERSON] and [PERSON] [61] consider business processes evolution impact to component-based software development. Changes in business processes are particularly frequent in the business rules domain, so relating the evolving business rules to software design to keep the software useful has been addressed in [69]. Contemporary solutions in relating business processes to software functions are directed towards moving from Business Process Models to Process-oriented software systems [70] and from Process Modeling to Workflow Automation Infrastructure [71].