## 5 Case Study Results
### Results of BPriS Method Utilization with Incremental Approach--Two Related Projects  
This subsection presents usability of the BPriS method for the two related software projects. Figure 13 presents a business process model with separate annotation of project scope for two projects. The project 1 scope is to develop billing software in a hospital, while the project 2 scope is to develop financial reporting software regarding billing in the hospital. From Figure 13 it is obvious that there is clear relationship between results of these two projects--project 2 depends on results of project 1. This dependency is also presented in Table 7. This table is an extended version of mapping table presented in Table 6. The extension is related to the first column regarding the project name. Table 8 presents DA-FOWIL for project 1 and project 2, based on mapping (Table 7) and selected multi-layered software architecture and work items list pattern. The final structure of the software developed within both projects is presented with UML use case diagram (Figure 14) and component diagram (Figure 15). \begin{table}
\begin{tabular}{c c c} \hline  & & **DA-FOWIL** \\ \hline
**PBP** & **SF** & **OR** & **WI** \\ \hline  & 32 & (4) Presentation layer Monthly billing report \\ \hline Monthly billing report print & 33 & (1) Data Layer (CRUD) Monthly billing report \\ \hline  & 34 & (2) Service Layer Monthly billing report \\ \hline  & 35 & (3) Business logic Layer Monthly billing report \\ \hline  & 36 & (4) Presentation layer Monthly billing report \\ \hline \end{tabular}
\end{table} 
Table 6: _Cont._Figure 14: UML use case diagram with software functions of the developed billing and reporting software. \begin{table}
\begin{tabular}{c c c c c c} \hline \hline
**Project** & **PBP** & **PBP Type** & **First Priority SF** & **Second Priority SF** & **Precondition SF** \\ \hline \multirow{4}{*}{Project 1} & \multirow{4}{*}{\
\begin{tabular}{c} Finance \\ (Billing) \\ \end{tabular} } & \multirow{4}{*}{Input} & \multirow{4}{*}{Billing data input} & \multirow{4}{*}{Bill print} & \multirow{4}{*}{Bill print} & \multirow{4}{*}{Bill print} \\  & & & & & Data input from previous \\  & & & & & business process: medical \\ \hline \multirow{4}{*}{Project 2} & \multirow{4}{*}{
\begin{tabular}{c} Quality \\ management \\ and reporting (in financial \\ domain) \\ \end{tabular} } & \multirow{4}{*}{Processing} & \multirow{4}{*}{Monthly billing report processing} & \multirow{4}{*}{Monthly billing report print} & \multirow{4}{*}{Billing data input} \\  & & & & & \\ \end{tabular}
\end{table} 
Table 7: Extended mapping table for the two related projects as a result of the BPriS method in the case study. Figure 13: Business process model with processes in two related software projects with each project’s scope visual boundaries. \begin{table}
\begin{tabular}{c c c c c} \hline  & & & & **DA-FOWIL** \\ \hline
**PROJECT** & **PBP** & **SF** & **OR** & **WI** \\ \hline \multirow{4}{*}{Project 1} & \multirow{4}{*}{Finance (Billing)} & Example of & & \\  & & coding table: & & \\  & & types of documents & & \\  & & data input & & \\ \hline \multirow{4}{*}{Project 1} & \multirow{4}{*}{Finance (Billing)} & \multirow{4}{*}{5-20} & \multirow{4}{*}{1} & \multirow{4}{*}{(1) Data Layer (CRUD) types of documents} \\  & & & & \\  & & data input & & \\ \hline \multirow{4}{*}{Project 1} & \multirow{4}{*}{Finance (Billing)} & \multirow{4}{*}{2} & \multirow{4}{*}{(2) Service Layer types of documents} \\  & & & & \\  & & & & \\ \hline \multirow{4}  
Figure 14 presents UML use case diagram with software functions organized as follows:  
* Coding tables input functions for data regarding hospitals, banks, patients, payment types, patients' employers). These data are needed for billing input and the billing input depends on them, as annotated with stereotype \"use\". * \"Billing input\" with the \"extend\" dependency with \"Bill print\". The \"Bill print\" function is an additional function that could be started after the billing input function is finished.