Skip to main content
SpringerLink
Log in

A streamlined, cost-effective database approach to manage requirements traceability

  • Published:
Software Quality Journal Aims and scope Submit manuscript

Abstract

Requirements traceability offers many benefits to software projects, and it has been identified as critical for successful development. However, numerous challenges exist in the implementation of traceability in the software engineering industry. Some of these challenges can be overcome through organizational policy and procedure changes, but the lack of cost-effective traceability models and tools remains an open problem. A novel, cost-effective solution for the traceability tool problem is proposed, prototyped, and tested in a case study using an actual software project. Metrics from the case study are presented to demonstrate the viability of the proposed solution for the traceability tool problem. The results show that the proposed method offers significant advantages over implementing traceability manually or using existing commercial traceability approaches.

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

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7

Similar content being viewed by others

References

  • Armbrust, O., Ocampo A., & Soto, M. (2005). Tracing process model evaluation: A semi-formal process modeling approach. In ECMDA traceability workshop (ECMDA-TW) 2005 proceedings (pp. 57–66). Nuremberg, Germany.

  • Brown, A. (2004). Oops! Coping with human error in IT systems. Queue, 2(8), 34–41.

    Article  Google Scholar 

  • Cleland-Huang, J. (2006), Just enough requirements traceability. In Proceedings of the 30th annual international computer software and applications conference (COMPSAC’06) (pp. 41–42).

  • Cleland-Huang, J., Chang, C., & Christensen, M. (2003). Event-based traceability for managing evolutionary change. IEEE Transactions on Software Engineering, 29(9), 796–810.

    Article  Google Scholar 

  • Egyed, A., & Grunbacher, P. (2002). Automating requirements traceability: beyond the record and replay paradigm. In Proceedings of the 17th IEEE international conference on automated software engineering (pp. 163–171). Edinburgh, United Kingdom.

  • Gills, M. (2005). Software Testing and Traceability. University of Latvia. http://www3.acadlib.lv/greydoc/Gilla_disertacija/MGills_ang.doc.

  • Gotel, O., & Finkelstein, A. (1994). An analysis of the requirements traceability problem. In Proceedings of the first international conference on requirements engineering (pp. 94–101). Colorado Springs, CO.

  • Hayes, J., & Dekhtyar, A. (2005). Humans in the traceability loop: Can’t live with ‘Em, can’t live without ‘Em. In Proceedings of the 3rd international workshop on traceability in emerging forms of software engineering, (pp. 20–23). Long Beach, CA.

  • International Council on Systems Engineering. (2008). INCOSE requirements management tools survey. http://www.paper-review.com/tools/rms/read.php.

  • Jarke, M. (1998). Requirements tracing. Communications of the ACM, 41(12), 32–36.

    Article  Google Scholar 

  • Lempia, D., & Miller, S. (2006). Requirements engineering management, presented at the 2006 National Software and Complex Electronic Hardware Standardization Conference, Atlanta, GA.

  • Lungu, N., & Muvuti, F. (2004).Service oriented architecture for a software traceability system. Technical Report CS04-14-00, Department of Computer Science, University of Cape Town.

  • Munson, E., & Nguyen, T. (2005). Concordance, conformance, versions, and traceability. In Proceedings of the third international workshop on traceability in emerging forms of software engineering (pp. 62–66). Long Beach, CA.

  • Naslavsky, L., Alspaugh, T., Richardson, D., & Ziv, H. (2005). Using scenarios to support traceability. In Proceedings of the third international workshop on traceability in emerging forms of software engineering (pp. 25–30). Long Beach, CA.

  • Ramesh, B. (1998). Factors influencing requirements traceability practice. Communications of the ACM, 41(12), 37–44.

    Article  Google Scholar 

  • Ramesh, B., & Jarke, M. (2001). Toward reference models for requirements traceability. IEEE Transactions on Software Engineering, 27(1), 58–93.

    Article  Google Scholar 

  • Spanoudakis, G., Zisman, A., Perez-Minana, E., & Krause, P. (2004). Rule-based generation of requirements traceability relations. Journal of Systems and Software, 72(2), 105–127.

    Article  Google Scholar 

  • Telelogic. (2008). Telelogic DOORS—requirements management for advanced systems and software development. http://www.telelogic.com/products/doors/doors/index.cfm.

  • Young, R. (2006). Twelve requirement basics for project success. CrossTalk The Journal of Defense Software Engineering, 19(12), 4–8.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Electrical Engineering and Computer Science, University of Kansas, Lawrence, KS, 66049, USA

    Hossein Saiedian

  2. Innovative Systems, Mitchell, SD, 57301, USA

    Andrew Kannenberg

  3. Department of Computer Science and Software Engineering, University of Detroit Mercy, Detroit, MI, 48221, USA

    Serhiy Morozov

Authors
  1. Hossein Saiedian
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Andrew Kannenberg
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Serhiy Morozov
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Hossein Saiedian.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Saiedian, H., Kannenberg, A. & Morozov, S. A streamlined, cost-effective database approach to manage requirements traceability. Software Qual J 21, 23–38 (2013). https://doi.org/10.1007/s11219-011-9166-3

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s11219-011-9166-3

Keywords

Search

Navigation