Skip to main content
SpringerLink
Log in

Traceability in the Co-evolution of Architectural Requirements and Design

  • Chapter
  • First Online:
Relating Software Requirements and Architectures

Abstract

Requirements and architectural design specifications can be conflicting and inconsistent, especially during the design period when requirements and architectural design are co-evolving. One reason is that stakeholders do not have up-to-date knowledge of each other’s work to fully understand potential conflicts and inconsistencies. Specifications are often documented in a natural language, which also makes it difficult for tracing related information automatically. In this chapter, we introduce a general-purpose ontology that we have developed to address this problem. We demonstrate an implementation of semantic wiki that supports traceability of co-evolving requirements specifications and architecture design.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 84.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 109.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    http://www.mediawiki.org/

  2. 2.

    http://www.wikipedia.org/

  3. 3.

    Resources in NIHR Portal project refer to all the information maintained by the Portal, e.g., sources of funding for different types of research.

References

  1. Gotel OCZ, Finkelstein ACW (1994) An analysis of the requirements traceability problem. In: IEEE International Symposium on Requirements Engineering (RE), 94–101

    Google Scholar 

  2. Ramesh B, Jarke M (2001) Towards reference models for requirements traceability. IEEE Trans Software Eng 27(1):58–93

    Article  Google Scholar 

  3. Spanoudakis G, Zisman A, Perez-Minana E, Krause P (2004) Rule-based generation of requirements traceability relations. J Syst Softw 72(2):105–127

    Article  Google Scholar 

  4. Egyed A, Grunbacher P (2005) Supporting software understanding with automated requirements traceability. Int J Software Engineer Knowledge Engineer 15(5):783–810

    Article  Google Scholar 

  5. Lago P, Muccini H, van Vliet H (2009) A scoped approach to traceability management. J Syst Softw 82(1):168–182

    Article  Google Scholar 

  6. IEEE (1996) IEEE/EIA Standard – Industry Implementation of ISO/IEC 12207:1995, Information Technology – Software life cycle processes (IEEE/EIA Std 12207.0–1996)

    Google Scholar 

  7. IEEE (1997) IEEE/EIA Guide – Industry Implementation of ISO/IEC 12207:1995, Standard for Information Technology – Software life cycle processes – Life cycle data (IEEE/EIA Std 12207.1–1997)

    Google Scholar 

  8. Farenhorst R, Izaks R, Lago P, van Vliet H (2008) A just-intime architectural knowledge sharing portal. In: 7th Working IEEE/IFIP Conference on Software Architecture (WICSA), 125–134

    Google Scholar 

  9. Bass L, Clements P, Kazman R (2003) Software architecture in practice, 2nd edn. Addison Wesley, Boston

    Google Scholar 

  10. Ali-Babar M, de Boer RC, Dingsøyr T, Farenhorst R (2007) Architectural knowledge management strategies: approaches in research and industry. In: 2nd Workshop on SHAring and Reusing architectural Knowledge – Architecture, Rationale, and Design Intent (SHARK/ADI)

    Google Scholar 

  11. Rus I, Lindvall M (2002) Knowledge management in software engineering. IEEE Softw 19(3):26–38

    Article  Google Scholar 

  12. Hansen MT, Nohria N, Tierney T (1999) What’s your strategy for managing knowledge? Harv Bus Rev 77(2):106–116

    Google Scholar 

  13. Robertson S, Robertson J (1999) Mastering the requirements process. Addison-Wesley, Harlow

    Google Scholar 

  14. Tang A, Jin Y, Han J (2007) A rationale-based architecture model for design traceability and reasoning. J Syst Softw 80(6):918–934

    Article  Google Scholar 

  15. IBM (2010) Rational DOORS – A requirements management tool for systems and advanced IT applications. http://www-01.ibm.com/software/awdtools/doors/, accessed on 2010-3-20

  16. IBM (2004) Rational RequisitePro - A requirements management tool. http://www-01.ibm.com/software/awdtools/reqpro/, accessed on 2010-3-20

  17. Hayes JH, Dekhtyar A, Osborne J (2003) Improving Requirements Tracing via Information Retrieval. In: 11th IEEE International Conference on Requirements Engineering (RE), 138–147

    Google Scholar 

  18. Assawamekin N, Sunetnanta T, Pluempitiwiriyawej C (2009) Mupret: an ontology-driven traceability tool for multiperspective requirements artifacts. In: ACIS-ICIS,. 943–948

    Google Scholar 

  19. Hayes JH, Dekhtyar A, Sundaram SK (2006) Advancing candidate link generation for requirements tracing: the study of methods. IEEE Trans Software Eng 32(1):4–19

    Article  Google Scholar 

  20. Cleland-Huang J, Chang CK, Christensen M (2003) Event-based traceability for managing evolutionary change. IEEE Trans Software Eng 29(9):796–810

    Article  Google Scholar 

  21. Mistrık I, Grundy J, Hoek A, Whitehead J (2010) Collaborative software engineering. Springer, Berlin

    Book  Google Scholar 

  22. Schaffert S, Bry F, Baumeister J, Kiesel M (2008) Semantic wikis. IEEE Softw 25(4):8–11

    Article  Google Scholar 

  23. Liang P, Avgeriou P, Clerc V (2009) Requirements reasoning for distributed requirements analysis using semantic wiki. In: 4th IEEE International Conference on Global Software Engineering (ICGSE), 388–393

    Google Scholar 

  24. Louridas P (2006) Using wikis in software development. IEEE Softw 23(2):88–91

    Article  Google Scholar 

  25. Hoenderboom B, Liang P (2009) A survey of semantic wikis for requirements engineering. SEARCH http://www.cs.rug.nl/search/uploads/Publications/hoenderboom2009ssw.pdf, accessed on 2010-3-20

  26. Bachmann F, Merson P (2005) Experience using the web-based tool wiki for architecture documentation. Technical Note CMU, SEI-2005-TN-041

    Google Scholar 

  27. Lassila O, Swick R (1999) Resource Description Framework (RDF) Model and Syntax. http://www.w3.org/TR/WD-rdfsyntax, accessed on 2010-3-20

  28. McGuinness D, van Harmelen F (2004) OWL web ontology language overview. W3C recommendation 10:2004–03

    Google Scholar 

  29. Aguiar A, David G (2005) Wikiwiki weaving heterogeneous software artifacts. In: international symposium on wikis, WikiSym, pp 67–74

    Google Scholar 

  30. Geisser M, Happel HJ, Hildenbrand T, Korthaus A, Seedorf S (2008) New applications for wikis in software engineering. In: PRIMIUM 145–160

    Google Scholar 

  31. Riechert T, Lohmann S (2007) Mapping cognitive models to social semantic spaces-collaborative development of project ontologies. In: 1st Conference on Social Semantic Web (CSSW) 91–98

    Google Scholar 

  32. Domges R, Pohl K (1998) Adapting traceability environments to project-specific needs. Commun ACM 41(12):54–62

    Article  Google Scholar 

  33. Lago P, Farenhorst R, Avgeriou P, Boer R, Clerc V, Jansen A, van Vliet H (2010) The GRIFFIN collaborative virtual community for architectural knowledge management. In: Mistrık I, Grundy J, van der Hoek A, Whitehead J (eds) Collaborative software engineering. Springer, Berlin

    Google Scholar 

  34. Kunz W, Rittel H (1970) Issues as elements of information systems. Center for Planning and Development Research, University of California, Berkeley

    Google Scholar 

  35. Kruchten P (2004) An ontology of architectural design decisions in software-intensive systems. In: 2nd Groningen Workshop on Software Variability Management (SVM)

    Google Scholar 

  36. Noy N, McGuinness D (2001) Ontology development 101: a guide to creating your first ontology

    Google Scholar 

  37. Powell A, Nilsson M, Naeve A, Johnston P (2007) Dublin Core Metadata Initiative – Abstract Model. http://dublincore.org/documents/abstract-model, accessed on 2010-3-20

  38. Krotzsch M, Vrandecic D, Volkel M (2006) Semantic Mediawiki. In: 5th International Semantic Web Conference (ISWC), 935–942

    Google Scholar 

  39. Prud’Hommeaux E, Seaborne A (2006) SPARQL Query Language for RDF. W3C working draft 20

    Google Scholar 

  40. NIHR (2006) NIHR Information Systems Portal User Requirements Specification. http://www.nihr.ac.uk/files/pdfs/NIHR4.2PortalURS002v3.pdf, accessed on 2010-3-20

