Project description
69-60<br />
Most required features and functions have their purpose defined with an awareness that there will be a different audience for some elements<br />
process diagrams are presented for major functions<br />
An Entity-Relationship Diagram, including most attributes and many clear relationships<br />
Details of most of the queries needed, how they might look and explanation as to why most of them are needed<br />
Clear and consistent designs for many of the forms and reports with indications who would use them and special features identified<br />

Consideration of the main user is clear including their likely skill level. <br />
A range of strategies are proposed to ensure data is valid <br />
A variety of error handling processes are proposed to avoid application crashes. The user is supported in some cases<br />
Clear. Covering most processes, error messages <br />
Some special features such as macros, vb code or other feature explained <br />
Clear, full and systematic testing evidenced for many aspects<br />
Honest reflection of many aspects of the database against the proposal<br />
69-60<br />
Described with many issues identified<br />
Purpose and many functions described Different audiences identified for many functions<br />
<br />
—<br />
Referencing Requirements:<br />
1. Analyse and represent an information system using data models <br />
2. Interrogate the data in a database<br />
3. Create a useable interface incorporating input and output<br />
4. Understand the implications of data security<br />
<br />
Task 1: To submit a proposal outlining the problem and suggested solution. (5% of the total marks for this assignment)<br />
Addressing learning outcome 1:<br />
1. Analyse and represent an information system using data models<br />
This initial statement of requirements should be about 400 words in length and must be agreed by the tutor before progression. It should outline, in non-technical language, the purpose of the database and what functions it is required to perform.<br />
Task 2: To document the design and solution (45% of the total marks for this assignment)<br />
Addressing learning outcomes 1 and 4: <br />

The documentation to consist of <br />
1b) Systems analysis (3 marks)<br />
After the initial statement has been agreed, a detailed systems analysis should be carried out, to determine in detail the required features and functions of the system. <br />
<br />
2) Design (12 marks)<br />
This will include a detailed Entity-Relationship Diagram, including attributes, together with details of queries needed, and designs for forms and reports. Consideration must be given to how users will operate the database, the sophistication of the users and how you propose to eliminate errors and maintain security of data.<br />
3) User Instructions (6 marks)<br />
Appropriate instructions for users on how to accomplish the various tasks within the database<br />
4) Technical Documentation (4 marks)<br />
For someone who may need to amend the database design: An explanation of any special features such as event coding, properties of controls etc<br />
5) Evidence of testing the database (10 marks)<br />
Documentary evidence that you have created adequate test data and satisfactorily tested the database. The test data should include an appropriate number of records and a suitable range of data.<br />
6) Evaluation of the final database (6 marks)<br />
Does it do what you set out in your initial proposal (requirements analysis)? What aspects need to be corrected, amended or completed? How could this database be improved?<br />
Part 3: To create a working database that meets the proposal (with Tutor amendments if required) (50% of the total marks for this assignment)<br />
Addressing learning outcomes 2, 3 and 4