1802ICT Project: Planning, Analysis, Design Report for Hospital System

This project report details the analysis, planning, and design of an information system for Royal Melbourne Hospital. It begins with a system vision document outlining the problem, system capabilities, and expected benefits, such as improved patient care and increased efficiency. The project includes a breakdown of estimated time for project completion, development costs, and annual operating costs. A comprehensive cost/benefit analysis is provided, highlighting both tangible and intangible benefits. Furthermore, the report assesses organizational, technological, resource, and schedule risks and feasibility. It establishes the project environment by outlining information capture methods, the work environment, and the processes and procedures to be used, including test-driven development and regular communication protocols. The system aims to automate back-office operations, improve patient loyalty, and reduce errors, with an anticipated budget of $50,000 and an annual operating cost of $5,000. The report covers all aspects from initial planning through to deployment and testing, providing a comprehensive overview of the project's lifecycle.

1802ICT Assignment – Project Planning, Analysis and Design
Report
Weight: 55%
Rationale:
The purpose of this assignment is to demonstrate your ability to apply all the concepts of
planning and project management to a practical scenario involving a business information
system. You are required to thoroughly analyse and design your proposed information
system.
Task:
You have been contracted by a company to develop an information system for $50,000.
During this assignment, you will undertake a thorough systems analysis and design on the
proposed system.
The business that you design the information system for is of your own choosing. Preferably
develop a system for an area that you are interested in, have had prior experience, or perhaps
for a company you work for.
You cannot design the system for the same company that another student has chosen, nor can
you reproduce a design for an existing well-known company. The information system you
chose should be of small to medium size/complexity.
You are required to deliver the following specifications before the project can commence:
1. Identify the Problem – Provide a system vision document that outlines the problem
description, system capabilities, and the expected business benefits (minimum 300
words).
(Insert system vision document here)
Problem description: Royal Melbourne Hospital is an Australia based health care organization that
has more than five hundred patients under its care. The Royal Melbourne Hospital is maintaining its
day to day operations like appoint arranging, attendance tracking and many more through the paper
works and spread sheet. This is becoming very difficult for the staff of Royal Melbourne Hospital to
maintain proper record and track patient request. This is leading to low quality service and reduction
in patient loyalty.
The organization is currently interested in an information system that can be able to hold data and

access to data at any time. The system should be able to perform all the back office operations
automatically.
System Capabilities: The expected capabilities of the system has been provided below.
i. The system should hold the data for a very long time
ii. The patients must enter login to the system
iii. The staff and doctors can access the system through special computer and id
recognition device
iv. The system must be able to perform back office tasks automatically
v. The system should process more than hundred requests in parallel
vi. The system must record the reports of the patient in proper format
vii. It must be able to store files of different extension
viii. The system must be able to provide the patient data to the doctors and patients
ix. The system must have an attendance tracking subsystem
Expected Benefits from System: The following benefits has been expected from the proposed
system.
i. The system must provide the opportunity of better patient treatment
ii. The errors in treatment reduced to one percent due to data availability
iii. Much less time in tracking the patient request
iv. Better patient loyalty
v. Increase forty percent efficiency in daily operations
vi. Zero errors in the present data
2. Quantify Project Approval Factors – Complete the following tasks (minimum 500
words):
a. Provide a table with a breakdown of the estimated time for project completion
using excel or a similar program.
(Insert table and explanation here)
Task Name Duration Start Finish
Implementing Information System in Royal
Melbourne Hospital 82 days Wed 9/20/17 Thu 1/11/18

