21
SRS Document for Ehospitals SRS Document For Ehospitals 1.0 Document Author: Authors: Keerthi Krishna Signatur e Version 1.0 17 th December 2012 Website Design, Developed, Commissioned and the Document Prepared by: Fomax Information Technologies Private Limited # 172, First Floor, 9th Main, 7 th Sector, Ehospitals Page 1 of 21 17 th December 2012

yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

Embed Size (px)

Citation preview

Page 1: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for Ehospitals

SRS Document

For

Ehospitals

1.0 Document Author:

Authors: Keerthi Krishna

Signature Version 1.0 17th December 2012

Website Design, Developed, Commissioned and the Document Prepared by:

Fomax Information Technologies Private Limited# 172, First Floor, 9th Main, 7th Sector,HSR Layout, Bangalore 560 102Karnataka State INDIA

Landline: + 91 80 2572 0700 / +91 80 6570 1483Website : www.fomaxtech.com

Ehospitals Page 1 of 16 17 th December 2012

Page 2: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for Ehospitals

3.0 Document Revision History

Date Version Author Change Comments

4.0 Document Review and Final Approval:

Reviewer Name : Insert Job Title:

Signature Date

Ehospitals Page 2 of 16 17 th December 2012

Page 3: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for Ehospitals

Table of Contents

1.0 Introduction...............................................................................................................................41.1. Purpose of the Document....................................................................................................41.2. Scope of the Document........................................................................................................41.3. Definitions, Acronyms and Abbreviationsy..........................................................................41.4. Overview...............................................................................................................................5

2.0 General Description...................................................................................................................52.1. Product Perspective..............................................................................................................52.2. Product Functions.................................................................................................................52.3. User Characteristics..............................................................................................................5

3.0 Requirments..............................................................................................................................63.1. Functional Requirments.......................................................................................................6 3.1.1. Admin Login.................................................................................................................... 6 3.1.2. Home Page Overview......................................................................................................63.2. Functionality of Admin........................................................................................................7 3.2.1. Dashboard........................................................................................................................7 3.2.2. Hospital Info.....................................................................................................................7 3.2.3. Our Services................................................................................................................... 10 3.2.4. Useful Links....................................................................................................................10 3.2.5. Testimonials................................................................................................................... 11 3.2.6. User Info.........................................................................................................................11 3.2.7. User Management.........................................................................................................11 3.2.8. Form............................................................................................................................... 12 3.2.9. CMS................................................................................................................................ 123.3 Functionality of User...........................................................................................................13 3.3.1. Login/Signup..................................................................................................................13 3.3.2. Search.............................................................................................................................13 3.3.3. Book An Appointment...................................................................................................14 3.3.4. View Profile....................................................................................................................15 3.3.5. Useful Links....................................................................................................................15 3.3.6. Testimonials................................................................................................................... 16 3.3.7. Contact Us......................................................................................................................16

4.0 Requirement from the Client End...........................................................................................17

Ehospitals Page 3 of 16 17 th December 2012

Page 4: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for Ehospitals

1.0 Introduction

1.1 Purpose of this document

This document specifies the Software Requirements Specification (SRS) for Ehospitals. The purpose of this document is to present a detailed description of the functionality of Ehospitals Website. It will explain the purpose and features of the system, the interfaces of the system and what the system will do.

1.2 Scope of this document

The scope of this document includes an overview of the Ehospitals Website, detailed information about the requirements, including functional requirements, interface requirements, non-functional requirements and additional constraints of the system.

1.3 Definitions, Acronyms and Abbreviations

SRS – Software Requirement Specification Admin – a person who will be managing the system for its intended purpose. User – a Person who will get access to view and request the options.

1.4 Overview

The remaining part of this document follows the format. Section 2 will cover the general Function about the system. Section 3.2 will cover the functional requirements of the Admin. Section 3.3 will cover the Information’s and Functionality of the Users. Section 4 will cover the information’s of Requirement from client end.

Ehospitals Page 4 of 16 17 th December 2012

Page 5: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for Ehospitals

2.0 General Description

2.1 Product Perspective

The system will be developed using PHP – Smarty Templates, HTML, and RDBMS as MySQL.

2.2 Product Functions

The product developed will provide an easy access and communication to Admin as well as Users. The major functions of the system are:

Functionality of Admin Module. Functionality of User Module.

2.3 User characteristics

The users of the system are normal persons who need help from Ehospitals.

Ehospitals Page 5 of 16 17 th December 2012

Page 6: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for Ehospitals3.0 Requirements

3.1 Functional Requirements

Admin is an authorized person to Access the Complete system. Gives Access to Users and maintains the detailed information of appointment, hospital and doctors.

The Entire project is going to develop in two modules:

