Process of Product Fragments Management in Distributed Development

  • Darijus Strašunskas
  • Sari Hakkarainen
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2888)


Management of product constituent fragments is essential for large scale logically or physically distributed projects. Geographically distributed development projects have special settings and needs – special attention has to be given to artifacts management because developers are likely to use different representation formats and a variety of tools for the artifact production. The question is: how can artifacts in different representation formats be related and managed?

Methodological support for artifacts management and traceability is presented in this paper. Product fragments from different development phases (i.e., requirements specification, design, code, test scenarios, and documentation) are interrelated through a conceptual domain model. Domain model is proposed as a means to capture information content despite heterogeneous representation. Given, a domain model with intra-related concepts and artifacts associated to the concepts we are able to interrelate heterogeneous artifacts and to predict and assess how one altered artifact may impact other artifacts. The approach covers the whole lifecycle of a system, enables artifacts’ management by associating them according semantics contained inside.


Domain Model Requirement Engineer Domain Concept Semantic Distance Change Operation 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Arkley, P., Mason, P., Riddle, S.: Enabling Traceability. In: Proceedings of the 1st International Workshop on Traceability, co-located with ASE 2002, Edinburgh, Scotland, UK, pp. 61–65 (September 2002)Google Scholar
  2. 2.
    Brasethvik, T., Gulla, J.A.: Natural Language Analysis for Semantic Document Modeling. In: Bouzeghoub, M., Kedad, Z., Métais, E. (eds.) NLDB 2000. LNCS, vol. 1959, p. 127. Springer, Heidelberg (2001)CrossRefGoogle Scholar
  3. 3.
    Cormen, T.H., Leiserson, C.E., Rivest, R.L., Stein, C.: Introduction to Algorithms, 2nd edn. The MIT Press and McGraw-Hill, Cambridge (2001)zbMATHGoogle Scholar
  4. 4.
    Dijkstra, E.W.: A note on two problems in connextion with graphs. Numer. Math. 1, 269–271 (1959)zbMATHCrossRefMathSciNetGoogle Scholar
  5. 5.
    Egyed, A.: Reasonings about Trace dependencies in a Multi-Dimensional Space. In: Proceedings of the 1st International Workshop on Traceability, co-located with ASE 2002, Edinburgh, Scotland, UK, pp. 42–45 (September 2002)Google Scholar
  6. 6.
    Farshchian, B.A.: A Framework for Supporting Shared Interaction in Distributed Product Development Projects, PhD thesis, NTNU, Trondheim, Norway (2001)Google Scholar
  7. 7.
    Frezza, S.T., Levitan, S.P., Chrysanthis, P.K.: Linking requirements and design data for automated functional evaluation. Computers in Industry 30(1), 13–25 (1996)CrossRefGoogle Scholar
  8. 8.
    Gotel, O.C.Z., Finkelstein, A.C.W.: An Analysis of the Requirements Traceability Problem. In: Proceeding of the 1st International Conference on Requirements Engineering (ICRE 1994), Colorado Springs, Colorado, USA, April 1994, pp. 94–102. IEEE Computer Society Press, Los Alamitos (1994)CrossRefGoogle Scholar
  9. 9.
    Greenspan, S., McGowan, C.: Structuring Software Development for Reliability. In: Microelectronics and Reliability, vol. 17, pp. 75–84 (1978)Google Scholar
  10. 10.
    Grünbacher, P., Egyed, A., Medvidovic, N.: Reconciling Software Requirements and Architectures - The CBSP Approach. In: Proceedings of the 5th IEEE International Symposium on Requirements Engineering (RE 2001), Toronto, Canada, pp. 202–211. Springer, Heidelberg (2001)Google Scholar
  11. 11.
    Letelier, P.: A framework for Requirements Traceability in UML based projects. In: Proceedings of the 1st International Workshop on Traceability, co-located with ASE 2002, Edinburgh, Scotland, UK, pp. 32–41 (September 2002)Google Scholar
  12. 12.
    Matulevicius, R.: MEIS requirements specification. Technical report, NTNU (2003)Google Scholar
  13. 13.
    Pinheiro, F., Goguen, J.: An Object-Oriented Tool for Tracing Requirements. IEEE Software 13(2), 52–64 (1996)CrossRefGoogle Scholar
  14. 14.
    Pohl, K.: PRO-ART: Enabling Requirements Pre-Traceability. In: Proceedings of the Second International Conference on Requirements Engineering (ICSE 1996), Colorado, USA, pp. 76–85 (1996)Google Scholar
  15. 15.
    Pohl, K., Brandenburg, M., Gülich, A.: Integrating Requirement and Architecture Information: A Scenario and Meta-Model Based Approach. In: Proceedings of the Seventh International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ 2001), Interlaken, Switzerland (2001)Google Scholar
  16. 16.
    Ramesh, B., Jarke, M.: Toward Reference Models for Requirements Traceability. IEEE Transactions on Software Engineering 27(1), 58–93 (2001)CrossRefGoogle Scholar
  17. 17.
    Rational Suite AnalystStudio. URL:
  18. 18.
    Strasunskas, D.: Traceability in a Collaborative Systems Development from Lifecycle Perspective. In: Proceedings of the 1st International Workshop on Traceability, co-located with ASE 2002, Edinburgh, Scotland, UK, pp. 54–60 (September 2002)Google Scholar
  19. 19.
    Solvberg, A.: Data and what they refer to. In: Chen, P.P., Akoka, J., Kangassalu, H., Thalheim, B. (eds.) Conceptual Modeling. LNCS, vol. 1565, p. 211. Springer, Heidelberg (1999)CrossRefGoogle Scholar
  20. 20.
    Solvberg, A., Brasethvik, T.: The Referent Model Language., Technical Report. NTNU, Trondheim, Norway URL:
  21. 21.
    Watkins, R., Neal, M.: Why and How of Requirements Tracing. IEEE Software 11(4), 104–106 (1994)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2003

Authors and Affiliations

  • Darijus Strašunskas
    • 1
  • Sari Hakkarainen
    • 1
  1. 1.Dept. of Computer and Information ScienceNorwegian Univ. of Science and TechnologyTrondheimNorway

Personalised recommendations