2019 | OriginalPaper | Chapter
Hint
Swipe to navigate through the chapters of this book
Published in:
Software Engineering for Resilient Systems
Requirement change management (RCM) for global software development (GSD), facilitated by the cloud platform, faces communication, coordination and control issues especially when there is no effective information and knowledge-sharing mechanisms. This paper describes a reasonably effective requirement change management approach for cloud-based GSD.
Objective: In this regard, we contribute a Reactive Middleware which facilitates a set of guidelines defined to manage change and traceability.
Methods: This Reactive Middleware provides services for user management, requirement management, change management, and traceability of cloud-based GSD projects. We present (1) a process model for change management and traceability (CM-T) for cloud-based GSD, and then (2) detail our management approach for system engineering processes as part of the presented GSD guidelines.
Results: To ensure that the defined CM-T process model complies with the CMMI Level 2 (Baseline) Capability, the process model is validated using an expert panel review process where a total average, 85.58% of the experts support the maturity of the process model. Also, we demonstrate the continual tight linkage of stakeholders’ requirements and system engineering processes towards change management and traceability, with an Airlock Control System case study.
Please log in to get access to this content
To get access to this content you need the following product:
Advertisement
Table 7.
Description of artefacts in the shared artefacts repository
SDLC phases
|
Artefacts description
|
---|---|
Requirements
|
System requirements documents are obtained from tools such as ProR
|
Specification
|
System model specifications as artefacts contain elements such as invariants, guards, actions, etc. Such elements are also extracted as dependent artefacts
|
Implementation
|
Implementable source codes of model specifications are generated with appropriate tools such as EB2ALL. It supports automatic code generation from Event-B to C, C++, Java and C#. Another tool example is EventB2Dafny. This tool extends the Boogie and Dafny tools, and allows the use of Dafny static analysis machinery based on design-by-contract principles. This yields artefacts in the form of executable input code for Boogie and Dafny tools
|
Documentation
|
Documentation artefacts are in the form of: (1) traceability logs, (2) incident reports, and (3) others such as designs, test plans, execution results, etc.
|
Fig. 6.
PMBOK
\(^{{\textregistered }}\) process group for system engineering life-cycle
Table 8.
Global software development management guidelines
Guidelines steps ID
|
Guidelines
|
---|---|
GS1
|
System development teams should appoint team leaders
|
GS2
|
These team leaders will constitute the GSD change managers
|
GS3
|
System requirements should be classified based on identified dependability quality attributes (i.e. safety, reliability, robustness, etc.), and are then prioritised relative to their importance to the system stakeholders
|
GS4
|
Team leaders must assign roles to all team members with the prioritised requirements in mind, and manage the development process with the adapted PMBOK guide
|
GS5
|
All other change agents especially the system engineering tools should be assigned a default privilege of review
|
GS6
|
All system artefacts should be saved in a shared artefacts repository
|
GS7
|
The privileges (i.e. none, view, modify, review, own) of system stakeholders or change agents will determine the access privileges to system artefacts
|
GS8
|
Change agents must subscribe to relevant artefacts after they are created, in order to receive notifications when they are changed
|
GS9
|
All related artefacts must be linked together to facilitate traceability
|
GS10
|
Changes made to any system artefacts must be logged
|
GS11
|
When changes affect the high priority set of requirements, appropriate local team leader must lead the change request review process (i.e. involving the CM-T model) of the GSD change managers
|
GS12
|
On the other hand, conflicts arising from changes to low priority set of requirements are resolved locally, lead by the local team leader
|
GS13
|
Changes in system artefacts should be traceable to manage its impact on related/linked requirements or artefacts
|
×
Fig. 7.
Candidate processes reflecting a CMMI level 2 (baseline) capability
Fig. 8.
Change management and traceability process model
×
×
1.
go back to reference Adjepon-Yamoah, D., Romanovsky, A., Iliasov, A.: A reactive architecture for cloud-based system engineering. In: Proceedings of the 2015 International Conference on Software and System Process, ICSSP 2015, pp. 77–81. ACM, New York (2015). https://doi.org/10.1145/2785592.2785611 Adjepon-Yamoah, D., Romanovsky, A., Iliasov, A.: A reactive architecture for cloud-based system engineering. In: Proceedings of the 2015 International Conference on Software and System Process, ICSSP 2015, pp. 77–81. ACM, New York (2015).
https://doi.org/10.1145/2785592.2785611
2.
go back to reference Adjepon-Yamoah, D.E.: Towards dependable change management and traceability for global software development. arXiv preprint arXiv:1608.05981 (2016) Adjepon-Yamoah, D.E.: Towards dependable change management and traceability for global software development. arXiv preprint
arXiv:1608.05981 (2016)
3.
go back to reference Akbar, M.A., et al.: Success factors influencing requirements change management process in global software development. J. Comput. Lang. 51, 112–130 (2019). https://doi.org/10.1016/j.cola.2018.12.005. http://www.sciencedirect.com/science/article/pii/S1045926X18301411 CrossRef Akbar, M.A., et al.: Success factors influencing requirements change management process in global software development. J. Comput. Lang.
51, 112–130 (2019).
https://doi.org/10.1016/j.cola.2018.12.005.
http://www.sciencedirect.com/science/article/pii/S1045926X18301411
CrossRef
4.
go back to reference Ali, N., Lai, R.: A method of requirements change management for global software development. Inf. Softw. Technol. 70, 49–67 (2016). https://doi.org/10.1016/j.infsof.2015.09.005. http://www.sciencedirect.com/science/article/pii/S0950584915001640 CrossRef Ali, N., Lai, R.: A method of requirements change management for global software development. Inf. Softw. Technol.
70, 49–67 (2016).
https://doi.org/10.1016/j.infsof.2015.09.005.
http://www.sciencedirect.com/science/article/pii/S0950584915001640
CrossRef
5.
go back to reference Ali, S., Iqbal, N., Hafeez, Y.: Towards requirement change management for global software development using case base reasoning. Mehran Univ. Res. J. Eng. Technol. 37(3), 639–652 (2018). https://doi.org/10.22581/muet1982.1803.17. http://publications.muet.edu.pk/index.php/muetrj/article/view/511 CrossRef Ali, S., Iqbal, N., Hafeez, Y.: Towards requirement change management for global software development using case base reasoning. Mehran Univ. Res. J. Eng. Technol.
37(3), 639–652 (2018).
https://doi.org/10.22581/muet1982.1803.17.
http://publications.muet.edu.pk/index.php/muetrj/article/view/511
CrossRef
6.
go back to reference Bibi, S., et al.: Requirement change management in global software environment using cloud computing. J. Softw. Eng. Appl. 7(8), 694–699 (2014) CrossRef Bibi, S., et al.: Requirement change management in global software environment using cloud computing. J. Softw. Eng. Appl.
7(8), 694–699 (2014)
CrossRef
7.
go back to reference Capability Maturity Model Integration Product Team: CMMI for Development, Version 1.3. Technical report CMU/SEI-2010-TR-033, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA (2010). http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=9661 Capability Maturity Model Integration Product Team: CMMI for Development, Version 1.3. Technical report CMU/SEI-2010-TR-033, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA (2010).
http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=9661
8.
go back to reference Cocco, L., Mannaro, K., Concas, G.: A model for global software development with cloud platforms. In: 38th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA), Cesme, Izmir, Turkey, pp. 446–452, September 2012. https://doi.org/10.1109/SEAA.2012.67 Cocco, L., Mannaro, K., Concas, G.: A model for global software development with cloud platforms. In: 38th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA), Cesme, Izmir, Turkey, pp. 446–452, September 2012.
https://doi.org/10.1109/SEAA.2012.67
9.
go back to reference Damian, D., Moitra, D.: Guest editors’ introduction: global software development: how far have we come? IEEE Softw. 23(5), 17–19 (2006). https://doi.org/10.1109/MS.2006.126 CrossRef Damian, D., Moitra, D.: Guest editors’ introduction: global software development: how far have we come? IEEE Softw.
23(5), 17–19 (2006).
https://doi.org/10.1109/MS.2006.126
CrossRef
10.
go back to reference Herbsleb, J., Moitra, D.: Global software development. IEEE Softw. 18(2), 16–20 (2001). https://doi.org/10.1109/52.914732 CrossRef Herbsleb, J., Moitra, D.: Global software development. IEEE Softw.
18(2), 16–20 (2001).
https://doi.org/10.1109/52.914732
CrossRef
11.
go back to reference Iliasov, A., et al.: Supporting reuse in event B development: modularisation approach. In: Frappier, M., Glässer, U., Khurshid, S., Laleau, R., Reeves, S. (eds.) ABZ 2010. LNCS, vol. 5977, pp. 174–188. Springer, Heidelberg (2010). https://doi.org/10.1007/978-3-642-11811-1_14 CrossRef Iliasov, A., et al.: Supporting reuse in event B development: modularisation approach. In: Frappier, M., Glässer, U., Khurshid, S., Laleau, R., Reeves, S. (eds.) ABZ 2010. LNCS, vol. 5977, pp. 174–188. Springer, Heidelberg (2010).
https://doi.org/10.1007/978-3-642-11811-1_14
CrossRef
12.
go back to reference Khan, A., Basri, S., Dominic, P.: A propose framework for requirement change management in global software development. In: 2012 International Conference on Computer Information Science (ICCIS), Kuala Lumpur, Malaysia, vol. 2, pp. 944–947, June 2012. https://doi.org/10.1109/ICCISci.2012.6297161 Khan, A., Basri, S., Dominic, P.: A propose framework for requirement change management in global software development. In: 2012 International Conference on Computer Information Science (ICCIS), Kuala Lumpur, Malaysia, vol. 2, pp. 944–947, June 2012.
https://doi.org/10.1109/ICCISci.2012.6297161
13.
go back to reference Kumar, S.A., Kumar, T.A.: Study the impact of requirements management characteristics in global software development projects: an ontology based approach. Int. J. Softw. Eng. Appl. 2(4), 107 (2011) Kumar, S.A., Kumar, T.A.: Study the impact of requirements management characteristics in global software development projects: an ontology based approach. Int. J. Softw. Eng. Appl.
2(4), 107 (2011)
14.
go back to reference Niazi, M., El-Attar, M., Usman, M., Ikram, N.: GlobReq: a framework for improving requirements engineering in global software development projects: preliminary results. In: 16th International Conference on Evaluation Assessment in Software Engineering (EASE 2012), pp. 166–170, May 2012. https://doi.org/10.1049/ic.2012.0021 Niazi, M., El-Attar, M., Usman, M., Ikram, N.: GlobReq: a framework for improving requirements engineering in global software development projects: preliminary results. In: 16th International Conference on Evaluation Assessment in Software Engineering (EASE 2012), pp. 166–170, May 2012.
https://doi.org/10.1049/ic.2012.0021
15.
go back to reference Object Management Group Inc.: Open Services for Lifecycle Collaboration (OSLC) (2019). http://open-services.net/ Object Management Group Inc.: Open Services for Lifecycle Collaboration (OSLC) (2019).
http://open-services.net/
16.
go back to reference Pan, Y., Hu, N.: Research on dependability of cloud computing systems. In: 2014 International Conference on Reliability, Maintainability and Safety (ICRMS), Guangzhou, China, pp. 435–439, August 2014. https://doi.org/10.1109/ICRMS.2014.7107234 Pan, Y., Hu, N.: Research on dependability of cloud computing systems. In: 2014 International Conference on Reliability, Maintainability and Safety (ICRMS), Guangzhou, China, pp. 435–439, August 2014.
https://doi.org/10.1109/ICRMS.2014.7107234
17.
go back to reference Project Management Institute: Adoption of the Project Management Institute (PMI) Standard: A Guide to the Project Management Body of Knowledge (PMBOK Guide)-2008 (4th edn.) IEEE P1490/D1, May 2011, pp. 1–505, June 2011. https://doi.org/10.1109/IEEESTD.2011.5937011 Project Management Institute: Adoption of the Project Management Institute (PMI) Standard: A Guide to the Project Management Body of Knowledge (PMBOK Guide)-2008 (4th edn.) IEEE P1490/D1, May 2011, pp. 1–505, June 2011.
https://doi.org/10.1109/IEEESTD.2011.5937011
18.
go back to reference Ramasubbu, N., Balan, R.K.: Globally distributed software development project performance: an empirical analysis. In: Proceedings of the the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on The Foundations of Software Engineering, ESEC-FSE 2007, pp. 125–134. ACM, New York (2007). https://doi.org/10.1145/1287624.1287643 Ramasubbu, N., Balan, R.K.: Globally distributed software development project performance: an empirical analysis. In: Proceedings of the the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on The Foundations of Software Engineering, ESEC-FSE 2007, pp. 125–134. ACM, New York (2007).
https://doi.org/10.1145/1287624.1287643
- Title
- Reactive Middleware for Effective Requirement Change Management of Cloud-Based Global Software Development
- DOI
- https://doi.org/10.1007/978-3-030-30856-8_4
- Author:
-
David Ebo Adjepon-Yamoah
- Publisher
- Springer International Publishing
- Sequence number
- 4