MSc - Information Technology
School of Computing, Engineering and Physical Sciences
London Campus
COURSEWORK
Aim
Design &
Implementation
of a Relational Database
System using
Microsoft Access
TASK:
APPOINTMENT
SCHEDULING
for a Service-based
Small & Medium Enterprise
(SME)
Requirement Analysis - 1
FUNCTIONAL
1. This is a family-owned business, and
2. They used to manage all services on
pen and paper,
3. Yet, it has grown to the point where this
method has become unfeasible and
4. Therefore, looking to professionalise
the management of the operation.
Requirement Analysis - 2
DATABASE
You have been contracted to
design and develop
a database system for the small SME
that provides services to
local end consumers.
The SME provides small home repairs like:
• Indoor painting,
• Joinery,
• Hand tools & etc
DATA - Requirement Analysis – 3
ENTITIES
These are:
• CLIENT
• EMPLOYEE
• SERVICE CATALOGUE
• INVOICE
CLIENT:
The system needs to store client details:
• CRUD operations on client details must
be allowed through forms
• Envisioned schema for this entity is:
• ClientID,
• ClientName,
• ClientAddress,
• ClientEmail,
• ClientMobile
EMPLOYEE:
• CRUD operations on client details must be
allowed through forms
• Envisioned schema for this entity includes:
• EmployeeID,
• EmployeePayrollNumber,
• EmployeeName,
• EmployeeMobile
• However, a solution (DS1) is needed to
• design a way to connect the
• Employee Entity with the Service Catalogue
• (DS1 = ClientAppointments)
SERVICE CATALOGUE:
The System must maintain a
catalogue of service offered
(such as: - Indoor Painting, Exterior Painting, Joinery, “Etc”)
• All services are offered at a base
• cost-per-hour rate
• plus expenses.
• Envisioned schema for this entity is:
• ServiceID,
• ServiceName,
• ServiceDescription,
• ServiceHourlyRate
SERVICE CATALOGUE:
At this point:
• A solution (DS2) is needed to:
• Design a way to connect ENTITIES
• Service with the CustomerCataloge
(i.e ServicesProvided):
Which conveys services performed to:
• Each customer
• On a specific date,
• Reporting the expenses &
• 3NF compliant
INVOICE
• An invoice is an Entity that provides flexibility to DS2.
• This allows the business to offer discounts and
• be more competitive in larger jobs.
Envisioned schema for this entity is
• InvoiceID,
• InvoiceNumber,
• InvoiceCost,
• InvoiceDiscount,
• InvoiceTotal
A solution (DS3) is needed to
• Design a way to connect ENTITIES
Invoice with the ClientAppointments (DS1)
• That is 3NF compliant and
• Conveys which appointments have been grouped together
• to produce an Invoice.
Other Requirements are:
2. INVOICE
• An invoice is an Entity that provides flexibility to DS2.
• This allows the business to offer discounts and
• be more competitive in larger jobs.
• Envisioned schema for this entity is
• InvoiceID,
• InvoiceNumber,
• InvoiceCost,
• InvoiceDiscount,
• InvoiceTotal
3. A solution (DS3) is needed to
• Design a way to connect the
• Invoice Entity with the ClientAppointments (DS1)
• That is 3NF compliant and
• Conveys which appointments have been grouped together
• to produce an Invoice.
Conceptualization
You have been contracted to:
a. Design and deliver a Database system
b. Using Microsoft Access.
c. Meet the aim of the stakeholders; which are:
To create a robust DBMS that efficiently manages:
a. Core entities,
b. Services,
c. Customers,
d. Orders, and Payments,
to facilitate seamless transactions and enhance
the overall user experience.
NB: - All services are offered at a base
cost-per-hour rate plus expenses.
PART – 4
RELATIONSHIPS
As per the description above,
the following Entity Relationships
have been identified, (see DS1, DS2 and DS3)
which are:
a. ClientAppointments,
b. ServicesProvided
c. InvoiceRows
PART – 4A
ClientAppointments
RELATIONSHIP
A one-to-many relationship
between Service and Client.
Here –
➢ Client can have multiple appointments,
➢ but each appointment is associated with a single
client.
➢ This relationship also details the EmployeeID that
provides the service &
➢ It is with an integrity constrain that the Employee
is able to provide the service.
4B - Other Relationships
ServicesProvided
A many-to-many relationship
between Service and Employee.
But an employee can
provide multiple services.
InvoiceRows,
• a one-to-many relationship
• This is between Invoice &
ClientAppointments.
GENERAL PROCEDURE
Using the Entity-Relationship (ER)
- You are required to:
DESIGN & IMPLEMENT
this database system through:
a. Data requirements analysis,
b. Conceptual design logical design
c. Implement and testing using MS Access.
The above specification lists the bare minimum needs.
However, for everything you do to develop this;
• You are required to document &
• Present a formative-based academic report.
Task - 1
CONCEPTUALIZATION
Using the concepts of the
Entity-Relationship (ER) data modelling.
Create a
Conceptual Schema
for the above database system
14%
Task – 1B - PROCEDURE
a. Show the following design steps:
• Draw partial ER diagrams
• Showing each entity and all its attributes individually;
b. Complete the ER diagram by using the notation shown in
the example of the Student relation given below:
c. Student
• bannerID = [PK],
• fName,
• lName,
• address,
• gender,
• NIN,
• compID,
• DOB,
• ProgrammeTitle
1. Primary key: = bannerID
2. Foreign key: = ProgrammeTitle
references Programme(pTitle)
3. Alternate key: = NIN
TASK-1C CONSIDERATIONS
Only primary key attributes should be
included in the simplified ER diagram
Your ER diagram must make use of the
building blocks of ER diagrams;
which including
• Primary key
• Alternate keys, (simple or composite),
• Composite attribute,
• Multi-valued attribute,
• Attribute of a relationship,
• Recursive relationship,
• 1:1 relationship,
• 1:M relationship, and
• M:N relationship, among others.
Task - 2
IMPLEMENTATION
Process
Create the
TABLES & RELATIONSHIPS
NB:
• All the elements shown above in blue in your relational
schema must be properly implemented.
• Enforce the referential integrity including
• update rules on each of the relationships btw tables
• Moreover, set field properties and in particular:
14%
Task - 3
POPULATE
the Tables with Data
a. Populate the tables with meaningful data.
b. Enter sufficient data that reflect:
• Relationships
• Structural constraints
• Participation constraints and
• Cardinality ratio specified with ‘min..max’) &
• Test with the queries in Task 4
2%
Task - 4
QUERY
the Database
Using SQL script
a. Write at least 10 queries and
b. Run them in your database,
c. Thereafter –
d. Show that your SQL lines work
(using screen capture)
9%
Task - 5
APPLICATION
of the Database
a. Develop & implement a MS-Access based application
• that will allow the database users
• to access and retrieve data from the database.
In your report
• The MS-Access based application should show or have:
• A 'user friendly' graphical interface.
• Allow the users to perform the following:
i. Run Use Cases for the System;
ii. View data in Tables Employee and
iii. Clients from the datasheet view
7%
Task - 6
CRITICAL
EVALUATION
Submit a critical assessment of your work you
learned to design and implement a relational database.
The value of this coursework in terms of:
• Understanding
• Appreciating
• The techniques &
• Methods (or otherwise)
Lastly - things that must be included here -
from each member of the group are:
a. A brief statement of ‘my contributions’
b. Must not be longer than one page.
Task-7
COURSEWORK
Submission
Guidelines
Note: - your coursework report should be typed using
Microsoft Word and nothing else
(e.g, PDF or any other software)
The report should have:
i. A cover sheet with the names and banner id of
all students involved in the submission.
ii. Heading for each task.
iii.Explain your reasoning and
iv.Provide adequate evidence of the work
(through screenshots, SQL statements, as necessary for each task).
➢ ONLY the TEAM LEAD can upload the report to the Aula.
➢ Keep your database safe until you have received the
official marks of the term, as you can be asked to
demonstrate your database.
➢ Zipped/ compressed your files at the submission point.
PRIVACY & SECURITY
The design presented above has no considered
data privacy and security requirements.
You are requested to produce a one-page critique of
the issues that can potentially become incidents.
You should include:
a. An Identification of Sensitive data
b. Data protection measures that you would add to design
c. GDPR compliance.
d. Reflect on data minimization,
e. Purpose limitation,
f. Storage limitation &
g. Data subject rights (e.g., right to access, rectify, or erase personal data).
h. Provide recommendations on how the system can adhere to these
principles and ensure the lawful processing of personal data.
COURSEWORK
Plagiarism
Plagiarism is a serious offense
in academia.
All submissions will be checked
for plagiarism.
Students should submit their
own work,
As copied, or downloaded work
will lead to zero marks. 30
COURSEWORK
DEADLINE
FRIDAY,
11th April 2025
@11:59 PM
32
DDI - Assignment  1.pdf hjhjjhhjkh jkhkjhkj hkljhk h

