Вы находитесь на странице: 1из 17

SOFTWARE REQUIREMENTS

SPECIFICATION

For
DRUGSCRIPTION

Version
1.0

Batch no.
5
Team members
SYED ALMAS
161019733055
MUHAMMED UBADAH
161019733045
SHOAIB MOHAMMED HABEEB
161019733052

To be completed by Supervisor
Date Received : _____/_____/_____
Signature : ______________________
SRS Approved : Yes / No
:Reason for Decline
_______________________________
_______________________________

TABLE OF CONTENT
1. Introduction ……………………………………………………………………………………...………….01

1.1 Purpose01
1.2 Document Conventions
…………………………………………………………………………………..02
1.3 Intended Audience and Reading Suggestions ……………………………………………………………
02
1.4 Project Scope
……………………………………………………………………………………………..02
1.5 Overview of the Document ………………………………………………………………………………
03

2. Overall Description
………………………………………………………………………………………..03
2.1 User Classes and Characteristics ……………………………………………………...…...………...
…..03
2.2 Operating Environment……………………………………………………...…...………...……...…….
03
2.3 Design and Implementation Constraints………………………………………………………………...
04
2.4 User Constraints ……………………………………………………...…...………...……...……………
04
2.5 User Documentation ……………………………………………………...…...………...………………
04
2.6 Assumptions and Dependencies ……………………………………………………...…...
…………….04
2.7 Time Dependencies……………………………………………………...…...…………………………
05
2.8 Space Dependencies 05

3. External Interface Requirements


…………………………………………………………………..…...05
3.1 User Interfaces …………………………...…………………………………………………..…..…..….
05
3.2 Hardware Interfaces …………………...……………………………………..…………………….……
06
3.3 Software Interfaces……………....…………………………………………………………………...….
06
3.4 Communications Interfaces…...…………………………………………………………………...…….
06

4. Functional Requirements
………………………………………………………………………………..06
4.1 User Registration …………………...……………………………………..…………………….……...06
4.2 Course Material Updates…………...……………………………………..…………………….……... 07
4.3 Add Event…………………...……………………………………..…………………….………………
07
4.4 Add holiday……………...………………………………………...…………………….………………
07
4.5 View or Download Study Material ……………………………..…………………….………………...08

5. Other Nonfunctional
Requirements……………………………………………………………..………08
5.1 Performance Requirements ………………...…………………………………………………...….……
08
5.2 Safety Requirements ………………...…………………………………………………...….
…………...08
5.3 Security Requirements ………………...…………………………………………………...….…………
08
5.4 Software Quality Attributes………………...…………………………………………………...….……
09

6. Unified Modeling language diagrams


……………………………………………………………..……09
6.1 Use Case Diagrams ……………………………...………………………………..…………………….
09
6.2 Sequence Diagrams ………………………...…………………………………………...………...…….
11
6.3 Activity Diagram ………………………...…………………………………………..…………...…….
12

Appendix A : Glossary ……………………………………………………………..……………………………13


Software Requirements Specification DrugScription
01

1. Introduction
This section is written to provide general information about our product
“DrugScription”. The main objective of our product is to provide our customer with all
the medical needs that a pharmacy can provide on their smartphones, customer can buy
medicine using our app and the local pharmacy will deliver the medicine via our
delivery executive, so that our customer does not need to physically go to pharmacy for
medicine and other essentials

1.1 Purpose

