Health Care Facility System

3.2 Software Design Specification

Software Design Specification

Page 1

Health Care Facility System

3.2.1 Introduction This chapter describes the design and architectural requirements and specifications in developing the Health Care Facility System. The purpose of this section is to provide a high-level design framework to build the Health Care Facility System. It will provide as a list of requirements against which to test the final project and determine if the researchers of this project were able to be successful on implementing the system according to design. 3.2.1.1 Goals and Objectives The underlying concepts are the goals and objectives of Health Care Facility System: a. Recording of Diseases occurred in municipals and Barangay. b. Allocation of vaccine and drugs request and re-order point of medicines and estimated life span of medicine. c. User-friendly, easy-to-use & web-enabled applications d. Enhancing the communication and establishing cooperation between the Barangay and the municipal.

3.2.1.2 Statement of Scope This part includes the description of the software functionality followed by detailed requirements. The first part is the login. A user should enter their username and password. The software will determine its privileges. Administrators are responsible for processing and accessing information from the other databases and systems. Doctor/Assistant Administrator are responsible for processing and accessing information of staffs and patient. Employee/Staffs they are responsible for adding and updating patients information. Health Care Facility System User Requirements

Software Design Specification

Page 2

Health Care Facility System

Req. No.

Priority Reference

Description

Access Privileges R1 High User There shall be three levels of access: and

administrator, Employee/Staff. R2 R3 R4 R5 High High Med High User User User User

Doctor/Assistant

Admin,

Admin are permitted to add and edit all data. Admin are allowed to view audit trails. All user privileges are allowed to view reports. Only Administrators can view executive and confidential reports. Staff/employee can only add and update patients info and view limited reports.

R6

Med

User

Security R7 High User Each user is required to login before accessing the services of HCFS. R8 R9 High High User User A password shall be given to each user If password is forgotten, a new password will be given Reports R10 High User Reports are administered by

administrator/assistant admin only R11 High User Reports are generated from the information returned by the database of the systems. User Interface R12 High User The system shall have a web-based platform that works with web browsers. R13 High User The system shall respond to all user requests within 25 seconds.

Software Design Specification

Page 3

Health Care Facility System

3.2.1.3 Software Context The Health Care Facility System considers the following concepts; the promulgation of national health standards, goals, priorities and indicators; development of special health programs and projects and advocacy for legislation on health policies and programs, it enables to help to secure people primary health, it accesses, analyzes and captures data from the database. With the help of Health Care Facility System, users are capable of making promotion, protection, preservation or restoration of the health of the people through the provision and delivery of health services and through the regulation and encouragement of providers of health goods and services that drive innovative decisions, asking questions and pursuing insights on their own or collaboratively, searching across all their data to get the big picture. 3.2.1.4 Major Constraints The Health Care Facility System is intended to help Local Government Units (LGU) on promoting, protection or restoration of the health of the people through the provision and delivery of the health services and through the regulation and encouragement of providers of health goods and services. As a part of the project it is capable of delivering a full range of reporting, analysis to enable the decision to quickly gain new insights and take

actions to drive better outcomes of performance with the flexibility of the Local Government Unit. 3.2.2 Data Design To understand the data design for the Health Care Facility System, it is important to have a look at the overall design of the application. As the application is being built in Java and MS SQL the overall application design can be categorized into three parts based on the above mentioned application developing languages. 1. Front End Graphical User Interface
Software Design Specification Page 4

Health Care Facility System

2. Back End Data 3. Internal Functional Procedures 3.2.2.1 Internal Data Structure Graphical User Interface (GUI) Java is being used for the development of the front end of the system as Graphical User Interface. Java provides a huge set of usable GUI components panel and frame for building GUI applications. Java GUI components allow users to interact with the software via mouse and keyboard as forms of inputs. Back End Data MS SQL is used for the development of the back end as the database technology and data storage system. MS SQL offers great reliability and ease of use. It includes several clients, utility programs and includes both command-line programs and graphical programs. It is mainly for administering data contained within tables and databases. Internal Functional Procedures For accessing or viewing any table, the data is fetched directly from the Database Management System to the Java database objects and are displayed directly on the screen. For report printing, temporary local variables have been defined in the procedures with meaningful names to store different values and then print the report. 3.2.2.2 Global Data Structure The only available data globally to the whole system is the database that is stored in MS SQL. After the connecting to the database, any data stored can be fetched and updated. 3.2.2.3 Temporary Data Structure
Software Design Specification Page 5

