COIT20248 Information Systems Analysis and Design Assignment 2

Desklib provides solved assignments and past papers to help students succeed.

COIT20248 Information Systems Analysis and
Design
Assignment 2 - Website Design and Modelling

Contents
Introduction:...............................................................................................................................3
Use Cases:..................................................................................................................................4
Context level Diagram:..............................................................................................................6
Level 0 data flow diagram:........................................................................................................7
ER Diagram:...............................................................................................................................8
CRUD Diagram:.......................................................................................................................10
Prototype:.................................................................................................................................11
Conclusion & Summary:..........................................................................................................17
Presentation:.............................................................................................................................17
References:...............................................................................................................................18

List of figures:
Figure 1: Use Case Diagram......................................................................................................6
Figure 2: Context Level Diagram..............................................................................................8
Figure 3: Level 0 data flow diagram........................................................................................10
Figure 4: Entity-relation diagram.............................................................................................12
Figure 5: Home Page................................................................................................................15
Figure 6: Features Page............................................................................................................16
Figure 7: Department Page.......................................................................................................17
Figure 8: Our Doctors..............................................................................................................18
Figure 9: Locations Page..........................................................................................................19
Figure 10: Contact Us Page......................................................................................................20
Figure 11: Slide 1.....................................................................................................................23
Figure 12: Slide 2.....................................................................................................................23
Figure 13: Slide 3.....................................................................................................................24
Figure 14: Slide 4.....................................................................................................................24
Figure 15: slide 5......................................................................................................................25
Figure 16: Slide 6.....................................................................................................................25
Figure 17: Slide 7.....................................................................................................................26
Figure 18: Slide 8.....................................................................................................................26
Figure 19: Slide 9.....................................................................................................................27
Figure 20: Slide 10...................................................................................................................27
Figure 21: Slide 11...................................................................................................................28
Figure 22: Slide 12...................................................................................................................28
Figure 23: Slide 13...................................................................................................................29
Figure 24: Slide 14...................................................................................................................29
Figure 25: Slide 15...................................................................................................................30
Figure 26: Slide 16...................................................................................................................30
Figure 27: Slide 17...................................................................................................................31
Figure 28: Slide 18...................................................................................................................31
Figure 29: Slide 19...................................................................................................................32
Figure 30: Slide 20...................................................................................................................32
Figure 31: Slide 21...................................................................................................................33
Figure 32: Slide 22...................................................................................................................33
Figure 33: Slide 23...................................................................................................................34
List of tables:
Table 1: Use Case Table............................................................................................................7
Table 2: Entity-Attributes........................................................................................................13
Table 3: CRUD Table..............................................................................................................14
Table 4: Member's Contribution..............................................................................................21

Introduction:
Information system used for the purpose to collect, store, process and distribute different
kinds of data in an organization system with using a format. The information is also about the
hardware, software and network of the organization. The current scenario is to design the
Hospital information system with implement different functionalities like electronic medical
record, radiology information system and many more. The major requirements of the system
are to secure the information with privacy on the user’s data and track all the records with
remote access to the data. The assignment includes use case diagram, context level diagram,
data flow diagram and ERD with CRUD diagram for the current scenario of Hospital
information system.
The objective of the project is to make transparency in the hospital to implement different
services and information system using different technologies. Secure the patient's data as well
as employees data in the newly implemented system and provide access to only authorised
people. Provide different services to patients with an effective cost.

Use Cases:
The initial stage of the development of software program including all the requirements is
known as the use case diagram. This diagram used to find the behaviour of the system or
users with the method and what it performs. Use cases represent with a visual and textual
way to define the concept of use case modelling. The use case diagram designs the
relationship between the users and functions of define system. It uses actors as the users and
functions as the use cases. The main purpose of the use case diagrams is to find the system
requirement, draw a valid system architecture and develop different domains and analysis
them. Represent a use case in the system with communication link ad actors with its function.
The users of the use case diagram are doctors, hospital staff, IT team and admin (Visual-
paradigm, 2019). Here defines the use case of the current scenario with the proper description
as below:

Figure 1: Use Case Diagram