More Related Content

DOC
RahulParwekar_Resume
PPTX
Boosting the Performance of your Rails Apps
DOC
Sasikumar Selvaraj CV- Mainframe
DOC
Tah 03302015 withendclient
DOC
CV_Mudit IBM MCA 10+ years MSBI, SQL, .NET
DOC
Sabith_Byari-Resume_Updated
DOC
Anil Kumar_ 2YearsExp
DOC
A.S.Sivaprakash
RahulParwekar_Resume
Boosting the Performance of your Rails Apps
Sasikumar Selvaraj CV- Mainframe
Tah 03302015 withendclient
CV_Mudit IBM MCA 10+ years MSBI, SQL, .NET
Sabith_Byari-Resume_Updated
Anil Kumar_ 2YearsExp
A.S.Sivaprakash

Similar to DDI - Assignment 1.pdf hjhjjhhjkh jkhkjhkj hkljhk h (20)

DOC
Anil Kumar_ 2YearsExp
DOC
Rakesh_Resume_2016
DOC
Sourabh_Resume_1
PDF
ClearCost Introduction 2015
DOC
AhmedWasfi2015
PPTX
Odbc and data access objects
DOC
Datstage_Developer_with_3.8yrs_exp
PPTX
Move a successful onpremise oltp application to the cloud
PPSX
Dennis Schmid Portfolio
DOC
250755494-advertising-agency-management-system-1-doc.doc
DOC
Health care resume_marcus_wesley_system_analyst[1][1]
PPTX
Advanced Test Design Methods
DOC
Pradeep vemula_5.1_ MF Resume
DOCX
Chris_Resume_2017
DOCX
Is 4 th
DOC
Saravanan rajalingam
DOC
Saravanan Rajalingam
DOC
Murali Tummala Resume
PDF
DAS Slides: Data Architect vs. Data Engineer vs. Data Modeler
Anil Kumar_ 2YearsExp
Rakesh_Resume_2016
Sourabh_Resume_1
ClearCost Introduction 2015
AhmedWasfi2015
Odbc and data access objects
Datstage_Developer_with_3.8yrs_exp
Move a successful onpremise oltp application to the cloud
Dennis Schmid Portfolio
250755494-advertising-agency-management-system-1-doc.doc
Health care resume_marcus_wesley_system_analyst[1][1]
Advanced Test Design Methods
Pradeep vemula_5.1_ MF Resume
Chris_Resume_2017
Is 4 th
Saravanan rajalingam
Saravanan Rajalingam
Murali Tummala Resume
DAS Slides: Data Architect vs. Data Engineer vs. Data Modeler
Ad

