Pharmacy Srs

Table of Contents Table of Contents  ........................................................................................................................... i Revision History  ............................................................................................................................. i 1. Introduction ............................................... ...................................................... .........................2 1.1 1.2 1.3 1.4 1.5

Purpose  ........................................................................................................................................ 2 Document Conventions  ............................................................................................................... 2 Intended Audience and Reading Suggestions .............................................................................. 3 Product Scope  .............................................................................................................................. 4 References   ................................................................................................................................... 5

2. Overall Description ...................................................... .................................................... ........6 2.1 2.2 2.3 2.4 2.5 2.6 2.7

Product Perspective   ..................................................................................................................... 6 Product Functions  ........................................................................................................................ 7 User Classes and Characteristics   ................................................................................................. 8 Operating Environment  ............................................................................................................. 10 Design and Implementation Constraints  .................................................................................... 11 Project Documentation  .............................................................................................................. 12 User Documentation  .................................................................................................................. 13

3. External Interface Requirements  .........................................................................................14 3.1 3.2 3.3 3.4

User Interfaces  ........................................................................................................................... 14 Hardware Interfaces  ................................................................................................................... 20 Software Interfaces  .................................................................................................................... 20 Communications Interfaces  ....................................................................................................... 20

4. System Features   .....................................................................................................................21 4.1 4.2 4.3 4.4

System Feature 1   ....................................................................................................................... 21 System Feature 2   ....................................................................................................................... 21 System Feature 3 (and so on)   .................................................................................................... 22 Use case Diagram …………………………………………………………………………… ..25

5. Other Nonfunctional Requirements ..................................................... ................................35 5.1 5.2 5.3 5.4 5.5

Performance Requirements ........................................................................................................ 35 Safety Requirements   .................................................................................................................. 35 Security Requirements  ............................................................................................................... 35 Software Quality Attributes  ....................................................................................................... 36 Business Rules  ........................................................................................................................... 36

Appendix A: Glossary ...................................................................................................................... Appendix B: Analysis Models  ......................................................................................................... Appendix C: To Be Determined List ................................................. .............................................

Revision History Name

Date

Reason For Changes

Version

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 co nventions that used in this SRS document. Main Section Titles Font: Times New Roman

Face: Bold

Size: 16

Face: Bold

Size: 14

Sub Section Titles Font: Times New Roman Other Text Explanations Font: Times New Roman

Face: Normal Size: 12

Text Sub headings Font: Times New Roman

Face: Bold

Size: 12

Face: Italic

Size: 12

Table and image figure Explanations Font: Times New Roman

2

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 co nventions that used in this SRS document. Main Section Titles Font: Times New Roman

Face: Bold

Size: 16

Face: Bold

Size: 14

Sub Section Titles Font: Times New Roman Other Text Explanations Font: Times New Roman

Face: Normal Size: 12

Text Sub headings Font: Times New Roman

Face: Bold

Size: 12

Face: Italic

Size: 12

Table and image figure Explanations Font: Times New Roman

2

1.3 Intended Audience and Reading Suggestions In the following section it will describe who the intended audiences are and what the important levels that they should specially read in this S RS document.



Client

In here manager of this project has the administrative power and other users have some minimum power to use this software. Therefore all the users in this system should have a clear idea about the hardware and software requirements that engaged with the final system. Therefore the authors would suggest to clients to go through the product functions, external interface requirements and system features.



Lecturer Since this is a student project, the lecturer in charge of ITP subject Ms.Geethanjali will

get a clear idea how this SRS is organized and design.



Supervisor Mr.S.M. Buddika Harshanth is the supervisor of this project and he can get a clear idea

about the SRS and give some suggestions to increase the correctness of this SRS document.



Team members There are seven members of this project team and also they are the developers of this

software solution they have a real advantage of quickly and easily understand the methodologies and techniques that are going to use in this project. As developers they go through the product functions, use case and activity diagrams, suggested user interfaces and the database scenario.