Project Planning 14 days Wed 9/20/17 Mon 10/9/17
Recognizing Scope of the Project 1 day Wed 9/20/17 Wed 9/20/17
Identifying the Deliverable of the Project 1 day Thu 9/21/17 Thu 9/21/17
Configuring the Project Acceptance 1 day Fri 9/22/17 Fri 9/22/17
Recruiting Project Team Members 3 days Mon 9/25/17 Wed 9/27/17
Developing Project Schedule 4 days Thu 9/28/17 Tue 10/3/17
Carry Out Cost Estimation 2 days Wed 10/4/17 Thu 10/5/17
Cost Benefit Analysis 2 days Fri 10/6/17 Mon 10/9/17
System Requirement 17 days Tue 10/10/17 Wed 11/1/17
Predefining the Requirements 3 days Tue 10/10/17 Thu 10/12/17
Selecting Requirement Gathering Techniques 2 days Fri 10/13/17 Mon 10/16/17
Gathering Requirements 3 days Tue 10/17/17 Thu 10/19/17
Evaluating Collected Requirements 2 days Fri 10/20/17 Mon 10/23/17
Recording the Data Found in Analysis 5 days Tue 10/24/17 Mon 10/30/17
Verifying the Requirements 2 days Tue 10/31/17 Wed 11/1/17
Design 16 days Thu 11/2/17 Thu 11/23/17
Designing the Architecture of the System 3 days Thu 11/2/17 Mon 11/6/17
User Interaction Designs 2 days Tue 11/7/17 Wed 11/8/17
System Interface Designs 2 days Thu 11/9/17 Fri 11/10/17
Confirming and Designing the Functions of
Application 1 day Mon 11/13/17 Mon 11/13/17
Database Relationship and Entity Identification 2 days Tue 11/14/17 Wed 11/15/17
Designing the Database 4 days Thu 11/16/17 Tue 11/21/17
Peripheral Device Identification and Communication
Design 2 days Wed 11/22/17 Thu 11/23/17
Implementation 29 days Fri 11/24/17 Wed 1/3/18
Programming the Application 12 days Fri 11/24/17 Mon 12/11/17
Developing the Database 6 days Tue 12/12/17 Tue 12/19/17
Developing the Software Units 5 days Wed 12/20/17 Tue 12/26/17
Including the Third Party Software 2 days Wed 12/27/17 Thu 12/28/17
Implementing the User Interface and API 4 days Fri 12/29/17 Wed 1/3/18
Test 5 days Thu 1/4/18 Wed 1/10/18
Software Unit Testing 1 day Thu 1/4/18 Thu 1/4/18
Testing the Database Functionality 1 day Fri 1/5/18 Fri 1/5/18
Testing the System Efficiency 1 day Mon 1/8/18 Mon 1/8/18
Database Efficiency Testing 1 day Tue 1/9/18 Tue 1/9/18
Documentation 1 day Wed 1/10/18 Wed 1/10/18
Deployment 1 day Thu 1/11/18 Thu 1/11/18
Go Live 1 day Thu 1/11/18 Thu 1/11/18

