Facilitating the Co-evolution of Standards and Models

The Information Model (IM) specified by the Network Function Virtualisation (NFV) Industry Specification Group (ISG) at the European Telecommunications Standards Institute (ETSI) provides a consolidated view of all information elements used in the various interfaces defined in the NFV standards. Its purpose is to enable quick identification of gaps and inconsistencies in the standards and in implementations of the standards. As the standards are increasing in volume, manual approaches for ensuring their consistency and their co-evolution with the IM are becoming unsustainable, especially considering the rapid release cycles. In this article, we present a model-based approach for facilitating the co-evolution of standards and models and the current state of its prototypical implementation put into place to support the work within the NFV Interfaces and Architecture (IFA) working group. The initial results from the application of the approach were reported to the NFV IFA working group and are expected to contribute towards maintaining the high quality of the standards as they continue to evolve.

[1]  Stefan Biffl,et al.  Model-based co-evolution of production systems and their libraries with AutomationML , 2015, 2015 IEEE 20th Conference on Emerging Technologies & Factory Automation (ETFA).

[2]  Liguo Yu,et al.  Understanding component co-evolution with a study on Linux , 2007, Empirical Software Engineering.

[3]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[4]  James Everett Young,et al.  ChronoTwigger: A Visual Analytics Tool for Understanding Source and Test Co-evolution , 2014, 2014 Second IEEE Working Conference on Software Visualization.

[5]  Sai Peck Lee,et al.  Achievements and Challenges in State-of-the-Art Software Traceability Between Test and Code Artifacts , 2014, IEEE Transactions on Reliability.

[6]  Jörn David,et al.  Traceability ReARMed , 2009, 2009 33rd Annual IEEE International Computer Software and Applications Conference.

[7]  Jane Cleland-Huang,et al.  Model-based traceability , 2009, 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering.

[8]  Jan-Philipp Steghöfer,et al.  Traceability maintenance: Factors and guidelines , 2016, 2016 31st IEEE/ACM International Conference on Automated Software Engineering (ASE).

[9]  Richard F. Paige,et al.  The Epsilon Transformation Language , 2008, ICMT@TOOLS.

[10]  Giuliano Antoniol,et al.  Information retrieval models for recovering traceability links between code and documentation , 2000, Proceedings 2000 International Conference on Software Maintenance.

[11]  Richard F. Paige,et al.  The Epsilon Object Language (EOL) , 2006, ECMDA-FA.

[12]  Jens von Pilgrim,et al.  A survey of traceability in requirements engineering and model-driven development , 2010, Software & Systems Modeling.

[13]  Per Runeson,et al.  Recovering from a decade: a systematic mapping of information retrieval approaches to software traceability , 2013, Empirical Software Engineering.

[14]  Arda Goknil,et al.  Survey of Traceability Approaches in Model-Driven Engineering , 2007, 11th IEEE International Enterprise Distributed Object Computing Conference (EDOC 2007).

[15]  Stephen Clark,et al.  Best Practices for Automated Traceability , 2007, Computer.