ITPEC IP October 2018 Question 99

Clear relationships between documents allow their consistency to be checked, which improves quality — documents in development and maintenance must be traceable to each other.

Requirements, design documents, programs and test specifications each derive from the one before. When each item states which item it comes from, a reviewer can check that every requirement is designed, built and tested, and that a change to one document is carried through to the others. Omissions and contradictions are found early, before they become defects.

Answer (b)

Why not others:

• •(a) — itemized lists, tables and charts usually make structure and content clearer than long natural-language text, so they should be used
• •(c) — duplicated content has to be changed in several places, and a missed copy leaves the documents inconsistent; redundancy lowers maintainability
• •(d) — documents are used for years by maintenance personnel who did not write the software, so they must be understandable to them, not mainly to the developers

Key rule: Good development documents are clear, non-redundant and traceable to each other, written for the people who will maintain the software later.

System Development Technology · AI-written, may contain errors