Pharmacy Stock Management System: Functions and Use Cases, Study Guides, Projects, Research of Software Engineering

The functions and use cases of a Pharmacy Stock Management System. Users can handle stock details, customer transactions, returns, supplier information, and cash billing. The system supports reports such as stock reports, purchase reports, and distribution reports. Users can log in as administrators or employees, and access different functionalities based on their roles. The system requires specific hardware and software installations, including MySQL 5.1 and iReport software.

Typology: Study Guides, Projects, Research

2021/2022

Uploaded on 09/22/2022

Ayush6665
Ayush6665 🇺🇸

1 document

1 / 38

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
i
Table of Contents
Table of Contents
........................................................................................................................... i
Revision History
............................................................................................................................. i
Introduction
...............................................
......................................................
.........................2
1.1
Purpose
........................................................................................................................................ 2
1.2
Document Conventions
............................................................................................................... 2
1.3
Intended Audience and Reading Suggestions
.............................................................................. 3
1.4
Product Scope
.............................................................................................................................. 4
1.5
References
................................................................................................................................... 5
2.
Overall Description
......................................................
....................................................
........6
2.1
Product Perspective
..................................................................................................................... 6
2.2
Product Functions
........................................................................................................................ 7
2.3
User Classes and Characteristics
................................................................................................. 8
2.4
Operating Environment
............................................................................................................. 10
2.5
Design and Implementation Constraints
.................................................................................... 11
2.6
Project Documentation
.............................................................................................................. 12
2.7
User Documentation
.................................................................................................................. 13
3.
External Interface Requirements
.........................................................................................14
3.1
User Interfaces
........................................................................................................................... 14
3.2
Hardware Interfaces
................................................................................................................... 20
3.3
Software Interfaces
.................................................................................................................... 20
3.4
Communications Interfaces
....................................................................................................... 20
System Features
.....................................................................................................................21
4.1
System Feature 1
....................................................................................................................... 21
4.2
System Feature 2
....................................................................................................................... 21
4.3
System Feature 3 (and so on)
.................................................................................................... 22
4.4
Use case Diagram
…………………………………………………………………………… ..25
Other Nonfunctional Requirements
.....................................................
................................35
5.1
Performance Requirements
........................................................................................................ 35
5.2
Safety Requirements
.................................................................................................................. 35
5.3
Security Requirements
............................................................................................................... 35
5.4
Software Quality Attributes
....................................................................................................... 36
5.5
Business Rules
........................................................................................................................... 36
Appendix A: Glossary
......................................................................................................................
Appendix B: Analysis Models
.........................................................................................................
Appendix C: To Be Determined List
.................................................
.............................................
Revision History
Name
Date
Reason
For
Changes
Version
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26

Partial preview of the text

Download Pharmacy Stock Management System: Functions and Use Cases and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!

i

Table of Contents

Table of Contents ........................................................................................................................... i Appendix A: Glossary...................................................................................................................... Appendix B: Analysis Models ......................................................................................................... Appendix C: To Be Determined List ..............................................................................................

Revision History

    1. Introduction .............................................................................................................................. Revision History i
  • 1.1 Purpose
    • 1.2 Document Conventions
    • 1.3 Intended Audience and Reading Suggestions..............................................................................
    • 1.4 Product Scope
    • 1.5 References
    1. Overall Description ..................................................................................................................
    • 2.1 Product Perspective
    • 2.2 Product Functions
    • 2.3 User Classes and Characteristics
    • 2.4 Operating Environment
    • 2.5 Design and Implementation Constraints
    • 2.6 Project Documentation
    • 2.7 User Documentation
    1. External Interface Requirements .........................................................................................
    • 3.1 User Interfaces
    • 3.2 Hardware Interfaces
    • 3.3 Software Interfaces
    • 3.4 Communications Interfaces
    1. System Features .....................................................................................................................
    • 4.1 System Feature
    • 4.2 System Feature
    • 4.3 System Feature 3 (and so on)
    • 4.4 Use case Diagram…………………………………………………………………………… ..
    1. Other Nonfunctional Requirements .....................................................................................
    • 5.1 Performance Requirements
    • 5.2 Safety Requirements
    • 5.3 Security Requirements
    • 5.4 Software Quality Attributes
    • 5.5 Business Rules

1. Introduction

