Open AccessA Mini Comparative Study of Requirements Modelling Diagrams towards Swimlane: Evidence of Enterprise Resource Planning System
Author(s) -
Noor Widasuria Abu Bakar,
Shahrulniza Musa,
Abdul Hadi Mohamad
Publication year - 2020
Publication title -
journal of physics. conference series
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.21
H-Index - 85
eISSN - 1742-6596
pISSN - 1742-6588
DOI - 10.1088/1742-6596/1529/5/052054
Subject(s) - use case diagram , computer science , communication diagram , class diagram , requirements engineering , activity diagram , system context diagram , software engineering , requirements analysis , systems engineering , diagram , unified modeling language , database , engineering , programming language , software
Model-based requirements engineering (MBRE) is an approach that empowers requirements engineers with adequate models to perform requirements engineering (RE) activities. This approach is increasingly becoming an essential part of system engineering projects as it reduces development time, enhances analysis capability and increases the potential for reuse. Use case diagram, activity diagram, business process management and notation diagram (BPMN) and swimlane diagram are among the diagram used in representing the requirements. However, the swimlane diagram has received little attention in the literature and lack of empirical support, particularly in the requirements engineering field. In this study, a multi-criteria comparative work is performed where three other diagrams are identified and examined against the swimlane diagram. Walkthrough sessions are conducted using enterprise application documents with real users to validate the model-based requirements exemplified using the swimlane diagram. These activities are carried out to highlight the efficacy of the swimlane diagram in representing requirements in the RE field. The results confirmed that the swimlane diagram outperforms NL in overall completion time for the requirement validation process. Furthermore, it gives users a better understanding as they did not need to read textual requirements which are typically ambiguous, confusing, and lengthy.