Finally, the above mentioned audience will be check this SRS document frequently to get a clear understand about this product as it go through in several design and implementation levels to ensure that the final system being comple ted by the given requirements.

3

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.

-

Since the client has a manual system they can use this proposed software system to

Goals:

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.

4

1.5 References

1." NetBeansTM IDE 4.0 Release Notes”, Oracle and/or its affiliates, [HTML]. th

Available: http://netbeans.org/community/releases/40/relnotes.html [Accessed on 29  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].

5

2. Overall Description 2.1 Product Perspective Wellawatte Drugs Pharmacy organization was started on year 2007. They are one of the leading pharmacy organizations in Srilanka. This organization was a well known one for supplying quality drugs & medicament equipment for their customers. so far they have set high standards in their business dealings. This organization is also having a very strong staffing system as well. They not only have business dealings with their customers. also they distributes drugs & medicament equipments to some other Pharmacy organizations as well. Up to now, all the transactions of this Organization were handled manually. But now they have decided to automate their system.To make their day to day activities easy. So now they require a strong Computer based System which will helps the pharmacists in order to make their day to day activities easy. such as inventory controlling, billing, staff management and report generating.This is newly design System to the Organization The System have ADMIN who has full-fledged rights with regards to managing resources such as check the Login Information, Update Data, Access to data base.

6

2.2 Product Functions 01. 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)

02. 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.

03. Handle stock returns & distributed stock return * Insert retunes drugs details (drug id, Drug Name, Return quantity, supplier id, distributor id)

04. 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.

05. Handle cash billing . *simply inserting drug details can generate a customer b ill

7

06. Handle staff details & staff salaries. * Insert employees details (Employee is, name, ad dress, Telephone no, Basic) * Calculate employee monthly salary *Administrator can view Salary report.

07. Handle financial detail. * Handle all financial details and insert these det ails 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 th is Product: 

Manager Who will be acting as the Administrator



WDP Employers who get details from the System and insert details to system

8

The functions that are available to the Manager are: 

Insert, Update, Delete and Find Drugs details.



Insert Purchase details.



View purchase report



Insert, Update, Delete and Find Suppler Details.



Insert, Update, Delete and Find Wholesale customer Details.



Insert distribute drug details



View distributed stock report.



Generate all kind of Bills



Insert, Update, Delete and Find Employee Details.



Calculate Employee Salary.



View employee salary.



Insert financial details.



View financial report.

The functions available to the WDP Employers: 

Insert, Update, Delete and Find Drugs details.



Insert Purchase details.



Insert, Update, Delete and Find Suppler Details.



Handle report



Insert, Update, Delete and Find Wholesale customer Details.



Insert distribute drug details



Generate all kind of Bills

9

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.

10

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.

11

2.6 Project Documentation



Project Charter

First we submit that documentation, it contain for Description of the Project, Group members, Project title and so on. That document creating to get Supervisor‟s Approval that‟s the main purpose of this document. 

Project Proposal

 Next we submitted Project proposal document. It contains for all project information and categorize in each part (Title Page, Abstract, Table of Contents, Problem Specification, Solution out line, Functions & etc). 

SRS

 Next submit that documentation. The SRS describes what the proposed system is going to do.

It‟s a document that will be shared by the - Customer, Designer, and Programmer and

even by other testing teams. It can be a legal document between the Customer and the Developer organizations. 

Prototype

Prototype is to allow users of the software to evaluate developers' proposals for the design of the eventual product by actually trying them out, rather than having to interpret and evaluate the design based on descriptions. Prototyping can also be used by end users to describe and prove requirements that developers have not considered so "controlling the prototype” can  be a key factor in the commercial relationship between developers and clients.



Final Documentation

Finally we submit that document. It‟s including progress of our tested product.

12

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.

13

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.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.