This document describes software requirements specification (SRS) for the College
Management System that provides access and management of information of different
modules in college-like Students, Guardians, Teachers/Faculty, Administration. Our
project is based on a database, which stores and maintains information of different
modules within the system. The advantage of a management system is to avoid entries
in hard copies & it saves burden of hard copies of data. The system is Web Application
and GUI for this system is developed in HTML & CSS. Database for this management
system is created in My SQL. There are two users for this system 1. Admin (have full
access to read & write all modules in management system) 2. Teacher (have access
limited to write & manage student marks, attendance, etc.). This is version 1.0 of
software requirements specification. Purpose of this document is to retrieve & analyze
ideas that define products & requirements that users need. This document describes
details of our product, its parameter, & its goals. This SRS document describes the
target audience, user interface of product & Software/Hardware requirements of our
product. This document also describes problems we have faced during designing &
implementation of products & also describes how we have solved this problem & make
our product more efficient. Management systems save human power & time cost to
perform the same task. The data in the database can be saved for a long time and can be
used for different purposes in the future. In management systems, there is a minor
chance of losing the data. This document also defines how customers and users see our
product and understand the functionality of the product. This document will help the
developers/designers in case of maintenance of the software product.

Software Requirements Specification C-NSAKCET


02

1.2 Document Conventions

When writing this SRS for College Management System the following terminologies
are used:

CMS: College Management System

GUI: Graphical User Interface.

DBMS: Database Management System.

SQL: Structured Query Language, used to create the database.

1.3 Intended Audience and Reading Suggestions

This document is to be read by the development team, project manager, marketing staff,
testers & documentation writers. Others involved need to review documents. Testers
need an understanding of system features to develop meaningful test cases & give
useful feedback. Developers need to know requirements of software products they need
to build. This document is for general discussions on implementation decisions
regarding the College Management System. Product developers should have good
knowledge about concepts of RDBMS, SQL, interfaces, & classes.

1.4 Product Scope

As Colleges are growing day by day & also increasing the complexity of storing
information about students related to the college system, they face many related issues:
attendance & fee of students, marks of students, etc. This project is based on an
educational institute system where this application gives maximum services in a single
software product that is used by teacher & system administration. This project includes
PHP, HTML, CSS & MySQL. HTML & CSS is used to design GUI for applications by
which users can interact with software applications. MySQL is used for creating
databases in which different information will be stored. Main focus of this project is to
give the best GUI for users & provide many modules in a single product. Admin can
view all of the information that is stored in the database through application & admin
also can modify this information because admin has full access to the system.

Software Requirements Specification C-NSAKCET


03

1.5 Overview of the document

Remainder section of this document provides System Planning, Overall Description,


Specific Requirements, Use Case Analysis, Process Model, Data Model & System
Design of product. System Planning consists of system requests of business plan,
feasibility analysis & work plan. Overall Description includes Product Functions, User
Characteristics, & General Constraints. Specific Requirements consists of Functional
Requirements, Non-Functional Requirements, UI Interface Requirement,
Communication Interface Requirement, and Hardware & Software Specifications.
System Design consists of System Architecture, and User Interface Design.

2. Overall Description

2.1 User Classes and Characteristics

Primary users are stakeholders, developers and mostly customers. This management
system is controlled by teachers & system administrators. In this system, admin is the
main user who has full access to the management system. Admin can view & modify all
information that is stored in the database. Admin can view and modify the student’s
records like student’s profile, attendance, fee, results, & details of teachers & other
employees in college, their personal information & their attendance for their salaries.
Teachers have access to view & modify student’s information like their attendance,
marks of exams to generate progress reports of students & study materials. When the
teacher “updates” the student's information then the admin can view this information.

2.2 Operating Environment


CMS is expected to be deployed in a real environment to manage DBMS inside college.
Centralized database is used to store information. Users only within college (members
of college staff) can use this management system. Users outside form the college cannot
access the management system. This application is a web application that can be run on
a web browser like Chrome, Mozilla Firefox, Internet Explorer etc.

Software Requirements Specification C-NSAKCET


04

2.3 Design and Implementation Constraints

During implementation of a product, different challenges are faced. Choosing an


interface for the management system was a paramount issue. Connecting the database
with the application was a major problem. MySQL is easy to install and connect with
applications. It is very easy to understand the implementation of the database and also
easy to create a new database and connect with the GUI application.

2.4 User Constraints

