Requirements of a system keep on changing based on the need of stakeholders or the system developers, making requirement engineering an important aspect in software development. This develops a need for appropriate requirement change management. The importance of requirements traceability is defining relationships between the requirements and artefacts extracted by the stakeholder during the software development life-cycle and gives vital information to encourage software understanding. In this paper, we have concentrated on developing a tool for requirement traceability that can be used to extend the requirement elicitation and identification of system-wide qualities using the notion of quality attribute scenarios to capture the non-functional requirements. It allows us to link the functional and non-functional requirements of the system based on the quality attribute scenarios template proposed by the Carnegie Mellon Software Engineering Institute (SEI). Apart from this, the paper focuses on tracing the functional and non-functional requirements of the system using the concept of requirement traceability matrix.
References
[1]
Nuseibeh, B. and Easterbrook, S. (2000) Requirements Engineering: A Roadmap. ICSE’00 Proceedings of the Conference on the Future of Software Engineering, Limerick, Ireland, 4-11 June 2000, 35-46. https://doi.org/10.1145/336512.336523
[2]
Mader, P., Jones, P.L., Zhang, Y. and Cleland-Huang, J. (2013) Strategic Traceability for Safety-Critical Projects. IEEE Software, 30, 58-66.
https://doi.org/10.1109/MS.2013.60
[3]
Pandey, S., Pokharel, S. and Hassan, R. (2018) Towards Cyber-Physical Requirement Engineering Elicitation Tool Support. 2018 World Automation Congress (WAC), Stevenson, WA, 3-6 June 2018, 1-5.
https://doi.org/10.23919/WAC.2018.8430399
[4]
Ward, J. and Daniel, E. (2006) Benefits Management: Delivering Value from IS & IT Investments. John Wiley & Sons, Chichester.
[5]
Barbacci, M.R., Ellison, R., Lattanze, A.J., Stafford, J.A., Weinstock, C.B. and Wood, W.G. (2002) Quality Attribute Workshops. Technical Report, CARNEGIE-MELLON UNIV PITTSBURGH PA SOFTWARE ENGINEERING INST.
https://doi.org/10.21236/ADA405790
[6]
Cheng, B.H.C. and Atlee, J.M. (2007) Research Directions in Requirements Engineering. 2007 Future of Software Engineering, Minneapolis, MN, 23-25 May 2007, 285-303. https://doi.org/10.1109/FOSE.2007.17
[7]
Kotonya, G. and Sommerville, I. (1998) Requirements Engineering: Processes and Techniques. Wiley Publishing, Hoboken, NJ.
[8]
Van Lamsweerde, A. (2009) Requirements Engineering: From System Goals to UMl Models to Software. John Wiley & Sons, Chichester.
[9]
Barbacci, M., Klein, M.H., Longstaff, T.A. and Weinstock, C.B. (1995) Quality Attributes. Technical Report, CARNEGIE-MELLON UNIV PITTSBURGH PA SOFTWARE ENGINEERING INST. https://doi.org/10.21236/ADA307888
[10]
Chung, L., Nixon, B.A., Yu, E. and Mylopoulos, J. (2012) Nonfunctional Requirements in Software Engineering. Springer Science & Business Media, Berlin.
[11]
Chung, L. and do Prado Leite, J.C.S. (2009) On Non-Functional Requirements in Software Engineering. In: Borgida, A.T., Chaudhri, V., Giorgini, P. and Yu, E., Eds., Conceptual Modeling: Foundations and applications, Springer, Berlin, 363-379.
https://doi.org/10.1007/978-3-642-02463-4_19
[12]
Tang, A. and Van Vliet, H. (2009) Modeling Constraints Improves Software Architecture Design Reasoning. 2009 Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture, Cambridge, UK, 14-17 September 2009, 253-256. https://doi.org/10.1109/WICSA.2009.5290813
[13]
Bass, L., Clements, P. and Kazman, R. (2003) Software Architecture in Practice. Addison-Wesley Professional, Boston, MA.
[14]
O’Brien, L., Merson, P. and Bass, L. (2007) Quality Attributes for Service-Oriented Architectures. Proceedings of the International Workshop on Systems Development in SOA Environments (SDSOA'07: ICSE Workshops 2007), Minneapolis, MN, 20-26 May 2007, 3. https://doi.org/10.1109/SDSOA.2007.10
[15]
Reza, H., Korvald, C., Straub, J., Hubber, J., Alexander, N. and Chawla, A. (2016) Toward Requirements Engineering of Cyber-Physical Systems: Modeling CubeSat. 2016 IEEE Aerospace Conference, Big Sky, MT, 5-12 March 2016, 1-13.
https://doi.org/10.1109/AERO.2016.7500897
[16]
Reza, H., Sehgal, R., Straub, J. and Alexander, N. (2017) Toward Model-Based Requirement Engineering Tool Support. 2017 IEEE Aerospace Conference, Big Sky, MT, 4-11 March 2017, 1-10. https://doi.org/10.1109/AERO.2017.7943647
[17]
Egyed, A. and Grunbacher, P. (2005) Supporting Software Understanding with Automated Requirements Traceability. International Journal of Software Engineering and Knowledge Engineering, 15, 783-810.
https://doi.org/10.1142/S0218194005002464
[18]
Nair, S., De La Vara, J.L. and Sen, S. (2013) A Review of Traceability Research at the Requirements Engineering Conferencere@21. 2013 21st IEEE International Requirements Engineering Conference (RE), Rio de Janeiro, 15-19 July 2013, 222-229.
https://doi.org/10.1109/RE.2013.6636722
[19]
Gotel, O., Cleland-Huang, J., Hayes, J.H., Zisman, A., Egyed, A., Grunbacher, P., Dekhtyar, A., Antoniol, G., Maletic, J. and Mader, P. (2012) Traceability Fundamentals. In: Cleland-Huang, J., Gotel, O. and Zisman, A., Eds., Software and Systems Traceability, Springer, Berlin, 3-22.
https://doi.org/10.1007/978-1-4471-2239-5_1
[20]
Gotel, O.C.Z and Finkelstein, C.W. (1994) An Analysis of the Requirements Traceability Problem. Proceedings of IEEE International Conference on Requirements Engineering, Colorado Springs, CO, 18-22 April 1994, 94-101.
[21]
(2018) Your Requirements Engineering Tool. Requirements Management Software. Online. http://www.visuresolutions.com/requirementsengineering.
[22]
(2018) Modern Requirements. Requirements Definition and Management. Online. http://www.modernrequirements.com/integreat/.
[23]
de Gea, J.M.C., Nicolás, J., Fernández Alemán, J.L., Toval, A., Ebert, C. and Vizcaíno, A. (2012) Requirements Engineering Tools: Capabilities, Survey and Assessment. Information and Software Technology, 54, 1142-1157.
https://doi.org/10.1016/j.infsof.2012.04.005
[24]
Reza, H., Jurgens, D., White, J., Anderson, J. and Peterson, J. (2005) An Architectural Design Selection Tool Based on Design Tactics, Scenarios and Nonfunctional Requirements. 2005 IEEE International Conference on Electro Information Technology, Lincoln, NE, 22-25 May 2005, 6.
[25]
dos Santos Romani, M.A., Lahoz, C.H.N. and Yano, E.T. (2010) Identifying Dependability Requirements for Space Software Systems. Journal of Aerospace Technology and Management, 2, 287-300. https://doi.org/10.5028/jatm.2010.02037810
[26]
Egyed, A. and Grunbacher, P. (2002) Automating Requirements Traceability: Beyond the Record & Replay Paradigm. Proceedings of the 17th IEEE International Conference on Automated Software Engineering, Edinburgh, UK, 23-27 September 2002, 163-171.
[27]
Pohl, K. (1996) PRO-ART: Enabling Requirements Pre-Traceability. Proceedings of the Second International Conference on Requirements Engineering, Colorado Springs, CO, 15-18 April 1996, 76-84.
[28]
David, C., Dekhtyar, A. and Hayes, J. (2010) Automated Requirements Traceability: The Study of Human Analysts. 2010 18th IEEE International Requirements Engineering Conference, Sydney, 27 September-1 October 2010, 231-240.
https://doi.org/10.1109/RE.2010.35
[29]
Gregoriades, A. and Sutcliffe, A. (2005) Scenario-Based Assessment of Nonfunctional Requirements. IEEE Transactions on Software Engineering, 31, 392-409.
https://doi.org/10.1109/TSE.2005.59
[30]
Hall, R.J. (2008) A Method and Tools for Large Scale Scenarios. Automated Software Engineering, 15, 113-148. https://doi.org/10.1007/s10515-008-0026-8
[31]
Bashir, M.F. and Qadir, M.A. (2006) Traceability Techniques: A Critical Study. 2006 IEEE International Multitopic Conference, Islamabad, Pakistan, 23-24 December, 265-268.
