Beruflich Dokumente
Kultur Dokumente
1. Introduction
SRS is a document that completely describes what the proposed software should do without describing how software will do it. The basic purpose of SRS is to bridge the communication gap between the parties involved in the development of the software SRS is the medium through which the client and the user needs are accurately specified. A good SRS should satisfy all the parties some thing very hard to achieve and involves trade offs and persuasion. Another important purpose of developing an SRS is helping the users to understand their own needs.
Purpose
The basic purpose of this document is to describe all the requirement for the Dental Master System For Dental Clinic(DMSDC). These requirements will help the port to keep the track of Cargo and ship details. DMSDC provides the easier to automate all the functionalities of a Doctor, Patients, Prescription, Medical etc...
Scope
This document describes the information of DMSDC. It helps in generating reports known as bill report, personal report, statistic report etc...
RDBMS: Relational Data Base Management System SRS: Software Requirement Specification DMSDC: Dental Master System For Dental Clinic GUI: Graphic User Interface
OverView
The software requirement specification is the requirement work product that formally specifies Dental Master System For Dental Clinic. The objective of this document therefore is to formally describe systems high level requirement including functional requirements, nonfunctional requirements and cinstraints. The software is intended to keep the track of ship details and cargo details. The developer will be responsible for developing the software, while the authorized operator will be responsible for data entry.
2 Overall Description
2.1 Product Perspective
activities of the doctors and patirnts such as generating reports like statistics reports, bill report, case report. This software collects all the data and stores in the respective databases. The benefit of using this software is its easy implementation and user friendly.
2.2 Product Functions Masters: This modules creates the initial data required so
that so the other functional modules can work open them. It maintains the basic records pertaining to Treatment details, prescription details consulting details, doctor detail, schedules, systemic alerts, Treatment details etc....
3 Specific Requirements
3.1 External Interfaces
The usre has to fill the appropriate form from the menu which will be displayed on the screen based on the type login. It will also provide dialog boxes to help the user to easily interact with the software. The input data is stored in the respective databases. There are all possible interaction of the software with the user and hardware.
Treatment: This module is used to store each Patient Treatment details along with Date, tooth number etc. Prescription: This module deals wiyh the activities related to storing the Prescription for a patient like Dosage, days etc. Case Reports This module is to see the full Patient History of Treatment, Priscription along with their dates. Admin: Includes the authorization right on Master tables data's, and also some special Rights. 3.3 Performance Requirements The software can take any number of input quantities provided the database size is large enough. This would depend on the user's system memory availability. The performance expected is 100%. 3.4 Design Constraints Developer is responsible for the development of the system and installing it. This application is design to run on Windows XP and above, using Vb.net as Front End and Microsoft Sql Server 2008 as Back End. 3.4.1 Software Constraints: This application is designed to run on Windows XP and above, using Vb.net as Front End and Microsoft sql Server as Back End.
2.256 MB RAM 3.Peripheral devices 3.5 System Attributes 3.5.1 Reliability The system is designed to have very simple database just to serve the exact need of the port. It is tested for all the constraints at development stage. 3.5.2 Availability This system will only available till the system on which it is installed is running. 3.5.3 Security This system is provided with the authentication without which no user can pass. So only the respective users are allowed to use the application. If the respective users share the authentication information then the system is open to outsiders. 3.5.4 Maintainability There will be no maintenance required for the software. The database is provided by the end-user and therefore is maintained by the user. 3.5.5 Portability The system is not portable as it is a standalone application running on single system with no shared database.