There will only be one administrator. Delete operation is available only to the
administrator. To reduce complexity of the system, there is no check on delete
operation. Hence, the administrator should be very careful before deletion of any record
and he/she will be responsible for data consistency.

2.5 User Documentation

● To use application, open the URL of website 


● Then go to the login page.
● Enter your login details provided by college.
● Dashboard will appear according to user login details.
● Use our application, download study materials, review attendance, marks, etc.

2.6 Assumptions and Dependencies


The login Id and password must be created by the system administrator and
communicated to the concerned user confidentially to avoid unauthorized access to the
system.
● It is assumed that a student registering for the subsequent semester has been
promoted to that semester by the university as per rules and has paid the desired
university fee. 
● Registration process will be open only for a specific duration.

Software Requirements Specification C-NSAKCET


05

2.7 Time Dependencies

In reference to requirements that are mentioned for running websites, we have assumed
that basic RAM & internet connection requirements are met by the end-user, if not then
certain delays may be encountered while loading & could lead to website crashes.

2.8 Space Dependencies

CMS is an online application and is independent of hard disk space of the end user.
However, websites contain downloadable materials which will consume space on the
Hard Disk of the end user, space consumed is subject to the download limit of the end
user.

3. External Interface Requirements

3.1 User Interfaces 

Home screen 
● It's the first screen the user sees when the application is opened.
● Users have options to view galleries, notices, events, get info about college etc.
● There is a login button located at the top right that redirects the user to the login
page.
● At the login page, the user may enter their credentials and access the portal.

General Layout  
The CMS will have following user-friendly and menu driven interfaces
● Login: to allow entry of authorized users
through valid login Id and password.
● College Details: to maintain college details.
● Programme Details: to maintain programme
details. 
● Faculty Details: to maintain the faculty details.
Software Requirements Specification C-NSAKCET
06

3.2 Hardware Interfaces

● Screen resolution of at least 640 x 480 or above.


● Support for printers (dot matrix, deskjet, laserjet).
● Computer systems will be in the networked environment as it is a multi-user
system.

3.3 Software Interfaces

● PHP 5.0 and above


● APACHE HTTP Server
● Front End: HTML and JavaScript, CSS
● Web designing language: PHP
● RDBMS (Back end): MySQL
● Microsoft Windows or Linux
● Xampp Server
● Clients of PC may use one of the following : Mozilla Firefox, Chrome etc.
3.4 Communications Interfaces

This project supports all types of web browsers. We are using simple protocols like
TCP/IP and HTTP to establish client server communication. Thus every time a request
is sent out from the client side it is done so using TCP/IP and then the server responds
with the information that had been requested for.

4. Functional Requirements

The application has the following Functional Requirements:

4.1 User Registration

Pre-condition: Must be a current member of the institution and one of the actors.
Steps: - Open the website.

Software Requirements Specification C-NSAKCET


07

- Login from Admin account.


- Select user registration from admin panel.
- Enter the user details and generate login credentials for the same.
Post condition: The user is successfully registered and can login and access the portal
from anywhere at any time.

4.2 Course material updates

Pre-condition: Category must be created


Steps:  - Open the website.
 - Login from Teacher account.
 - Select study material option.
 - Enter material name.
 - Choose file from your pc.
Post condition: Study material added successfully.
4.3 Add Events

Pre-condition: From and to date must be entered.


Steps:  - Open the website.
 - Login from Admin account.
 - Select event option.
 - Enter title, place, from date, to date.
- Choose image from your pc.
Post condition: Event added successfully.

4.4 Add Holiday

Pre-condition: Date and title must be entered.


Steps:  - Open the website.
 - Login from Admin account.
 - Select event option.
 - Enter title, date, notice.
Post condition: Holiday added successfully.
Software Requirements Specification C-NSAKCET 08

4.5 View or Download Study material

Pre-condition: From and to date must be enter.


Steps:  - Open the website.
 - Login from Student account.
 - Select study material option.
 - View or go to download option.