Health Care Facility System

The Health Care Facility System does not use any intermediate temporary files of its own. As data is being stored in the database, all the intermediate data it being stored by the DBMS. 3.2.2.4 Database Description All tables with their corresponding attributes and descriptions are mentioned below:

Table Name: Attributes: Description:

hcfs_r _user_01 User_Id, User_Username, User_password, User_AccessKey, User_Employee_Id This table holds all the general information of all the users of HCFS. The primary key of this table is User_Id.

Table Name: Attributes: Description:

hcfs_r _facility_02 Facility_Id, Facility_location, Facility_Barangay, Facility_Officer_In_Charge, Facility_User_Id This table holds all the general information of all facilities of HCFS. The primary key of this table is Facility_Id. hcfs_r _Item_03 Item_Id , Item_Name, Item_Description , Item_Type This table holds all the general information of Item of HCFS. The primary key of this table is Item_Id. hcfs_r _disease_04 Disease_Id , Disease_Name,Disease_Description This table holds all the general information of Disease of HCFS. The primary key of this table is Disease_Id. hcfs_r _disease_05 Disease_Id , Disease_Name,Disease_Description This table holds all the general information of Disease of HCFS. The primary key of this table is Disease_Id. hcfs_r _program _06 Program_Id , Program_Name,Program_Description Program_Status , Program_Type

Table Name: Attributes: Description:

Table Name: Attributes: Description:

Table Name: Attributes: Description:

Table Name: Attributes:

Software Design Specification

Page 6

Health Care Facility System

Description:

This table holds all the general information of Program_of HCFS. The primary key of this table is Program_Id. hcfs_r _program _07 Treatment_Type_Id,Treatment_Type_Name, Treatment_Type_Program_Id This table holds all the general information of Treatment Type of HCFS. The primary key of this table is Treatment_Type_Id.

Table Name: Attributes: Description:

Table Name: Attributes:

Description:

hcfs_t _donor _08 Donor_Id , Donor_Date_Issued, Donor_Item_Id , Donor_Item_Quantity , Donor_Notes , Donor_Type, Donor_User_Id This table holds all the general information of Donor of HCFS. The primary key of this table is Donor_Id. hcfs_t _supply_09 Supply_Id ,Supply_Item_Id , Supply_Date , Supply_Status , Supply_Type , Supply_Description , Supply_Facility_Id , Supply_User_Id . This table holds all the general information of Supply of HCFS. The primary key of this table is Supply_Id.

Table Name: Attributes:

Description:

Table Name: Attributes:

Description:

hcfs_t _supply_09 Supply_Id ,Supply_Item_Id , Supply_Date , Supply_Status , Supply_Type , Supply_Description , Supply_Facility_Id , Supply_User_Id . This table holds all the general information of Supply of HCFS. The primary key of this table is Supply_Id. hcfs_t _message_10 Message_Id,Message_Title , Message_Content , Message_Date , Message_Status, Message_Receiver_Id , Message_User_Id. This table holds all the general information of Message of HCFS. The primary key of this table is Message_Id. hcfs_t _medication_11 Medication_Id, Medication_No_of_Medication, Medication_Date , Medication_Item_Id, Medication_Quantity , Medication_User_Id. This table holds all the general information of Medication of HCFS. The primary key of this table is Medication_Id.
Page 7

Table Name: Attributes: Description:

Table Name: Attributes: Description:

Software Design Specification

Health Care Facility System

Table Name: Attributes: Description:

hcfs_t _treatment_12 Treatment_Id , Treatment_No_of_Treatment , Treatment_Date ,Treatment_Item_Id , Treatment_Quantity , Treatment_User_Id. This table holds all the general information of Treatment of HCFS. The primary key of this table is Treatment_Id. hcfs_t _checkup_13 CheckUp_Id, CheckUp_No_of_Checkup , CheckUp_Date ,CheckUp_Item_Id , CheckUp_Quantity , CheckUp_User_Id. This table holds all the general information of CheckUp of HCFS. The primary key of this table is CheckUp_Id. hcfs_t _inventory_14 Inventory_Id , Inventory_Item_Id , Inventory_Quantity , Inventory_Date_In , Inventory_Date_Expiration, Inventory_User_Id. This table holds all the general information of Inventory of HCFS. The primary key of this table is Inventory_Id. hcfs_t _distribution_15 Distribution_Id , Distribution_Facility_Id , Distribution_Item_Id , Distribution_Quantity, Distribution_User_Id This table holds all the general information of Distribution of HCFS. The primary key of this table is Distribution_Id.

