Chapter 2

Software Requirement and Specification

2.1 Introduction:
A software requirement specification (SRS) is a comprehensive description on the
intended purpose and environment for software under development. The SRS fully
describes what the software will do and how it will be expected to perform.

An SRS minimises the time and effort required by developer to achieve

desired goals and also minimise the development cost. A good SRS defines how an
application will interact with system hardware, other programs and human users in
a wide variety of real-world situation.

2.1.1 Purpose:
The purpose of this document is to specify each requirement of the system in
detail, while helping the client object a better understanding of the project. The
document describes the project target audience and its user interface, hardware and
software requirements.

2.1.2 Scope:
The document specifies requirements of the system. The validation of the
process is done through software requirement specification. If there are any
changes in the software in future, the changes are done through software
requirement specification. First, the developer is responsible in case any change is
seen in near future. The clarification must be changed in the recording of the
system requirement specification.

2.1.3 Definition, Acronyms and Abbreviation:

Admin:
Admin is the administrator who is responsible for maintaining, adding and status of
all the records of healthcare.

User:
Users of HEALTHCARE software
HEALTHCARE: e-pharmacy
SQL: Structured Query Language
VB.Net: Visual Basic.Net
DFD: Data Flow Diagram
CFD: Context Flow Diagram
ER: Entity Relationship
SRS: Software Requirement Specification
GUI: Graphical User Interface

2.1.4 Overview:
The HEALTHCARE software is developed for e-pharmacy.
HEALTHCARE software is also developed for admin to maintain all the records
of the pharmacy.

2.2 Languages and Tools:

2.2.1 Frontend: VB.Net

VB.Net stands for Visual Basic.Net, it is a computer programming language
developed by Microsoft.
It was first released in 2002 to replace Visual Basic 6. VB.Net is an object-
oriented programming language. The language was designed in such a way that it
is easy to understand to both novice and advanced programmers. It consists of
automatic code formatting, XML designer, improved object browser etc and also
garbage collection is automated and it consist of a standard library.

2.2.2 Backend: SQL Server 2008

Microsoft SQL server is a relational database management system
(RDBMS) designed to run on platform ranging from laptops to large
multiprocessor servers. SQL server is commonly used for websites and support
current users.
A relational database management system (RDBMS) is a program that lets
you create, update and administer a relational database. Most commercial
RDBMS’s use the Structured Query Language (SQL) to access the database.

2.3 Overall description

2.3.1 Product Perspective:

  HEALTHCARE software is an integrated system and contains both admin
and employee components.
 The employee component is used to manage the daily transaction of the e-
pharmacy.
 The admin component is used by the administrator for performing admin
level functions such as items for purchase, updates, sales details, employee
details and stock details.
2.3.2 Product Functions:
 The main function of HEALTHCARE software is to manage and provide the
best services available online to all its users.
 The system can be used to store available medical products for purchase and
to provide stock details for the same.

2.3.3 User Characteristics:

 The user needs to have the basic computer knowledge to operate the system.
The type of users and their characteristics:
 Admin
1. Providing medicine and other items for purchase.
2. Providing various medicine and wellness details, employee
details,stock details, login details and salary details.
3. Providing registration for the employees.
4. Generating sales and stock report.
5. Provides specific prices of medicine and wellness.
6. He can make a payment of employees.
 Employee
1. Viewing various medical information.
2. Employee who have been given username and password by the
admin can only make a bill.

2.3.4 General Constraints:

 User of the system must be comfortable with English language.
 Developed system should run on type of operating system that supports
VB.Net and SQL server.

2.3.5 Hardware Requirements:

  Any standard keyboard.
 Any standard mouse.
 Any standard CD-ROM.

2.3.6 Assumptions and dependencies

 Admin should be careful in handling or modifying data knowingly or
unknowingly which will lead to inconsistency of the database.

2.4 Specific Requirements

2.4.1 External internal requirements

The interface should be simple and easy to understand and use. It should
always be interactive interface. It should prompt the user and administrator for
proper input criteria.

2.4.1.1 User Interfaces:

In this project, forms are used as user interface. The project is well defined
to meet the requirements. This includes forms for entering required information or
data for displaying it.
 Text field for entering details.
 Command button to save and edit an appropriate information.
 Labels for identifying the appropriate information.
 Combo box list to view and select.
 Table to store the data.
 Grid view to view the data stored in the table.

2.4.1.2 Hardware Interfaces:

 RAM :4GB
 Input device : Keyboard, Mouse
 Output device : Monitor, printer
 Storage :40GB
 Processor :Intel COREi3.