ID Duration Start Finish Predecessors Resource Names
0 82 days Wed 9/20/17 Thu 1/11/18
1 14 days Wed 9/20/17 Mon 10/9/17
2 1 day Wed 9/20/17 Wed 9/20/17
3 1 day Thu 9/21/17 Thu 9/21/17 2
4 1 day Fri 9/22/17 Fri 9/22/17 3
5 3 days Mon 9/25/17 Wed 9/27/17 4
6 4 days Thu 9/28/17 Tue 10/3/17 5
7 2 days Wed 10/4/17 Thu 10/5/17 6
8 2 days Fri 10/6/17 Mon 10/9/17 7
9 17 days Tue 10/10/17 Wed 11/1/17
10 3 days Tue 10/10/17 Thu 10/12/17 8
11 2 days Fri 10/13/17 Mon 10/16/17 10
12 3 days Tue 10/17/17 Thu 10/19/17 11
13 2 days Fri 10/20/17 Mon 10/23/17 12
14 5 days Tue 10/24/17 Mon 10/30/17 13
15 2 days Tue 10/31/17 Wed 11/1/17 14
16 16 days Thu 11/2/17 Thu 11/23/17
17 3 days Thu 11/2/17 Mon 11/6/17 15
18 2 days Tue 11/7/17 Wed 11/8/17 17
19 2 days Thu 11/9/17 Fri 11/10/17 18
20 1 day Mon 11/13/17 Mon 11/13/17 19
21 2 days Tue 11/14/17 Wed 11/15/17 20
22 4 days Thu 11/16/17 Tue 11/21/17 21
23 2 days Wed 11/22/17 Thu 11/23/17 22
24 29 days Fri 11/24/17 Wed 1/3/18
25 12 days Fri 11/24/17 Mon 12/11/17 23
26 6 days Tue 12/12/17 Tue 12/19/17 25
27 5 days Wed 12/20/17 Tue 12/26/17 26
28 2 days Wed 12/27/17 Thu 12/28/17 27
29 4 days Fri 12/29/17 Wed 1/3/18 28
30 5 days Thu 1/4/18 Wed 1/10/18
31 1 day Thu 1/4/18 Thu 1/4/18 29
32 1 day Fri 1/5/18 Fri 1/5/18 31
33 1 day Mon 1/8/18 Mon 1/8/18 32
34 1 day Tue 1/9/18 Tue 1/9/18 33
35 1 day Wed 1/10/18 Wed 1/10/18 34
36 1 day Thu 1/11/18 Thu 1/11/18
37 1 day Thu 1/11/18 Thu 1/11/18 35
W S T M F T S W S T M F T S W S T M F T S W S T M F T S W S T
Sep 10, '17 Sep 24, '17 Oct 8, '17 Oct 22, '17 Nov 5, '17 Nov 19, '17 Dec 3, '17 Dec 17, '17 Dec 31, '17 Jan 14, '18
b. Provide a table with a summary of the development costs for the project and
system using excel or a similar program (use Australian dollars).
(Insert table and explanation here)
Summary of Development Costs for Royal Melbourne Hospital Management System
Expenses Amount
Hardware $23,000
Human Resource $8,000
Legal Affairs $3,000
Software $11,000
Additional $5000
Total $50,000
The hardware are data tapes, servers, computers and printers
The software are chatting software, attendance application and many more
Contract is done with third party software

c. Provide a table with a summary of the estimated annual operating costs using
excel or a similar program (use Australian dollars).
(Insert table and explanation here)
Summary of the estimated annual operating costs
Recurring expense Amount
Hardware Maintenance $3,000
Software Renewal $1,500
Contract Renewal $500
Total $5,000
d. Undertake a cost/benefit analysis:
i. Describe the anticipated benefits from the deployment of the new
system (outline tangible and intangible benefits).
(Insert answer here)
Tangible Benefits:
i. Reduction in additional cost in patient concession for mistakes generated from data
errors
ii. Attracting new patients
Intangible Benefits:
i. Better patient treatment
ii. Increased patient loyalty
ii. Provide a table with a summary of estimated annual benefits.
(Insert table and explanation here)
Estimated Annual Benefits
Benefit or cost saving Amount
New patient $49,000
Reduction in Operations $51,000
Total $1,00,000
New patients will come to Royal Melbourne Hospital for the improved care
The operation cost will reduce as the system will do back-office operations

3. Perform a Risk and Feasibility Analysis – Complete the following tasks (minimum
500 words):
a. Determine organisational risks and feasibility.
(Insert answer here)
Bigger, more intricate wellbeing frameworks have demonstrated especially responsive to the
presentation of mechanical advancement. This is to some degree on account of their huge
human, hierarchical and money related capital, yet additionally their mind boggling
administration structures with awesome degrees of progressive system. Accordingly,
accessible proof features the significance of senior initiative and lead proficient (or
"champion") bolster, bringing about more prominent proprietorship encompassing execution
exercises. The underlying execution can be problematic for hierarchical working and
individual methods for acting as staff endeavor to comprehend new work processes. Making
extra time accessible to singular clients, for instance, by proactively decreasing workloads
amid this day and age as well as presenting the innovation when there are no other real
changes in the association, can relieve the danger of unintended outcome.
b. Evaluate technological risks and feasibility.
(Insert answer here)
The technical risks are as following.
i. High probability that this necessity is difficult to comprehend and actualize due to
misty syntactic depiction
ii. Necessities' progressions happen regularly on account of solid business targets yet it
may cause danger generally item conveyance
iii. Notes and suppositions in necessities contain notes and presumptions which may
bring about growing incorrectly usefulness
iv. Unseemly portrayal of necessities contains pseudo-code, references to different
records or prerequisites, and so on which may diminish its understandability from
semantic perspective
v. Untraceable prerequisites has broad coupling with different necessities which may
make it powerless towards external elements. Late changes of this prerequisites is
profoundly likely
vi. Various "wishes" in one necessity contains numerous solicitations which may make it
hard to create and test