Table Name: Attributes: Description:

Table Name: Attributes:

Description:

Table Name: Attributes: Description:

Software Design Specification

Page 8

Health Care Facility System

3.2.3 Architecture and Component Level Design 3.2.3.1 Architectural Diagram

Software Design Specification

Page 9

Health Care Facility System

3.2.3.2 Description of Components 3.2.3.2.1 Component User 3.2.3.2.1.1 Processing Narrative of Component User The component User contains the class User. It contains the basic attributes of the Administrator. It also contains the functions and processes that enters and get the data from the database. The class User holds the data and functions that are unique. The primary role of this class is to declare the variables of basic data of the user and to get relative data in and out of the database. 3.2.3.2.1.2 Interface Description of the Component User The component user has an interface with the class Administrator which attributes and functions are inherited. The users are identified thru the accounts that are set by the administration. This is to limit and set restrictions to users of the system. The attributes shown in this interface and also the functions that are related to these attributes to set and get from the database are defined in this class. 3.2.3.2.1.3 Algorithmic Description of Component User Component User; The primary duty of this component is to set basic user data and set restrictions into the database and get data from the database Start Declare variables of the basic data Set the basic data of the user in the database Get the data from the database End

Software Design Specification

Page 10

Health Care Facility System

3.2.3.2.1.4 Design Class Hierarchy

Restrictions/Limitations This component can only be called when the user meets the requirements. 3.2.3.2.2 Component Administrator 3.2.3.2.2.1 Processing Narrative of Component Administrator The component Administrator contains the class Administrator. It contains the basic attributes an Administrator. It also contains the functions and processes that enters and get the data from the database. The primary role of this class is to declare the variables of basic data of the user and to get relative data in and out of the database. 3.2.3.2.2.2 Interface Description of the Component Administrator The component administrator has an interface with the different class which attributes and functions are inherited. The Administrator class is the one that is in charge of the control of data and information displayed for the user. The administrator attributes are share with the class User and other attributes related to the administrator class. 3.2.3.2.2.3 Algorithmic Description of Component Administrator Component Administrator;

Software Design Specification

Page 11

Health Care Facility System

The primary duty of this component is to get data from the database to be displayed into the report. Start Login Set the data of the Admin to the database Set the data of the Health Care to the database Get the data from database Display the data to the Reports End 3.2.3.2.2.4 Design Class Hierarchy

Software Design Specification

Page 12

Health Care Facility System

3.2.3.2.3.5 Restrictions /limitations The component Administrator is only allowed to view and print reports. Any action to modify the data from the database is not allowed. 3.2.3.3 Dynamic behavior for component 3.2.3.3.1 Interaction Diagrams A sequence diagram, for each use case, the component realizes, is presented TOP

Figure A

This is a sequence diagram where the use case component is the Administrator. The first event, system ready, derived from the external environment, capabilities and channels behavior to an Administrator object. The Administrator enters a password. A request lookup event is passed to system
Software Design Specification Page 13

Health Care Facility System

that looks up the password in the software system and returns a result (found or not found) to Monitor. A valid password results in a password correct event to the software system which then gives access to the Administrator and the Administrator can add/update/delete all the data. And this data can be displayed on the monitor or printed from the printer upon request.

Figure B This is a sequence diagram where the use case component is the Assistant Admin/doctor. The first event, system ready, derived from the external environment, capabilities and channels behavior to a doctor object. The doctor enters a password. A request lookup event is passed to system that looks up the password in the software system and returns a result (found or not found) to Monitor. A valid password results in a password correct event to the software system which then gives access to the doctor and the doctor can only
Software Design Specification Page 14

Health Care Facility System

add/update limited entities. And this data can be displayed on the monitor or printed from the printer upon request.