14

 Figure: 3.1.2

 Figure: 3.1.2

- This is our Home page. shows after the login and load this form. If

Administrator login into the Home page, He can control all the functions of the system. Such as Stock details, Stock distribution, Stock returns & Distributed stock return, Supplier Salary Information, Customer payments, Financial details & Reports.

15

 Figure: 3.1.3

 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 b y user/Administrator. 16

 Figure: 3.1.5  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.6  Figure: 3.1.6 - Billing, it includes Customer payments.

17

 Figure: 3.1.7

 Figure: 3.1.7 - Staff details form & Staff Salary form, it includes details about Staff, & Staff salaries. Those details can update or delete and view by Administrator.

18

 Figure: 3.1.8

 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.

19

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 data base. 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 20

4. System Features 4.1 Login The User or administrator can Login and Logout. When the administrator logs into the system the system will check for validity of login. If the Login and password are valid, the administrator will be able to modify, view report, add, delete and all other functions that can be  performed on the data. When the User Logs into the system the system will check for validity of login .If the Login and password are valid, the user can perform only the billing details.

4.2 Database Access Proposed Database is intended to store, retrieve, update, and manipulate information related to system which include. 

Stock details.



Stock distribution.



Stock returns & Distributed Stock return.



Supplier details.



Cash billing.



Staff details & Staff salaries.



Financial details.

Reports Generating Proposed system support generates reports to relevant transactions steps. System should generate the following reports. 

Stock report



Stock Purchase report.



Distribution stock report.



Stock Return report.



Employee Salary report.



Monthly income report.

21

4.3 Function Requirements 4.3.1 Handle stock details.

Stock detail function is a major function in pharmacy database system. It includes all the major details about medicine and other selling items. In this stock each item has a unique code number. By using the code number items can uniquely identity and find the drug information with find function. If you buy a new stock or return a stock, it is necessary to include it to database based on code number. During the transactions sometimes a discount was given by suppliers to pharmacy. User of the software should have to insert these discounts and the total amount of prize which they have to pay to supplier. The system will automatically do the calculation between prize and discount, and give the final total to be paid. By this pharmacy staff can manage a stock which has correct and up to date details. The following figure represents the basic idea of the pharmacy database stock. Also the user of the system should be able to insert a new item to database, delete a current item from database and update the details of a current item (ex : change a prize of a single unit of Aspirin). So we provide facility to perform those kinds of insert, delete and update in this system. Inside of this function we provide an additional object to user to generate a report about current available stock information and it generate stock purchase report. Also the user can find drug information through drug id or drug name, with find function

4.3.2 Handle stock distribution

Distributing medicine and other selling items among other pharmacies is another function of this pharmacy organization. So that is wholesale. The system has to maintain another function to generate these kinds of wholesale transactions. User of the system should have to insert customer name, item code, prize of a single unit and quantity. The system will automatically calculate the final prize that customer has to be paid. Following figure gives the basic idea of stock distribution function. In this system we provide an additional object to view a report about Distribution stock.

22

4.3.3

Handle returns stock details & distributed return stock details

Return stock is based on expire items and damage items. The usual system is if there is expiration or damage item, each item or items should need to return to manufacture or distributer  before six months, sometimes the wholesale customers can be return back stocks to the  pharmacy. In addition to that if you return some expire or damage item, the user should need to insert the value of minus quantity (return quantity) to stock database. The system will automatically subtract the return stock from current available stock of each item and give the final result of stock. (Stock quantity –  return quantity = current available quantity). In here when the user inserts these returning stock details, the system will automatically update the stock database. (By subtracting returning stock from available stock). Following figure gives the basic idea about the return stock.

4.3.4

Handle supplier details

This function handles about suppliers such as companies, manufactures or any kind of distributers. In this system suppliers can uniquely identify by their names or their id. Also user of the system should be able to insert supplier information (supplier id, name, address, telephone no etc...). Also user can delete or update supplier. The user can find supplier information through supplier id, with find function. Furthermore there is an additional function to generate a report about supplier details which include all the necessary information of suppliers.