Recently uploaded (20)

PPTX
Stats annual compiled ipd opd ot br 2024
PPTX
indiraparyavaranbhavan-240418134200-31d840b3.pptx
PDF
Concepts of Database Management, 10th Edition by Lisa Friedrichsen Test Bank.pdf
PPTX
865628565-Pertemuan-2-chapter-03-NUMERICAL-MEASURES.pptx
PDF
Grey Minimalist Professional Project Presentation (1).pdf
PPTX
Hushh.ai: Your Personal Data, Your Business
PDF
2025-08 San Francisco FinOps Meetup: Tiering, Intelligently.
PPTX
inbound2857676998455010149.pptxmmmmmmmmm
PPT
dsa Lec-1 Introduction FOR THE STUDENTS OF bscs
PDF
Mcdonald's : a half century growth . pdf
PPTX
Chapter security of computer_8_v8.1.pptx
PPTX
machinelearningoverview-250809184828-927201d2.pptx
PPTX
Machine Learning and working of machine Learning
PPTX
cp-and-safeguarding-training-2018-2019-mmfv2-230818062456-767bc1a7.pptx
PPTX
AI AND ML PROPOSAL PRESENTATION MUST.pptx
PPTX
DATA ANALYTICS COURSE IN PITAMPURA.pptx
PPTX
PPT for Diseases.pptx, there are 3 types of diseases
PPTX
GPS sensor used agriculture land for automation
PPTX
DIGITAL DESIGN AND.pptx hhhhhhhhhhhhhhhhh
PDF
CS3352FOUNDATION OF DATA SCIENCE _1_MAterial.pdf
Stats annual compiled ipd opd ot br 2024
indiraparyavaranbhavan-240418134200-31d840b3.pptx
Concepts of Database Management, 10th Edition by Lisa Friedrichsen Test Bank.pdf
865628565-Pertemuan-2-chapter-03-NUMERICAL-MEASURES.pptx
Grey Minimalist Professional Project Presentation (1).pdf
Hushh.ai: Your Personal Data, Your Business
2025-08 San Francisco FinOps Meetup: Tiering, Intelligently.
inbound2857676998455010149.pptxmmmmmmmmm
dsa Lec-1 Introduction FOR THE STUDENTS OF bscs
Mcdonald's : a half century growth . pdf
Chapter security of computer_8_v8.1.pptx
machinelearningoverview-250809184828-927201d2.pptx
Machine Learning and working of machine Learning
cp-and-safeguarding-training-2018-2019-mmfv2-230818062456-767bc1a7.pptx
AI AND ML PROPOSAL PRESENTATION MUST.pptx
DATA ANALYTICS COURSE IN PITAMPURA.pptx
PPT for Diseases.pptx, there are 3 types of diseases
GPS sensor used agriculture land for automation
DIGITAL DESIGN AND.pptx hhhhhhhhhhhhhhhhh
CS3352FOUNDATION OF DATA SCIENCE _1_MAterial.pdf
Ad

DDI - Assignment 1.pdf hjhjjhhjkh jkhkjhkj hkljhk h

  • 1. MSc - Information Technology School of Computing, Engineering and Physical Sciences London Campus
  • 2. COURSEWORK Aim Design & Implementation of a Relational Database System using Microsoft Access
  • 4. Requirement Analysis - 1 FUNCTIONAL 1. This is a family-owned business, and 2. They used to manage all services on pen and paper, 3. Yet, it has grown to the point where this method has become unfeasible and 4. Therefore, looking to professionalise the management of the operation.
  • 5. Requirement Analysis - 2 DATABASE You have been contracted to design and develop a database system for the small SME that provides services to local end consumers. The SME provides small home repairs like: • Indoor painting, • Joinery, • Hand tools & etc
  • 6. DATA - Requirement Analysis – 3 ENTITIES These are: • CLIENT • EMPLOYEE • SERVICE CATALOGUE • INVOICE
  • 7. CLIENT: The system needs to store client details: • CRUD operations on client details must be allowed through forms • Envisioned schema for this entity is: • ClientID, • ClientName, • ClientAddress, • ClientEmail, • ClientMobile
  • 8. EMPLOYEE: • CRUD operations on client details must be allowed through forms • Envisioned schema for this entity includes: • EmployeeID, • EmployeePayrollNumber, • EmployeeName, • EmployeeMobile • However, a solution (DS1) is needed to • design a way to connect the • Employee Entity with the Service Catalogue • (DS1 = ClientAppointments)
  • 9. SERVICE CATALOGUE: The System must maintain a catalogue of service offered (such as: - Indoor Painting, Exterior Painting, Joinery, “Etc”) • All services are offered at a base • cost-per-hour rate • plus expenses. • Envisioned schema for this entity is: • ServiceID, • ServiceName, • ServiceDescription, • ServiceHourlyRate
  • 10. SERVICE CATALOGUE: At this point: • A solution (DS2) is needed to: • Design a way to connect ENTITIES • Service with the CustomerCataloge (i.e ServicesProvided): Which conveys services performed to: • Each customer • On a specific date, • Reporting the expenses & • 3NF compliant
  • 11. INVOICE • An invoice is an Entity that provides flexibility to DS2. • This allows the business to offer discounts and • be more competitive in larger jobs. Envisioned schema for this entity is • InvoiceID, • InvoiceNumber, • InvoiceCost, • InvoiceDiscount, • InvoiceTotal A solution (DS3) is needed to • Design a way to connect ENTITIES Invoice with the ClientAppointments (DS1) • That is 3NF compliant and • Conveys which appointments have been grouped together • to produce an Invoice.
  • 12. Other Requirements are: 2. INVOICE • An invoice is an Entity that provides flexibility to DS2. • This allows the business to offer discounts and • be more competitive in larger jobs. • Envisioned schema for this entity is • InvoiceID, • InvoiceNumber, • InvoiceCost, • InvoiceDiscount, • InvoiceTotal 3. A solution (DS3) is needed to • Design a way to connect the • Invoice Entity with the ClientAppointments (DS1) • That is 3NF compliant and • Conveys which appointments have been grouped together • to produce an Invoice.
  • 13. Conceptualization You have been contracted to: a. Design and deliver a Database system b. Using Microsoft Access. c. Meet the aim of the stakeholders; which are: To create a robust DBMS that efficiently manages: a. Core entities, b. Services, c. Customers, d. Orders, and Payments, to facilitate seamless transactions and enhance the overall user experience. NB: - All services are offered at a base cost-per-hour rate plus expenses.
  • 14. PART – 4 RELATIONSHIPS As per the description above, the following Entity Relationships have been identified, (see DS1, DS2 and DS3) which are: a. ClientAppointments, b. ServicesProvided c. InvoiceRows
  • 15. PART – 4A ClientAppointments RELATIONSHIP A one-to-many relationship between Service and Client. Here – ➢ Client can have multiple appointments, ➢ but each appointment is associated with a single client. ➢ This relationship also details the EmployeeID that provides the service & ➢ It is with an integrity constrain that the Employee is able to provide the service.
  • 16. 4B - Other Relationships ServicesProvided A many-to-many relationship between Service and Employee. But an employee can provide multiple services. InvoiceRows, • a one-to-many relationship • This is between Invoice & ClientAppointments.
  • 17. GENERAL PROCEDURE Using the Entity-Relationship (ER) - You are required to: DESIGN & IMPLEMENT this database system through: a. Data requirements analysis, b. Conceptual design logical design c. Implement and testing using MS Access. The above specification lists the bare minimum needs. However, for everything you do to develop this; • You are required to document & • Present a formative-based academic report.
  • 18. Task - 1 CONCEPTUALIZATION Using the concepts of the Entity-Relationship (ER) data modelling. Create a Conceptual Schema for the above database system 14%
  • 19. Task – 1B - PROCEDURE a. Show the following design steps: • Draw partial ER diagrams • Showing each entity and all its attributes individually; b. Complete the ER diagram by using the notation shown in the example of the Student relation given below: c. Student • bannerID = [PK], • fName, • lName, • address, • gender, • NIN, • compID, • DOB, • ProgrammeTitle 1. Primary key: = bannerID 2. Foreign key: = ProgrammeTitle references Programme(pTitle) 3. Alternate key: = NIN
  • 20. TASK-1C CONSIDERATIONS Only primary key attributes should be included in the simplified ER diagram Your ER diagram must make use of the building blocks of ER diagrams; which including • Primary key • Alternate keys, (simple or composite), • Composite attribute, • Multi-valued attribute, • Attribute of a relationship, • Recursive relationship, • 1:1 relationship, • 1:M relationship, and • M:N relationship, among others.
  • 21. Task - 2 IMPLEMENTATION Process Create the TABLES & RELATIONSHIPS NB: • All the elements shown above in blue in your relational schema must be properly implemented. • Enforce the referential integrity including • update rules on each of the relationships btw tables • Moreover, set field properties and in particular: 14%
  • 22. Task - 3 POPULATE the Tables with Data a. Populate the tables with meaningful data. b. Enter sufficient data that reflect: • Relationships • Structural constraints • Participation constraints and • Cardinality ratio specified with ‘min..max’) & • Test with the queries in Task 4 2%
  • 23. Task - 4 QUERY the Database Using SQL script a. Write at least 10 queries and b. Run them in your database, c. Thereafter – d. Show that your SQL lines work (using screen capture) 9%
  • 24. Task - 5 APPLICATION of the Database a. Develop & implement a MS-Access based application • that will allow the database users • to access and retrieve data from the database. In your report • The MS-Access based application should show or have: • A 'user friendly' graphical interface. • Allow the users to perform the following: i. Run Use Cases for the System; ii. View data in Tables Employee and iii. Clients from the datasheet view 7%
  • 25. Task - 6 CRITICAL EVALUATION Submit a critical assessment of your work you learned to design and implement a relational database. The value of this coursework in terms of: • Understanding • Appreciating • The techniques & • Methods (or otherwise) Lastly - things that must be included here - from each member of the group are: a. A brief statement of ‘my contributions’ b. Must not be longer than one page.
  • 27. Note: - your coursework report should be typed using Microsoft Word and nothing else (e.g, PDF or any other software) The report should have: i. A cover sheet with the names and banner id of all students involved in the submission. ii. Heading for each task. iii.Explain your reasoning and iv.Provide adequate evidence of the work (through screenshots, SQL statements, as necessary for each task). ➢ ONLY the TEAM LEAD can upload the report to the Aula. ➢ Keep your database safe until you have received the official marks of the term, as you can be asked to demonstrate your database. ➢ Zipped/ compressed your files at the submission point.
  • 28. PRIVACY & SECURITY The design presented above has no considered data privacy and security requirements. You are requested to produce a one-page critique of the issues that can potentially become incidents. You should include: a. An Identification of Sensitive data b. Data protection measures that you would add to design c. GDPR compliance. d. Reflect on data minimization, e. Purpose limitation, f. Storage limitation & g. Data subject rights (e.g., right to access, rectify, or erase personal data). h. Provide recommendations on how the system can adhere to these principles and ensure the lawful processing of personal data.
  • 30. Plagiarism is a serious offense in academia. All submissions will be checked for plagiarism. Students should submit their own work, As copied, or downloaded work will lead to zero marks. 30
  • 32. 32