Software Requirements Specifications

Online Eye Care System

Project Code:
CPMIT17S1-4

Internal Advisor:
Mr.Ramzaan Malik
Miss Samreen Razzaq

External Advisor:
Miss Laraib

Project Manager:
Mr. Amir Zia
Project Team:
Maryam Ramzan (MITF17E049)
Ammara Shafiq (MITF17E015)
Muhammad Arslan Zafar (MITF17E046)
(Group-4)

Submission Date:
Nov.28,2018

_____________________
<Project code> Software Requirements Specifications <Version x>

Project Manager’s Signature

Document Information
Category Information

Customer Uos
Project Online eye care system
Document Requirement Specifications
Document Version 1.0
Identifier
Status Draft
Maryam Ramzan (MITF17E049)
Author(s) Ammara Shafiq (MITF17E015)
Muhammad Arslan Zafar (MITF17E046)
Approver(s) PM
Issue Date Nov. 22, 2018
Document Location
1. Advisor
Distribution 2. PM
3. Project Office

Definition of Terms, Acronyms and Abbreviations

This section should provide the definitions of all terms, acronyms, and abbreviations required to interpret
the terms used in the document properly.

Term Description
ASP Active Server Pages
RS Requirements Specifications

Nov.28, 2018 Page 2 of 8

<Project code> Software Requirements Specifications

Table of Contents

1. INTRODUCTION..........................................................................................................................5
1.1 Purpose of Document.........................................................................................................................5
1.2 Project Overview..................................................................................................................................5
1.3 Scope.....................................................................................................................................................5

2. OVERALL SYSTEM DESCRIPTION.......................................................................................5

2.1 User characteristics.............................................................................................................................5
2.2 Operating environment.......................................................................................................................5
2.3 System constraints..............................................................................................................................5

3. EXTERNAL INTERFACE REQUIREMENTS........................................................................6

3.1 Hardware Interfaces............................................................................................................................6
3.2 Software Interfaces..............................................................................................................................6
3.3 Communications Interfaces................................................................................................................6

4. FUNCTIONAL REQUIREMENTS............................................................................................6
5. NON-FUNCTIONAL REQUIREMENTS..................................................................................6
5.1 Performance Requirements...............................................................................................................6
5.2 Safety Requirements...........................................................................................................................6
5.3 Security Requirements........................................................................................................................6
5.4 User Documentation............................................................................................................................7

6. ASSUMPTIONS AND DEPENDENCIES.................................................................................7

7. REFERENCES...................................................................................................................................7
8. Appendices...................................................................................................................................7

Nov.28, 2018 Page 3 of 8

<Project code> Software Requirements Specifications

1. Introduction

1.1 Purpose of Document

This document is a key document among all stakeholders. All stakeholders like developers, coder, manager and
designer can read this document. Developers and coders can take guideline from this document. If they want to
modify or change something in system.

1.2 Project Overview

Our project is such type of website for online appointment. We want to make a website named as online eye care
system. It will provide the information about doctors for appointment. It will provide the result fastly.poeople who
want appointment and doctor’s information, system can fulfills their need within seconds.

1.3 Scope
This system will replace the old system that is currently used in most hospitals. This environment of this system is
based on php and MySql. This system has three users, which are for the patient, doctors and administrator. Each of
these users has their own permitted area in order to access this system. This project is useful for the user to book for
an appointment for an eye check up through the system rather than manually. The appointment details will be
booked and on the prescribe date the can directly visit to the hospitals...

2. Overall System Description

We make this system using a machine such as laptop. Different languages will use in it like HTML, CSS, Jquery,
php and platform will use Dreamweaver. The online eye care system web service requires an Apache web server
able to run PHP. And browser use to show the output. Agile approach will use. Assumptions and dependencies.
2.1 User characteristics
Admin
Admin has all the administrative rights. He can update the information, he can delete any information that is now
not in use. Admin can update his information.
Viewer
Visitor can read doctor‘s information .Visitor also can view and visit doctor’s profile.
Visitor can also view whole website.
Doctor
Doctor can accept and reject appointments. He can also change appointment time. Doctor can view patient’s
medical record. Doctor can update his information.
Patient
Patient can take appointments. Patient can also cancel his appointment. Patient can also update his information.
2.2 Operating environment
Visitors, registered user and Admin can use this system. But registered user can use this system most other then.
User must have Mobile phone or any laptop and must have internet facility they can use.
2.3 System constraints
Constraints are the limitations which are outside the control of the project must be managed within these
constraints
 Software constraints
 The software constraints include all the software which we use to make this system for example:
 AdobeDreamwevar: for designing the website.
 Microsoft Visio 2010, Star UML: Diagrams Designing Tools (See Appendix A)
Nov.28, 2018 Page 4 of 8
<Project code> Software Requirements Specifications

 Microsoft Office 2007: Documentation tool

 Xampp: Testing tool
 Database system to store and retrieve data from database.
 Hardware constraints
 We require the internet enabled machine to run the application. We also need printer to generate receipt.
 Cultural constraints
 Languages used are
 JavaScript: For evaluation at user end
 MySQL: Database
 Xampp: local Web Server

 Legal constraints
 Environmental constraints
 Internet enabled machine is the necessary to run this application.
 User constraints
 This project is designed for the hospitals. It is user friendly and has user friendly interface.

3. External Interface Requirements

It includes the followings.

3.1 Hardware Interfaces

Online eye care system client side service requires a PC able to run windows XP or higher. Online eye care system
server side service requires the ability to grow dynamically based upon number of clients and frequency of
communications but does not initially require a large amount of space or resources to run. A functional mouse and
keyboard are required for fully functionality of both the client and server sides of online eye care system .

3.2 Software Interfaces

Online eye care system integrates with multiple software’s including Word press for web site generation and
management, online eye care system also utilizes an Apache server with PHP functionality and both an offline and
online MySQL database for time management. On the client side of the product online eye care system must run on
a Windows XP or better OS.

3.3 Communications Interfaces

All communications and syncing between the client and server happen in XML formatted messages sent in HTTP
messages. (See Appendix B)

4. Functional Requirements
4.1 Patient registration
The system should make provision for a way to identify every patient uniquely. In the prototypes used for the current
study a unique patient number was generated automatically for every new patient registered .

4.2 Administration
Management can rely on the system. Admin can update, change, and delete any record or information on the
website.

Nov.28, 2018 Page 5 of 8

<Project code> Software Requirements Specifications

4.3 Medical Record

Recording of medical intervention, i.e. consultation details, results of special investigations, conditions
diagnosed treatments, etc.
4.4 Report generation
The system shall generate reports on patients about the following information: patient’s medical record,
patient’s name and the doctor’s name which was assigned
4.5 Database
Each patient shall have the following mandatory information: first name, last name, phone number, address, city,
country, patient identification number. 

4.6 Update Information

System shall allow the user to update any of the patient’s information as phone number, city, address etc.  

5. Non-functional Requirements

5.1 Performance Requirements

 Response Time
 The system shall give responses in 1 second after checking the patient’s information. 
 Capacity 
 The System must support 1000 people at a time. 
 User-interface 
 The user-interface screen shall respond in a few seconds. 
 
5.2 Safety Requirements
Humans are error-prone, but the negative effects of common errors should be limited. E.g. users should realize that
a given command will delete data, and be asked to confirm their intent or have the option to undo.
5.3 Security Requirements
Each member is required to enter an individual Username & password when accessing the software.
Administrators have the option of increasing the level of password security their members must use. The data in
the database is secured through multiple layers of Protection. One of those security layers involves member
passwords. For maximum Security of your software, each member must protect their password.
5.4 Availability 
 The system shall be available all the time

5.5 User Documentation

Typically it contains:
 Table of content
 Short introduction and overview of system.
Nov.28, 2018 Page 6 of 8
<Project code> Software Requirements Specifications

 Brief technical details such as hardware and software requirement to run the system
 User guide: This is the bulk of the system
 Glossary of technical terms
 Trouble Shooting : Usually a simple list of things to check before calling for further help
 Index

6. Assumptions and Dependencies

The daily reports of process will be generated by queries on the database. The user must know how to interact
with the system. Database administrator will be responsible for manipulating with database.

7. References
Ref. No. Document Title Date of Release/ Publication Document Source
1 Project Proposal Oct 18, 2018
Assumptions& Nov 22, 2018 www.wiluprojects.com
2
dependencies
Functional and non- Nov 25,2018 www.quora.com/What-
functional requirement are-the-requirements-for-
a-hospital-management-
system
3
https://www.scribd.com/docu
ment/247913699/SRS-for-
Hospital-Management-
System

8. Appendices
Appendix A:
(UML is a common language for business analysts, software architects and developers used to describe, specify,
design, and document existing or new business processes, structure and behavior of artifacts of software
systems.)
Appendix B:
(HTTP is based on the client-server architecture model and a stateless request/response protocol that operates by
exchanging messages across a reliable TCP/IP connection.  HTTP messages are passed in a format similar to
that used by the Internet mail [RFC5322] and the Multipurpose Internet Mail Extensions (MIME))
Appendix C:
(External interface requirements specify hardware, software, or database elements with which a system or
component must interface... This section provides information to ensure that the system will communicate
properly with external component)

Nov.28, 2018 Page 7 of 8

<Project code> Software Requirements Specifications

Nov.28, 2018 Page 8 of 8