ISOM5260代做、代写SQL程序、代做SQL设计报告、代写SQL语言程序

日期：2018-10-07 09:56

ISOM5260: Project Introduction

Note: This project is recommended for students who have taken Database Management courses in their

Undergraduate/Postgraduate studies or have practical experience working on Databases.

Due Date: Oct 20, 2018

You are required to build a simple information system with graphical user interface and a database, and

also to compile valuable managerial information from the database using SQL. You may choose to build

with any database product like Microsoft Access, Oracle, MySQL, etc. The steps are explained briefly as

follows:

1. Identifying the functional requirements of the Student Admission System

The system should involve 5-7 entities in the E-R diagram or at least 10 tables in the relational

database. The following data has to be captured by the system: Applicants’ personal data, academic

background and working experience, the programme information to be chosen by applicants,

application results, etc. You should also document the scope and business values of the system, other

requirements can be documented if necessary.

2. Conceptual Data Modeling

After identifying entities and attributes, make use of E-R model to show the relationship among

entities. Note that the E-R model is to be shown in the attribute level, while all entities, attributes,

primary keys, maximum and minimum cardinalities are to be shown. You can make use of Microsoft

Visio for drawing the E-R model. You may also consider using Computer Aided Software Engineering

(CASE) tools, for instance, Toad Data Modeler, to build the E-R model.

A list of business rules and assumptions that must be enforced in the database are required to be

documented in detail.

3. Create a logical database design and physical database development

From the basis of the E-R model you created, develop a Relational Schema of the database. As a logical

database design, show all functional dependencies in the database. Normalization is to be performed

in logical database design, if necessary. The logical database design should be normalized into third

normal form (3NF). In the meantime, you may also want to document any further assumptions,

constraints and business rules.

4. Input records to each of the tables

There are no absolute requirements on how much data should be in tables of the database, however,

you should input adequate records to facilitate queries and reports generation. Input the records into

the database using INSERT INTO statements of SQL.

ISOM 5260 Project Description Page 2 of 3

5. Setup queries using SQL

Create 10-15 sets SQL statements in which you feel users may find useful in their operations.

Document the SQL statements and state the purposes. Besides basic SQL statements, you should also

write up advanced SQL statements like processing multiple tables. Aggregation functions may be

applicable in dealing with numbers in tables.

Note: The above descriptions are appeared as a basic requirement of the project. You can have more

deliverables as you wish.

ISOM 5260 Project Description Page 3 of 3

Basic Deliverables

- A hardcopy and softcopy of documentation showing the following:

1. Project Initiation Document

Business Values of the system

Briefly mention the reasons of supporting the development of this new database

system and to determine what benefits the system will bring users, or other

stakeholders.

Scope of the system

Briefly describe the basic requirements on how the system is going to perform

State any other requirements if necessary

2. Design Specification

Conceptual Data Model - E-R model and Business Rules

Present the finalized E-R diagram and provide necessary explanations of the model,

such as why specific entity class, relationships and attributes are modeled in your

model. State all the business rules, constraints and assumptions you made that must

be enforced in the database system

Logical Data Model - Relational Schema

You should map the E-R diagram into relations, normalize the relations into 3NF.

Show all the functional dependencies for every relation and claim which normal form

each relation is in

Data Dictionary

Explain all relations including their attributes, keys and foreign keys

Show the description of all tables in the database

3. Configuration Specification

SQL Statements configurations and specifications

Document all SQL statements (10-15 sets) you used in the database, explain the SQL

statements and describe how these statements are useful in users’ perspective

4. A brief conclusion showing any thoughts you have on the project, such as, suggestions and

comments for further development.

- A workable database

Note: If you choose Oracle database as your platform for the substitute project, a new Oracle

database account, password and connection string will be provided. You do not need to build the

substitute project using your OWN database.