Srs E-Drugstore Administration

srs (software requirments specifications)

SRS E-Drugstore Administration

E-Drugstore Administration is specially designed for the purpose of adding Medical item’s/Medicine detail. The system elaborates the basic concept for storing and generating Medical item’s detail. These items will be distributed in different categories for example there is different type of Medicine for a same disease in the Drugstore i.e. Disprin and Panadol so we can search it easily under the appropriate label and inform the customer about their price and quantity if needed. In this system, staff can sign up as a system admin, He/she can have full access to the system for maintaining daily records. It will be a windows-based application which has been developed to make all the operations fast and easy. The design of E-Drugstore Administration is easy to use for every type of users because a lot of Drugstores have salespersons which are not very much qualified. Whereas, in our application there is a facility of report generation which gives detail information about Drugstore item’s sell and purchase and make staff possible to get hard copy of related reports.


Scope of Project E-Drugstore Administration:

Project scope is the part of project planning that involves determining and documenting a list of specific project  goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target

Functional and Non Functional Requirements of E-Drugstore Administration:

Functional Requirements of E-Drugstore Administration:

A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs




  • Application is user friendly.
  • Application Perform fast manipulation and calculations.
  • Application is adaptable.
  • Application will be able to work on all types of operating systems.
  • Application will be capable to handle multi user activities simultaneously.
  • There will be back up system to face any problem in system
  • All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
  • Response Time is very awesome.
Some others are:
  • Accessibility
  • Maintainability
  •  Fault Tolerance.
  • Security
  • Robustnes


Use Case Diagram of Implementation of E-Drugstore Administration

a use case diagram can summarize the details of your system’s users   and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve



Usage Scenarios Implementation of E-Drugstore Administration:

A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a  User.


ADOPTED METHODOLOGY for E-Drugstore Administration:

The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.


Work Plan of E-Drugstore Administration:

Work plan

for complete srs contact us

watsapp: 03469806607