Backward Requirements Traceability within the Topology-based Model Driven Software Development

Erika Asnina, Bernards Gulbis, Janis Osis, Gundars Alksnis, Uldis Donins, Armands Slihte

Abstract

The inconsistence between software and specifications leads to unpredictable side effects after change implementation. Impact analysis may be useful here, but manual control of trace links is very expensive. Model Driven Architecture and automated transformations should make the impact analysis easier. The issue is that the impact analysis of changes in software to real world functional units is intuitive. Formalization of specifications of the environment and software functionality as well as their analysis by means of Topological Functioning Model extends possibilities of the impact analysis. This paper demonstrates the establishment of formal trace links to real world functional units and entities from user requirements and analysis artifacts. These links show element interdependence explicitly, and, hence, make the impact analysis more thorough.

References

  1. Aizenbud-Reshef, N., Nolan, B. T., Rubin, J., & Shaham-Gafni, Y. (2006). Model traceability. IBM SYSTEMS JOURNAL , 45 (3), pp. 515-526.
  2. Asnina, E., & Osis, J. (2010). Computation independent models: bridging problem and solution domains. Proceedings of the 2nd InternationalWorkshop on Model-Driven Architecture and Modeling Theory-Driven Development MDA & MTDD 2010, In conjunction with ENASE 2010, Athens, Greece, July 2010 (pp. 23-32). Portugal: SciTePress.
  3. Asnina, E., & Osis, J. (2011). Topological Functioning Model as a CIM-Business Model. In J. Osis, & E. Asnina, Model-Driven Domain Analysis and Software Development: Architectures and Functions (pp. 40-64). Hershey, New York, USA: IGI Global.
  4. De Castro, V., Marcos, E., & Vara, J. M. (2011). Applying CIM-to-PIM model trnsformations for the service-oriented development of information systems. Information and Software Technology , 53, 87-105.
  5. Gotel, O. C., & Finkelstein, A. C. (1994). An Analysis of the Requirements Traceability Problem. Proceedings of the First International Conference on Requirements Engineering, 1994 (pp. 94 - 101). Colorado Springs, CO , USA: IEEE.
  6. Grammel, B., & Kastenholz, S. (2010). A Generic Traceability Framework for Facet-based Traceability Data Extraction in Model-driven Software Development. Proceedings of the 6th ECMFA Traceability Workshop (ECMFA-TW), June 15th 2010, Paris, France (pp. 7- 14). ACM Press.
  7. Nicolás, J., & Toval, A. (2009). On the generation of requirements specifications from software engineering models: A systematic literature review. Information and Software Technology , 51, 1291-1307.
  8. Osis, J. (2006). Formal Computation Independent Model within the MDA Life Cycle. (P. Loucopoulos, & K. Lyytinen, Eds.) International transactions on system science and applications , 1 (2), pp. 159-166.
  9. Osis, J., & Asnina, E. (2008). A Business Model to Make Software Development Less Intuitive. Proceedings of 2008 International Conference on Innovation in Sofware Engineering (ISE 2008). December 10-12, 2008, Vienna, Austria (pp. 1240-1245). IEEE Computer Society Publishing.
  10. Osis, J., & Asnina, E. (2011). Topological Modeling for Model-Driven Domain Analysis and Software Development. In J. Osis, & E. Asnina, Model-Driven Domain Analysis and Software Development: Architectures and Functions (pp. 15-39). Hershey, New York, USA: IGI Global.
  11. Osis, J., & Donins, U. (2010). Formalization of the UML Class Diagrams. In Evaluation of Novel Approaches to Software Engineering (pp. 180-192). Berlin: Springer-Verlag.
  12. Osis, J., & Slihte, A. (2010). Transforming Textual Use Cases to a Computation Independent Model. Proceedings of the 2nd InternationalWorkshop on Model-Driven Architecture and Modeling Theory-Driven Development MDA & MTDD 2010, In conjunction with ENASE 2010, Athens, Greece, July 2010 (pp. 33-42). Portugal: SciTePress.
  13. Sahraoui, A.-E.-K. (2005). Requirements traceability issues: generic model, methodology and formal basis. International Journal of Information Technology & Decision Making , 4 (1), 59-80.
  14. Yang, H., & Ward, M. (2002). Successful Evolution of Software Systems. Boston, London: Artech House, Incorporated.
Download


Paper Citation


in Harvard Style

Asnina E., Gulbis B., Osis J., Alksnis G., Donins U. and Slihte A. (2011). Backward Requirements Traceability within the Topology-based Model Driven Software Development . In Proceedings of the 3rd International Workshop on Model-Driven Architecture and Modeling-Driven Software Development - Volume 1: MDA & MDSD, (ENASE 2011) ISBN 978-989-8425-59-1, pages 36-45


in Bibtex Style

@conference{mda & mdsd11,
author={Erika Asnina and Bernards Gulbis and Janis Osis and Gundars Alksnis and Uldis Donins and Armands Slihte},
title={Backward Requirements Traceability within the Topology-based Model Driven Software Development},
booktitle={Proceedings of the 3rd International Workshop on Model-Driven Architecture and Modeling-Driven Software Development - Volume 1: MDA & MDSD, (ENASE 2011)},
year={2011},
pages={36-45},
publisher={SciTePress},
organization={INSTICC},
doi={},
isbn={978-989-8425-59-1},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 3rd International Workshop on Model-Driven Architecture and Modeling-Driven Software Development - Volume 1: MDA & MDSD, (ENASE 2011)
TI - Backward Requirements Traceability within the Topology-based Model Driven Software Development
SN - 978-989-8425-59-1
AU - Asnina E.
AU - Gulbis B.
AU - Osis J.
AU - Alksnis G.
AU - Donins U.
AU - Slihte A.
PY - 2011
SP - 36
EP - 45
DO -