Download references

Acknowledgments

This research has been partially sponsored by the Dutch “Regeling Kenniswerkers”, project KWR09164, Stephenson: Architecture knowledge sharing practices in software product lines for print systems, the Natural Science Foundation of China (NSFC) under Grant No. 60950110352, STAND: Semantic-enabled collaboration Towards Analysis, Negotiation and Documentation on distributed requirements engineering, and NSFC under Grant No.60903034, QuASAK: Quality Assurance in Software architecting process using Architectural Knowledge.

Author information

Authors and Affiliations

  1. Swinburne University of Technology, Hawthorn, VIC, 3122, Australia

    Antony Tang

  2. Department of Mathematics and Computing Science, University of Groningen, Groningen, 9747 AG, The Netherlands

    Peng Liang

  3. VU University Amsterdam, FEW, Computer Science, Amsterdam, 1081 HV, The Netherlands

    Viktor Clerc & Hans van Vliet

Authors
  1. Antony Tang
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Peng Liang
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Viktor Clerc
    View author publications

    You can also search for this author in PubMed Google Scholar

  4. Hans van Vliet
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Antony Tang .

Editor information

Editors and Affiliations

  1. University of Groningen, Nijenborgh 9, Groningen, 9747, Netherlands

    Paris Avgeriou

  2. Faculty of Information, Swinburne University of Technology, PO Box 218, Victoria, 3122, Australia

    John Grundy

  3. The Open University, Milton Keynes, MK7 6AA, UK

    Jon G. Hall

  4. Dept. Computer Science, Vrije Universiteit, De Boelelaan 1081 A, Amsterdam, 1081 HV, Netherlands

    Patricia Lago

  5. Werderstr. 45, Heidelberg, 69120, Germany

    Ivan Mistrík

Rights and permissions

Reprints and permissions

Copyright information

© 2011 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Tang, A., Liang, P., Clerc, V., van Vliet, H. (2011). Traceability in the Co-evolution of Architectural Requirements and Design. In: Avgeriou, P., Grundy, J., Hall, J.G., Lago, P., Mistrík, I. (eds) Relating Software Requirements and Architectures. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-21001-3_4

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-21001-3_4

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-21000-6

  • Online ISBN: 978-3-642-21001-3

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation