Analyze Requirements for PAIS with Best Practice
International Journal of Hybrid Information Technology
Traditional requirements analysis is focused on capture functions of the system that are being built from scratch. As the size and complexity of process-aware information system continues to grow, the use of COTS (Commercial off-the-shelf) software packages is being viewed as a solution. Use of COTS packages accelerates the implementation process to some extent, however, it puts enterprises into a dilemma: whether to adapt asis business processes or to customize software packages. In order to
... lp the enterprises get out of the dilemma, a methodology is proposed to automatically elicit software requirement using best practice as domain knowledge. The methodology involves three phases: business modeling, gap detecting and gap bridging. Firstly, VPML is employed to describe as-is business process, Secondly, semantics computing technology is employed to analyze the gap between enterprise needs and COTS software capacity. At last, Goal Reasoning Technology is employed to encourage enterprise users and software vendors take participate in decision making process together. Then the business-driven approach is proposed  . It emphasizes on the unique characteristic of business processes of the organization. The business-driven approach is more flexible than the solution-driven one. However it often leads to some unnecessary customizations for software packages, therefore it makes implementation more timeconsuming and expansive. Apparently, it is an important issue to balance between customization and standardization in procuring requirements for PAIS. The standardization of business process reduces the development cost; however it cannot cover all aspects of business processes. On the other hand, the customization of software is more flexible. However it is too expensive and time-consuming. In this study, a holistic methodology is proposed to elicit software requirements for PAIS implementation. The logic behind it is that business and software adapt for each other. That is, the user clearly represents business processes of their enterprise, and reference model are used to represent the business processes supported by PAIS. Then a meet-in-middle method is employed to elicit software requirements for PAIS. The structure of this paper is organized as follows. In the next section, the framework of methodology is proposed to elicit requirements for PAIS with reference models. Section 3 gives a detail presentation of the method to make decision in requirements elicitation. Section 4 is the conclusion.