1.1 Purpose

This software requirement specification (SRS) is design and its main objective is to illustrate all the requirements of the project Pharmacy Management System. This SRS document mention all the information related to the project and it will gives the detail description of each and every functional and non functional requirement that proposed by the client. And also this SRS will illustrate what are the main user interfaces that the system looks like after the implementation and how they connect each other using some sketching. Then the client can easily understand the system final system. This SRS document is design after having some consultations with the client and after getting a complete understand about the client‟s requirements. Therefore the final software solution of the development team will be meet all the clients requirements and all the functionalities will be function as the describe here in this SRS document.

1.2 Document Conventions

The followings are the list of standards and typographical conventions that used in this SRS document. Main Section Titles Font: Times New Roman Face: Bold Size: 16 Sub Section Titles Font: Times New Roman Face: Bold Size: 14 Other Text Explanations Font: Times New Roman Face: Normal Size: 12 Text Sub headings Font: Times New Roman Face: Bold Size: 12 Table and image figure Explanations Font: Times New Roman Face: Italic Size: 12

1.4 Product Scope

Project Title: Pharmacy Management System

Description: Wellawatte Drugs Pharmacy organization was started on year 2007 which always supply quality & standard drugs & medicament equipment to their customers. Until today all the transactions were handled by manually. But now they need a computer system to handle their manual process due to capital requirments of information handling & report generating.So the proposed computer system can be handled all these information and a perfect report generating.

Product Characteristics:

  • Tracking status of every transaction.
  • Handle Stock details.
  • Secured database
  • Generate all kind of reports.
  • Handle Staff Details.

Benefits for the client:

  • Easy to maintain all the transaction details.
  • Increase the accuracy of data.
  • Provide a well organized process to track the current status of transaction.
  • Increase the efficiency and performance of the system.
  • Informing process via report generating.
  • Security and integrity.

Goals:

  • Since the client has a manual system they can use this proposed software system to increase the productivity of their project.
  • Also using this software solution they can achieve their business goals with less amount of time
  • As developers, the main goal of the development team is complete this project within allocated time period and within the budget allocated.

1.5 References

1."NetBeansTM IDE 4.0 Release Notes”, Oracle and/or its affiliates, [HTML]. Available: http://netbeans.org/community/releases/40/relnotes.html [Accessed on 29 th^ July 2011]

2."Installing MySQL on Windows”, Oracle and/or its affiliates, Available:http://dev.mysql.com/doc/refman/5.1/en/windows-installation.html[Accessed on 3rd August 2011].

2.2 Product Functions

  1. Handle stock details
  • Insert to database the details about drugs (drug id, Name, Mfc, location, Category, quantity,)

  • Insert to database the details about purchase (Drug id, Name, Mfc, Location, Category, quantity, Expire date and Supplier id)

  • Also can get three kind of reports-Stock Report, purchase report, and reorder level report)

  1. Handle stock distribution
  • User of the system need to insert customer name, item code, prize of a single unit and quantity

  • Also can get report about stock distribution report.

  1. Handle stock returns & distributed stock return
  • Insert retunes drugs details (drug id, Drug Name, Return quantity, supplier id, distributor id)
  1. Handle supplier details
  • Insert to database the details about supplier (supplier id, name, address, telephone)

  • User can find details about supplier by giving supplier id.

  1. Handle cash billing.

*simply inserting drug details can generate a customer bill

  1. Handle staff details & staff salaries.
  • Insert employees details (Employee is, name, address, Telephone no, Basic)

  • Calculate employee monthly salary

*Administrator can view Salary report.

  1. Handle financial detail.
  • Handle all financial details and insert these details in to database.

  • Administrator can get report about the monthly profit details by giving the relevant month.

2.3 User Classes and Characteristics

Manager who is the Major user of the Product consider as the Administrator, who use the System with All privilege levels have to Manager And the other users of the System known as WDP Employers can Add, Delete, update View the data from the System they have least privileges.

There are two different users who will be using this Product:  Manager Who will be acting as the Administrator  WDP Employers who get details from the System and insert details to system