c. Assess resource risks and feasibility.
(Insert answer here)
The group should be painstakingly built with the ranges of abilities important to every
subsystem. On the off chance that information holes are experienced, outside mastery should
be contactable amid the task life expectancy. For every part there necessities to exist no less
than one potential reinforcement who can be approached short notice should the colleague be
not able work for any reason.
d. Identify schedule risks and feasibility.
(Insert answer here)
The schedule risks are as following.
i. Lack of time provided for several or single activity
ii. The project cannot accept new requirement provided by client Royal Melbourne
Hospital
iii. The team members are not available on the time for a specific activity
iv. Ineffective to attract the stakeholder interest
v. Time consuming in the long run
vi. Improper time distribution for project activities
4. Establish the Project Environment – Complete the following tasks (minimum 500
words):
a. Provide a table outlining information that will be captured during system
development, the tools and software that will be used to develop the system,
and outline who can update / view the information.
(Insert table and explanation here)
Information Capture Method
User Requirement Questionnaire and Interviews
System Requirement Questionnaire, Interviews, Survey, Case Study
revision and many more

System Specification Requirement Analysis
Project Requirement Analysing All the gathered data
b. Describe the work environment.
(Insert answer here)
So as to minimize expenses, the workplace will be on a work from home premise. The
software engineers will approach free incorporated improvement situations (IDEs) that help
Java, HTML, CSS, Javascript and a virtual MySQL server. They will be enlisted and ready to
get to a typical git store. Each colleague will have an assigned work telephone number and
email for correspondence and furthermore be enrolled on Slack and Skype with the last being
introduced on their workstations.
c. Describe the processes and procedures that will be used. (Page 276)
(Insert answer here)
The programming will be isolated into singular errands in gatherings between the venture
chief and two software engineers. The senior software engineer ought to be viewed as the
consultative specialist in relegating the work. Once the senior software engineer has
organized the assignments, they are then ready to designate segments of work to the lesser
developer as needed.The thought is that the senior developer will chip away at the primary
rationale behind the frameworks, while the lesser developer will give a supporting part.
Specific care should be taken by the senior developer in the correspondence over the product
engineering and between various subystems.
Test-driven improvement (TDD) will frame the reason for all programming undertakings.
This implies unit tests will be composed before the code to take out time spent investigating.
When tests are passed, code can be refactored as important with the goal that the code stays
brief all through the length of the undertaking. With a specific end goal to counteract
predisposition in testing, every developer will check the other's work after specific modules
have been finished. This should be possible by the programming making their own particular
tests and testing the other developer's code through them.
The meeting minutes, criticism and plan determination will all be put away on Slack for
simple survey. The venture supervisor will be in charge of staying up with the latest and
guaranteeing that the group is on track. Casual Skype session will be held once every two
days and the aftereffects of those additionally recorded on Slack. The undertaking supervisor
will likewise send bi-week after week messages to the Luminscape officials to impart the
task's advance.
Code will be submitted onto a git store which naturally sends a caution on the group's Slack

