Requirements analysis process using role-based goal modeling

Requirements analysis is the process of analyzing the requirements of various stakeholders that represent the specification of system behavior. This must be stated precisely in order to proceed to the design phase. It is noted that the current process of requirements analysis is not sufficient for identifying and representing the existence of multiple stakeholders, which could lead to various conflicts and overlapping requirements. Furthermore, the involvement of various stakeholders normally leads to inconsistencies and misinterpretation of requirements. Therefore, this study is conducted to enhance goal modeling representation, namely role-based goal modeling. Role-based goal modeling highlights each stakeholder’s role identification in discovering the intentions and requirements of various stakeholders including the integration of data elements in order to determine the dependency of data when dealing with multiple stakeholders. An Integrated Plantation System was selected as a case study for this research with participation from different stakeholders. Besides that, the Integrated Learning Management System and NIMSAD approaches were used to evaluate the proposed method. From the result, it is found that role-based goal modeling showed improvement in deriving high feasibility (five goals) and high adequacy (one goal) requirements for implementation. The integration of data elements indicates high complexity when multiple stakeholders interact with the same data element. In sum, role-based goal modeling can facilitate the process of analyzing and prioritizing requirements from multiple stakeholders in the early stages of the development process

On scoping stakeholders and artifacts in software process

Stakeholder and artifact are regarded as two important elements in software engineering processes, but they are rarely systematically investigated in software process modeling and simulation. Inspired by the Workshop of Modeling Systems and Software Engineering Processes in 2008 at University of Southern California and our previous studies on integrating stakeholders’ perspectives into software process modeling, we undertook a study on the application of these entities in software engineering, through both a systematic review and a complementary web survey within software process research and practice communities. Our results reveal that the portion of studies on process stakeholders and process artifacts in software engineering is unexpectedly small, and there lacks consistent understanding of process stakeholder roles. By further analysis of stakeholder roles and artifact types based on our results, we define the stakeholder and artifact in the lieu of software process engineering, and differentiate stakeholder and artifact in different application scopes