Abstract
In the recent years, we have seen the emergence and the growing of the software requirements engineering. Software requirements should be managed by using traceability. This will allow to better solve their conflicts and to eliminate faked or frivolous requirements that lack any justification. Meanwhile, writing the software requirements specification (SRS) must include traceability to allow a more efficient reading. Many standards have been proposed to provide efficient SRS templates such as the IEEE 830 standard. These standards present the content of the specification in a linear way, which often limits its use possibilities to a sequential reading. The proposed model of SRS uses a semi-structured data approach aiming at transforming the SRS into a hypermedia and is based on: (1) the IEEE 830 standard offering the SRS a tree’s structure; and (2) the requirements traceability links offering the SRS a network structure. Such links could connect each requirement backward from its source and forward to its corresponding design artefacts. The main contributions of this paper are: (1) building an XML schema for the proposed SRS model; and (2) building a prototype of a web-based system named SRSM (SRS Manager), based on the previous SRS model.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Asuncion, H.U., Franccois, F., Taylor, R.N.: An end-to-end industrial software traceability tool. In: Proceedings of the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on The Foundations of Software Engineering, pp. 115–124 (2007)
Gupta, S.C., Nguyen, T.N., Munson, E.V.: The software concordance: A user interface for advanced software documents. In: Proceedings of 6th IASTED International Conference on Software Engineering and Applications. MIT, Cambridge (2002)
Hokkanen, M.: Requirements Traceability. Lappeenranta University of Technology (2001)
I.C.S.S.E.S. Committee and I.S.S. Board, IEEE Recommended Practice for Software Requirements Specifications, IEEEStd.830-1998
Lauesen, S.: Software Requirements: Styles and Techniques. Addison-Wesley, Harlow (2002)
Leino, V.: Documenting Requirements Traceability Information: A Case Study. Helsinki University of Technology (2001)
Maletic, J.I., Collard, M.L., Simoes, B.: An XML based approach to support the evolution of model-to-model traceability links. In: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 67–72 (2005)
Maletic, J., Munson, E., Marcus, A., Nguyen, T.: Using a hypertext model for traceability link conformance analysis. In: Proceedings of International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE 2003), Montreal, Canada, pp. 47–54 (2003)
Marcus, A., Maletic, J.I., Sergeyev, A.: Recovery of traceability links between software documentation and source code. International Journal of Software Engineering and Knowledge Engineering 15(5), 811–836 (2005)
Munson, E.: The software concordance: Bringing hypermedia to software development environments. In: Proceedings SBMIDIA 1999, Goias, Brasil, pp. 1–12 (1999)
OzkayaI, A., Akin, Ö.: Tool support for computer-aided requirement traceability in architectural design: The case of Design Track. Automation in Construction 16, 674–684 (2007)
Sommerville, I.: Software Engineering. Pearson/Addison-Wesley (2010)
Soonsongtanee, S., Limpiyakorn, Y.: Enhancement of requirements traceability with state diagrams. In: 2nd International Conference on Computer Engineering and Technology (ICCET), vol. 2, pp. 243–248 (2010)
Spanoudakis, G., Garces, A.A., Zisman, A.: Revising rules to capture requirements traceability relations: A machine learning approach. In: Proceedings of the 15th International Conference in Software Engineering and Knowledge Engineering (SEKE 2003), pp. 570–577 (2003)
Spanoudakis, G., Zisman, A.: Software traceability: a roadmap. Handbook of Software Engineering and Knowledge Engineering 3, 395–428 (2005)
Westfall, L.: Software requirements engineering: what, why, who, when, and how. Software Quality Professional 7(17) (2005)
Winkler, S., von Pilgrim, J.: A survey of traceability in requirements engineering and model-driven development. Software and Systems Modeling 9(4), 529–565 (2010)
Zisman, A., Spanoudakis, G., Perez-Minana, E., Krause, P.: Tracing software requirements artefacts. In: Proceedings of 2003 International Conference on Software Engineering Research and Practice (SERP 2003), Las Vegas, Nevada, USA, pp. 448–455 (2003)
Westfall, L.: Bidirectional Requirements Traceability (2006); The Westfall Team. Web (December 2011), http://www.compaid.com/caiinternet/ezine/westfall-bidirectional.pdf
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this paper
Cite this paper
Chikh, A., Aldayel, M. (2014). Reengineering Requirements Specification Based on IEEE 830 Standard and Traceability. In: Rocha, Á., Correia, A., Tan, F., Stroetmann, K. (eds) New Perspectives in Information Systems and Technologies, Volume 1. Advances in Intelligent Systems and Computing, vol 275. Springer, Cham. https://doi.org/10.1007/978-3-319-05951-8_21
Download citation
DOI: https://doi.org/10.1007/978-3-319-05951-8_21
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-05950-1
Online ISBN: 978-3-319-05951-8
eBook Packages: EngineeringEngineering (R0)