Project to be completed by: Monday 30/04/12.
| Background & identification | |
| Description of the current system | |
| Identification of prospective user(s) | |
| Identification of needs & limitations | |
| Interview + other research such as documents | |
| Data sources & destinations | |
| Data volumes | |
| Analysis data dictionary | |
| Data flow diagrams and/or E-R model | |
| Object analysis diagrams, inheritance, aggregation | |
| Numbered general & specific objectives for the proposed system | |
| Feasibility of potential solutions | |
| Justification of chosen solution | |
| Evidence of use of appropriate analysis techniques |
Note that not all aspects of the list below need be included in a particular project: it depends on the nature of your project.
| Overall system design | |
| Modular structure | |
| Data requirements (design data dictionary) | |
| Description of record structure | |
| Validation required | |
| File organisation & processing | |
| Sample of planned SQL queries | |
| Identification of storage material and format | |
| Algorithms for data transformation | |
| Class definitions, object properties & methods (diagrams) | |
| User interface design rationale | |
| UI sample of planned data capture and entry | |
| UI sample of planned valid output designs | |
| Database design (to 3NF/BCNF) and E-R model | |
| Security and integrity of data | |
| System security | |
| Overall test strategy |
This is less structured than other sections. Just get on and code the solution! To be completed by 7/03/11. Brought forward by one week to give more time for testing & documentation.
| Design of test plan | 20/2/12 |
| Minimal set of test data | 20/2/12 |
| Expected results for typical data | 20/2/12 |
| Expected results for erroneous data | 20/2/12 |
| Expected results for extreme data | 20/2/12 |
| Hard copy of test runs | 30/3/12 |
| Cross-referenced to test plan | 30/3/12 |
System Maintenance
| System overview | 16/4/12 |
| Sample of detailed algorithm design | 16/4/12 |
| Annotated program listing | 16/4/12 |
| Procedure and variable lists or package items | 16/4/12 |
User Manual
| Contents page | 16/4/12 |
| Brief introduction | 16/4/12 |
| How to use the system | 16/4/12 |
| Screen displays | 16/4/12 |
| Error messages | 16/4/12 |
Appraisal
| Were the objectives met (from Analysis)? | 30/4/12 |
| Feedback from user e.g. letter, interview | 30/4/12 |
| Suggestions for further improvement/extensions | 30/4/12 |
Quality of Communication
| Contents page | 30/4/12 |
| Clear and logical organisation | 30/4/12 |
| Set out in sections identified in specification | 30/4/12 |
| Page numbers | 30/4/12 |
| Continuous prose | 30/4/12 |
| Good use of English | 30/4/12 |
| Word-processed, clear fonts | 30/4/12 |
| Appropriate word processing techniques | 30/4/12 |