Advertisement

Graceful Integration of Process Capability Improvement, Formal Modeling and Web Technology for Traceability

  • Miklós Biró
  • Felix Kossak
  • József Klespitz
  • Levente Kovács
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 748)

Abstract

This paper discusses the need and leveraging potential of formal modeling and web technology for progressing towards the goal of automating the establishment, maintenance and assessment of the completeness of traceability and the consistency of the requirements. The generic Augmented Lifecycle Space method, devised in an earlier paper, is applied as the approach to improve the capability of software processes requiring bidirectional traceability as well as consistency of the requirements in either homogeneous or heterogeneous development environments capitalizing on the emerging Open Services for Lifecycle Collaboration (OSLC) initiative. One of the important features of the presented new approach is that it allows for the so called “graceful integration” of formal modeling. Formal modeling is fundamentally necessary for securing completeness and consistency, but customarily rejected due to the usually prohibiting up-front effort needed to formally process all artifacts of an already established traditional system; Graceful integration can considerably lower this threshold.

Keywords

Application lifecycle management Process assessment Process improvement Formal modeling Open services for lifecycle collaboration Tools integration Heterogeneous tool environment Requirements traceability Requirements consistency 

Notes

Acknowledgement

The authors are grateful for the support of Research and Innovation Center of Óbuda University. The work is supported by the European Research Council Starting Grant ERC-StG 679681.

The research reported in this paper has been supported by the Austrian Ministry for Transport, Innovation and Technology, the Federal Ministry of Science, Research and Economy, and the Province of Upper Austria in the frame of the COMET center SCCH.

