J-PRiM: A Java Tool for a Process Reengineering i* Methodology

Abstract

Steps TS 1 Analysis of the Current Process 1.1. Analysis of the Current Process F 1.2. Documenting the Current Process F 2 Construction of the i* Model 2.1. Actor Identification and Modelling F 2.2. Building the Operational i* Model A 2.3. Building the Intentional i* Model G 2.4. Checking the Resulting i* Model A 3 Generation of Alternatives 3.1. Reengineering the current System G 3.2. Adding/Removing System Actors F 3.3. Reallocating Responsibilities G/A 3.4. Checking Consistency between Alternatives A 4 Evaluation of Alternatives 4.1. Choosing Suitable Properties F 4.2. Defining Property Metrics F 4.3. Evaluating Alternative Models A 4.4. Evaluation Trade-off Analysis G 5 Specification of the New System N/S Table 1. PRiM phases and steps, showing how each step is supported by J-PRiM

ReeF: Defining a Customizable Reengineering Framework

“…This includes the definition of more method chunks and method artefacts into the method base and how to document and classify them in order to facilitate their customization. We are mainly interested in the use of i* and the method chunks proposed in PRiM as a basis for this process and we want to adapt J-PRiM [15] in order to provide tool support for the whole process.…”

“…The PRiM method is based on an exhaustive state-of-the-art on business process reengineering methods [12] complemented with well established requirements engineering techniques such as KAOS [8]. The use of these techniques provides an additional strength to all the phases defined on the method, and they have facilitated the development of J-PRiM [15], a tool that supports the application of the method. These are arguments that support using PRiM as starting point for formulating the framework.…”

Towards interoperability of i* models using iStarML

“…An example is the interconnection of the REDEPEND tool (developed by City University) [47] and the HiME tool (developed by Technical University of Catalonia) [48] both of them compliant to the seminal i* definition by Eric Yu. The main purpose here is to share models developed in each site.…”

“…Interconnection of two i*-related tools that have different purposes. A simple example would come again considering REDEPEND and the J-PRiM tool [47] not just as modelling tools but also their own capabilities. For instance, among the facilities of REDEPEND we find the ability of generating a system requirements document in textual form from an i* model.…”

“…In this case, we have a worst case representing, at least, a 42.9% of declared first adopters. If we analyze this proportion, under the Rogers's innovation adoption theory [47], we can see that first adopters normally became 13.5% and the "early majority", after first adoptions, became 34% of the population. Therefore, although this 42.9% of declared adopters does not seems to be very high with respect to the whole i* community, on the light of Rogers's theory it seems one of the most optimistic findings of this survey.…”