Commenced in January 2007
Frequency: Monthly
Edition: International
Paper Count: 30067
Impact Analysis Based on Change Requirement Traceability in Object Oriented Software Systems

Authors: Sunil Tumkur Dakshinamurthy, Mamootil Zachariah Kurian

Abstract:

Change requirement traceability in object oriented software systems is one of the challenging areas in research. We know that the traces between links of different artifacts are to be automated or semi-automated in the software development life cycle (SDLC). The aim of this paper is discussing and implementing aspects of dynamically linking the artifacts such as requirements, high level design, code and test cases through the Extensible Markup Language (XML) or by dynamically generating Object Oriented (OO) metrics. Also, non-functional requirements (NFR) aspects such as stability, completeness, clarity, validity, feasibility and precision are discussed. We discuss this as a Fifth Taxonomy, which is a system vulnerability concern.

Keywords: Artifacts, NFRs, OO metrics, SDLC, XML.

Digital Object Identifier (DOI): doi.org/10.5281/zenodo.1339592

Procedia APA BibTeX Chicago EndNote Harvard JSON MLA RIS XML ISO 690 PDF

References:


[1] Dean Leffingwell and D. Widrig “The Role Requirements Traceability in System Development”, Rational Software 2002.
[2] Mohamamd Farahan Bashir, Muhammad Abdul Qadir, “Traceability Techniques: A Case Study”, IEEE 2006, pp.265-268.
[3] M. Ajmal Chaumun, Hind Kabaili, Rudolf K. Keller and Francois Lustman, “A Change Impact Model for Changeability Assessment in object-Oriented Software System”, NSERC and NSC, Canada 2000.
[4] Martin Glinz, “On Non-Functional Requirements”, Proceedings of the 15th IEEE International Requirements Engineering Conference, Delhi, India,2007.
[5] S. Kang, “A Formal Requirementation of Platform Feature-to-Requirement Traceability for Software Product Line Development,” Computer Software and Applications Conference (COMPSAC),2014, IEEE 38th Annual Conference.
[6] P. Rempel, “An empirical study on project specific traceability strategies” IEEE International Conference, Requirements Engineering Conference (RE), 2013.
[7] N. Ali, “Trust-Based Requirements Traceability” IEEE 19 th International Conference on Program Comphrension (ICPC).
[8] Lawrence Chung, Brian A. Nixon, Eric Yu John Mylopoulos – Non-Functional Requirements in Software Engineering, Springer Scinece + Business Medica, LLC.
[9] Suhel Ahmad Khan, Raees Ahmad Khan, “Analyzability Quantification Model of Object Oriented Design,” ScienceDirect, Procedia Technology 4(2012)536-542, doi:10.1016/j.protcy.2012.05.085.
[10] I. Somerville. (2007) Software engineering (8th ed.). Boston: Pearson education.
[11] T D Sunil, M Z Kurian, “A Methodology to Evaluate Object-Oriented Software Systems Using Change Requirement Traceability Based on Impact Analysis”, International Journal of Software Engineering & Application (IJSEA), Vol.5, No.3, May 2014.
[12] De. Weck, O.L Roos, D., & Magee, C.L. (2011) Engineering systems: Meeting human need in a complex technological work, Cambridge: MIT Press.
[13] Kevin MacG. Adams “Topics in Safety, Risk, Reliability and Quality”, Non-functional Requirements in Systems Analysis and Design, Springer International Publishing Switzerland 2015.
[14] Lian. Wen, R Geoff. Dromey “From Requirements Change to Design Change: A Formal Path”, World Appl.Sci.J.28(10):1366-1374,2013.