P4DTI issue job000272

TitleSource code doesn't refer to its documentation
Statusclosed
Priorityessential
Assigned userRichard Brooksby
Productproject
OrganizationRavenbrook
DescriptionThe Integrator's Guide and the design documents refer to the code in some detail, but the code doesn't refer back. This means that developers may forget to bring the manuals and design up to date when they change the code.
AnalysisAll modules need to have introductions that set out the requirements that the module is designed to meet. They should also be formatted as documents.
Go through the Integrator's Guide. Whenever it refers to the code, make references back from the code to the manual. Similarly for the design documents.
How foundinspection
Evidence<http://info.ravenbrook.com/mail/2001/03/22/16-24-46/0.txt>
Observed in1.0.5
Introduced in1.0.0
Created byGareth Rees
Created on2001-03-22 17:25:37
Last modified byGareth Rees
Last modified on2010-10-06 21:38:41
History2001-03-22 GDR Created.

Fixes

Change Effect Date User Description
23598 closed 2001-10-28 21:16:22 Gareth Rees Formatted Bugzilla modules as documents.