3.2.4 User Interface Design The application has a graphical user interface, which is built completely in java. Among the variety of libraries available in java we have chosen java swing library for development as more variety of component available in it and more sophisticated techniques are available to change to appearance of those components if required in future.

3.2.4.1 Description of the User interface 3.2.4.1.1 Screen Images The GUI for the Health Care Facility System is very user friendly, easy to navigate and very easy to learn that requires only a little of understanding to use it.

Below is the detailed images and description of the GUI. The object and action is performed when you clicked them are also identified.

The first image is the login screen. The user is supposed to have a username and a password in order to login. When the user clicks the login, the user will be redirected to the main page of the system. Otherwise if the username or password is not correct, they will be notified that they entered the wrong combination of username and password.

Software Design Specification

Page 15

Health Care Facility System

Below is the administrator interface. This interface has only those options that are only accessible to the administrator. The GUI below is self-explanatory. The administrator is supposed to click on any available options to add, update or access them. Once clicked another GUI will appear that will have further option in any of the above button is clicked.

Software Design Specification

Page 16

Health Care Facility System

When you click the print report on the menu of the administrator this will give the access to the reports generated by the system and the user can print a physical copy of that report. Also the administrator has the menu of adding a new user of the system which has to be an employee. When you click the add user on the menu of the administrator this will give the user the privilege to add a new user of the system on a different GUI. When the cancel button is clicked the interface will go back to menu.

When you click the Received Supply this will give the user the privilege to add a new supply and this will update the supply information. When the cancel button is clicked the interface will go back to menu.

Software Design Specification

Page 17

Health Care Facility System

3.2.4.1.2 Objects and actions The above shown GUI windows consist of java swing components. The windows consist of label for displaying a text. Text fields for entering or editing text. And command buttons are used for execution procedures. 3.2.4.2 Interface Design rules Strive for consistency the developers strive for consistency of the designs that will be used on the system so that the users will not have a hard time on understanding the interfaces. Offer informative feedback For every action that is done, there is a feedback on it so that the user will know what happen on the transaction. Offer simple error handling developers design the system so the user cannot make a serious error that users cannot understand. Permit easy reversal of actions users can undo the performed action once they made an error or mistake. Enable frequent user to use shortcuts frequent users of the system can use function keys and shortcuts so that users can easily go to their desired screen or option.

Software Design Specification

Page 18

Health Care Facility System

3.2.4.3 Components available Java swing library have many components available but for now only frames, text labels, text fields and buttons are being used on the GUI. Among them only the buttons have been added to the mouse action listener. Rests have no action listener attached to them. More components may be added in the future if necessary.

3.2.4.4 UIDs description No user interface development system has been used in the development of the Health Care Facility System. The system will only be used by authorized personnel and will not be available to the public.

3.2.4.5 Reports The reports of the system are shown in Analytical representation. The summary report will be shown to the report of Health Care Facility System. Moreover, the system will produce reports for weekly, daily, monthly, annually or as if needed the report. 3.2.5 Restrictions, Limitations and Constraints a. The system should integrate with the other systems and will show different important reports. b. The system is written in Java and the database is MS SQL. c. The system will be only used by Administrator, Health Officer and Health Workers. 3.2.6 Testing Issues The various tests to be conducted to validate the software developed are login test, get/collect data test, test session and view report test.

Software Design Specification

Page 19

Health Care Facility System

Classes of Testing

Description

Expected Software Response

Performance Bounds

Components to be Identified

Log In

Test Data

This test class is defined to validate whether the user is able to log in with his username and password. This test class is defined to validate whether all the information within or from the other interrelated systems are being processed and collected. This test class is defined

The user will be able to log in when he enters his username and password.

The user should not log in if enters a wrong username or password.

The administrator will be able to collect data within or from the other interrelated systems when he clicks the appropriate button for getting data.

User

This test will print session User

Test Session

to the information. the

validate whether session information is

being displayed or not. Test Report This test class is defined to validate whether all the reports of HCFS are working. The user will be able to view all the reports and perform analytical approaches and decision making by accessing the report view which automatically displays information

Reports

Software Design Specification

Page 20

Health Care Facility System

of different health center and search for the desired report to be printed.

Software Design Specification

Page 21