4.3.5

Handle cash billing

Billing is an important function in pharmacy system because all the transactions between customer and pharmacy happen under this function. In this system there is a unique code for all selling items. The user of the system should have to insert the name of the item or code number (if he/she can remember) and the quantity of each selling item. The database of this system has the price of a single unit of each item. In addition to that system will automatically calculate and give the final price that customer should has to pay.

23

4.3.6

Handle staff details & staff salaries

In the pharmacy system there is a working staff. So their information such as names, OT hours, monthly salary and holiday working charges should be managed. In this system staff member can identify by his/her ID because ID is unique for each member. User of this system should have to insert basic salary, holiday working chargers, OT hours per month based on their names and ID. Then the system will automatically calculate the total monthly salary that should have to be paid to each staff member. Following figure show the basic idea of staff function. The user of the system should be able to insert a new staff member to the system, delete a current staff member from the system and update member details. So we provide facility to perform those kinds of insert, delete and update in this system. And also the user of the system can be able to view a report which include information about staff details and staff salaries. Furthermore we give another option to change the value of basic salary, value of OT hour and value of a one day of holiday charge inside of this function. Because the values which mentioned above can be changed time to time.

4.3.7

Handle financial detail

The system provides facility to generate the final income report of this pharmacy organization per month. To calculate the final income of each month the user should need to insert all the general payments of this organization such as water bills, electricity bills, staff salaries, business taxes and etc. The system will automatically calculate all of these payments and give the final income of each month.

24

4.4 Use Case Diagrams Generate bills for sale Bills for retail

Bills for wholesale

Manage item details

insert delete

update

Handle wholesale stock Distribution.

Handle Purchase stock Employee

Manage return stock from wholesale customer Manage supplier details

insert

delete

update

Stock details report

Purchase details report

Login

View stock database reports Manager

View billing reports

Manage return stock to su liers

insert

delete

update

Manage employee details

insert

delete

update

Set em lo ee salar View staff re ort 25

4.4.1 Use Case Scenario for Set Employee salary

Use Case Name

Set the Salaries of employees in staff.

Preconditions

User must log to system by administrator login.

Primary Actors

Manager

Main Flow of Events

1. Go to Tools tab in Home and click “Staff Salary”. 2. Enter the necessary details (member name, member ID, etc) 3. Press OK button to view final salary of each employee.

Extensions

2a. Inserted details of employee such as member ID and member are invalid.

4.4.2 Use Case Scenario for View Staff report

Use Case Name

View “staff member salary report”

Preconditions

User must log to system by administrator login.

Primary Actors

Manager

Main Flow of Events

1. Go to Report tab in Home and click “Staff salary report”. 2. Insert necessary details. 3. Click “View staff member salary report” button.

Extensions

3a. Salary of each employee is not inserted.

26

4.4.3 Use Case Scenario for Manage employee details

Use Case Name

Insert a new employee to database.

Preconditions

User must log to system by administrator login.

Primary Actors

Manager

Main Flow of Events

1. Go to Details tab in Home and click “Staff member details”. 2. Insert required details. (name, ID, tel_no, address, basic salary) 3. Press “Save” button.

Extensions

3a. Employee who is newly entered to database already exists.

Use Case Name

Delete an employee from database.

Preconditions

User must log to system by administrator login.

Primary Actors

Manager

Main Flow of Events

1. Go to Details tab in Home and click “Staff member details”. 2. Insert member name and member ID and press “Search” button. 3. If the member is available, press “Delete” button.

Extensions

2a. Employee who is going to delete from database is not available.

27

Use Case Name

Update details of an employee.

Preconditions

User must log to system by administrator login.

Primary Actors

Manager

Main Flow of Events