Table 1: Use Case Table
Sr. No. Function Description
1. Registration Register the patient in the system to enter basic
details by the hospital staff.
1.2 Quick registration This function is for the emergency patients with
the quick registration facility
2. Biometric/Password Implement biometric with username password
functionality to access the daily record of
employees
4. Insurance process Cover the insurance process in the newly
integrated system by the hospital staff
5. E-prescription Provide e-prescription by the doctors for the long-
distance patients
6. Investigation/inquiry Get the solutions of any queries of the users by the
hospital staff and know the estimated cost of the
treatment
7. Implement EMR, LIS,
RIS & PACS
Implement different services to track the complete
process of the system and manage the database of
the users
8. Implement Economic
Order Quantity
Start this service to check the medicines with their
expires date and change them
9. Secure system/manage
information
Implement security in the system and manage the
information of different users
10. Track & Alert Track the stakeholders with the work status in all
conditions
10.1 Bar code implementation Implement bar code functionality for the
employees and patients
11. MIS Implement management information system in the
with standards rules and regulations.

Context level Diagram:
The context diagram for the hospital information system used to define the boundaries
between the environment and the system. Different entities are used to define in this diagram
with their interaction functions. The advantages of the context diagram are like:
 The boundaries and scope of the system define with the presented interface
 It is not required to have the technical background to understand the context level
diagram
 It is easy to draw and amend as per requirement and it is beneficial for the
stakeholders, developers, data analyst and business analyst
Figure 2: Context Level Diagram
The above diagram of context level includes six entities, IT team, reception, admin, hospital
staff, doctors and patients. These six entities have a different goal like doctors get the patient
details and provide e-prescription. The patient entity gets the medical report to providing its
data to the information system or the hospital staff. The admin and hospital staff entities
different kinds of works as, send the staff details to implement different services. Provide the
patient's details to register successfully on the information system. The insurance approved to
providing the patient details to the information system or the hospital staff members. The
reception gets the patient details to provide the cost estimation of the treatment (lucidchart,
2019).

Level 0 data flow diagram:
The graphical representation of the flow of data in the system of business information is
known as a data flow diagram. This diagram has two types, physical and logical. The
physical DFD used to define the implementation of the logical flow of data and the logical
type used to define the data flow with a system for the performance of functionality of the
business. DFD is used to define process and functions that to store and capture the data
between the system and its components or environment. It works as a communication tool
between the system and user designer. The basic use of DFD is to define the logical
information flow and the simplicity of notation with the establishment of the requirement of
automated and manual. DFD categorised in different levels, these are level 0, level 1 and
level 2. Level 0 the basic level diagram that is also known as a context diagram and represent
a node to show the process with the connection to entities. Level 1 includes the subprocess to
represent the flow of data and level 2 divide more a process with subprocesses. the below
diagram of data flow uses some symbols to represent the process, data store an entity with the
data flow. Circles used to represent the process, rectangle used to represent the data store, the
square is for entity and arrow refers to the data flow. Here is the data flow diagram of the
hospital information system (Bangerter, 2017).

Figure 3: Level 0 data flow diagram

ER Diagram:
Entity relationship diagram is used to represent the database design by using entities and
attributes. It creates a relationship between attributes and entities. It is also known as the ER
model. Different kinds of use cases are used in the ER modelling like, database design,
database debugging, database creation and patching with aid in requirements gathering.
The entity is the object that defines in the database and used to fill in the table. the attribute is
the property of the entities that used to create a physical database. For example, a student is
the entity of a database and student id, name, address, phone number are the attribute of the
student entity.
The concept of the primary key and foreign is defined in the database where the primary key
is the unique entity of the database and foreign is key is a reference of the primary key. A
foreign key of a table is the primary key of another table.
The relationship is the term used to create a relation between two entities with associated
numbers. It has different types like one to one, one to many, many to one and many to many.
The entity relationship diagrams have three different types, conceptual, physical and logical.
Present the ERD of the current scenario of the hospital information system is here with
different entities, attributes and their relationship. An entity represents with the symbol of a
rectangle; the relationship represents the shape of a diamond and attributes with the circle or
oval shape (Rouse, 2018).

Figure 4: Entity-relation diagram
The above diagram of the entity-relationship model for the hospital information system
includes different entities with attributes as below: