Identifying commonality features of fine grain artefacts for a software traceability approach

Changes are inevitable for the software to evolve. User change requirements can occur to any phases of software development and the development of software artefacts such as documents, classes, methods, data elements, test cases, test suites, and etc. Linking all the possible artefacts of software development requires a good traceability approach. A traceability approach is an essential to cope up with changes in maintenance process. Poor traceability approach during maintenance process will result the entire affected artefacts becoming obsolete. Current traceability approaches and tools have limited features such as lack of support at fine grain level as opposed to file structure/ coarse grain level, lack of software artefacts coverage across the entire phases of software development lifecycle. This paper presents a finding concerning traceability features in an approach for fine grain software artefacts