References

  1. 1.
    Abrial, J.-R.: Modeling in Event-B System and Software Design. Cambridge University Press, Cambridge (2010)CrossRefMATHGoogle Scholar
  2. 2.
    Ambler, S.: Tracing your design. Dr. Dobb’s J. World Softw. Dev. (1999). http://www.drdobbs.com/tracing-your-design/184415675. Accessed 08 Apr 2016)
  3. 3.
    Ambler, S.: Agile Requirements best practices. In: Agile Modeling (2014) http://www.agilemodeling.com/essays/agileRequirementsBestPractices.htm. Accessed 08 Apr 2016
  4. 4.
    University of Milan: “Asmeta”. http://asmeta.sourceforge.net/. Accessed 31 Mar 2017
  5. 5.
    Automotive SIG. VDA QMC Working Group 13: Automotive SPICE Process As-sessment/Reference Model, v3.0 (2015). http://www.automotivespice.com/fileadmin/software-download/Automotive_SPICE_PAM_30.pdf. Accessed 08 Apr 2016
  6. 6.
    Biehl,M.: OSLC-Style Tool Adapter for MATLAB/Simulink. http://open-services.net/pub/Main/PLMWorkgroupWorkingMeetingJune282011/simulink-oslc-demo-2.pdf. Accessed 07 Apr 2017
  7. 7.
    Biró, M., Feuer, É., Haase, V.H., Koch, G.R., Kugler, H.J., Messnarz, R., Remzső, T.: BOOTSTRAP and ISCN: a current look at the European software quality network. In: Sima, D., Haring, G. (eds.) Proceedings of the Conference on the Challenge of Networking: Connecting Equipment, Humans, Institutions (CON 1993), R. Oldenbourg Verlag GmbH, pp. 97–105 (1993). http://dl.acm.org/citation.cfm?id=200895.200906. Accessed 07 Apr 2017
  8. 8.
    Biro, M.: Open Services for software process compliance engineering. In: Geffert, V., Preneel, B., Rovan, B., Štuller, J., Tjoa, A.M. (eds.) SOFSEM 2014. LNCS, vol. 8327, pp. 1–6. Springer, Cham (2014). doi: 10.1007/978-3-319-04298-5_1 CrossRefGoogle Scholar
  9. 9.
    Biró, M.: Functional safety, traceability, and open services. In: Madeyski, L., Ochodek, M. (ed.) Software Engineering from Research and Practice Perspective. Wyd. Nakom, Poznan, pp. 73–82. ISBN 978-83-63919-16-0Google Scholar
  10. 10.
    Biró, M., Klespitz, J., Gmeiner, J., Illibauer, C., Kovács, L.: Towards Automated Traceability Assessment through Augmented Lifecycle Space. In: Kreiner, C., O’Connor, R., Poth, A., Messnarz, R. (eds.) EuroSPI 2016. CCIS, vol. 633, pp. 73–82. Springer, Cham (2016)Google Scholar
  11. 11.
    Börger, E., Stärk, R.: Abstract State Machines. A Method for High-Level System Design and Analysis. Springer, Heidelberg (2003)CrossRefMATHGoogle Scholar
  12. 12.
    Chapman, D.: What is application lifecycle management? (2010) http://www.davidchappell.com/writing/white_papers/What_is_ALM_v2.0–Chappell.pdf. Accessed 08 Apr 2016
  13. 13.
    Cleland-Huang, J, Gotel, O. C., Huffman Hayes, J., Mäder, P., Zisman, A.: Software trace-ability: trends and future directions. In: Proceedings of the on Future of Software Engineering, pp. 55–69. ACM (2014)Google Scholar
  14. 14.
    Generate C and C++ code optimized for embedded systems. https://www.mathworks.com/products/embedded-coder.html
  15. 15.
    Ferrari, A., Fantechi, A., Gnesi, S., Magnani, G.: Model-based development and formal methods in the railway industry. IEEE software 30(3), 28–34 (2013). (https://doi.ieeecomputersociety.org/cms/Computer.org/dl/mags/so/2013/03/figures/mso20130300281.gif), (source of the mentioned picture)CrossRefGoogle Scholar
  16. 16.
    Gotel, O., Cleland-Huang, J., Hayes, J.H., Zisman, A., Egyed, A., Grünbacher, P., Dekhtyar, A., Antoniol, G., Maletic, J.: The grand challenge of traceability (v1.0). In: Cleland-Huang, J., Gotel, O., Zisman, A. (eds.) Software and Systems Traceability, pp. 343–409. Springer, London (2012)Google Scholar
  17. 17.
    Gurevich, Y.: Sequential abstract state machines capture sequential algorithms. ACM Trans. Comput. Logic 1(1), 77–111 (2000)MathSciNetCrossRefMATHGoogle Scholar
  18. 18.
    Ibrahim, S., Idris, N.B., Munro, M., Deraman, A.: Implementing a document-based requirements traceability: a case study. In: IASTED International Conference on Software Engineering, pp. 124–131 (2005)Google Scholar
  19. 19.
    Functional safety. International Electrotechnical Commission®. http://www.iec.ch/about/brochures/pdf/technology/functional_safety.pdf. Accessed 31 Mar 2017
  20. 20.
    Kamalrudin, M., Sidek, S.: A review on software requirements validation and consistency management. Int. J. Softw. Eng. Appl. 9(10), 39–58 (2015)Google Scholar
  21. 21.
    Lacheiner, H., Ramler, R.: Application lifecycle management as infrastructure for software processes improvement and evolution: Experience and insights from industry. In: Biffl, S., Koivuluoma, M., Abrahamsson, P. (eds.) Proceedings of the 37th EUROMICRO Conference on Software Engineering and Advanced Applications - SEAA 2011, pp. 286–293. IEEE, August/September 2011Google Scholar
  22. 22.
    Eclipse Lyo: Enabling tool integration with OSLC. http://www.eclipse.org/lyo/. Accessed 31 Mar 2017
  23. 23.
    Mashkoor, A., Biro, M., Dolgos, M., Timar, P.: Refinement-based development of software-controlled safety-critical active medical devices. In: Winkler, D., Biffl, S., Bergsmann, J. (eds.) SWQD 2015. LNBIP, vol. 200, pp. 120–132. Springer, Cham (2015). doi: 10.1007/978-3-319-13251-8_8 Google Scholar
  24. 24.
    McCaffery, F., Casey, V., Sivakumar, M.S., Coleman, G., Donnelly, P., Burton, J.: Medical device software traceability. In: Cleland-Huang, J., Gotel, O., Zisman, A. (eds.) Software and Systems Traceability, pp. 321–339. Springer, London (2012)CrossRefGoogle Scholar
  25. 25.
    Open Services for Lifecycle Collaboration: an open community building practical specifications for integrating software. http://open-services.net/. Accessed 31 Mar 2017
  26. 26.
    Pirklbauer, G., Ramler, R., Zeilinger, R.: An integration-oriented model for application lifecycle management. In: Proceedings of the 11th International Conference con Enterprise Information Systems (ICEIS 2009), pp. 399–403. INSTICC (2009)Google Scholar
  27. 27.
    Ramesh, B., Jarke, M.: Towards reference models for requirements traceability. IEEE Trans. Software Eng. 27(1), 58–93 (2001)CrossRefGoogle Scholar
  28. 28.
    Ramler, Rudolf, Lacheiner, Hermann, Kern, Albin: Rule-Based Detection of Process Conformance Violations in Application Lifecycle Management. In: Winkler, Dietmar, O’Connor, Rory V., Messnarz, Richard (eds.) EuroSPI 2012. CCIS, vol. 301, pp. 37–48. Springer, Heidelberg (2012). doi: 10.1007/978-3-642-31199-4_4 CrossRefGoogle Scholar
  29. 29.
    Regan, Gilbert, Biro, Miklos, Mc Caffery, Fergal, Mc Daid, Kevin, Flood, Derek: A traceability process assessment model for the medical device domain. In: Barafort, Béatrix, O’Connor, R.V., Poth, Alexander, Messnarz, Richard (eds.) EuroSPI 2014. CCIS, vol. 425, pp. 206–216. Springer, Heidelberg (2014). doi: 10.1007/978-3-662-43896-1_18 Google Scholar
  30. 30.
    Regan, G., Biro, M., Flood, D., McCaffery, F.: Assessing traceability—practical experiences and lessons learned. J. Softw. Evol. Process 27(8), 591–601 (2015). http://dx.doi.org/10.1002/smr.1728. Accessed 31 Mar 2017CrossRefGoogle Scholar
  31. 31.
    Reichwein, A.: Java-based Implementation of OSLC Simulink Adapter. https://github.com/ld4mbse/oslc-adapter-simulink. Accessed 07 Apr 2017
  32. 32.
    Rempel, P., Mäder, P.: Preventing defects: the impact of requirements traceability completeness on software quality. IEEE Trans. Softw. Eng. PP(99), 1 (2016)CrossRefGoogle Scholar
  33. 33.
    Event-B and the Rodin Platform. http://www.event-b.org/. Accessed 31 Mar 2017
  34. 34.
    OMG: OMG Systems Modeling Language (OMG SYSMLTM), Version 1.4. http://www.omg.org/spec/SysML/1.4/. Accessed 31 Mar 2017
  35. 35.
    Apache Wink. https://wink.apache.org/. Accessed 31 Mar 2017

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  • Miklós Biró
    • 1
    • 3
  • Felix Kossak
    • 1
  • József Klespitz
    • 2
  • Levente Kovács
    • 2
  1. 1.Software Competence Center HagenbergHagenbergAustria
  2. 2.Óbuda UniversityBudapestHungary
  3. 3.Johannes Kepler UniversitätLinzAustria

Personalised recommendations