1. IS 184 System Integration, Testing and Documentation
Deliverable 1: Project Proposal
Date Given: Thursday, November 27, 2014
Submission DEADLINE: Monday, December 1, 2014
Project Title
1.0 Team Profile
Team Member Strengths Member Role
Diez, Ozelle Roxy E.
Daleon, Crizza
Espolong, Stephanie A.
1.1 Proposed Project Description
1.1.1Subsystem A
Subsystem A Name: Medicine Inventory
Description: Medicine inventory shows the list of all medicine available.
Functional Requirements: Provids comprehensive reports on medicine consumption patterns and
regular updates on expired/out of stock medicines.
1.1.2 Subsystem B
Subsystem B Name: Patient Scheduling
Description: Patient Scheduling shows patient’s schedule for the next visitation.
Functional Requirements: Show the schedule in a column grid.
2.0 Objectives:
The main objective of the developers is to provide a subsystem into the existing system of the
individual treatment record in Rural Health Unit. The project aims at exploring novel ways of
organizing and using digital technology to enhance the quality of services rendered to patients. The
ultimate goal is to create a subsystem that would show the list of medicine inventory and patient
scheduling.
3.0 Methodology:
In making the proposed subsystem, the developers follow a step-by-step process to know how to
start and ensure the satisfaction of the client based on the requirements provided and to make the
system work in terms of its reliability, security, and functionality.
1. In the planning phase, the developers were brainstorming for the proposed subsystem. The
developers conducted a preliminary survey to determine the problem and the scope of the project.
2. In the analysis phase, the developers were gathering data through initiating consultations and
assessments to have some document requirements. Also, the developers model a diagram to have an
overview on the functions of the system.

2. 3. Inthe design phase, the developers designed the interfaceof the projectincluding the input, output
and the processes to identify what will be needed to be coded.
4. In the implementation phase, through the information gathered, it is now easy for the developers
to both organizes the data in the algorithm needed for the source code and provides a means to
introduce the interpretations of it into quantitative methods.
5. In the testing phase, the developers checksif the system is working and investigates the system to
provide clients the quality of the system. It is also an independent view of the software to appreciate
and understand the risks of the software implementation.
6. In the maintenance phase, the developers maintain the system by providing change, update,
addition and correction for the system.
4.0 Related Work
Format:
Subsystem/System name: Medicine Inventory
Brief Description:
 Medicine Inventory Management Subsystem is designed to ensure effectivemanagement and
monitoring of requisition, allocation, disbursement, receipt and consumption in Rural Health
Clinic across the process. In addition to providing comprehensive reports on medicine
consumption patterns and regular updates on expired/out of stock medicines; this system
allows nurses/facilitator to manage medicine requisitions and allocation to facilities in the
community.
Subsystem/System name: Patient Scheduling
Brief Description:
 Patient Scheduling System helps the busy front desk schedule patients faster, reduce
appointment no-show, increase copay collection and deliver the information needed to
manage the practice with certainty. And see patient’s schedule in a column on the grid
alongside the schedules of the treating clinicians.
Reference: http://pitb.gov.pk/mims
http://www.asapsystems.com/medical_supplies_inventory.php
http://spectrasoft.com/
Attachment:
Project Log File: