Assignment Brief

BTEC Level 4-5 HNC/HND Diploma (QCF)

To be filled by the Learner
Name of the Learner :
Edexcel No
Date of Submission

:
:

Centre No

Batch:

Unit Assessment Information

Qualification
Development

: Higher National Diploma in Computing and Systems

Unit Code & Title

: H/601/1991 Unit 33 - Data Analysis and Design

Assessment Title & Nos

(No 1 of 1)

: Database solution for ACE cabs

Learning outcomes and grading opportunities:

LO 01:Understand data models and database technologies
Learning
LO1.1 LO1.2 LO1.3
Outcomes
LO 02: Be able to design and implement relational database
systems
Learning
LO2.1 LO2.2 LO2.3
Outcomes
LO 03: Be able to use manipulation and querying tools
Learning
LO3.1 LO3.2 LO3.3
Outcomes
LO 04: Be able to test and document relational database systems.
Learning
LO4.1 LO4.2 LO4.3 LO4.4 LO4.5
Outcomes
Merit and Distinction Descriptor
Assessor

: Ms.Mahesha

Internal Examiner (IE) :

Date Reviewed

: Date of IE

Date Issued :

Date Due

All rights reserved ESOFT Metro Campus, Sri Lanka

Page 1 of 11

Statement of Originality and Student Declaration

I hereby, declare that I know what plagiarism entails, namely to use anothers work
and to present it as my own without attributing the sources in the correct way. I
further understand what it means to copy anothers work.
1. I know that plagiarism is a punishable offence because it constitutes theft.
2. I understand the plagiarism and copying policy of the Edexcel UK.
3. I know what the consequences will be if I plagiaries or copy anothers work in
any of the assignments for this program.
4. I declare therefore that all work presented by me for every aspects of my
program, will be my own, and where I have made use of anothers work, I will
attribute the source in the correct way.
5. I acknowledge that the attachment of this document signed or not,
constitutes a binding agreement between myself and Edexcel UK.
6. I understand that my assignment will not be considered as submitted if this
document is not attached to the attached.
Students Signature:
Date:.

All rights reserved ESOFT Metro Campus, Sri Lanka

Page 2 of 11

Case study
Hospital Management System
XYZ hospital includes a number of departments, rooms, doctors, nurses and other
staff working in the hospital. Patients having different kinds of ailments come to the
hospital and get checkup done from the doctors. If required they are admitted in the
hospital and discharged after the treatment.
In hospital, there are many departments like Dental, Anesthetics, I.C.U., Blood Bank,
Operation Theater, Laboratory, M.R.I., Cardiology, Corpse, etc. There is an OPD
where patients come and get a card (that is, entry card of the patient) for check up
from the doctor. After making entry in the card, they go to the concerned doctors
room and the doctor checks up their ailments. According to the ailments, the doctor
either prescribes medicine or admits the patient in the concerned department. The
information stored on department includes the department name, department
location, and facilities available in that department.
The patient may choose either private or general room according to his/her need. It
contains details of all rooms in the hospital. The details stored relevant to the room
are room number, room type (general or private), status (whether occupied or not),
if occupied, then patient number, patient name, charges per day, etc.
When patient arrives, a patient number is generated. Other details like name, age,
sex, address, city, phone number, entry date, and name of the doctor referred to,
diagnosis, and department name are also stored. After storing the necessary details
patient is sent to the doctor for checkup.
But before getting admission in the hospital, the patient has to fulfill certain
formalities of the hospital like room charges, etc. After the treatment is completed,
the doctor discharges the patient. Before discharging from the hospital, the patient
again has to complete certain formalities of the hospital like balance charges, test
charges, operation charges (if any), blood charges, doctors charges, patient
number, treatment given, treatment advice, payment made, mode of payment,
date of discharge, etc.
If patient is operated in the hospital, his/her details are stored. Information stored
includes patient number, date of admission, date of operation, number of the doctor
who conducted the operation, number of the Operation Theater in which operation
was carried out, type of operation, patients condition before and after operation,
treatment advice, etc.
Next we talk about the doctors of the hospital. There are two types of the doctors in
the hospital, namely, regular doctors and call on doctors. Regular doctors are those
doctors who come to the hospital daily. Calls on doctors are those doctors who are
called by the hospital if the concerned doctor is not available. Doctors are referred

All rights reserved ESOFT Metro Campus, Sri Lanka

Page 3 of 11

to by their doctor number. Other personal details like name, qualification, fees per
call, payment due, address, phone number, specialization etc., are also stored.
The main purpose of this case study is to design and develop a database for the
hospital to maintain the records of various categories of patients like regular
patients; patients admitted etc., departments, rooms, and doctors in the hospital. It
also maintains records of the checkup of patients done by the doctors, the patients
that have been operated, and patients discharged from the hospital.
Task 1
1.1. What is a data model? (LO.1.1)
1.2. Explain the advantages and disadvantages of data models (D2.3), and
discuss why relational model is best fit for above scenario. (LO.1.1)
1.3. Prepare a power point presentation to discuss the benefits and
limitations of different database technologies such as distributed
database, data warehouse, etc. (LO.1.2) (M2.1)
1.4. Analyze different approaches such as top-down approach, bottom-up
approach in database designing.(LO 1.3)
Task 2
2.1. Draw an ER diagram for the above scenario. Make sure to indicate
primary keys, cardinality constraints, weak entities (if any), and
participation constraints.
2.2. List any assumptions and extra constraints which cannot be captured
by the ER diagram.
2.3. For each entity set and relationship, write a short description in plain
English of what it represents or models.
2.4. Translate the ER diagram in Relational Schemas. (LO 2.1)
2.5. Translate the ER diagram into relational database tables (give the SQL
DDL statements). (LO 2.2)
2.6. Create a simple interface to insert, update and delete data in the
database using a suitable IDE. (LO 2.3)
Task 3
3.1. What is a database query? Describe the advantages of SQL queries ?
(LO 3.1)
3.2. After creating the tables, write and run the following SQL queries on
your database.
For each of the problems show:
Your SQL query
The result you obtained (LO 3.2)
a. Display the all the patients admitted in Cardiology department.
b. Filter the call on doctors with their specialization.

