Abstract
Process-oriented requirements engineering approaches are often required to deal with the effective adaptation of existing processes in order to easily introduce new or updated requirements. Such approaches are based on the adoption of widely used notations, such as the one introduced by the Business Process Model and Notation (BPMN) standard. However, BPMN models do not convey enough information on the involved entities and how they interact with process activities, thus leading to ambiguities, as well as to incomplete and inconsistent requirements definitions. This paper proposes an approach that allows stakeholders and software analysts to easily merge and integrate behavioral and data properties in a BPMN model, so as to fully exploit the potential of BPMN without incurring into the aforementioned limitation. The proposed approach introduces a lightweight BPMN extension that specifically addresses the annotation of data properties in terms of constraints, i.e., pre- and post-conditions that the different process activities must satisfy. The visual representation of the annotated model conveys all the information required both by stakeholders, to understand and validate requirements, and by software analysts and developers, to easily map these updates to the corresponding software implementation. The presented approach is illustrated by use of two running examples, which have also been used to carry out a preliminary validation activity.
Highlights
Requirements engineering is the essential software engineering process for eliciting, specifying, verifying and maintaining the requirements of a software product throughout its lifecycle [1]
Among the various issues that may lead to the introduction of faulty requirements in terms of, e.g., ambiguity, incompleteness and inconsistency, the heterogeneity of the different stakeholders and their relevant views is significant. This paper addresses such an issue by focusing on the extension of a business process notation, namely, Business Process Model and Notation (BPMN) (Business Process Management and Notation) [4], which has proven to be easy to understand for the various stakeholders involved in a software requirements engineering effort, minimizing the risks of misunderstandings and omissions
The use of notations that provide an effective support to both business process management and requirements engineering approaches allows business and software analysts to bridge the gap between them and take advantage of both approaches [8]
Summary
Requirements engineering is the essential software engineering process for eliciting, specifying, verifying and maintaining the requirements of a software product throughout its lifecycle [1]. This paper’s proposal is effective in application domains that are characterized by a significant variability in terms of stakeholder needs and constraints [12], such as in the healthcare domain, where business processes may require frequent updates in order to address new recommendations given by public authorities (see, e.g., [13]). In these domains, the use of requirements engineering based on business processes requires software analysts to quickly react to process changes that have an impact in terms of new or updated requirements.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.