2.4 Operating Environment

 Product Operate Environment (Windows XP) - Because pharmacy used the XP as the O/S so we must to make Windows Application to compatible to this O/S.

 Running Environment (.JDK and JRK) - We make this software Product Using Net Beans IDE 6.9. So run this Software Product in the Client Pc its needs to have JDK and JRK.

 Database (MySQL 5.1)- We use MySQL 5.1 as Our Data base so also run this S/W Application We need to Install Data base to the client pc as well.

 Hardware platform – Above mention Database, Running Environment and Operate Environment require 2.0 GHz Pentium Dual Core or higher, 1GB of RAM, VGA 32bit 800x 600 minimum resolutions.

 Reports (iReports) - We use iReport software to get all kind of reports, so we need to install iReport software to client pc.

2.5 Design and Implementation Constraints

When creating software we can choose two options (web based, desktop based) but we have decided to create our software using Desktop based environment. The reason for not choosing a web based System is because web base system refers to those applications or services that are resident on a server which is accessible using a Web browser and any one can access from anywhere in the world via the Web, therefore the system is unsecured. It is harm full for our privacy. That is the main reason for choosing a desktop based system.

Our product is developed using (Netbeans IDE and My SQL tools). The Java is a open source tool kit that‟s why we have decided to use (Netbeans IDE and My SQL tools) because it provides more user friendliness.

We have some parallel operations we developed our product using Netbeans IDE and My SQL Server. So then our interface design and database creations are going on parallel operations.

2.7 User Documentation

This product includes SRS document, Final documentation, User manuals.

The SRS document includes.

 Introduction  Overall Description  External Interface Requirements  System Features  Other Nonfunctional Requirements  Other Requirements

And user manual include contain both a written guide and the associated images. In the case of computer applications, it is usual to include screenshots of how the program should look, and hardware manuals often include clear, simplified diagrams. The language used is matched to the intended audience to a minimum or explained thoroughly. That situation there is no more online help for this product. The product will be compatible with our client computer requirements. The databases will be created in the MySQL server 5.1. Our contact information will include email address and Phone Numbers.

3. External Interface Requirements

3.1 User Interfaces

The Net Beans IDE 6.8 is an integrated development environment (IDE) for software applications. It provides developers with a visual layout designer to support the rapid design and development of graphical user interface (GUI) components. That product will use Windows Forms. Windows Forms requires the JDK & JRK running on the client computer.

Figure: 3.1.

Figure: 3.1.1 - This is the first form in our system. It‟s a login page that can be use for Administer and other users. If it is logging to the admin he‟s can be get a full permission in a system. That is a include data insert, delete or update and view. The user can be use only billing information. User can‟t perform all transactions of system and can‟t view information in database.

Figure: 3.1.

Figure: 3.1.3 - Stock detail form, it includes all the details of stock. Those details can insert, update or delete by user/Administrator.

Figure: 3.1. 4 Figure: 3.1. 4 Stock return Disribution , it includes all the details of stock return Distribution. Those details can insert, update or delete by user/Administrator.

Figure: 3.1. Figure: 3.1.5 - Supplier Details, it includes all the details of Suppliers. Those details can insert, update or delete by user/Administrator.

Figure: 3.1. Figure: 3.1.6 - Billing, it includes Customer payments.

Figure: 3.1.

Figure: 3.1.8 - Finance Details form , through this Adminstrator can calculate the income, Expenses & profit of the month. As well as he can view the monthly income report.

3.2 Hardware Interfaces

The system that we create includes hardware components mainly as printer. The printer is mainly using for generating bills and reports. The system and database is connecting as internal network connection. That database is in the database server.

3.3 Software Interfaces

 Database It is obtained MySQL 5.1 server for creating database. This server needs to run other requirements plug-ins.  MySQL provides excellent facility to editing and executing queries and launching standard wizard task.  SQL Server Profiler provides a graphical user interface for monitoring an instance of the SQL Server database engine or an instance of Analysis Services.  Database Engine Tuning Advisor helps create optimal sets of indexes, indexed views, and partitions.  Manage SQL Server objects from the command prompt.  Manage server and client network configuration settings.  Integration Services provides a set of graphical tools and programmable objects for moving, copying & transferring data.

 Reporting tools The iReport software we use as the reporting tool in our system. Using iReports user can generate all kind of reports which he need.

3.4 Communication Interface

 The database is communicated with MySQL server.  Create an Applications communicate with JDK, JRK and operating system.  Then software adapt MySQL server and communicate with database