University of Limerick Institutional Repository

Design through documentation: the path to software quality

DSpace Repository

Show simple item record

dc.contributor.author Parnas, David Lorge
dc.date.accessioned 2009-03-03T14:30:15Z
dc.date.available 2009-03-03T14:30:15Z
dc.date.issued 2003
dc.identifier.uri http://hdl.handle.net/10344/121
dc.description non-peer-reviewed
dc.description.abstract In traditional engineering design, preparation of a sequence of documents precedes the actual construction begins. Each document is used for review and analysis and, after revision, serves as input to the next phase in the development. When errors are discovered or changes are required, the design documents previously approved are updated and reviewed again. Each new document is reviewed against the previous documents. Whenever a document is revised, those based on it are reviewed and revised if necessary. In software design this approach is rarely properly applied. Practitioners seem unable or willing to write the precise documents that would be required. Instead, they write vague statements that cannot be subject to rigorous analysis and are of little value to those making the next decisions. We will provide precise definitions of a set of software documents and how these documents can be produced as part of an improved software development process. en
dc.language.iso eng en
dc.subject documentation en
dc.title Design through documentation: the path to software quality en
dc.type Report en
dc.type.supercollection all_ul_research en
dc.type.restriction none en
dc.contributor.sponsor SFI


Files in this item

This item appears in the following Collection(s)

Show simple item record

Search DSpace


Browse

My Account

Statistics