Abstract

DECLARATION
ACKNOLEDGMENT
DEDICATION

Contents
Chapter 1........................................................................................................................................8
1.1 INTRODUCTION....................................................................................................................8
1. Project Overview......................................................................................................................8
2. Scope..........................................................................................................................................8
3. Goals..........................................................................................................................................8
3.1 Document Conventions................................................................................................................9
3.2 Project Planning...........................................................................................................................9
3.3 Risk Management........................................................................................................................9
3.3.1 Project Risks:........................................................................................................................9
3.3.2 Product Risks:......................................................................................................................9
3.3.3 Project Features...................................................................................................................9
3.3.4 User Classes and Characteristics........................................................................................10
3.3.5 Admin:...............................................................................................................................10
3.3.6 End User:............................................................................................................................10
4. Operating Environment........................................................................................................10
5. Design and Implementation Constraints.............................................................................10
5.1 Design constraints......................................................................................................................10
5.2 Methodology..............................................................................................................................10
5.3 Development tool.......................................................................................................................10
5.4 Database.....................................................................................................................................10
5.5 Reports.......................................................................................................................................10
Chapter 2......................................................................................................................................11
1. Functional Requirements......................................................................................................11
Hospital Management System..........................................................................................................11
2.1.2 Nonfunctional Requirements.............................................................................................12
Performance Requirements...............................................................................................................12
Security Requirements......................................................................................................................12
Maintainability...................................................................................................................................12
Serviceability.....................................................................................................................................12
Privacy 12
 Quality 13
Response time:..................................................................................................................................13
Stability: 13
Supportability:...................................................................................................................................13
2.1.3 Testability:.........................................................................................................................13
User Cases.........................................................................................................................................14
2.1.4 Administration Login..........................................................................................................14
2.1.5 Administration Logout.......................................................................................................15
2.1.6 Doctor................................................................................................................................16
2.1.7 Test Adder..........................................................................................................................16
2.1.8 Token.................................................................................................................................17
2.1.9 Rooms Status.....................................................................................................................17
2.1.10 Refractive...........................................................................................................................18
2.1.11 LAB Test.............................................................................................................................18
2.1.12 Doctor Salary form.............................................................................................................19
2.1.13 Salary details.....................................................................................................................19
2.2 Problem Domain........................................................................................................................20
2.2.1 Problems............................................................................................................................20
2.2.2 Existing Methodologies.........................................................................................................20
There are many projects and systems that are based on the methodologies of software engineering. The
methodologies have to common phase like:..........................................................................................20
 Requirement...................................................................................................................................20
2.2.8 Adopt Methodologies.............................................................................................................26
We are using the waterfall model. Water fall model is the simplest model of software development
paradigm. It says the all phases of SDLC will function one after another is linear manner. That is,
when the first phase is finished then only the second phase start and so on..........................................26
2.2.9 Reason for Choosing Methodology........................................................................................26
Chapter 3......................................................................................................................................27
ANALYSIS AND DESIGN.........................................................................................................27
3.1 Analysis Model..........................................................................................................................27
3.1.1 USE cases...........................................................................................................................27
.......27
3.1.2 ERD:...................................................................................................................................28
.......28
3.1.3 Class diagram:...............................................................................................................29
3.2 Sequence Diagram (SD) of each use case..................................................................................29
3.2.1 Hospital LOGIN diagram...................................................................................................29
TESTING AND IMPLEMENTATION.....................................................................................29
4.1.2 Integration Testing:............................................................................................................30
Integration testing is a type of testing occurs when two or more modules are combined together.
This is necessary because if two modules are not working properly together then your system fails.
Hence we test multiple probability modules for proper working of the system...............................30
 4.1.4 White Box Testing:.............................................................................................................30
White box testing is the detailed investigation of internal logic and structure of the code. White box
testing is also called glass testing or open box testing. In order to perform white box testing on an
application, the tester needs to possess knowledge of the internal working of the code. The tester
needs to have a look inside the source code and find out which unit/chunk of the code is behaving
inappropriately..................................................................................................................................30
DEVELOPMENT.................................................................................................................................40
5.1 HOSPITAL MANAGEMENT SYSTEM..................................................................................40
5.1.1 CHART OF HOSPITAL MANAGEMENT SYSTEM..........................................................40

Chapter 1
1.1 INTRODUCTION
2. Project Overview
3. Scope

SMS is intended to help the any institute that wants to store their students and
management records into the computer. Our software is specially designed for an
educational institute. It will store all the personal and academic information of the
students. It will also store the fee information of the students. Management will get
information of any student who studied/studying in this institute till now easily. This
software will also help the management to store their employee’s information including
their personal information and salary information. Payroll system is very important of
any organization .so this software will also handle the pay roll system of institute. It will
also store the results of the students.

4. Goals
Now these days computer play an important role in any organization because computer
can easily manage the great number of data as compare to human. User can easily
access data on right time in computer. So it is difficult for the management to get
information about the institute on right time. When computer system play in the
institute it will make easy to manage and access data of the institute. The School
management system (SMS) based upon the following objectives:

Record Keeping

The first objective of this system is to maintain the data of all the student and teacher in
database. It maintains the personal record as well as the academic record of the student.
It maintains student fee record and dues record. Teacher personal record and salary
record are also store in the software. SMS also manage class record, subject record,
examination record.

 Reports
Reports are the most important outputs of school management system (SMS). SMS
create the following reports.

Total number of student in the class

Student admission reports

Character certificate of the student

Submitted Fee reports

Submitted due reports

Teacher Appointment Letter

Teacher Experience reports

Salary reports

Bonus reports

Examination report

Detail Marks Certificate

4.1 Document Conventions

Product Risks

4.3.1 Project Features

User Classes and Characteristics

4.3.2 Admin:

End User
5. Operating Environment

6. Design and Implementation Constraints

6.2 Methodology

6.3 Development tool

6.4 Reports