CAPE COMPUTER

SCIENCE: CASE Done by: The

6ixx(Bradlee and others)

ANALYSIS
BACKGROUND
The institution is called Medical Associates
It is a private hospital located in Half-Way-Tree
Consists of well-trained consultants, physicians and surgeons
Their mission is “To create a new standard of healthcare delivery
and compassionate customer care to our parents and visitors”
Their vision is “To deliver the highest standard of healthcare in
Jamaica and the Caribbean”
PROBLEM CONTEXT
There is no sense of priority in the arrangement of appointments
The appointments are written in only 1 location, making it not
portable
The appointment data was not recorded as if the notice board was
erased
The notice board only covers the current day, doctors are unable to
be prepared for the next day
Since appointments are being written, there is room for human
error
Hospital only employs the use of email, leading to difficulty in
communicating appointment times to patients
OBJECTIVES OF THE NEW
SYSTEM
Provide a user-friendly interface for the reception and entry of data
Save information entered to a file, which can be transported and
utilized by any device
Keep track of the appointments for multiple doctors
Allow the user to move appointment dates
Advise appointment dates based on priority
Ensure that the correct data is entered, through methods such as
validation checks
PROCESS MODEL –
INCREMENTAL
DEVELOPMENT
Enables the ease of customer feedback upon completing a phase
A hospital is busy, and as such, they cannot afford to be without
this crucial software so they can run efficiently
The cost of accommodating changing customer requirements is
reduced
PROCESS MODEL –
INCREMENTAL
DEVELOPMENT
Allows the programmer to go back and make changes at the end of
each phase unlike the waterfall model
Although Component Based Software Engineering may be quicker,
cheaper and easier, Medical Associates did not have a previous
software to use and improve on
The amount of analysis and documentation that has to be redone is
much less than is required with the waterfall model
Customers can comment on demonstrations of the software and
see how much has been implemented
The hospital is able to use and gain value from the software earlier
than is possible with the waterfall model
FEASABILITY
Technically Feasible
Economically Feasible
Operationally Feasible
Schedule Feasability
REQUIREMENTS ELICITATION
TECHNIQUES
Brainstorming
Interviews
Questionnaires
Prototyping
FIN