One is admin module where he can access the complete system i.e He can create user to manage the admin module, manage the registered users, hospitals, doctors etc and also can manage entire contents in the website.

Other is User module where a particular user can register to Ehospitals and can take the appointment for particular hospital / doctors or user can search the hospital according to the location, hospital, specialty and doctors.

3.1.1 Admin Login

The system should allow the Admin to login under a secure system by providing their Valid Username and Password.

3.1.2 Home Page Overview

The Home page of this System consist the Login Function, Doctors Profile, Search, FAQ, Services and Contact Us information respectively.

3.2 Functionality of Admin

Ehospitals Page 6 of 16 17 th December 2012

Page 7: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for Ehospitals3.2.1 Dashboard

The Dashboard lists the daily appointment details, newly registered users, Hospital info and doctors’ info.

Appointment Details: Mainly five appointments should display in the dashboard as latest appointment should come first and there should be a view all link under the details, this link should redirect to a page with all appointment details.

Newly registered users, Hospital info and doctors’ info also should be same as that of appointment details.

3.2.2 Hospital Info

From here admin can view/add/edit/activate/deactivate/delete hospital information as well as doctors information.

There should be 7 submenus under this such as:1: Hospitals2: Location3: Country4: Area5: Specialty6: Add Hospital Info7: Add Doctors Info

1. Hospitals

From here admin can view all hospital information with status. There should be a search option to search the hospital and admin can add/edit/activate/deactivate/delete the hospital information.

Add Hospital

Admin can add main hospitals name.

Ehospitals Page 7 of 16 17 th December 2012

Page 8: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for EhospitalsFields:

Hospital Name –

2. Location

Admin should be able Add, Edit, Search and Manage the location.

Fields:

Location –

3. Country

Admin should be able Add, Edit, Search and manage all countries.

Fields:

Country –

4. Area

Admin should be able Add, Edit, Search and Manage the area.

Admin can add area by selecting the location.

Fields: Location – (It should be drop down where all the location added by the admin should display here.)Area –

5. Specialty

Admin should be able Add, Edit, Search & Manage the specialty.

Fields: Specialty – 6. Hospital Info

Ehospitals Page 8 of 16 17 th December 2012

Page 9: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for Ehospitals

Admin should be able Add, Edit, Search & Manage the hospital Info. From here admin must be able to view all corresponding doctors’ which belongs to that particular hospital.

Fields: Hospital Name – Location – Area – Specialty – Hospital Logo -

All the above fields except Hospital logo should be drop down and each of them will be interdependent.

7. Add Doctor Info

Admin should be able to add the complete details of doctors.

Fields:

Title – First Name – Last Name – Gender – (It should be a check box where admin can check the particular checkbox)Designation – Qualification – Experience – Hospital Country – (should be a drop down where admin can select the country which will be added under country.)Location – (should be a drop down where admin can select the location)Area – (should be a drop down where admin can select the area)Primary Hospital – (should be a drop down where admin can select from the drop down)Specialty – (should be a drop down)Secondary Hospital – (should be a drop down)Nationality – (should be a drop down)Email Id –

Ehospitals Page 9 of 16 17 th December 2012

Page 10: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for EhospitalsMobile No – Timing – (two sections will be displayed here. Ie Session 1 and Session 2, from here admin will be able to select the timing of the doctor.ie his/her OPD schedule).Doctors Image –

*Note 1: All the details added here should display in User module.

*Note 2: If admin tries to delete any one of the above field, it will affect other fields also.

*Note 3: Please look into the above fields and verify if the fields suggested are sufficient or add / delete fields based on the requirement.

3.2.3 Our services

From here admin can view users query which send by the user and also he/she can search the users. Copy of this mail should reach to administrator’s email.

3.2.4 Useful Links

Admin can add the details of useful links such as Blood bank and Ambulance. These details will be displayed in the front end under useful links.

Fields:Type – Name – Location – Area – Phone Number –

*Note: Please look into the above fields and verify if the fields suggested are sufficient or add / delete fields based on the requirement.

3.2.5 Testimonials

Admin can add the testimonial which will be displayed in the frontend under testimonials and also admin can search the testimonial using the search option.

Fields:

Ehospitals Page 10 of 16 17 th December 2012

Page 11: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for Ehospitals

Type –Content – Name – Hospital –

*Note: Please look into the above fields and verify if the fields suggested are sufficient or add / delete fields based on the requirement.

3.2.6 User Info

This section manages all the registered users of Ehospitals and it allows the functionality for admin to activate /de-activate/delete the users and also helps admin to search the user using search functionality.

3.2.7 User Management

From this User management section admin can add/edit/activate/deactivate particular users and also allows admin to change or modify password of particular users. Those particular users can access the admin panel. (i.e. data entry person can view customers and appointment details and he can edit hospital information but administrator have right to do all the activities in this site.)

