# Domain Model Based Design of Business Process Architectures
## 7 Discussion
\begin{table}
\begin{tabular}{p{142.3 pt} p{142.3 pt}} \hline \hline
**Sub-Category** & **Details** \\ \hline \multirow{2}{*}{\begin{tabular}{} \end{tabular} } & Half the participants claimed that the method was objective, complete, and clear, e.g., “it is well-defined algorithm” (P2). In terms of the learning curve, the background of the participant seemed to be relevant, e.g., “I believe that it [the method] calls for [UML] notation knowledge, which is more usual in IT professionals” (P5). \\ \multirow{2}{*}{\begin{tabular}{} \end{tabular} } & In terms of efficiency, a third of the participants perceived the method as adequate for automation, e.g., “All of this can be automated” (P2). A participant claimed a considerable effort might be needed to apply the method to a simple case (P2). \\ \multirow{2}{*}{\begin{tabular}{} \end{tabular} } & A participant perceived the method to be general in terms of “being applicable to any company, to different departments within a company, as well as to the company as a whole” (P1). Other participants raised concerns about the generality of the method related to company size, the proportion of process types, as well as to the IT capabilities within the company. Overall, they believe the method to be adequate for middle-size companies with in-house IT capabilities, and a small proportion of manual processes. \\ \multirow{2}{*}{\begin{tabular}{} \end{tabular} } & A participant pointed out that the method was prone to customization: “it could be adapted to resources of the company, e.g., using alternative notations” (P6). A third of the participants claimed that training would be needed to apply the method. A third of the participants made suggestions to improve operationality, i.e., use of templates (P5) and clear definition of roles for method execution (P6). \\ \multirow{2}{*}{\begin{tabular}{} \end{tabular} } & A participant with a background in ArchiMate pointed out the potential to integrate other elements of the language (i.e., capabilities) lead to a broader architectural view (P2). Another participant discussed the potential of using the model for a diagnosis of the process architecture (P5). Both participants also pointed out how the information of the resulting models could be used to be integrated to define parameters of detailed process models and business rules. \\ \multirow{2}{*}{\
\begin{tabular}{} \end{tabular} } & A third of the participants perceive that the method is suitable to provide a business-level perspective. Most participants perceive the value of the method in bridging the process level with the implementation level, e.g., “this might close the gap between process analysts and software developers” for developing applications that automate the named processes” (P2). \\ \multirow{2}{*}{
\begin{tabular}{} \end{tabular} } & A third of the participants perceived that using the domain model as a starting point to be beneficial. This allowed building the model “from a reality-based artifact” (P4). A third of the participants also found the interdependence between the domain and the architecture model to be a challenge for maintainability. \\ \hline \hline \end{tabular}
\end{table} 
Table 10: Affinity diagram results for category ’Method’. Second, the resulting BPA models of the dBPA method consider composition, specialization, trigger, and resource flow process relations (DD2). Though discussed in the literature of business process relations, see [1; 16; 38], these four types of relations have been rarely simultaneously incorporated in BPA design approaches so far. The integration of the variety of possible process relations allows providing a more realistic picture of the structure of business processes: in terms of model quality, this contributes to improving the model completeness. Additionally, as posited by [64], the extent to which a business process is interconnected to other business processes in a BPA can be used for prioritizing process improvement initiatives in an organization.