Show simple item record

dc.contributor.authorHenry, Sallie M.en_US
dc.contributor.authorWake, Steven A.en_US
dc.contributor.authorLi, Weien_US
dc.date.accessioned2013-06-19T14:36:36Z
dc.date.available2013-06-19T14:36:36Z
dc.date.issued1992-05-01
dc.identifierhttp://eprints.cs.vt.edu/archive/00000339/en_US
dc.identifier.urihttp://hdl.handle.net/10919/19777
dc.description.abstractSoftware metrics attempt to uncover difficult or complex components of a software system. The hypothesis is that complex components are more difficult to understand, hence they are hard to maintain and more prone to error. Discovery of these complex components can aid the software developer in selecting which components to redesign, direct the testing effort, and indicate the maintenance effort required. Previous studies have demonstrated two main concepts: (1) there exists a high correlation between design complexity and source code complexity, and (2) metrics applied to source code have a high correlation to the maintenance activity needed. This previous research motivates us to develop a methodology which uses complexity metrics throughout the software life cycle. Programmer productivity may be increased and software development cost may be reduced if error prone software is discovered early in the life cycle.en_US
dc.format.mimetypeapplication/pdfen_US
dc.publisherDepartment of Computer Science, Virginia Polytechnic Institute & State Universityen_US
dc.relation.ispartofHistorical Collection(Till Dec 2001)en_US
dc.titleThe Use of Complexity Metrics Throughout the Software Lifecycleen_US
dc.typeTechnical reporten_US
dc.identifier.trnumberTR-92-59en_US
dc.type.dcmitypeTexten_US
dc.identifier.sourceurlhttp://eprints.cs.vt.edu/archive/00000339/01/TR-92-59.pdf


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record