System Analysis and Design

Isaac.w
TEMAOS [Company address]
SYSTEM ANALYSIS AND DESIGN

Question 1
Following the creation of a customer database, the following is a table showing the work
breakdown followed by the calculation of the duration dates of the same and the critical path.
Task Description Duration Predecessors
1 System design 5 days 0
2 Subsystem A design 5 days 1
3 Subsystem B design 4 days 2
4 Subsystem C design 5 days 3
5 Programming A
design
9 days 4
6 Programming B
design
5 days 5
7 Programming C
design
8 days 6
8 Testing 4 days 7
Calculations
Task Description Start date Finish date
1 System design 14th may 18th may
2 Subsystem A design 19th may 23nd may
3 Subsystem B design 24th may 27th may
4 Subsystem C design 28th may 1st June
5 Programming A
design
2nd June 10th June
6 Programming B
design
11th June 15th June
7 Programming C
design
16th June 23rd June
8 Testing 24th June 27th June

Critical path;
Question 2
Hospital management system
The system will incorporate some entities, which will support the system and ensure full
realization of its functionality. This will include the following;
I. The system name entity.
Captures the names of the patient for the sake of record keeping.
II. System number entity
Matches the number type keyed in from the user and returns the number value in string.
This entity will be of much use to keep the records of the inpatients admitted per day and
the patients that received treatment.
III. System date period
Gives indicates the interval in date wise for the records and for further references that
may require the same for instance the period that an inpatient has observed while in the
bed ward for the purposes of bill settlement.
IV. System date- time entity.
Like the date period entity, the date-time entity indicates the interval only that this
indicates the specific date, day and the time, real-time of the whole interval.
V. System composite entity
Matches the date references.
VI. System mapping entity.

Indicates the amount of money together with the currency name. For instance, in the
indication of the charge of the total bill, it can either be in dollars or Euros, depending on
the currency preferred by the hospital management.
The use case being the processes that a patient has to undergo stage by stage and the actors being
the executors of the process, which can be either a human or a system. In the system use case and
actors scenario can be applicable in three cases;
 Admission
 Booking appointment
 Booking a bed in the ward.
1. Use case admission.
This case involves the registration process and confirmation of details to proceed for
treatment. In this case, either the patient applies electronically or through a handwritten
form where he/she writes his /her personal information; the name, home address, gender,
contact, age and year of birth. The details in the form are then entered into the Hospital
management system database. This is done after a subscription fee for the form is paid
where now the administrator keys in the information including the date and time of
admission and the patient are issued with a card to proceeds to see the doctor.
2. Use case Appointment.
In this case, the patient is booking an appointment through hospital management. This
can be achieved through phone or upon arrival of the patient. The patient submits his/her
personal information and in return, the date is given and time to visit or see the doctor.
3. Use case ward bed.
It involves the patient confirmation from the doctor that the patient needs to stay for
treatment after which the bed is secured for the patient and a fee is paid for the same by
the patient and the information is transferred or updated in the management’s database.
The system actors being;
 The billing system
 The general doctor
 Receptionist administrator