channel. A strategy of making confers routinely and regularly will be supported, especially
after effective testing. As has been specified, the test-driven advancement will assist
guarantee bugs are kept to a base, with any vital troubleshooting apportioned time.
5. Schedule the Work – Complete the following tasks (minimum 300 words):
a. Provide a work breakdown structure (WBS) for one (1) of the subsystems.
(Insert WBS here)
WBS Task Name
0 Implementing Information System in Royal Melbourne Hospital
1 Project Planning
1.1 Recognizing Scope of the Project
1.2 Identifying the Deliverable of the Project
1.3 Configuring the Project Acceptance
1.4 Recruiting Project Team Members
1.5 Developing Project Schedule
1.6 Carry Out Cost Estimation
1.7 Cost Benefit Analysis
2 System Requirement
2.1 Predefining the Requirements
2.2 Selecting Requirement Gathering Techniques
2.3 Gathering Requirements
2.4 Evaluating Collected Requirements
2.5 Recording the Data Found in Analysis
2.6 Verifying the Requirements
3 Design
3.1 Designing the Architecture of the System
3.2 User Interaction Designs
3.3 System Interface Designs
3.4 Confirming and Designing the Functions of Application
3.5 Database Relationship and Entity Identification
3.6 Designing the Database
3.7 Peripheral Device Identification and Communication Design
4 Implementation
4.1 Programming the Application
4.2 Developing the Database
4.3 Developing the Software Units
4.4 Including the Third Party Software
4.5 Implementing the User Interface and API
5 Test
5.1 Software Unit Testing
5.2 Testing the Database Functionality
5.3 Testing the System Efficiency
5.4 Database Efficiency Testing

5.5 Documentation
6 Deployment
6.1 Go Live
b. Provide a Gantt chart showing the WBS project activities timeline. You must
use Microsoft Project and provide a screen capture.
(Insert Gantt chart here)
WBS Task Name Duration Start Finish Predecessors
0 Implementing Information System at
Royal Melbourne Hospital 42 days Wed
9/20/17
Thu
11/16/17
1 Project Planning 10 days Wed
9/20/17
Tue
10/3/17
1.1 Project Scope Identification 1 day Wed
9/20/17
Wed
9/20/17
1.2 Project Deliverable Developing 1 day Thu
9/21/17
Thu
9/21/17 2
1.3 Project Acceptance Criteria Setup 1 day Fri 9/22/17 Fri 9/22/17 3
1.4 Project Team Form 3 days Mon
9/25/17
Wed
9/27/17 4
1.5 Project Scheduling and Cost Estimation 4 days Thu
9/28/17
Tue
10/3/17 5
2 System Requirement 10 days Wed
10/4/17
Tue
10/17/17
2.1 Requirement Identification 3 days Wed
10/4/17 Fri 10/6/17 6
2.2 Requirement Analysis 2 days Mon
10/9/17
Tue
10/10/17 8
2.3 Requirement Documentation 5 days Wed
10/11/17
Tue
10/17/17 9
2.4 Requirement Verification 2 days Wed
10/11/17
Thu
10/12/17 9
3 Design 9 days Fri
10/13/17
Wed
10/25/17
3.1 System Architecture Design 3 days Fri
10/13/17
Tue
10/17/17 11
3.2 System Functionalities Identification 2 days Wed
10/18/17
Thu
10/19/17 13
3.3 Software Designing 1 day Fri
10/20/17
Fri
10/20/17 14
3.4 Website Modification Identification 2 days Fri
10/13/17
Mon
10/16/17 11

