Yousra Odeh
ABSTRACT
Requirements engineering phase is the cornerstone in engineering any software system. During this phase, one of its biggest and common challenges is to bridge the communication gap between business and IT people in order to increase customer satisfaction regarding resultant approved software specification. One of the standardized business analysis and modelling techniques is BPMN. However, the requirements engineering community is poor in publishing a guide for using standardized tools during engineering software requirements. This research aims at analyzing the use of BPMN during requirements engineering process and how it will assist the requirements engineers in overcoming common challenges during their duties. The analysis in this research is based on analyzing the usage of BPMN during engineering requirements within three real-life projects. Employing the BPMN while engineering requirements has demonstrated a creation of common communication channel between participants, who are from different backgrounds, and increased satisfaction of customers and requirements engineers regarding resultant software specification.
- Aburub, F., Odeh, M. and Beeson, I. (2007) Modeling Non-Functional Requirements for Business Process. J. Information and Software Technology. 49(11-12) (November 2007), 1162--1171. Google Scholar
Digital Library
- Chung, L., Nixon, B. and Mylopoulos, J. (2000) Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers., London, UK.Google Scholar
- Martino, B., Esposito, A., Nacchia, S. and Maisto, S. 2015. Semantic annotation of BPMN: current approaches and new methodologies. In Proceedings of the 17th International Conference on Information Integration and Web-based Applications & Services (Brussels, Belgium --- December 11-13, 2015). iiWAS' 2015. ACM, New York, NY, 204--209. Google ScholarDigital Library
- Odeh, Y. 2015. GQ-BPAOntoSOA: A goal- and object-based semantic framework for deriving software services from an organisations goals and riva business process architecture. Doctoral Thesis. URL:https://eprints.uwe.ac.uk/secure/25286., University of the West of England.Google Scholar
- Sommerville, I. 2016. Software Engineering. Pearson., Essex, UK. Google ScholarDigital Library
- White, S. and Miers, D. 2014. The complete business process handbook: Body of knowledge from process modeling to BPM Volume I:1. Morgan Kaufmann., Waltham, USA. Google ScholarDigital Library
- Wiegers, K. and Beatty, J. 2013. Software Requirements. Microsoft Press., Redmond, Washington. Google ScholarDigital Library
- Wieringa, R. 2005. Requirements Researchers: are we really doing research?. J. Requirements Engineering. 10, 4 (Aug. 2005), 304--306. Google ScholarDigital Library
- Yousef, R., Odeh, M., Coward, D. and Sharieh. 2009. BPAOntoSOA: A generic framework to derive software service oriented models from business process architectures. In Second International Conference on the Applications of Digital Information and Web Technologies (London, UK, August 4-6, 2009). ICADIWT'09. IEEE, USA, 50--55.Google ScholarCross Ref
Index Terms
- BPMN in Engineering Software Requirements: An Introductory Brief Guide
Recommendations
How to elicit and specify software requirements from BPMN diagrams?
SBSI '18: Proceedings of the XIV Brazilian Symposium on Information SystemsDifferent techniques for eliciting requirements from business process models have arisen due to the importance of software requirements to be aligned with the business in order to achieve organizational goals. Although there are several ways to ...
A Requirements Engineering Methodology for Real-Time Processing Requirements
This paper describes a methodology for the generation of software requirements for large, real-time unmanned weapons systems. It describes what needs to be done, how to evaluate the intermediate products, and how to use automated aids to improve the ...
Secure Tropos framework for software product lines requirements engineering
Security and requirements engineering are two of the most important factors of success in the development of a software product line (SPL). Goal-driven security requirements engineering approaches, such as Secure Tropos, have been proposed as a suitable ...
Comments