## 6 Discussion
### Usability, Limitations and Future Development of the BPriS Method  
The proposed BPriS method could be utilized in different contexts:  
* The case study in this manuscript demonstrated applicability to a small number of business processes, but the same procedure could be performed with any business process model complexity. In dealing with complex business process models, automation of BPriS method utilization could be very beneficial. * The BPriS method proposes business process categorization according to [32], but it could be applied with any workflow pattern. * Software architectures and development technologies change over time. The mapping table could be used to discuss different implementation alternatives (within the same or with different technologies) for the same software functions and for the support to the same primitive business processes. * Information system solutions sometimes are integrated from software components created by using different technologies and architectures. Mapping table could be used to enable integration of diversity of software implementation solutions designs. * Better insight into business processes and requirements are usually obtained dynamically during a project. Business processes change over time, due to changes in legislation or business strategy enforced by the market. Mapping table enables flexibility in software design support to different business processes. It is also a useful tool to record and monitor changes in business processes and software design support. * Mapping table enables integration of results of software design from different software projects that are related in the broader scope of project management in the program management (long term development with multiple projects). * Mapping table and DA-FOWIL enable organization of software development with multiple teams working on the same software solution. In software companies, teams are organized according to their specialties for particular software architecture modules--front end (presentation layer), back end (business logic layer), data layer, services layer etc....Mapping table and DA-FOWIL enables integrated and filtered (by particular work items list types--according to software architecture elements) presentation of software functions and work items. * Limitations of the presented BPriS method could be related to:
* Business process model is created outside of BPriS method utilization. It could be created with diversity of workflow patterns. It is expected that the business process model is complete, correct and not ambiguous. * Granulation of the software functional pattern and work items pattern--the proposed BPriS method was presented as a general framework with examples of software functional patterns and work items list patterns (based on software architectures). More precise items could be derived from software development practice and available development technologies. In this manuscript, it was not necessary to present work items list patterns and the case study results with better granularity (more details about particular activities in creating elements of this solution), since software development professionals know what to do (what are the subtasks) when a particular task (work item) is presented with general level of details. For example, when the task is to make a data layer with CRUD operations for a \"Types of documents\" data table, it is obvious that there should be classes that have methods supporting each CRUD operation (Create, Read, Update, Delete) in collaboration with the database. * Software functional pattern and work items list pattern depend on implementation technology that is available to software development team (according to technology availability and complexity, software team knowledge, experience and available resources for technology implementation).