3.5 Database Design 4 days Wed
10/18/17
Mon
10/23/17 13
3.6 Peripheral Device Identification 2 days Tue
10/24/17
Wed
10/25/17 17
4 Implementation 13 days Thu
10/26/17
Mon
11/13/17
4.1 Implementing Information System 12 days Thu
10/26/17
Fri
11/10/17 18
4.2 Implementing Sales Force Automation 6 days Thu
10/26/17
Thu
11/2/17 18
4.3 Implementing Additional Computers
Required 5 days Fri 11/3/17 Thu
11/9/17 21
4.4 Connecting ERP with SFA 2 days Fri
11/10/17
Mon
11/13/17 22
4.5 Modifying Website 4 days Fri 11/3/17 Wed
11/8/17 21
5 Test 5 days Thu
11/9/17
Wed
11/15/17
5.1 System Testing 1 day Thu
11/9/17
Thu
11/9/17 24
5.2 Database Connection Testing 1 day Fri
11/10/17
Fri
11/10/17 26
5.3 Network Testing 1 day Mon
11/13/17
Mon
11/13/17 27
5.4 Unit Testing 1 day Tue
11/14/17
Tue
11/14/17 28
5.5 Test Outcome Documentation 1 day Wed
11/15/17
Wed
11/15/17 29
6 Deployment 1 day Thu
11/16/17
Thu
11/16/17
6.1 Go Live 1 day Thu
11/16/17
Thu
11/16/17 30

ID Duration Start Finish Predecessors Resource Names
0 42 days Wed
9/20/17
Thu
11/16/17
1 10 days Wed 9/20/17Tue 10/3/17
2 1 day Wed 9/20/17Wed 9/20/17
3 1 day Thu 9/21/17Thu 9/21/172
4 1 day Fri 9/22/17 Fri 9/22/17 3
5 3 days Mon 9/25/17Wed 9/27/174
6 4 days Thu
9/28/17
Tue
10/3/17
5
7 10 days Wed 10/4/17Tue 10/17/17
8 3 days Wed 10/4/17Fri 10/6/17 6
9 2 days Mon 10/9/17Tue 10/10/178
10 5 days Wed 10/11/17Tue 10/17/179
11 2 days Wed 10/11/17Thu 10/12/179
12 9 days Fri 10/13/17Wed 10/25/17
13 3 days Fri 10/13/17Tue 10/17/1711
14 2 days Wed 10/18/17Thu 10/19/1713
15 1 day Fri 10/20/17Fri 10/20/1714
16 2 days Fri 10/13/17Mon 10/16/1711
17 4 days Wed 10/18/17Mon 10/23/1713
18 2 days Tue 10/24/17Wed 10/25/1717
19 13 days Thu 10/26/17Mon 11/13/17
20 12 days Thu 10/26/17Fri 11/10/1718
21 6 days Thu 10/26/17Thu 11/2/1718
22 5 days Fri 11/3/17 Thu 11/9/1721
23 2 days Fri 11/10/17Mon 11/13/1722
24 4 days Fri 11/3/17 Wed 11/8/1721
25 5 days Thu 11/9/17Wed 11/15/17
26 1 day Thu 11/9/17Thu 11/9/1724
27 1 day Fri 11/10/17Fri 11/10/1726
28 1 day Mon 11/13/17Mon 11/13/1727
29 1 day Tue 11/14/17Tue 11/14/1728
30 1 day Wed 11/15/17Wed 11/15/1729
31 1 day Thu 11/16/17Thu 11/16/17
32 1 day Thu 11/16/17Thu 11/16/1730
W S T M F T S W S T M F T S W S
Sep 10, '17 Sep 24, '17 Oct 8, '17 Oct 22, '17 Nov 5, '17 Nov 19, '17

6. Discover and Understand the Requirements – Define the functional and non-
functional requirements for the system using the FURPS+ framework (minimum 300
words).
(Insert answer here)
Usability: The system can be used by the users from the very first day. The navigation and
use of the system will be similar to well-known applications. The users can learn the use of
the system with three days.
Reliability: The system is very reliable and effective. The users can get the assistance of the
system whenever needed. The system can be trusted in maintaining the back-office processes.
The system should be used at all times of need.
Correctness: The applications and software that will be used in the system will be very
powerful. Those applications can does all the meaningful processes correctly. The system
will be calculating the patient invoice, due payment, appoint date suggest and many more.
Durability: The system is very strong and will not fail very easily. The average time of
system failure can be estimated as 4 years. The system cannot be damaged completely. The
database of the system will be managed through a separate subsystem so that any cyber attack
cannot access database.
Security: Authentication of User is required so as to keep any malevolent or unintended
control of the configurable items. Administrators will have enlisted usernames and
passwords. The CMS will utilize HTTPS to guarantee that the customer and server
correspondence is secured against being perused or altered by an outsider.
Interface: The interface of the system will serve as the interaction medium between the user
and system. The user interface components will depend on the purpose of the section and user
requirement.
7. Identify the internal, external, operational, and executive stakeholders for the system
(minimum 300 words).
(Insert answer here)
Internal Operational: Doctors, Physicians, Staff, Nurses
External Operational: Patients
Internal Executive: Manager, CEO, Head of the Department