All rights reserved ESOFT Metro Campus, Sri Lanka

Page 4 of 11

c. Delete the patients treated in OPD

d. Write an update query to update a particular record in the database
3.3. How meaningful data has been extracted through the use of query
tools. Explain with examples. (LO 3.3)
3.1. Provide suitable test cases and a test plan to test the database.(LO
4.1)(LO 4.2)
3.2. Demonstrate how MS SQL effectively supporting to the designer when
they implement the database through the documentation. (User screen
shots) (LO 4.3)
3.3. Explain how verification and validation are addressed in your database
using stored procedures.(LO 4.4)
3.4. Discuss the security policies relevant to any database management
system.(LO4.5)

All rights reserved ESOFT Metro Campus, Sri Lanka

Page 5 of 11

Observation Sheet
Activ
ity
No
1

Activity

Insert data to the tables

Learning
Outcome
(LO)
LO4.1

Data manipulations

LO4.1

(Update/Delete)
Implement user privileges

LO4.5

Execute triggers and stored

procedures

D3.5
LO 4.4

Test the database with a test plan

LO4.2

Dat
e

Feedback
(Pass/ Redo)

Comments:

Assessor Name

:.

Assessor Signature

:.

All rights reserved ESOFT Metro Campus, Sri Lanka

Page 6 of 11

Possible
evidence
LO1- Understand data models and database technologies
1.1 critically compare different data models and schemas
Task 1.1
Task 1.2
Outcomes/Criteria for PASS

1.2 critically discuss the benefits and limitations of different

database technologies
1.3 analyse different approaches to database design

Page

Feedback

Task 1.3
Task 1.4

LO2 - Be able to design and implement relational database systems

2.1 design a relational database system to meet a given
requirement
2.2 build a relational database system based on a prepared
design
2.3 apply a range of database tools and techniques to
enhance the user interface
LO3 -Be able to use manipulation and querying tools

Task 2.4

3.1 explain the benefits of using manipulation and query

tools in a relational database system

Task 3.1

3.2 implement a query language into the relational database

system

Task 3.2

3.3 critically evaluate how meaningful data has been

extracted through the use of query tools

Task 3.3

Task 2.5
Task 2.6

All rights reserved ESOFT Metro Campus, Sri Lanka

Page 7 of 11

LO4 - Be able to test and document relational database systems

4.1 critically review and test a relational database system

Task 3.4

4.2 create documentation to support the implementation and

testing of a
relational database system

Task 3.5

4.3 create user documentation for a developed relational

database system

Task 3.6

4.4 explain how verification and validation has been

addressed

Task 3.7

4.5 explain how control mechanisms have been used.

Task 3.8

Grade Descriptor for MERIT

M1
Identify and apply strategies to find
appropriate solutions

Possible evidence

Feedback

Use join queries to bring

M1.2

complex problems with more than one

variable have been
explored
M2
Select / design appropriate methods /
techniques
M2.1
relevant theories and techniques have been
applied
M2.3
a range of sources of information has been
used
M3

Present and communicate appropriate

findings

summarized

records

from

two different tables.

Proper use of Harvard
referencing.

Documentation is well
structured adhering to the
formatting guidelines with

All rights reserved ESOFT Metro Campus, Sri Lanka

Page 8 of 11

M3.3

A range of methods of presentation have

been used and technical language has been
accurately used

non-overlapping facts.
Data provided are accurate,
reliable and consistent

Grade Descriptor for DISTINCTION

D1
Use critical reflection to evaluate own
work and justify valid conclusions

Possible evidence
Report: shown in the selfreflection section

D1.3

Self-criticism of approach has taken place

Good conclusion with

suggestions for further
improvement

D1.4

Realistic improvements have been proposed

against defined characteristics for subject

D2

Take responsibility for managing and

organising activities

D2.3
D3

Activities have been managed

Demonstrate convergent / lateral /
creative thinking

D3.5

Innovation and creative thoughts have been

applied

Feedback

Gantt chart must be

provided at the appendix
section and submit the work
on time.
Evidences on Use of
triggers, views and stored
procedure.
Whether the queries are
correct, the number of
tables they reference, and
the running time.

All rights reserved ESOFT Metro Campus, Sri Lanka

Page 9 of 11

Strengths:

Weaknesses:

Future Improvements & Assessor Comment:

Assessor:

Signature:

Date: ____/____/______

Internal Verifiers Comments:

All rights reserved ESOFT Metro Campus, Sri Lanka

Page 10 of 11

Internal Verifier:
____/____/______

Signature:

All rights reserved ESOFT Metro Campus, Sri Lanka

Date:

Page 11 of 11