1. Go to Details tab in Home and click “Staff member details”. 2. Insert member name and member ID and press “Search” button. 3. If the member is available, press “Update” button.

Extensions

2a. Employee who is going to update is not available in database.

4.4.4 Use Case Scenario for Generate bills

Use Case Name

Generate bills for retails and whole sales.

Preconditions

User must log to system by user login or administrator login.

Primary Actors

Employee

Primary Actors

Manager

Main Flow of Events

1. Go to Tools tab in Home and click “Customer billing”. 2. Enter the item code and quantity for each item. 3. Search the availability of requesting items. 4. Calculate the final price of each customer has to pay. 5. Print the bill.

Extensions

3a. Requesting items are not available. 4a. Error in printer.

28

4.4.5 Use Case Scenario for Manage item details

Use Case Name

Insert a new item to database.

Preconditions

User must log to system by user login or administrator login.

Primary Actors

Employee

Primary Actors

Manager

Main Flow of Events

1. Go to Details tab in Home and click “ Manage item”. 2. Insert necessary details (Drug ID, Batch ID,…etc) 3. Press “New Item” button.

Extensions

3a. The item which is newly entered to database, already exists.

Use Case Name

Delete an item from database.

Preconditions

User must log to system by user login or administrator login.

Primary Actors

Employee

Primary Actors

Manager

Main Flow of Events

1. Go to Details tab in Home and click “Manage item”. 2. Insert Drug ID, Batch ID and press “Find” button. 3. Press “Delete” button.

Extensions

2a. The item which is going to delete from database, is not available.

29

Use Case Name

Update details of an item in database.

Preconditions

User must log to system by user login or administrator login.

Primary Actors

Employee

Primary Actors

Manager

Main Flow of Events

1. Go to Details tab in Home and click “Manage item”. 2. Insert Drug ID, Batch ID and press “Find” button. 3. Insert new details. 4. Press “Update” button.

Extensions

2a. The item which is going to update, is not available.

4.4.6 Use Case Scenario for Wholesale stock Distribution.

Use Case Name

Insert a new Wholesale customer to the database.

Preconditions

User must log to the system by user login or administrator login.

Primary Actors

Employee

Primary Actors

Manager

Main Flow of Events

1. Go to Details tab in Home and click “wholesale customer details”. 2. Insert necessary details(Name, ID, Phone no, and Address) 3. Press “Insert” button.

Extensions

3a. wholesale customer, who is newly entered to the database, already exists.

30

Use Case Name

Delete a Wholesale customer from the database.

Preconditions

User must log to the system by user login or administrator login.

Primary Actors

Employee

Primary Actors

Manager

Main Flow of Events

1. Go to Details tab in Home and click “wholesale customer details”. 2. Insert the Customer ID and Customer Name and then press “Search” button. 3. If the customer is available press “Delete” button.

Extensions

3a. Wholesale customer who is going to be deleting from database is not available.

Use Case Name

Update details of a Wholesale customer

Preconditions

User must log to system by user login or administrator login.

Primary Actors

Employee

Primary Actors

Manager

Main Flow of Events

1. Go to Details tab in Home and click “wholesale customer details”. 2. Insert the Customer ID and Customer Name and then press “Search” button. 3. If the customer is available insert new details. 4.  press „Update” button

Extensions

4a. Wholesale customer who is going to be updated is not available.

31

Use Case Name

Handle wholesale stock Distribution.

Preconditions

User must log to system by user login or administrator login.

Primary Actors

Employee

Primary Actors

Manager

Main Flow of Events

1. Go to Tools tab in Home and click “wholesale stock distribution “. 2. User enters the necessary details (invoice no, customer id and name, item code ,item name, single quantity price and quantity) 3. Clicks the “Calculate” button to find the final price.

Extensions

2a. Details which are inserted (such as customer ID, customer name) are invalid.

4.4.7 Use Case Scenario for return stock from Wholesale customer. Use case Name :