External Operational: Government, Shareholders
8. Target a specific group of operational stakeholders and create a questionnaire that will
be used to collect information about their system needs. Be sure to use a combination
of open and closed-ended questions and identify the stakeholder that your
questionnaire is targeting (minimum 300 words).
(Insert questionnaire here)
The questionnaire asked to the receptionist are as following.
i. What kind of facility is required to support business more?
ii. What kind of data is required most to start major operations?
iii. Which is accessed most?
iv. Is every query of patient is solved?
v. If it does then does it happen in time?
vi. What should not be in the system?
vii. Which data you want to access?
viii. What modification do you think is required to enhance patient service?
9. Identify all the object classes and provide a complete domain model class diagram for
the system. You must use Microsoft Visio.
(Insert domain model class diagram here)
The class diagram includes four classes that has represented the components for the system
application. One patient can make appointment several times. The date of the appointment will be
registered. One health record will be maintained for each patient. One doctor will be seeing a
patient. The doctor specialist will be recorded into the system.

10. For each subsystem, identify and provide brief use case descriptions for all use cases.
(Insert brief use case descriptions here)
Registration: The patient will register into the system. The system will store personal and account
information. The system will provide an id and password at the end of registration.
Request for Doctor: The patient will request to visit a doctor. The system will check for doctors that
are available and make an appointment.
Patient health record: The patient health record can be seen by doctors and patients only.
Patient Appointment: The receptionist can see which patient has appointment with which doctor.
Doctor Attendance: The receptionist can access the record of present doctors regarding a day.
11. For one particular subsystem, identify and provide one (1) fully developed use case
description.
(Insert use case descriptions here)
Use Case Name: Login
Scenario: Patient login to the system
Triggering Event: A session against a particular patient will initiate
Brief Description: The patient will login to the system to access the data and
function
Actors: Patient
Related Use Case: Registration
Stakeholders: Patient, Patient Care
Preconditions: Patient must be registered
Post conditions: Patient should not be banned from system
Flow of Activities Actor System
The patient will login to
system
The system will check for id
and password verification
The patient will redirected to
profile page is id and password
is correct
If not then to registration page
Exception Conditions Patient is logged in but not directed to profile page

12. For the identified use case, provide one (1) use case diagram. You must use
Microsoft Visio.
(Insert use case diagrams here)
The system will be used by three users, has been visualized as the actors of the Use Case. Only the
receptionist can access the attendance of all the doctors along with the appointment of the patients.
The patient have to register into the system and login to request for doctor. Both doctor and patient
can access the health record of patient.

13. For the use case diagram provide a corresponding activity diagram to illustrate all the
steps within the use case. You must use Microsoft Visio.
(Insert activity diagrams here)
The activity diagram visualizes the process of setting an appointment with the doctor. The
patient request for doctor. The system checks if the any of the mentioned doctors in the
mentioned specialist type is available or not. If doctor is available, then the system asks for a
date. The system searches available doctors on that date. The system finalizes the

appointment and send an notification with appointment details to the patient.
14. For the activity diagram provide a corresponding system sequence diagram (SSD).
You must use Microsoft Visio.
(Insert SSD here)
The sequence shows that the request the doctor to the system. The system retrieve data from the
database regarding the customer authorization. If the patient is new then patient will register. Then
the patient enter date and appointment is set.

