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
Q. Explain about Software Risks - Dependencies? Dependencies: -Many risks arise because of dependencies of project on outside agencies or factors. It isn't easy to control thes

Q. Usual stages of the simplified design process? Pre-production design Design brief it is an early often the beginning statement of design goals Analysis i

Distinguish software faults and software failures Ans: In case of a failure, the software does not do what the user expects. A fault is a programming error that may or may not

What is a vertical microinstruction? Ans) A vertical microinstruction is a microinstruction that states one of a sequence of operations required to carry out a machine language

What is Branch coverage? Ans) Test coverage criteria which needs that for each decision point each possible branch be implemented at least once. Syn: decision coverage. Contrast

QUESTION (a) Compare the worker pool multi-threading architecture with the thread-per-request architecture. (b) What thread operations are the most significant in cost? (

Use the Newton divided-di_erence method to construct interpolating polynomials of degree one, two, and three for the following data. Approximate f(0.18) using each of the polynomia

Glass box testing is the similar as white box testing. It's a testing approach that consider the application's program structure, and derives test cases from the application's prog

I have a comprehensive question in this course need to solve

Explain the term - Code Complete - Phase of development where functionality is implemented completely with only bug fixes remaining. - All functions from functional specific