{"id":{"repo_id":"cape-town","oai_identifier":"oai:open.uct.ac.za:11427/14129"},"canonical_url":"https://search.dev.ndltd.org/etd/cape-town/oai:open.uct.ac.za:11427/14129","repository":{"repo_id":"cape-town","name":"University of Cape Town","base_url":"https://open.uct.ac.za/oai/request"},"display":{"title":"Effective and efficient requirement traceability in the software development and Information Technology industry","abstract":"Requirements traceability has been identified as a quality factor and a characteristic a system should possess and include as a non-functional requirement. Requirements engineering processes should always include methods and tools of maintaining traces and relationships between requirements and product artefacts. To investigate the extent to which requirements traceability is used in software and information technology projects, a theoretical model of requirements traceability was presented in this research. Five organizations were investigated through semi-structured interviews and their requirements tracing practices were compared with the theoretical model. The extent to which organizations apply requirements traceability practices in their projects differs and as a result they were categorised as inactive, dormant and active users in this research. The advent of agile development methods is one of the major factors affecting requirements traceability practices. Among other recommended areas of further research, there is need for future research to look at how agile development and traditional methods can be implemented together in requirement tracing practices.","abstract_html":"Requirements traceability has been identified as a quality factor and a characteristic a system should possess and include as a non-functional requirement. Requirements engineering processes should always include methods and tools of maintaining traces and relationships between requirements and product artefacts. To investigate the extent to which requirements traceability is used in software and information technology projects, a theoretical model of requirements traceability was presented in this research. Five organizations were investigated through semi-structured interviews and their requirements tracing practices were compared with the theoretical model. The extent to which organizations apply requirements traceability practices in their projects differs and as a result they were categorised as inactive, dormant and active users in this research. The advent of agile development methods is one of the major factors affecting requirements traceability practices. Among other recommended areas of further research, there is need for future research to look at how agile development and traditional methods can be implemented together in requirement tracing practices.","abstract_has_math":false,"creators":["Shereni, Tafadzwa"],"institution":"Department of Construction Economics and Management","degree_name":null,"degree_level":null,"degree_discipline":null,"degree_department":null,"school":null,"contributors":[],"advisors":["Jay, Ian"],"committee_chairs":[],"committee_members":[],"year":2015,"date_issued":"2015","date_published":"2015","updated_at":"2026-07-22T22:23:44Z","subjects":[],"languages":["eng"],"rights":[],"rights_urls":[],"identifier_entries":[]},"links":{"outbound_url":"http://hdl.handle.net/11427/14129","outbound_label":"Handle","outbound_source":"dc:identifier.uri"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor.advisor","label":"Advisor","values":["Jay, Ian"]},{"key":"dc:creator","label":"Author","values":["Shereni, Tafadzwa"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date.accessioned","label":"Dc Date Accessioned","values":["2015-09-30T13:42:24Z"]},{"key":"dc:date.available","label":"Dc Date Available","values":["2015-09-30T13:42:24Z"]},{"key":"dc:date.issued","label":"Date","values":["2015"]},{"key":"dc:publisher.department","label":"Dc Publisher Department","values":["Department of Construction Economics and Management"]},{"key":"dc:publisher.institution","label":"Dc Publisher Institution","values":["University of Cape Town"]},{"key":"dc:type","label":"Dc Type","values":["Master Thesis"]},{"key":"dc:type.qualificationlevel","label":"Dc Type Qualificationlevel","values":["Masters"]},{"key":"dc:type.qualificationname","label":"Dc Type Qualificationname","values":["MSc"]}]},{"id":"language_rights","label":"Language and Rights","entries":[{"key":"dc:language.iso","label":"Language (ISO)","values":["eng"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier.uri","label":"Identifier URI","values":["http://hdl.handle.net/11427/14129"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description.abstract","label":"Abstract","values":["Requirements traceability has been identified as a quality factor and a characteristic a system should possess and include as a non-functional requirement. Requirements engineering processes should always include methods and tools of maintaining traces and relationships between requirements and product artefacts. To investigate the extent to which requirements traceability is used in software and information technology projects, a theoretical model of requirements traceability was presented in this research. Five organizations were investigated through semi-structured interviews and their requirements tracing practices were compared with the theoretical model. The extent to which organizations apply requirements traceability practices in their projects differs and as a result they were categorised as inactive, dormant and active users in this research. The advent of agile development methods is one of the major factors affecting requirements traceability practices. Among other recommended areas of further research, there is need for future research to look at how agile development and traditional methods can be implemented together in requirement tracing practices."]},{"key":"dc:title","label":"Title","values":["Effective and efficient requirement traceability in the software development and Information Technology industry"]}]}],"canonical_facts":{"dc:contributor.advisor":["Jay, Ian"],"dc:creator":["Shereni, Tafadzwa"],"dc:date.accessioned":["2015-09-30T13:42:24Z"],"dc:date.available":["2015-09-30T13:42:24Z"],"dc:date.issued":["2015"],"dc:description.abstract":["Requirements traceability has been identified as a quality factor and a characteristic a system should possess and include as a non-functional requirement. Requirements engineering processes should always include methods and tools of maintaining traces and relationships between requirements and product artefacts. To investigate the extent to which requirements traceability is used in software and information technology projects, a theoretical model of requirements traceability was presented in this research. Five organizations were investigated through semi-structured interviews and their requirements tracing practices were compared with the theoretical model. The extent to which organizations apply requirements traceability practices in their projects differs and as a result they were categorised as inactive, dormant and active users in this research. The advent of agile development methods is one of the major factors affecting requirements traceability practices. Among other recommended areas of further research, there is need for future research to look at how agile development and traditional methods can be implemented together in requirement tracing practices."],"dc:identifier.uri":["http://hdl.handle.net/11427/14129"],"dc:language.iso":["eng"],"dc:publisher.department":["Department of Construction Economics and Management"],"dc:publisher.institution":["University of Cape Town"],"dc:title":["Effective and efficient requirement traceability in the software development and Information Technology industry"],"dc:type":["Master Thesis"],"dc:type.qualificationlevel":["Masters"],"dc:type.qualificationname":["MSc"]},"updated_at":"2026-07-22T22:23:44Z"}