Manage return stock from Wholesale customer.

Preconditions :

User must log to the system.

Primary Actors :

Employee and Administrator

Main Flow of Events

1

User selects “Details” and selects “Return Wholesale customer stock”.

2

User enters stock return details.

3

User click “Return” button.

4

System reduces the return stock from the current stock.

2.1

User updates the details in the database.

2.2

User deletes the details in the database.

2.3

User inserts details to the database.

Extension:

32

4.4.8 Use Case Scenario for Return stock from Supplier

Use case Name :

Return stock from Supplier

Preconditions :

User must logged to the system

Primary Actors :

Administrator and User

Main Flow of Events

1

User selects “Details” and selects “Return Supplier stock”.

2

User enters supplier stock return details.

3

User click Add button

4

System reduces the return stock from the current stock.

2.1

User insert the details to the database

Extensions

4.4.9 Use Case Scenario for Manage Supplier Details

Use case Name :

Manage Supplier Details

Preconditions :

User must logged to the system

Primary Actors :

Administrator  and User 

Main Flow of Events

1

User selects “Details” and select “Supplier Details”.

2

User enters the supplier ID .

3

User click find  button

4

System will find the supplier detail in the database.

2.1

User insert the details to the database

Extensions :

33

Use case Name :

Manage Supplier Details

Preconditions :

User must logged to the system

Primary Actors :

Administrator  and User 

Main Flow of Events

1

User selects “Details” and select “Supplier Details”.

2

User deletes the supplier details.

3

User click Delete  button

4

System deletes the supplier detail in the database.

Extensions :

Step

34

5.Other non functional Requirements. 5.1 Performance Requrements This pharmacy Management System is minimum hardware and software requriments.We need following performance to run our system properly. o

500MZh pentium II or higher

o

512 MB of RAM

o

800 * 600 minimum resolution

In Our system we have several Graphical User Interfaces and Inorder to moving one GUI to another GUI no need to wait more than three seconds. In the case of printing requrements the printing hardware performance is out of the control of our system. The system will take no longer than 10 seconds for the system to initiate request to a  printer.The system will take no longer than 5 seconds to calculate tatal amount of a bill. In this  process the system need more memory usage more than minimum memory usage.

5.2 Safety Requrements Data handle is an important part of our system. We use one central database to store our system data. If any power failure, virus attack or data crash can lost all data of the database. Therefore we recommend taking the backup for database after doing any updating. And also recommend use separate power supply and install updating virus guard to the database machine.

5.3 Security Requrements Wellawatta Drug Pharmacy Management System has two type of users. There are administrator and other employees. System will provide different accesse permisions to these users. Users will allocate to be allocated to user name and password to access the system. Users can change their password in one time, but they can‟t change their user name. Administrator can access all function of the s ystem. He or she becomes a main user of the system. But other type of users can access limited amoun t of the functions.

35

5.4 Software Quality Attributes Availability

This pharmacy Management system is only available for PMS client desktop machine. We give them to final version of developing system. If any user logging to the system, system identify type of user and give permission to do their work. Operability

System allows the user to operate with a mouse unless input is required form the keyboard. This is allowing to user to insert data easily. Correctness

We are doing various test cases and check the accuracy of the system. If any errors found we correct them before delivering the software to client. Flexibility

After delivering software if client want to do any changing we hope to do that changes immediately without any charges. Maintainability

We give our Clint to one year maintain warranty. We fix all trouble within the warranty  period. This Pharmacy Manage system is not portable software and also it is not reusability software for other pharmacies. At the software delivery time it will be delivered with a user manual which will detail the use of the system client.

5.5 Business Rules. System administrator can view each operation an y time. If there are any changes the system is capable of handling such information.

36

Appendix A: Glossary WDP

--

Wellewatte Drugs Pharmacy

SRS

--

software requirement specification

JDK

--

Java Development Kit

37