Abstract
ABSTRACTIdeally, there should always be an isomorphic mapping between the collection of requirements (system, software, etc.) and the collection of software which is intended to satisfy those requirements. This would normally always be the case with custom developed software. But with the increased use of various types of Non‐Development Items (NDI) (e.g. COTS, GOTS, Reusable code, GFE), there is an increasing possibility that such NDI will include functionality for which there is no requirement. This non‐required or non‐specified type of software functionality will be referred to as Dormant Code (DC). This paper will focus on issues and problems caused by DC and will offer some approaches to address these issues.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
