Scribd
Upload
221 views12 pages

Assignment Report Template

This document outlines an assignment to design a database for managing a clinic called Klinik Sejahtera. Students are asked to complete two parts: (1) design the database including an entity relationship diagram and business rules, and (2) implement the database in Microsoft Access including tables, queries, forms, reports, and a switchboard. The marking scheme evaluates students on properly designing the database, implementing tables and records, creating useful queries, forms, and reports, and developing a switchboard to navigate the database objects.

Uploaded by

Brady Honyuonn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
221 views12 pages

Assignment Report Template

This document outlines an assignment to design a database for managing a clinic called Klinik Sejahtera. Students are asked to complete two parts: (1) design the database including an entity relationship diagram and business rules, and (2) implement the database in Microsoft Access including tables, queries, forms, reports, and a switchboard. The marking scheme evaluates students on properly designing the database, implementing tables and records, creating useful queries, forms, and reports, and developing a switchboard to navigate the database objects.

Uploaded by

Brady Honyuonn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 12

UCCD1203 DATABASE DEVELOPMENT

AND APPLICATIONS
Assignment for Jan 2023

Group No:

N Student ID Name Program Lecture Signature


o Class
1.
2.
3.
4.

Marking Section:

Section Marks

Part A
Part B

TOTAL
MARKING SCHEME

The Klinik Sejahtera Case Study

Check list for Part A – Database Design (5%)

Study the user requirements of the Klinik Sejahtera given in this document.
1. Introduction (5 marks)
Describe the system overview, 3 main objectives of this project, and the list
of database user.

2. ER model (15 marks)


You are required to design an ER diagram for the case study given, identify
entities, identify relationships, identify associate attribute and determine
keys. Check the ERD with the requirements stated in the case. Resolve all the
many-many relationships.

3. Business Rule Requirements (10 marks)


Identify the business rule involve based on the ERD. Please include any
assumptions that you make.

4. Report (5 marks)
Submit your report with proper technical report writing skills (cover page,
headers & footers, page numbering, headings, sections numbering, proper
fonts, spell checked, proper alignments, spacing, marking scheme, table of
contents etc).

SUBTOTAL:
Check list for Part B – The Implementation of Database using Microsoft Access (5%)

1. Tables and records (15 marks)


Create all the relations in the ERD and insert the necessary records. (at least
10 records per table except staff records)

2. Queries (15 marks)


Create 3 useful queries based on the given case study and include the
corresponding SQL command. Explain the purpose of each query.

3. Forms (15 marks)


Create 3 useful forms based on the given case study. You may use
subform(s). Explain the purpose of each form. Include colours/images to
make your form look interesting.

4. Reports (15 marks)


Create 3 useful reports based on the given case study. Explain the purpose of
each form. Design your reports so that it will look proper and easy to
understand.

5. Switchboard (5 marks)
Create a switchboard that includes all the tables, forms, queries and reports.
Make sure the switchboard can start automatically when the database is
open, and include an exit button allowing user to quit the database.

SUBTOTAL:
TABLE OF CONTENTS

FRONT PAGE i
MARKING SCHEME ii
TABLE OF CONTENTS iv
LIST OF FIGURES v
LIST OF TABLES vi

CHAPTER 1 PROJECT BACKGROUND 1


1.1 System Overview
1.2 Project Objectives
1.3 Target Database User

CHAPTER 2 DATABASE DESIGN


2.1 List of entities and attributes
2.2 Entity Relationship Diagram (ERD)
2.3 Assumptions and Business Rules

CHAPTER 3 DATABASE DEVELOPMENT


3.1 List of tables
3.1.1 Data Dictionary and Table Records
3.1 Switchboard

CHAPTER 4 DATABASE OBJECTS


4.1 Queries
4.2 Forms
4.1 Reports

CHAPTER 5 CONCLUSION
5.1 System Weakness
5.2 Future Improvement
LIST OF FIGURES

Figure Number Title Page

Figure 1.1
Figure x.x
Figure x.x
Figure x.x
Figure x.x
Figure x.x
LIST OF TABLES

Table Number Title Page

Table 1.1
Table x.x
Table x.x
CHAPTER 1

Project Background
In this chapter, we present the ……
The outline of the report ………

1.1 System Overview


This project is designed and developed for ….

1.2 Project Objectives


i. Objective 1
ii. Objective 2
iii. Objective 3

1.3 Target Database User


The targeted user for this database ….
CHAPTER 2

Database Design

2.1 List of entities and attributes

Entity Attributes

2.2 Entity Relationship Diagram (ERD)

2.3 Assumptions and Business Rules

a) List of assumptions
b) List of business rules (according to ERD)
CHAPTER 3

Database Development

3.1 List of Tables


In this project, tables involve including ….

3.1.1 Data Dictionary and Table Records

a) Table name
- Data dictionary
- Table records
b) Table name
- Data dictionary
- Table records
c) Table name
- Data dictionary
- Table records

3.2 Switchboard

Switchboard in Microsoft Access is …. (include the screenshot of the switchboard)


CHAPTER 4

Database Objects
Database object is …

4.1 Queries
Queries are used for …
4.1.1 Query 1
Explanation:
Sample query 1:

4.1.2 Query 2
Explanation:
Sample query 2:

4.1.3 Query 3
Explanation:
Sample query 3:

4.2 Forms
Forms are used for …
4.2.1 Form 1
Explanation:
Sample form 1:

4.2.2 Form 2
Explanation:
Sample form 2:

4.2.3 Form 3
Explanation:
Sample form 3:
4.3 Report
Reports are used for …
4.3.1 Report 1
Explanation:
Sample report 1:

4.3.2 Report 2
Explanation:
Sample report 2:

4.3.3 Report 3
Explanation:
Sample report 3:
CHAPTER 5

Conclusion

5.1 System Weakness

5.2 Future Improvement

You might also like