Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Dispensary Management System, Thesis of Software Engineering

it is basically a project thesis .in universities and high school to avoid manual management system for health centre.it is basically intranet software.

Typology: Thesis

2021/2022

Available from 12/12/2022

55-sabreena-ayoub
55-sabreena-ayoub 🇮🇳

1 document

1 / 77

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
DISPENSARY MANAGEMENT SYSTEM FOR
NORTH CAMPUS
Project Report
By
Sabreena Ayoub
&
Yusra Manzoor
Under the Supervision of
(Er. Haris Manzoor Qazi)
(Assistant Professor)
DEPARTMENT OF COMPUTER SCIENCE AND
ENGINEERING
UNIVERSITY OF KASHMIR
NORTH CAMPUS
DELINA, BARAMULLA- 193101
2022
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32
pf33
pf34
pf35
pf36
pf37
pf38
pf39
pf3a
pf3b
pf3c
pf3d
pf3e
pf3f
pf40
pf41
pf42
pf43
pf44
pf45
pf46
pf47
pf48
pf49
pf4a
pf4b
pf4c
pf4d

Partial preview of the text

Download Dispensary Management System and more Thesis Software Engineering in PDF only on Docsity!

DISPENSARY MANAGEMENT SYSTEM FOR

NORTH CAMPUS

Project Report

By

Sabreena Ayoub

Yusra Manzoor

Under the Supervision of

(Er. Haris Manzoor Qazi)

(Assistant Professor)

DEPARTMENT OF COMPUTER SCIENCE AND

ENGINEERING

UNIVERSITY OF KASHMIR

NORTH CAMPUS

DELINA, BARAMULLA- 193101

DISPENSARY MANAGEMENT SYSTEM FOR

NORTH CAMPUS

Project Report Submitted in Partial Fulfillment of

The Requirements for the Degree of

Bachelor of Technology

In

Computer Science and Engineering

By

Sabreena Ayoub (Roll No. 18048112055)

Yusra Manzoor (Roll No.18048112060)

Under the Supervision of

(Er. Haris Manzoor Qazi)

(Assistant Professor)

DEPARTMENT OF COMPUTER SCIENCE AND

ENGINEERING

UNIVERSITY OF KASHMIR

NORTH CAMPUS

DELINA, BARAMULLA - 193101

Acknowledgment

First of all we thank Almighty Allah (SWT) who has bestowed us with His blessings and empowered us enough to be working on this project. It is our esteemed pleasure to present a project on “Dispensary Management System for North Campus”. Any Achievement big or small should have a catalyst and constant encouragement and advice of valuable and noble minds for our efforts to bring out this project. The satisfaction that accompanies the successful completion of any task would be incomplete without mentioning those who made it possible because success is the epitome of hard work, determination, and dedication. We express our deep gratitude to our project guide, Er. Haris Manzoor Qazi , gave us the inspiration to pursue the project and guided us with dedication. We also express our deep gratitude to our project coordinator Er. Khalid Hussain for his support and guidance. We would also like to thank all the teaching and non teaching staff of the Department of Computer Science and Engineering North Campus for helping us at various stages of our project work. Last but not least we are thankful to all faculty members and lab instructors whose support at various stages, this project would not have materialized. Sabreena Ayoub (18048112055) Yusra Manzoor (18048112060) November 2022 University of Kashmir, North Campus, Delina, Baramulla

Abstract

Dispensary Management system is an Intranet Software.A significant part of the operation of any dispensary involves the acquisition,management and timely retrieval of great volumes of information.This information typically involves ,patient’s personal information and medical history,staff information and various facilities waiting lists.All of such information must be managed in an efficient and cost wise fashion so that dispensary management system making it more efficient and error free.It aims at standardizing data,consolidating data ensuring data integrity and reducing inconsistencies. This Dispensary Management System is particularly designed for North Campus to replace their existing manual,paper based system..The system keeps track of stock and the Admin will be able to know what is further needed to add to the dispensary stock and keeps note of the quantity sold as well. This system helps in the selection of suitable drugs, and may also obtain health histories. Accurately managing stock amounts, medical records date-wise, month wise and also medical records between customized dates, and suitable storage necessitates reliable tracking.These functions are to be provided in an efficient,cost effective manner,with the goal of reducing te time and resources currently required for such tasks.

