First-cut entity relationship, Software Engineering

A University has asked you to design and implement a simple database to store student and module details (including details of which school students belong to and which schools run which module), upon student enrolment. Students are enrolled as a member of a school (e.g. School of Mathematics and Computer Science), whilst also being enrolled onto a number of modules, student contact details are also required. The modules a student may be enrolled onto are run by schools (e.g. Introduction to Information Systems is run by the School of Mathematics and Computer Science), with students limited to modules that are run by the school that they belong to. While designing and implementing the database system (following the steps below), you should apply common sense and make any necessary minor administrative decisions. You work report is to document your work in carrying out the following steps, and include sufficient information about the system implemented (as well as its design) that it can be understood without difficulty.

1. Produce a first-cut Entity Relationship (ER) Diagram for the system.

2. Carry out the Relational Data Analysis procedure from the "Structured System Analysis and Design" (PDF file). Include details for each normal form, and the resulting ER Diagram.

3. Compare your ER Diagrams from steps 1 and 2. Comment on any differences and make any changes you consider necessary to produce a final ER Diagram. Should there be no differences, instead discuss what differences there could have been.

4. Following the example from the (PDF file) on databases use your ER Diagram to produce a Relational Database Schema, and include in your report each table complete with a small set of realistic but imaginary sample data: between five and fifteen records per table.

5. Implement your database in Microsoft Office Access, complete with this sample data. Remember to use appropriate data types and to implement necessary relationships.

6. Design, and implement in Microsoft Office Access, forms for the entry of data into the database. Include screenshots of sample forms as an appendix in your report.

7. Design, and implement in Microsoft Office Access 2003, a report that summarizes the number of students on each module. Include a sample report (output) as an appendix in your report.

8. Conclude your work report with a section that evaluates the strengths and weaknesses of the system, how it could be improved and what you would do differently 'next time'.

Posted Date: 3/6/2013 1:46:12 AM | Location : United States







Related Discussions:- First-cut entity relationship, Assignment Help, Ask Question on First-cut entity relationship, Get Answer, Expert's Help, First-cut entity relationship Discussions

Write discussion on First-cut entity relationship
Your posts are moderated
Related Questions
Handling customer complaints There are always some customers who complain after completing the sales. Like customer objections, don't take complaints negatively. Other than

Define maintenance. Maintenance is defined as the procedure in which changes are executed by either modifying the existing system's architecture or by adding new mechanism to t

What are the misunderstanding arise in software development Some of the common misunderstandings regarding software development are given below. 1.  Correcting errors is eas

Mention some of the drawbacks of RAD model. Not suitable for largescale projects. Commitment of developers & customers are required. Not appropriate when technical ris

A set of people, machines, and methods prepared to accomplish a set of specified functions.


I am not properly understanding the basis difference between black box testing and white box testing. Please explain in simple way and with some example so that I can easily under

What are the various testing strategies for conventional software? i. Unit testing ii. Validation testing. iii. Integration testing. iv. System testing.

System evolution of life cycle process The lifetime of verge systems is too long. They must evolve to meet change requests. The evolution may be expensive. Existing sy