Documente Academic
Documente Profesional
Documente Cultură
Specification
for
2 November, 2015
Table of Contents
1. Introduction..............................................................................................................................1
1.1 Purpose.................................................................................................................................1
1.2 Document Conventions........................................................................................................1
1.3 Intended Audience and Reading Suggestions.......................................................................1
1.4 Product Scope......................................................................................................................1
1.5 References............................................................................................................................2
2. Overall Description..................................................................................................................2
2.1 Product Perspective..............................................................................................................2
2.2 Product Functions................................................................................................................2
2.3 User Classes and Characteristics..........................................................................................2
2.4 Operating Environment........................................................................................................3
2.5 Design and Implementation Constraints...............................................................................4
2.6 User Documentation............................................................................................................4
2.7 Assumptions and Dependencies...........................................................................................4
3. External Interface Requirements............................................................................................5
3.1 User Interfaces.....................................................................................................................5
3.2 Hardware Interfaces.............................................................................................................5
3.3 Software Interfaces..............................................................................................................5
3.4 Communications Interfaces..................................................................................................5
4. System Features........................................................................................................................5
4.1 System Feature 1.................................................................Error! Bookmark not defined.
4.2 System Feature 2 (and so on)..............................................Error! Bookmark not defined.
5. Other Nonfunctional Requirements.......................................................................................8
5.1 Performance Requirements..................................................................................................8
5.2 Safety Requirements...........................................................Error! Bookmark not defined.
5.3 Security Requirements..........................................................................................................8
5.4 Software Quality Attributes..................................................................................................8
5.5 Business Rules......................................................................................................................9
6. Other Requirements...................................................................Error! Bookmark not defined.
Appendix A: Glossary......................................................................Error! Bookmark not defined.
1.
Introduction
1.1
Purpose
The project Cloud based patient monitoring system is a complete website for
patients in the medical field. Its aimed to provide services that will help people who were
or are patients in medical institutions. This website is very user friendly and works in a
simplistic manner according to the general individual.
1.2
Document Conventions
DB
XML
HTML
Data base
Extended Markup Language
Hypertext Markup Language
1.3
References
http://http://stackoverflow.com/
2.
Overall Description
2.1
Product Perspective
The product is independent and totally self-contained. The need for patients to physically
carry around his/her medical records from one medical facility to another was found to be
very difficult for the consumers. This is a virtual platform for medical facilities and patients
that give a complete solution to all these problems. It is indented for all type all of the
patients in the medical field.
2.2
Product Functions
2.2.1 MedicalRecordStorage
2.2.1.1Userlogin
When a patient is at a medical facility, they may give their user ID and password,
allowing the facility to access their previous medical records instantly.
2.2.2
CancerCellDetection
2.3
users would have basic proficiency in operating computers and would have a working
knowledge of English language. Also, the maintainers of the system (administrators) would
have a working knowledge of databases and system maintenance.
2.4
Operating Environment
Our system works in all type of operating system. Hardware requirement is any
2.5
This is developed in Windows OS. Thus it will give its better performance in
Windows.
Internet connectivity is also a major constraint to this project.
2.6
User Documentation
The software design does not demand any user documentation because of its simple
interface. Any user with minimal web surfing knowledge could navigate and modify easily.
2.7
This software will be designed according to the current versions of Hypertext and
hypermedia communication.
The availability of a database management system on the server has been assumed.
Availability of a web-server with support (through plug-ins, if required) for server-side
programming tools like JSP, Servelets and Python etc. has been assumed.
3.
3.1
User Interfaces
3.2
Hardware Interfaces
The cloud based patient monitoring system will run on any electronic devices which support
web browsers.
3.3
Software Interfaces
Software used
Front End
Back End
Operating system
Web Browser
3.4
Description
HTML, CSS
Python, Microsoft SQL Server
Windows 10
Mozilla Firefox, Google Chrome,
Communications Interfaces
The cloud based patient monitoring system uses simple HTTP protocol over internet.
4.
System Features
A Web Browser preferably Google Chrome/Mozilla Firefox should be used at end-
user side.
4.1
User Login
4.1.1 Login
Login/Register module requires a method to interact with database to add and
access user information to allow login in and sign ups.
4.1.2. Input:
Username
password
4.1.3. Processing:
Processing is done by Python/JSP script which fetches data from forms using
POST/GET methods.
4.1.4Output:
4.2
4.2.1 Input:
4.2.2. Processing:
Records are stored category wise in table by using MySQL database.
4.2.4 Output:
The required medical records with images are displayed as result.
5.
5.1
Performance Requirements
With an Internet connectivity, the system is assumed to work well other than for
external hardware crashes or unforeseen circumstances like fire, theft etc. The System
Configurations and the operating platform may affect the system performance as it is with
all other software. A tuned OS will be a better working environment.
5.2
Security Requirements
Our website is accessible through user account logins and access levels have been
appropriately set up for registered users so that he/she gets higher security. It is assumed that
user information provided at the time of sign up is accurate. But new users are considered
are guests and access provided till he log out.
5.3
5.3.1 Availability
As it is a website all can access easily. Only needs a suitable electronic
device with an Internet connection and supporting browser.
5.3.2 Portability
The cloud based patient monitoring system can run on any type of
operating systems.
5.3.3 Maintainability:
Coding follows MVC conventions and is therefore easily maintainable.
5.3.4 Reliability
Any update that is made to cloud based patient monitoring system via
either of the access method is immediately reflected in that.
5.3.5 Reusability
The code is reusable as it follows Modular Programming approach.
5.3.6 Usability
Ease of use and easy to learn.
5.4
Business Rules
AppendixA:Glossary
. H/W- hardware.
S/W- software.
OS-Operating System.