Software Requirements Specification for The Smart Pharmacy, Study Guides, Projects, Research of Project Management

Download Software Requirements Specification for The Smart Pharmacy and more Study Guides, Projects, Research Project Management in PDF only on Docsity!

The Smart Pharmacy

Software Requirements Specification

Version 1. Group Id: Supervisor Name:

Revision History Date (dd/mm/yyyy) Version Description Author Current date 1.0 The aim of this project is to develop a website named as “The Smart Pharmacy” to store data and enables functionality that organizes and maintains the medication use process within pharmacies.

Table of Contents

Functional Requirements:

Provide a bulleted list of functional requirements

1. Staff management
2. Flexible payment options
3. Reports and analyses
4. Management of expiry dates
5. Barcode Management
6. Stock and Sales Management
7. Print Sales Invoice
8. Prescription Management Requirements Not Necessary But Appreciated:

• Use Ajax based requests.
• Use of Frontend Libraries such as Bootstrap, Material Design etc.
• You can use libraries from Github for payment options.
• Use Git as version control for project.

Tools:

Any web development tool e.g. PHP, ASP.NET, and Java, along with any Database.

Non-Functional Requirements:

• This is a WEB application
• System will be available for 24/7.
• All user manuals should be provided in the necessary format.
• Application should support all simultaneous users.

• Transaction should be completed within 1/5th of second.
• There are back up procedure to maintain record.

Use Case Diagrams:

Use Case Title Login Use Case ID UC- Actions  Input user name  Input password Description This Use Case provides access to user to get login into its system after verifying password and username. Alternative Path Can not access the system Pre- Condition User name , user password Post-Condition User has been login. Author Admin or register users Exceptions Invalid user name and password 4.2. Use Case Title Logout Use Case ID UC- Actions  Admin or register tenant is login  Admin gets user add form  Fill user information  Save Description This Use Case described that admin can add a new user to the system. Alternative Path Pre-Condition  Admin is login  Admin gets user add form Post-condition User is added. Author NA Exceptions N/A

Use Case Title Forget password Use Case ID UC- Actions Register user can forget password Description User can reset its password if he forget Alternative Path Pre-Condition User must be register Post-condition Set new password Author User Exceptions User id is incorrect` 4.4. Use Case Title Registration Use Case ID UC- Actions  Unregister user can register himself or herself. Description This Use case described registration process Alternative Path Pre-Condition Click Registration button Post-condition User can register himself or herself. Author Exceptions N/A 4.5. Use Case Title Pharmacy Approval notification Use Case ID UC- Actions  Approve drug Description Medicine can be approve by using this usecase Alternative Path logout

Author NA Exceptions Place order

Use Case Title View Order Details Use Case ID UC- Actions View order Description This Use Case described that how user can Mange Items Alternative Path Pre-Condition User have valid information Post-condition Can view order Author NA Exceptions Not view order detail

Use Case Title PICKED UP Use Case ID UC- Actions  Order Picked up Description This Use Case described that how user can Mange customer Alternative Path Pre-Condition User have valid information Post-condition Can submit registration Author NA Exceptions Not picked up order

Use Case Title Generate Invoice Use Case ID UC- Actions  Generate invoice Description This use case tell how generate invoice

Alternative Path Pre-Condition User have valid information Post-condition Can submit registration Author NA Exceptions Generate invoice

Use Case Title Pharmacy Approval Use Case ID UC- Actions  Bill approve Description This Use Case described that how user can Mange customer Alternative Path Pre-Condition User have valid information Post-condition Can submit registration Author NA Exceptions Not approval

Use Case Title Cancel Order Use Case ID UC- Actions  Cancel Order Description This Use Case described that how user can Mange customer Alternative Path Pre-Condition User have valid information Post-condition Cancel Order Author NA Exceptions Not cancel order

Spiral:

Spiral module is like that we did our all small jobs together.

Work Plan: