2. END USER REQUIREMENTS
• The end users are the people who are going to be using the database.
• The end user requirements are the tasks they expect to be able to do
using the database.
3. END USER REQUIREMENTS
search appointments for any doctor
search patient medical history
search patient personal details
search all patients using
certain medication
search all patients in a
given age range
calculate the average patient
rating by for each doctor
sort by patient name
sort by patient house
number and postcode
sort number of visits by a each
patient in the past 12 months
Some possible end user requirements for a doctor’s surgery database are
shown below.
4. FUNCTIONAL REQUIREMENTS
• The processes and activities that the system has to perform
• The information that the system has to contain to be able to carry out its
functions
5. FUNCTIONAL REQUIREMENTS
Some of the tables and fields for a doctor’s surgery database are shown
below.
Primary and foreign keys are not shown as part of the functional
requirements.
Doctor
• Forename
• Surname
• DOB
• Telephone
• Address
• Salary
Patient
• Forename
• Surname
• DOB
• Address
• Telephone
• Medication
• Last visit
• Next of kin
Appointment
• Date
• Time
• Patient rating
6. FUNCTIONAL REQUIREMENTS
Some of the processes and activities for a doctor’s surgery database are
shown below.
Simple and complex
queries to search the
database
An average function to work
out the average rating for
each doctor
A simple sort to query the
results
A count function to work out
the number of visits for a
patient in the past 12
months