15. Design the system components – Provide a high-level architectural diagram and
explain the environment within which the system will operate (i.e., stand alone,
networked, hosting options, cloud infrastructure, etc.) (minimum 300 words).
(Insert high-level architectural diagram and explanation here)

16. Provide story boards illustrating the user interface for at least four (4) screens. Discuss
how you have applied best-practice user-interface design concepts (minimum 300
words).
(Insert user interface diagrams here)
Login Page:

Registration Page:
Patient Profile Page

Chat:

17. Deploy the solution – Describe the approach for planning and managing
implementation, testing, and deployment for the system (minimum 500 words).
(Insert answer here)
The creation condition will be arranged of different equipment and programming segments.
As delineated in the abnormal states programming engineering chart, the framework requires
a database server, an application server and a web server. The web server has the site and a
stored duplicate of the Joomla CMS and database. Refreshing these reserved duplicates will
be performed by means of the in-house application server.
The product parts of the framework depend on the Simple Object Access Protocol (SOAP)
cooperation standard. Extensible Markup Language (XML) records will be sent between the
web benefit and the frontend (regardless of whether the site or the CMS proofreader).
Cleanser calls will be made by the PHP code behind. Calls to the database will be made
utilizing MySQL questions through PHP classes. Luminscape should buy and put in new
database and application servers. The web server is given by ausweb.com facilitating.
Gatherings will be directed with the I.T. director to guarantee every specialized detail are
clung to. The sending of the framework is required to happen with insignificant interruption
because of the way that the framework takes into account a completely new retail item run
which is as yet being created. This is rather than integrating the databases with the current
business run. The organization in this way, will normally take a more straightforward course.
This implies the establishment of the new framework will be rapidly made operational
without shutting off more seasoned frameworks.
The information required once the framework begins is to be acquired from the MySQL
database and served on another database server. This implies existing databases won't should
be reused, nor will the replicating and changing over of information from old databases need
to occur. Despite the fact that it could be conceivable to utilize a portion of the normal item
things from the business run databases, the work required in change would be outlandishly
more prominent than manual information section for this situation. Since the retail items
themselves have not been finished, the heft of the information section work will be performed
inside the CMS manager in any case. The forming framework to be utilized through
advancement will be Git. This is a free appropriated source code control framework. It
permits the capacity of source code records in an archive, includes checking methodology
and executes software engineer verification. On the off chance that a software engineer
wishes to roll out an improvement to the ace source code, they can make a branch for a
working duplicate and consolidation it back onto the ace when wanted. This keeps any
significant issues from being erroneously spared and furthermore implies that numerous
developers won't have the capacity to refresh a similar record simultaneously. Regardless of
the possibility that an issue happens that is unworkable in the present source code, the

developer can return to a prior record.
The real form control of the framework itself will be attempted with alpha, beta and creation
discharge stages. Any further updates will appear as a support discharge. Mistakes or change
solicitations can be influenced by means of to telephone or email correspondence.
Luminscape utilizes SharePoint intranet usefulness and prompts that reports can be made to
the I.T. supervisor who would then be able to look for work tickets for any progressions to be
actualized.
You must use Microsoft Project for the Gantt chart and Microsoft Visio for all UML
diagrams produced for this assignment, otherwise your answers will not be marked. All
diagrams must be part of a single file. Additional files and attachments will not be
marked.
All tables, diagrams, and charts must be accompanied by a one paragraph description
(minimum 100 words) to help explain your rationale and logic. Note that presentation,
spelling, and grammar are extremely important aspects of your design. Be sure to proof read
your work prior to submission.
Submission Information:
1. Compile all the diagrams and specifications professionally into a single MS Word
document. (Do not submit a pdf file.)
2. Use the following format for the Word document’s filename:
Last Name_First Name_Student Number.doc
(e.g., Smith_John_s2841999.doc)
3. Carefully review the assignment marking criteria.
4. Do not compress your assignment file.
5. Submit your assignment online by going to the “Assignment” section of the course
web site.