2.4.1.3 Software Interfaces:

 Operating System : Windows 8 and above
  Fronted : VB.Net
 Backend :SQL Server 2008
2.4.2 Function requirement specifications

2.4.2.1 Module Description:

2.4.2.1.1 Admin Module:

Module Name Login
Description This module allows the admin to access all his
authority.
Data Inputs  User Name
 Password
Processing  Admin will enter his user name and password
accordingly.
 This information is accessed from table
TblLogin.
 Password is verified in the table TblLogin.

Module name Product details

Description This module allows the admin analyse the products.
Data Inputs  Product ID
 Product Name
Processing  Admin can enter product name and product ID
 This information accessed from is table
TblProduct.

Module Name Employee management

Description This module allows the admin to register the employee.
Data Inputs  Employee ID
 Employee Name
 Age
  Gender
 DOJ
 Phone No
 User Name
 Password
 Address
Processing  Registered information will store in the table
TblEmp.
 If require admin can give User name and
password to an employee which is stored in the
TblLogin.
 The registered employee’s details can also be
edited here.
 Information are stored in table TblEmp,TblLogin.
 Admin can add, edit, remove the employee.

Module Name Customer details

Description This module allows the admin to retrieve the details of
the customer.
Data Inputs  Customer ID
 Customer Name
Processing  Admin will enter the Customer name, Customer
ID.
 This information is retrieve from table
TblCustomer.

2.4.2.1.2 Customer Module:

Module Name Login
Description Here customer can login to the device based on the
registered user name and password.
Data Inputs  User Name
  Password
Processing  Customer will enter his user name and password
to login and order the products.
 The login information is verified in table
TblLogin.

Module name Register

Description This module allows the Customer to register.
Data Inputs  First Name
 Last Name
 Email ID
 Mobile NO
 Password
Processing
 Registered information will store in the table
TblLogin.

Module Name Review and Ratings

Description Customer can give the ratings and feedback.
Data Inputs  Review
 Ratings

Processing
 This information is stored in the table TblReview.
 Feedback for the product are stored in the table

2.4.2.1.3 Employee Module:

Module Name Login
Description Here employee can login to the device based on given user
name and password given by admin.
Data Inputs  User Name
 Password
Processing  Employee can enter his user name and password in
order to access his authorities.
 This information is stored in the table TblLogin.

Module Name Add Product

Description Here employee can add new product.
Data Inputs  Product Type
 Product Name
 Stock
 Unit Price
 Manufacturer
 Images
 Description
Processing .
 These informations are stored in table TblProduct.

Module Name Delivery Management

Description Here employee can order product to the sellers.
Data Inputs  Product ID
 Product Type
 Quantity
 Price
 Customer ID
 Customer Name
 Address
Processing .
 These informations are mailed to sellers on customer
purchase
Module Name Stock Management
Description Here employee can communicate with the sellers about
available stocks and display it.
Data Inputs  Product ID
 Stock
Processing .
 Employees can communicate with the sellers trough
mail.
 Stocks will be updated to table TblProduct

2.4.3 Performance Requirement:

This part of SRS specifies the performance constraints on the software
system. All the requirements relating to the performance characteristics of the
system must be clearly specified.
There are two types of performance requirements
1. Static
2. Dynamic
Static Requirements: Static Requirements are those that do not impose
constraints on the execution characteristics of the system. These includes
requirements like the
number of terminals to be supported and the number of files that system has no
produce and their sizes.
Dynamic Requirements: Dynamic Requirements specifying constraints on the
execution behaviour of the system this typically include response time and
throughput constraints on the system.

2.4.4 Design Constraints:

When the developer states design of the system there exist number of
factors in client’s environment that may be restrict the choices. Such
 factors include standards that must be followed, resource limits,
operating environment, reliability and security.
 Security: only the authorised users are allowed to use this
application.
 Reliability: Reliability includes the factor that it gives the proper
result. If the system does not find the required result then an
appropriate notification id displayed in form of message in pop up.
 Portability: System is adoptable to any computer and work more
efficiently in windows XP and above operating systems.
 Reusability: The system modules are reusable for the next
development process. With the user of this system developer can
enhance it with other improved or additional feature.
 Extensibility: It allows an easy functionality and add interface that
suits to current requirement of the user.

2.4.5 Other Requirements:

When the system in completely developed and submitted to the
management, few sessions will be required to make the users of the system
understand about the functionality of it and some time to adopt the system. After
those sessions it is required that the members from the development team should
spend some time in the system background for an agreed time period. That new
time period used in identifying new bugs that could not be reached in the earlier
phases of the development process.