List of Figures

  1. Fig 1. Waterfall model (Page No. 6 )
  2. Fig 2: Project Resources (Page No. 12 )
  3. Fig 3: Web Application Process (Page No. 17 )
  4. Fig 4. Requirement Engineering Process (Page No. 22 )
  5. Fig 5 Internet Application Engineering (Page No. 26 )
  6. Fig 6. Depicts a design pyramid for Web Engineering. (Page No. 28 )
  7. Fig 7. Detailed life cycle of Project (Page No. 18 )
  8. Screenshots of the Project (Fig 12 to Fig 38) (Page No. 55 - 68 )

List of Acronyms

  1. DFD:-Data Flow Diagram
  2. HTML:-HyperText Markup Language
  3. CSS:-Cascading Style Sheets
  4. SQL:-Structured Query Language
  5. PHP:-Personal Home Page/Hypertext Preprocessor

Dispensary Management System for North Campus Department of Computer Science and Engineering

CHAPTER 1

OBJECTIVE & SCOPE

Dispensary Management System for North Campus Department of Computer Science and Engineering

1.1 Objective

Dispensary Management is an intranet software which allows admin to access the information about the patient’s past records and allows them to manage stock accordingly. University Dispensary Management is designed for efficient data analysis and report generation of medical related data at our campus. This application allows Admin to add Patient’s details in a secured way. Main feature of this system is stock management. The system keeps track of stock and Admin will be able to know what is further needed to add to the dispensary stock and keeps note of the quantity sold as well. This system helps in the selection of suitable drugs, may also obtain health histories. Accurately managing stock amounts, medical records date wise, monthwise and also medical records between customized dates, and suitable storage necessitates reliable tracking.

1.2 Scope

● Dispensary information: Through this service one can access the dispensary related information of the campus. ● Patient (student,teaching or non teaching) record: This application will keep the medical records of the patient. Also, if there will be any deletion of the record by mistake, it can be restored back to the application and data will remain updated. ● Student record: In this application, admin can check the records of students of each class section wise so as to keep data updated. ● Stock record: stock is maintained in such a way that it is very easy to access. ● Notifications: Every time when any medicine remains less or we can say when any thing in stock is about to be out of stock the Admin will be notified.

1.3 Problems in existing system:

