Hope Gospel Mission Resident Services Tracking System Data Flow Diagrams

1
Hope Gospel MissionResident Services Tracking
SystemData Flow Diagrams

• IS 460 Notes
• By Paul Chen, Matt LeClair
• Tom Hilton

2
Hope Gospel MissionResident Services Tracking
SystemData Flow Diagrams

• Context Diagram

Report Request
Applicant Information
Applicant
Staff
Admission Approval or Rejection
Report
Map
3
Hope Gospel MissionResident Services Tracking
SystemData Flow Diagrams

• Level 0

Report Request
Applicant Information
Applicant Name ID
Applicant
Data Item Prompt
Admission Approval or Rejection
Data Items
Data Query
Prior Application Data
Report
ApprovedApplication
Data
VerifiedApprovedApplication
Other Resident Data
Request for Resident Information Maintenance
BACK
4
Hope Gospel MissionResident Services Tracking
SystemData Flow Diagrams

• Level 1 Process 1, Perform Intake Procedure

Applicant Information
Applicant
Admission Application
Applicant Name and ID
VerifiedAdmissionApplication
Prior Application Data
Application Data
Application Request
Application Approval or Rejection
Approved Application
BACK
5
Hope Gospel MissionResident Services Tracking
SystemData Flow Diagrams

• Level 1 Process 2, Maintain Resident Information

Approved Application to Add
Verified Approved Application
Verified Changed Resident Data
Approved Application to Edit
Approved Application
Request for Resident Information Maintenance
ID of Resident to Delete
Verified ID of Resident to Delete
Determination to Cancel Operation
BACK
6
Hope Gospel MissionResident Services Tracking
SystemData Flow Diagrams

• Level 1 Process 3, Generate Reports

Report Request
Data Item Prompt
Report Specification
Report
Data Items
Data
Data Query
BACK
7
Hope Gospel MissionResident Services Tracking
SystemData Flow Diagrams

• Level 2 Process 1.1, Receive Admission Application

Applicant
Admission Application
Application Information
New Applicant Data
Applicant Name and ID
Prior Applicant Data
BACK
8
Hope Gospel MissionResident Services Tracking
SystemData Flow Diagrams

• Level 2 Process 1.3, Review Application

Application Request
Approved Application
FormattedAdmissionApplication
Application Data
Application Approval or Rejection
Applicant
BACK
9
1.1.1 Check for Prior Application Pseudocode

• Select
• From APPLICANT_DATA ALIAS D2
• For D2.NAME NAME
• And D2.PK ID

BACK
10
1.1.2 Enter or Edit Applicant Data Pseudocode

• REM repeat for all applicant data
• IF D2.fieldname ltgt varname
• WHERE D2.PK ID
• THEN
• UPDATE APPLICANT_DATA ALIAS D2
• SET D2.fieldname varname
• WHERE D2.PK ID
• ENDIF

BACK
11
1.2 Verify Admission Application Pseudocode

• Run Form Admission_Application_Verification
• On D2.Applicant_Data
• Allow Update on all fields
• On Send Commit to D2.Applicant_Data

BACK
12
1.3.1 Display Admission Application Pseudocode

• On Applicant_Data ALIAS D2
• Run Report D2.Application_Display
• ReadOnly
• On Send Return to calling module

BACK
13
1.3.2 Approve or Reject Application Pseudocode

• IF Accepted
• THEN
• UPDATE Applicant_Data ALIAS D2
• SET Admitted Admitted Today()
• WHERE D2.PK ID
• Run Print_Admission_Voucher
• ELSE
• UPDATE Applicant_Data ALIAS D2
• SET Admitted Rejected Today()
• WHERE D2.PK ID
• ENDIF

BACK
14
2.1 Determine Operation Pseudocode

• Input AddEditDelete
• Select Case AddEditDelete
• Case Add
• Run AddNewResident
• Case Edit
• Run EditResident (IDparm ID)
• Case Delete
• Run DeleteResident (IDparm ID)
• Case Else
• Return
• End Select

BACK
15
2.2 Add New ResidentPseudocode

• INSERT INTO D1_Resident_Data
• VALUES (Lname, Fname, etc.)

BACK
16
2.3 Edit Existing ResidentPseudocode

• UPDATE Resident_Data ALIAS D1
• SET D1.Lname VarLname, D1.Fname VarFname,
  etc.
• WHERE D1.PK IDparm

BACK
17
2.4 Delete Existing Resident Pseudocode

• DELETE FROM Resident_Data ALIAS D1
• WHERE D1.PK IDparm

BACK
18
2.5 Cancel OperationPseudocode

• Just drop through the Case statement in 2.1 and
  return.

BACK
19
3.1 Specify ReportPseudocode

• Input ReportType
• Select Case ReportType
• Case 1
• Run Report1
• Case 2
• Run Report2
• Case 3
• Run Report3
• Case Else
• Return
• End Select

BACK
20
3.2 Construct Data Query Pseudocode

• Display Column Names in Resident_Data ALIAS D1
• Allow User to choose Columns to report
• Display unique values in D1.PK
• Allow User to choose Rows to report
• Construct Filter per User specifications

BACK
21
3.3 Issue ReportPseudocode

• Using Filter from 3.2
• SELECT Filtered.Columns
• FROM Resident_Data ALIAS D1
• WHERE ID Filtered.Rows(1)
• OR ID Filtered.Rows(2)
• OR etc.

BACK
22
D1 ER Diagram
EMPLOYER
11
INTAKE MANAGER
0M
VISIT-EMPLOYER
EMERGENCY CONTACT
HOMELESS REASON
M0
11
11
11
11
0M
M0
M0
VISIT
VISIT-PHASE
VISIT-HOMELESSREASON
0M
11
M1
11
0M
11
0M
M1
11
0M
10
11
VISIT-CLINIC
CHAPLAIN
PHASE
M0
RESIDENT
11
0M
11
11
11
0M
11
CLINIC
EDUCATION LEVEL
MEDICAL RECORD
1M
M0
CRIMINAL RECORD
RESIDENT PROGRESS
To P2
To L1
To P3
To L0
23
Levels of Diagrams
BACK