Post condition: Material downloaded successfully.

5. Other Non-Functional Requirements

5.1 Performance Requirements

Performance should not be an issue because all of our actions involve small pieces of
data. Changing screens will require very little computation and thus will occur very
quickly. Page load should only take a few seconds as long as the device can maintain a
steady internet connection.

5.2 Safety Requirements

CMS is an online application and hence does not affect the user’s personal files stored
locally on their hard drive. It cannot cause any damage to the device or its internal
components.

5.3 Security Requirements

This application assumes that only the user or whoever the admin allows will have
access to the portal. The identity of the user upon opening the website is first verified,
since it is password protected, the user’s identity must be authenticated first for them to
gain access. Besides, no critical transactional or personal information apart from name
and email id is accessible by the users or shared on the portal. This eliminates risking
any major damages in an unlikely event of a security breach. Also, data is protected and
encrypted by SSL encryption.

Software Requirements Specification C-NSAKCET 09

5.4 Software Quality Attributes

The graphical user interface of CMS is to be designed with usability as the first priority.
The website will be presented and organized in a manner that is both visually appealing
and easy for the user to navigate. There will be feedback and visual cues such as
notifications to inform users of updates & pop-ups to provide users with instructions. To
ensure reliability and correctness, the app will take into account situations in which a
user loses internet connection or for whatever reason cannot establish a connection with
the server. These users will still be able to use the application, but any Bills,
transactions, etc. posted while disconnected will be cached until the connection is
restored.
6. Unified Modeling Language (UML)

UML represents a collection of best engineering practices that have proven successful in
the modeling of large and complex systems. The UML is a very important part of
developing object oriented software and the software development process. The UML
uses mostly graphical notations to express the design of software projects

6.1 Use Case Diagram

Use case diagram identifies the functionality provided by the system (Use Case), user
who interacts with the system (actors), and association between users and functionality.
Use case is used in analysis phase of software development to articulate high-level
requirements of system primary goals ofUse Case diagram include.
• Providing a high-level view of what the system does.
• Identifying the users (“actors”) of the system.
• Determining areas needing human-computer interfaces.
Use case extends beyond pictorial diagrams. In fact, text-based use case descriptions are
when used to supplement diagrams, and explore the use case functionality in more
detail.

Software Requirements Specification C-NSAKCET 10

(I) Admin and Faculty


(II) Parent and Student

Explanation:
The above two diagrams illustrate the different actors present in our project,. i.e Admin,
Faculty, Student and Parent and the behavioral role of each of them.

Software Requirements Specification C-NSAKCET 11


6.2 Sequence Diagram

A sequence diagram shows object interactions arranged in time sequence. It depicts the


objects and classes involved in the scenario and the sequence of messages exchanged
between the objects needed to carry out the functionality of the scenario.

(i) Sequence Diagram for Admin

(ii) Sequence diagram for Faculty

Software Requirements Specification C-NSAKCET 12


(iii) Sequence Diagram for Student

Explanation:
The above three sequence diagrams show how instructions travel from the user’s
interface to the database and then back to their screen in a sequential manner.

6.3 Activity Diagram

Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.

Explanation:
This diagram consists of 3 main actors & depicts what activity each actor can perform.
In other words, you can see which function each actor has access to & to what extent.

Software Requirements Specification C-NSAKCET 13


Appendix A: Glossary

SRS : Software Requirements Specification

GUI : Graphical User Interface

HTML : Hypertext Markup Language

CSS : Cascading Style Sheets

CMS : College Management System

DBMS : Database Management System

SQL : Structured Query Language

RDBMS : Relational Database Management System

PHP : Hypertext Preprocessor

UI : User Interface

URL : Uniform Resource Locator

RAM : Random-access memory

TCP/IP : Transmission Control Protocol/Internet Protocol

SSL : Secure Sockets Layer

UML : Unified Modeling Language

Вам также может понравиться