System Analysis Report

1
System Analysis Report

• Presentation
• CSA GROUP 2Z
• Z3

2
Group Members

• Cheung Man Ching (Hilda)
• Lau Tsoi San (Sandy)
• Pang Ka Wai (Grace)
• Tham Chun Fung (Bony)
• Tang Hing Wah (Michael)

3
We will present the following things

• Introduction
• Updated problem and Requirement
• Data flow diagram
• Entity relationship diagram

4
Introduction

• Kowloon hospital received the planning proposal
• It is approved to start the Analysis Report
• Objectives
• To analysis how the system could work efficiently

5
In this report

• Review the problems
• To truly understand the updated requirements
• Construct the Data flow diagram
• Construct the Entity relationship diagram

6
Updated Problems

• 1.Data inaccuracy
• Poor hand-writing
• Re-entry data
• 2.Difficult to understand patient condition
• Lack of related details report
• 3.Time consuming
• It wastes many time to write down comment and
  assessment result
• Hard to search record from the shelf

7
Updated Problem

• 4.Waste space
• 5.Difficult to do analysis and statistic
• 6.OT feel boring and unwilling to write the
  comment as lots of comment are duplicated

8
Updated Requirement

• Divided into two phase
• Phase 1
• PDA application
• automation of the existing manual processes
• Filling progress note, patient training record
  and assessment forms

9
Updated Requirement

• Phase 2
• Desktop applications
• Patient Management systems
• Printing different forms and reports
• Patient attendance
• Plan schedule of the daily training time of
  patients.

10
Updated Requirement

• Phase 1 should develop first
• Phase 2 should developed After detailed
  requirements to be provided by Kowloon Hospital

11
Data Flow Diagram (1)
12
Data Flow Diagram (2)
13
Data Flow Diagram (3)
14
Data Flow Diagram (4)
15
Data Flow Diagram (5)
16
Data Flow Diagram (6)
17
Function Description Elementary Description

• After the DFDs of the system is completed, we
  need to have function description to describe
  what is done in the process and elementary
  descriptions to describe how the process will done

18
PDA (1)

• Get Patient Detail (1.1.1)
• Patient ----? OT database

19
PDA (2)

• Show Assessment Form (1.1.2)
• Assessment form ----? OT and Patient
• ---------? Assessment

20
PDA (3)

• Calculate score (1.1.3)
• Calculate the score of the assessment taken by
  patient

21
PDA (4)

• Taking Training (1.2)
• Patient take the training

22
Conduit (1)

• Upload Result (2.1)
• Upload the assessment result to PC

23
Conduit (2)

• Upload Training
• Upload the training from PC ? PDA

24
Conduit (3)

• Download Patient (2.3)
• Download patient info from PC ? PDA device for
  the OT

25
Conduit (4)

• Download Assessment (2.4)
• Download the assessment form from PC ? PDA
  device.

26
PC (1)

• Design Assessment (3.1)
• Design a new assessment form ? PC

27
PC (2)

• Prepare Training Record
• Print the selected patients training record

28
PC (3)

• Prepare Progress Note
• Print the selected patients progress note

29
PC (4)

• Get the patient info from the Patient System and
  update local database if needed.

30
Required System Logical Data Structure

• An entity-relationship diagram(ERD) which is a
  data modeling technique that creates a graphical
  representation of the entities, and the
  relationships between entities
• Five entities in the systems Patient, OT,
  Assessment, Progress and Training.

31
ERD of the system
Progress
have
OT
Patient
take
in charge
take
Training
32
Entity relationship

• Patient take assessment relationship
• in order to facilitate the design of a relational
  database, this may converted into two one to many
  relationships though the use of an associative
  entity

Patient
take
Assessment
33
Entity relationship(cont)

• Normalized Patient taken assessment ERD

34
Entity relationship(cont)

• OT in charge patient ERD
• The relation between the patient and OT is many
  to one

Patient
In charge
35
Entity relationship(cont)

• Patient have progress relationship
• The relation between the patient and the progress
  is one to one.

Patient
have
Progress
36
Entity relationship(cont)

• Patient take training relationship
• The relation between the patient and trainings is
  many to one
• Converted into two one to many relationships

Patient
take
Training
37
The attributes of each entity

• Patient ( patient_id, patient_name, add, tel,
• ot_id, sex, dob )
• OT ( ot_id, ot_name)
• Assessment ( ass_id, ass_descr,
• question_no,
• question_descr, part)
• Training ( training_id, training_descr )

38
The attributes of each entity (cont)

• Ass_taken (patient_id, ass_id,
• ass_take_date,
• ass_take_time, question_no,
• ass_taken_id, score))
• Train_taken (patient_id, training_id,
• training_unit,
  train_date)
• Progress ( patient_id, progress_descr,
• record_date)

39
Normalized Relations

• To avoid the anomalies within the database
• Looking for all attributes that are dependent on
  only part of the primary key
• The relation of Assessment and Ass_taken can
  be normalized as follow
• Ass_desc ( ass_id, ass_descr)
• Question_descr (ass_id, question_no,
• question_descr,
  part)
• Ass_taken (ass_taken_id, patient_id , ass_id,
• ass_take_date,
• ass_take_time)
• Score (ass_taken_id, question_no, score)

40
Normalized Relations(cont)

• After the above step the relations are well
  normalized as follow
• Patient (patient_id, patient_name, add, tel,
  ot_id)
• OT ( ot_id, ot_name)
• Ass_descr ( ass_id, ass_descr)
• Question_descr (ass_id, question_no,
  question_descr, part)
• Ass_taken (ass_taken_id, patient_id , ass_id,
  ass_take_date, ass_take_time)

41
Normalized Relations(cont)

• Score (ass_taken_id, question_no,
• score)
• Training ( training_id, training_descr )
• Train_taken (patient_id, training_id,
• training_unit,
  train_date)
• Progress (patient_id, progress_descry,
• record_date)

42
ERD of the system after normalization
43
Data Dictionary

• The data dictionary will include
• Ø          The entity descriptions
• Ø          The attribute descriptions

44
Entity Description

• We have 9 entities in the database

45
Entity Description (Condt)
Patient Information
Patient Entity
46
Entity Description (Condt)
OT Information
OT Entity
47
Entity Description (Condt)
Assessment Information description
Ass_descr Entity
48
Entity Description (Condt)
Assessment question details
Question_descr Entity
49
Entity Description (Condt)
The details of Assessment taken by the patient
Ass_taken Entity
50
Entity Description (Condt)
Score of each question of the assessment
Score Entity
51
Entity Description (Condt)
Training Description
Training Entity
52
Entity Description (Condt)
Training Information
Train_taken Entity
53
Entity Description (Condt)
Progress note Information
Progress Entity
54
Attribute Description
55
Attribute Description (Condt)