● It was limited to a single system. ● It was less user-friendly. ● There is a lot of manual work (Manual system does not mean that we are working with pen and paper, it also includes working on spread sheets and other simple software's) 2

Dispensary Management System for North Campus Department of Computer Science and Engineering

CHAPTER 2

REQUIREMENT ANALYSIS &

PLANNING

Dispensary Management System for North Campus Department of Computer Science and Engineering

2.1 User requirements:

The following requirements are raised during the analysis of the needs of the users: ⮚ A dispensary admin should be able to login to the system through the first page of the Application. ⮚ The Admin can create users as per user requirement. ⮚ Admin can upload the data for the Stock. ⮚ Admin can provide report to the patient with the date and prescribed medicines and Doctor advise. After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of the existing running system is also difficult, improper understanding of the present system can lead to diversion from solution.

2.2 Analysis Model

This document plays a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during the testing phase. Any changes made to the requirements in the future will have to go through a formal change approval process. The classical waterfall model is the basic software development life cycle model. It is very simple but idealistic. Earlier this model was very popular but nowadays it is not used. But it is very important because all the other software development life cycle models are based on the classical waterfall model. The classical waterfall model divides the life cycle into a set of phases. This model considers that one phase can be started after the completion of the previous phase. That is the output of one phase will be the input to the next phase. Thus the development 5

Dispensary Management System for North Campus Department of Computer Science and Engineering The procedure model known as the waterfall model is based on the phases defined by Royce – but the term itself has come about since then. In the essay written by Royce, the term “waterfall” does not even appear.

2.3 Graphical user interface:

In the flexibility of the uses the interface has been developed with a graphics concept in mind, associated through a browser interface. The GUI’S at the top level have been categorized as

  1. Administrative user interface
  2. The operational or generic user interface The administrative user interface concentrates on the consistent information that is practically part of the organizational activities and which needs proper authentication for the data collection. The interfaces help the administrations with all the transactional states like Data insertion, Data deletion and Date updating along with the extensive data search capabilities. The operational or generic user interface helps the users upon the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information helps the ordinary users in managing their own information in a customized manner as per the assisted flexibilities.

2.4 Study of the System

The system after careful analysis has been identified to be presented with the following modules: The modules involved are:

  1. Admin Login : Through this service one can access the information about the campus dispensary such as stock, patient records, students, reporting, notifications etc. 7

Dispensary Management System for North Campus Department of Computer Science and Engineering

CHAPTER 3

SYSTEM DEVELOPMENT

LIFECYCLE

Dispensary Management System for North Campus Department of Computer Science and Engineering application could overload the system or require additional hardware. This requires financial consideration to accommodate technical enhancement. The study should answer the following questions:

  1. Whether the project can carry out the existing equipment?
  2. Whether the existing software is enough?
  3. If a new technology is required, how best can it be implemented? Operational feasibility: Operational Feasibility is concerned with human, organizational and political aspects. Operational feasibility covers two aspects. One is the technical performance aspect and the other is acceptance within the organization. Technical performance includes issues such as determining whether the system can provide the right information for the organization’s personnel, and whether the system can be organized so that it always delivers this information at the right place at the right time. Operational feasibility must determine how the proposed system will fit in with the current operations and what, if any, job reconstruction and retraining will be needed to implement the system. The evaluation must then determine the general attitudes and job skills of existing personnel. Economic feasibility: Among the most important information contained in the feasibility study is cost benefit analysis and assessment of the economic justification for a computer-based system project. Cost benefit analysis delineates cost for the project development and weighs them against tangible and in-tangible benefits of a system. Cost benefit analysis is complicated by the criteria that vary with the characteristics of the system to be developed, the relative size of the project and the expected return on investment desired as part of the company's strategic plan. In addition, many benefits derived from a computer-based system are in-tangible (e.g., better design quality through iterative optimization, increased customer satisfaction through programmable control etc.). as this is an academic project for our university, so neither it requires a huge amount of money nor any costly tools or infrastructure to be set up for it. Behavioral feasibility:
It evaluates and estimates the user attitude or behavior towards the development
of a new system. It helps in determining if the system requires special effort to
educate, retrain, transfer, and changes in employee’s job status in new ways of

Dispensary Management System for North Campus Department of Computer Science and Engineering

conducting business.

3.2 Project Planning

Software project Management begins with a set of activities that are collectively
called Project Planning. Before the project begins, the manager and the
software team must estimate the work to be done, the resources that will be
required, and the time that will elapse from start to finish.
Planning involves estimation – your attempt to determine how much money, how
much effort, how much resources and how much time it will take to build a
specific software-based system or product.
Estimate begins with a description of the scope of the product. Until the scope is
“bounded” it’s not possible to develop a meaningful estimate. The problem is
then decomposed into a set of smaller problems and each of these is estimated
using historical data and experience as guides. It is advisable to generate your
estimates using at least two different methods (as a cross check). Problem
complexity and risks are considered before a final estimate is made.

3.3 Project Planning Objectives:

1. Software scope: The first activity in software project planning is the determination of software scope. Software scope describes the data and control to be processed, function, performance, constraints, interfaces and reliability. 2. Feasibility: Once the scope has been identified, it is reasonable to risk: “can we build software to meet the scope? Is the project feasible?”

3. Resources: Another software planning task is the estimation of the resources

required to accomplish the software development effort.

4. Decomposition: Software project estimation is a form of problem solving and, in

most cases, the problem to be solved is too complex to be considered in one piece. For this reason, we decompose the problem, re-characterizing it as a set of smaller problems. Decomposition can be: decomposition of problem and decomposition of process. 11