Add New User Fields:

Full Name – User Name – Password –Confirm Password –Email Id – Roll status –

Password Management Fields:

Select User – (It’s a drop down where admin can select the user.)Old Password – New password –

Ehospitals Page 11 of 16 17 th December 2012

Page 12: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for EhospitalsConfirm Password –

*Note: Please look into the above fields and verify if the fields suggested are sufficient or add / delete fields based on the requirement.

3.2.8 Form

Admin should able to view three submenus under this.

1. Appointment Form2. Enquiry /Contact Us form3. Donation Form

Here admin can view the details of all the form with attachment which send by the user.

3.2.9 CMS

From here admin can manage all the contents in the website.

3.3 Functionality of User Module

This is the front end of the application where user can view all the details such as hospitals, doctors, FAQ etc which will be updated by the admin.

3.3.1 Login/sign up:

For Booking an appointment user have to login to the application.

Fields:Signup:Name - Contact No – Email Id –

Ehospitals Page 12 of 16 17 th December 2012

Page 13: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for EhospitalsPassword – Captcha

After sign up user will get a confirmation mail with his/her username and password and same user details’ will store in the admin module. Admin can view this user details from Admin module – User Info.

Login:User Name – Password –

3.3.2 Search

There should be a search option in home page with following details:

Fields:

Doctor/Specialist Name – Specialty – Hospital –Location –

When user clicks on search button with or without entering the details, it should redirect to a new page with all doctors list according to his/her search. In this page we need to display the doctor name, image, qualification, specialty and hospital which will be updated by the admin from admin module. Below this there should be two button such as “Book an Appointment” and “View Profile”. For booking appointment the user must login to the application. If it’s not a registered user then this book an appointment should redirect to sign up page in the application. If user login to this application, book an appointment should redirect to a page with following details:

3.3.3 Book an Appointment

Fields:

Doctors Name – (This filed should be read only. i.e user can’t edit this filed)Patient Name – Patient Age –

Ehospitals Page 13 of 16 17 th December 2012

Page 14: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for EhospitalsGender – Phone No –Email –Date/Time of the appointment – Hospital – (It should be a drop down if the same doctor is working in more than one hospital)Comment –

In the right side of this page user can view the same doctor details such as his/her OPD schedule, Qualification and experience which will be updated by the admin. Also user can view the number of appointments of that doctor (There must be maximum 10 appointments /Session).This should automatically updated by the system. Admin can view the appointment details from admin module – Appointment Info. Here admin can change the status of the user.

User should take the appointment before two weeks otherwise it should show an error message. After booking an appointment user will get a mail with complete details and a link to cancel his/her appointment.

3.3.4 View Profile

From here user can view complete details of the doctors such as Qualification, Specialty, experience, Affiliations/Membership, Awards & Achievements, Availability and Hospital which he/she is working.

3.3.5 Our Services

User can view 3 sub menus under this such as Domestic, International and Network Hospitals.

Domestic: It’s a static content.

International: It’s a static content. But in the right side of the page user can view an enquiry form where he/she can ask there query.

Fields:

Ehospitals Page 14 of 16 17 th December 2012

Page 15: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for EhospitalsName - Contact No – Email Id – Subject – (It should be a drop down which contains General feedback/support, Appointment status, others ) Enquiry – Captcha

Network Hospitals:

User can view all the network hospitals which will be updated by the admin from the admin module.

3.3.6 Useful Links

From here user can view emergency contact details of Ambulance, Blood bank and organ donation.

There should be a Donation form from which interested user can send their details to admin. These details should store in the admin module. Also admin will get a mail regarding this.

Fields:

Name - Contact No – Email Id – Location – Donation – (It should be a drop down)Enquiry – Captcha

3.3.7 Testimonials

User can view all the active testimonials which will be updated by the admin.

3.3.8 Contact Us

User can view the contact details of the admin.

Ehospitals Page 15 of 16 17 th December 2012

Page 16: yaskawaindia.inyaskawaindia.in/.../2012/12/SRS-Document-For-Ehospitals.docx · Web viewSRS Document for Ehospitals SRS Document for Ehospitals Ehospitals Page 17 of 17 17th December

SRS Document for Ehospitals

*Note: About Us/Our services/Eye, Organ, Insurance/FAQ/Contact Us etc are static content .ie admin cant edit this content. But we can make this as CMS but we need little time.

4.0 Requirement from the Client End

Require the entire location/area list of all Hospital/sub hospital for which the doctors will be included in this website.

We require the department or specialty list for listing the Doctors. We require the list of doctors from each location. Require details for useful links.

Ehospitals Page 16 of 16 17 th December 2012