A PAT-only subtopic (not examinable in the written papers) covering the professional documents that should accompany a complete software project.
| Document | Purpose |
|---|---|
| Specification Document | Defines WHAT the software must do — the requirements, from the client/user's perspective |
| Design Document | Defines HOW the software will meet those requirements — planned classes, data structures, interface layout, algorithms |
| Technical Document | Describes the technical implementation details — how the system was actually built, for future developers/maintainers |
| Testing Document | Records the test plan, test data used (standard/extreme/abnormal), and the results of testing |
💡 Exam Tip
Think of these four documents as following the natural project lifecycle: Specification (what's needed) → Design (how it'll be built) → Technical (how it actually was built) → Testing (proof that it works) — a complete PAT should be able to show evidence of all four.