The Elaboration Report is a more detailed version of (and uses the same technical format as) the Preliminary Investigation Report. A detailed design shows a blueprint of HOW to build the information system. The audience for this report is technical users. It will become the basis for your system documentation.
Executive Summary
The Executive summary highlights the following details:
a) the purpose of the this report, refined project scope (major functions)
b) the structural content of this report
c) the anticipated benefits
d) the major recommendations for this phase of the development.
Table of Contents
The Table of Contents shows the structure and organization of this report in the same format as previous reports.
Introduction
The Introduction (1-2 pages) will show the same information as the Preliminary Investigation Report with an updated status of the project and any corrections from the last report. Include ideas in this section and throughout the report to show how the project supports local or global sustainability.
Data Set/Feature Engineering
Use an introductory paragraph describing the content of this section. Define data requirements and feature engineering with specific knowledge of the system on which they will be implemented. If adapting an existing dataset, highlight the new components required by the project (colour code).
Architectural Design
Identify the overall physical nature of the system to be implemented – i.e. web-based application, client/server network application, stand-alone application. Describe what hardware/software (including OS) is in place and what needs to be acquired. Use a diagram to show this high level view of system. If integrating with existing system, highlight the new components required by the project.
Program Design
Start with an introductory sentence to describe the contents of this section and the choice of models. Describe the program components and AI techniques needed.
Provide sections referencing:
1) Cross reference table to list functional requirements and identify associated use case and sequence diagrams.
| Functional Requirement Number | Functional RequirementNarrative | Use Case(s) | Backlog |
| SFR1 | The system shall … | UC1 |
2) Functional descriptions including program design models:
a) SCHEMA OF ENTIRE Dataset
b) Breakdown of the SCHEMA
c) User stories in the format As a _______I need _______ in order to ______
d) Use Case diagrams (high level and elaborated)- numbered UC1, UC2, …
e) High Level Context Diagram of entire system
Recommendations
The Recommendations (1 page) state that system development is feasible and the project should proceed with the next iteration of elaboration and system construction. Specifically state how conversion of the current system (if necessary) will proceed and what type of training will be required by the users of the system.
Appendices
The Appendices include:
a) Corrections from last report.
b) Other project specific material referenced in report (research?)