A TABLE OF CONTENTS identifying sections of the report as well as the corresponding page numbers. Please number your sections and make sure that your first section (your introduction) is number 1. 3...

A TABLE OF CONTENTS identifying sections of the report as well as the corresponding page numbers. Please number your sections and make sure that your first section (your introduction) is number 1.


3    An INTRODUCTION to the report (that contains, at least, the background to the report and a paragraph that tells the reader what to expect to read about in the report).


4    A section on PLANNING containing the following:
4.1    Strategic planning factors (organisational goals/objectives, critical success factors, and problem areas).
4.2    A functional decomposition diagram outlining the core processes (i.e. the forms and reports) of the application.
4.3    A list of the pairs of relationship structural business rules along with justifications that are explicitly derived from the sources. There are only two possible sources: 1) direct quotes (not implications) from the requirements and 2) clarification received from the client.
Note: a relationship, in this context, is defined by the line drawn between 2 entities or the line drawn from one entity back to itself. So, if your conceptual ERD has 8 relationships then your list must contain 8 pairs of business rules.
4.4    A conceptual entity-relationship diagram (ERD) directly derived from your pairs of relationship structural business rules.
4.5    A conceptual level business function (process) to data entity planning matrix that cross references the processes defined in your functional decomposition diagram with the entities defined in your conceptual entity-relationship diagram.


5    A section on the LOGICAL DESIGN containing the following:
5.1    One normalised logical entity-relationship diagram (ERD) with a set of relations (in standard relation notation) showing primary keys, foreign keys and non-key attributes (please note that lookup tables are only required for fields where there are more than five possible choices).
5.2    Eight    detailed normalised entity-relationship diagrams (each with a set of relations (in standard relation notation) that only lists those attributes required for that process), one for each of the eight main processes.
5.3    For each table in the logical design a data dictionary, containing details (field name and field description only).