## 6 Discussion
### Contribution Compared to Existing Solutions
\begin{table}
\begin{tabular}{c c c} \hline \hline
**ASPECT** & **Ref.** & **BPriS Method and Artifacts** \\ \hline \multirow{8}{*}{Software functional patterns} & Conceptual, design and programming patterns [86], structural patterns [91] of classes in object-oriented programming [89] & \\  & Software usability patterns [99] as commonly used software functions & Software functional patterns as typical functions for some type of software, \\  & Functional patterns for software product lines [104; 105] & supported by a particular technology (similar approach to [100; 101; 102]) \\  & Software functional patterns to support development of different types (regarding implementation technology) of & \\  & software [100; 101; 102; 103] & \\ \hline \multirow{8}{*}{Agile software development planning and automation} & Software development process model, agile continuous planning [106], delivery and integration [107] & Development planning based on business process model, software functional patterns and work items list patterns \\  & & Integration [107] & Table for mapping primitive business processes processes to prioritized sets of software functions \\  & & Automation and DevOps practice [121; 122] & Work items list patterns based on software architectures \\ \hline \multirow{8}{*}{Agile software release planning and prioritization} & Requirements-based prioritization of work items list [125] & \\  & Agile projects prioritization of software requirements [127] & Work items list prioritized according to business processes classification and segmentation, software functional patterns and prioritization in the mapping table, work items list patterns and software architecture-based prioritization with bottom-up approach \\ \hline \multirow{8}{*}{Workflow patterns} & Patterns in organization of processes [33], useful for workflow management systems Action patterns in business process models that appear together and could be assigned to objects in software implementation [96] & BPriS method do not propose workflow patterns, since it is out of scope of this method (BPM is an input to BPriS method), workflow pattern from [32] is used for business process level of prioritization—(1) core, (2) supporting, (3) management \\ \hline \multirow{8}{*}{Software development items list patterns} & Extraction of software development workflow items from past projects and prediction of new workflow items [144] & Prioritization of work items list is based on: (1) business processes categorization and software development prioritization according to business process categories, (2) prioritization of software functions assigned to each process (first priority, second priority, preconditions), (3) bottom-up approach to software architecture elements that are included in the work items list pattern. \\ \hline \hline \end{tabular}
\end{table} 
Table 9: _Cont._Business process mapping to software design--existing approaches do not address mapping between business process model primitive processes to software functions and do not enable multiple functional designs related to diversity of possible solutions within the same or different technologies. The BPriS method enables comparison and integration of different functional design solutions. * Software semantic coupling--in previous research, coupling is related to structural and behavioral dependencies between classes in object-oriented programming, while semantics is related to texts in source code (identifiers). These approaches do not consider software functionality as a basis for semantic relationships. The BPriS method proposes semantic relationship between (1) software functions that support the same business process; (2) relationships between software functions of neighbor business processes. * Software functional patterns--are recognized as needed in the software industry, to be abstracted as commonly used in software, particularly to support different types of software.