Department of Computer Science & Information Technology ... · Online Pharmacy Management System Date: 15 Oct,2017 I.T Hub Sargodha 1 Department of Computer Science & Information

I.T Hub Sargodha Version 1.0

Online Pharmacy Management System Date: 15 Oct,2017

I.T Hub Sargodha 1

Department of Computer Science & Information

Technology

University of Sargodha

Online Pharmacy Management System Version 1.0



I.T Hub Sargodha 2

Contents

CHAPTER 1: FINAL PROJECT PROPOSAL ......................................................................... 5

..................................................................................................................................................... 5 1.1: INTRODUCTION: .................................................................................................................... 5 1.2: PROJECT TITLE: ..................................................................................................................... 5 1.3: PROJECT OVERVIEW STATEMENT: ........................................................................................ 5

1.3.1. Purpose: ........................................................................................................................ 5

1.3.2. Scope: ........................................................................................................................... 6

1.3.3. Definition: .................................................................................................................... 6

1.3.4. Project Overview Statement Template: ....................................................................... 6 1.4. GOALS & OBJECTIVES:.......................................................................................................... 8

1.5. LIST OF OPTIONAL FUNCTIONAL UNITS: ................................................................................. 8 1.6. EXCLUSIONS: ........................................................................................................................ 8

1.7. APPLICATION ARCHITECTURE: .............................................................................................. 9 1.8. GANTT CHART: ..................................................................................................................... 9 1.9 HARDWARE AND SOFTWARE SPECIFICATIONS: .................................................................... 10

1.9.1. Hardware Requirements: ........................................................................................... 10 1.9.2. Software Requirement ............................................................................................... 10

1.10. TOOLS AND TECHNOLOGIES USED WITH REASONING: ........................................................ 10 1.10.1 Front-End /Back-End technologies: .......................................................................... 11

1.10.2. Tools: ........................................................................................................................ 11

CHAPTER NO 2: FIRST DELIVERABLE ............................................................................. 12

2.1. PROJECT/PRODUCT FEASIBILITY REPORT:........................................................................... 12

2.1.1. Technical Feasibility: ................................................................................................ 12 2.1.3. Economic Feasibility: ................................................................................................ 12 2.1.4. Schedule Feasibility: .................................................................................................. 12

2.1.5. Specification Feasibility: ........................................................................................... 13 2.1.6. Information Feasibility: ............................................................................................. 13

2.1.7. Motivational Feasibility: ............................................................................................ 13 2.1.8. Legal & Ethical Feasibility: ...................................................................................... 13

2.2. PROJECT/PRODUCT SCOPE: ................................................................................................. 13

2.3. PROJECT/PRODUCT COSTING: ............................................................................................. 13 2.3.1. Project Cost Estimation by Function Point Analysis: .............................................. 13 2.3.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost Model) .......... 14 2.3.3. Activity Based Costing: .............................................................................................. 15

2.4. TASK DEPENDENCY TABLE: ................................................................................................ 15 2.5. CPM - CRITICAL PATH METHOD: ....................................................................................... 16

2.5.1. Specify the Individual Activities: .............................................................................. 16 2.5.2 Determine the Sequence of the Activities: ................................................................. 16 2.5.3. Draw the Network Diagram: ..................................................................................... 16 3.5.4. Estimate Activity Completion Time: ...................................................................... 16



I.T Hub Sargodha 3

2.5. 5. Identify the Critical Path: ......................................................................................... 17 2.6. GANTT CHART: .................................................................................................................... 17

2.7. INTRODUCTION TO TEAM MEMBER AND THEIR SKILL SET: ................................................... 17 2.8. TASK AND MEMBER ASSIGNMENT TABLE: .......................................................................... 18

2.8.1. Allocation of People to Activities: ............................................................................. 18 2.9. TOOLS AND TECHNOLOGY WITH REASONING: ..................................................................... 18

2.9.1. Technologies: ............................................................................................................. 19

2.10. VISION DOCUMENT: .......................................................................................................... 19 2.10.2. Scope: ....................................................................................................................... 19 2.10.3. Definition: ................................................................................................................ 19

2.12. PRODUCT FEATURES / PRODUCT DECOMPOSITION: ........................................................... 20

CHAPTER 3: SECOND DELIVERABLE FOR OBJECT ORIENTED APPROACH ...... 21

3.1. EXISTING SYSTEM: .............................................................................................................. 21 3.2 SCOPE OF THE SYSTEM: ........................................................................................................ 21

3.3 SUMMARY OF REQUIREMENTS: (INITIAL REQUIREMENTS): .................................................. 21 3.4 IDENTIFY EXTERNAL ENTITIES:............................................................................................ 21

3.5 CAPTURE “SHALL” STATEMENT: .......................................................................................... 22 3.6 ALLOCATE REQUIREMENTS:................................................................................................. 22 3.7 PRIORITIES REQUIREMENTS: ................................................................................................ 22

3.8 REQUIREMENTS TRACEABILITY MATRIX: ............................................................................ 23 3.9 HIGH LEVEL USE-CASE DIAGRAMS: PHARMACY MANAGEMENT SYSTEM: .......................... 24

3.10 ANALYSIS LEVEL USE-CASE DIAGRAM: PHARMACY MANAGEMENT SYSTEM: ................... 25 3.11. USE CASE DESCRIPTION: ................................................................................................... 26

3.11.1. User Registration: .................................................................................................... 26

3.11.2. Log in: ...................................................................................................................... 26

3.11.3. Manage medicine: .................................................................................................... 27 3.11.4. Order: ....................................................................................................................... 28

CHAPTER 4: THIRD DELIVERABLE FOR OBJECT ORIENTED APPROACH .......... 29

................................................................................................................................................... 29 4.1 ARTIFACTS WHICH ARE INCLUDED IN THIS CHAPTER: .......................................................... 29 4.2 DOMAIN MODEL: ................................................................................................................. 29

4.3. CUSTOMER’S SEQUENCE DIAGRAM OF PHARMACY MANAGEMENT SYSTEM: ..................... 30 4.4 ADMIN SEQUENCE DIAGRAM: .............................................................................................. 31 4.5 SYSTEM SEQUENCE DIAGRAM FOR PHARMACY MANAGEMENT SYSTEM: ............................ 32 4.6 COLLABORATION DIAGRAM: ................................................................................................ 33

4.7 DESIGN CLASS DIAGRAM: .................................................................................................... 34 4.8 ENTITY RELATIONSHIP DIAGRAM: ....................................................................................... 35 4.9 STATE CHART DIAGRAM FOR PHARMACY MANAGEMENT SYSTEM: .................................... 36

CHAPTER 5: 4TH DELIVERABLE (USER INTERFACE DESIGN) .................................. 37

5.1. SITE MAPS: ......................................................................................................................... 37 5.2.1. Administrator and Customer login: .......................................................................... 38 5.2.2. Customer registration: ............................................................................................... 39 5.2.3. Add new item to the stock: ..................................................................................... 39



I.T Hub Sargodha 4

5.2.4. Update Stock. .............................................................................................................. 40 5.2.5. Order Placement: ....................................................................................................... 40

5.2.6. Order Detail on the Admin page: .............................................................................. 41 5.3. NAVIGATIONAL MAPS: ........................................................................................................ 41

5.3.1. View Stock: ................................................................................................................. 41 5.3.2. View Comments of Customers: ................................................................................. 42 5.3.3. View Customers inforamtion: .................................................................................... 42

5.3.4. View Invoice: .............................................................................................................. 42 5.3.5: Contact Us Page: ....................................................................................................... 43

CHAPTER 6: FIFTH DELIVERABLE SOFTWARE TEST ................................................ 44

6.1 INTRODUCTION:............................................................................................................... 45

6.2 PURPOSE OF TESTING: ..................................................................................................... 45 6.3 PROJECT OVERVIEW: ....................................................................................................... 45 6.4 SCOPE OF TESTING: ......................................................................................................... 45

6.5 TEST PLAN STRATEGY: ................................................................................................... 45 6.5.1 Unit Testing: ........................................................................................................... 45

6.5.2 Integration Testing: ............................................................................................... 45 6.5.3 System Testing: ...................................................................................................... 45

6.6 TEST ENVIRONMENT: ...................................................................................................... 46

6.7 SCHEDULE: ...................................................................................................................... 46 6.8 CONTROL ACTIVITIES: .................................................................................................... 46

6.9 FUNCTIONS TO BE TESTED: .............................................................................................. 46 6.10 FUNCTIONS NOT TO BE TESTED: ................................................................................... 46 6.11 TEST CASES: ................................................................................................................ 46

6.11.1 Test Case 01: .......................................................................................................... 46

6.11.2 Test Case 02: .......................................................................................................... 47 6.11.3 Test Case 03: .......................................................................................................... 48 6.11.4 Test Case 04: .......................................................................................................... 49

6.11.5 Test Case 05: .......................................................................................................... 50 6.11.6 Test Case 06: .......................................................................................................... 50



I.T Hub Sargodha 5

Chapter 1: Final Project Proposal

1.1: Introduction:

The practice of pharmacy involves the general implementation of medical orders which entails

the evaluation and the interpretation of the medical orders, the administration of drugs,

dispensation of prescribed drugs from qualified medical practitioners, the review of prescribed

drug regimen, and the correct storage of medicine items. In addition, the birth of modern pharmacy has brought with it some positive effects in the

society; like the increase in life expectancy globally from 45 years to 50 years, which some

argue is as a result of the number of breakthroughs recorded in pharmacy over the last

century. These breakthroughs such as: the discovery of new compounds in battling existing

ailments and the invention of methods and devices to accurately dispense drugs have been

welcomed with open arms by the society.

More so, the hospital pharmacy is usually located in hospitals (government-owned or

private) and provides in-house pharmaceutical care to patients. Hospital pharmacists are those

that function within a hospital pharmacy system and are tasked with the dispensing of

prescriptions, the purchase of medicines, and the testing of these medicines. In the hospital

pharmacy, access to medical records make it easy to influence the selection of drugs based on

allergies or previous problems encountered. Subsequently, the power to control the process of

going into the acquisition of drugs and other pharmaceutical devices, help in ensuring the supply

of premium quality drugs.

Also, the community pharmacies may not have the permission to dispense certain drugs which

may be due to the nature of such drugs and the prices of drugs are not as subsidies as those in

hospital pharmacies.

The proposed system aims to connect and serve as an intermediary between hospital pharmacies

and drug manufacturers, through a platform that allows the order of drugs with the click of a

button, and simultaneously keeps track of what drugs have been ordered and in what quantity.

1.2: Project Title:

Online Pharmacy Management System.

1.3: Project Overview Statement:

1.3.1. Purpose:

This document (SRS ” Software Requirements Specification”) gives a complete details

about the particularization and functions of ONLINE PHARMACY MANAGEMENT SYSTEM. The main purpose of developing this software is to replace the existing manual

system with the modern technology. To perform all the operations of pharmacy in a computerized environment. To facilitate the customer, to reduce the man power and also to

save the time which was wasted on paper work, so all the work is done on the computer. To keep the records of medicines stock update easily such type of system was needed by the pharmacist through which they can easily handle all the activities and operations about the

pharmacy.



I.T Hub Sargodha 6

1.3.2. Scope:

The scope of any project much matter in its success. A system is provided to the admin of

pharmacy through which he can easily maintain the all the records of medicines, he can add new medicines in the stock, delete medicine from the stock, he can search the stored item

through their name or batch number. The system will generate alerts about the expiry of items 3 month before their expiry date and also will not allow to sale the expired items, automatically will remove those items from the stock which are expired. The system will

also generate alerts about the items whose stock has reached to end. The system also will keep the records about the manufacturer companies of medicines and also their supplier.

The system will keep complete information about the customer his/her name, email address/mobile number, gender, country, city and postal address. The system will first

register the new customer before placing an order for the registration the customer will have to provide complete information about him/her and after registration and authentication he will be able to place an order for the sake of purchasing his/her required items from our

website. The client will select the category of medicines and the will search the required medicine by its name or batch no.

The system will also keep the complete information about the payments of orders weather these payments are related to customer or supplier of the medicine, but there is not online

payment method, the payments from the customer will receive at the time of delivery of order.

1.3.3. Definition:

“ONLINE PHARMACY MANAGEMENT SYSTEM” can handle data of medicine

items and customers. This will be most useful for the pharmacist to manage the records about the

pharmacy as well as for the customers to purchase their required medicine easily by sitting in

their home.

1.3.4. Project Overview Statement Template:

Project Title: ONLINE PHARMACY MANAGEMENT SYSTEM

Project Manager: Sir Umair Mujtaba Khan

Project Members: Muhammad Shakir , Muhammad Nabeel

Name Registration

#

Email Address Signature

Muhammad

Shakir

15MIT4417 [email protected] M.Shakir

Muhammad

Nabeel

15MIT4412 [email protected] M. Nabeel

Project Goal: This Software Requirements Specification provides a complete

description of all the functions and specifications ONLINE PHARMACY

MANAGEMENT SYSTEM. A pharmacist can easily maintain the record about the

medicines and the accounts records of pharmacy.

mailto:[email protected]

mailto:[email protected]



I.T Hub Sargodha 7

Objectives:

Sr.# 1 Through this system the customer can easily order his/her required medicine

items.

2 This portal will be most useful for the pharmacist to handle the records 3 Admin also can maintain the record about the supplier and customers.

The project’s success is based on following criteria:

1. The project will be considered as a successful if the system will be able to include/adjust the new conditions, otherwise will not be consider as a

successful project.

2. The system ensures around-the-clock availability, mean the system should be available at any time when it is access.

3. The system will be considered as a successful if it performs its all functions as they are described in the documentation if not perform according to the stated conditions the will not be considered as a successful system.

4. The responsiveness is much compulsory for the success of any system, a system will be considered as a successful system if it responses timely because

now a day clients are in hurry they do not want wait more than 5 to 10 seconds.

5. The proposed system provides ease of use, effectiveness, efficiency,

learnability and an overall users’ satisfaction in addition to perform these tasks:

i. It can handle records about the medicines items. ii. The customer can order online if he is registered.

iii. Admin can generate the reports about the sales and purchases of medicines

iv. Admin can also maintain the record about the supplier and customers. v. The admin can also easily modify the data records about medicine items.

Assumptions, Risks and Obstacles: 1. It is assumed that all the users of our system have the knowledge of computer

if they have no knowledge about the computer use then this may cause risk. 2. Because our system is web based so it is assumed that the all the user have

internet connection. 3. Customer can refuse or send back the delivered ordered due to not required

company’s item. 4. This system is being developed with the cooperation, readiness and support of

all executive level management would be required from the initiation of project and till the completion and deployment phase. Lack of readiness, cooperation, and support of all executive level management can lead to an

unfinished system. 5. IT infrastructure with proper hardware would be required for the effective and

successful deployment and running of the system. 6. Time, technical expertise & budget constrains may introduce serious obstacles

towards the completion of the project. 7. It is not necessary that accuracy will be 100% adapted.



I.T Hub Sargodha 8

Organization Address (if any):

IT-Hub, 113/3 Stadium Road Sargodha.

Type of project: Research Development

Target End users:

Admin, Customer

Development Technology: Object Oriented Structured

Platform: web based Distributed

Desktop based Setup Configurations

Other_____________________

Approved By: Sir Umair Mujtaba Khan

Date:08 Sep 2017

1.4. Goals & Objectives:

The main objective of the application is to automate the existing system of manually maintained

records of the counter sales, purchases, reorder levels, Supplier and Customer monetary positions and

other related transactions made by the admin. This application can be used by any other store to

automate the process of manually maintaining the records related to the subject of maintaining the

stock and liquid flows.

1.5. List of optional functional units:

1. Stock Reports.

2. Hospital management system.

3. Android app.

1.6. Exclusions:

It is online pharmacy management system not include online payaments.



I.T Hub Sargodha 9

1.7. Application Architecture:

It is 3-tier application.

Figure 1.1

1.8. Gantt Chart:

ID Task Name Start Finish DurationMay 201 7 Jun 2017 Jul 2017 Aug 2017

5-21 5-28 6-4 6-11 6-18 6-25 7-2 7-9 7-16 7-23 7-30

1 14d6/8/20175/22/2017Proposal

2 11d23-Jun-176/9/2017SRS

3 13d12-Jul-176/26/2017Planning and Analysis

4 20d09-Aug-177/13/2017First Deliverable

5 20d06-Sep-178/10/2017Second Deliverable

6 17d9/29/20179/7/2017User Interface and Design

7 15d20-Oct-1710/2/2017Testing

8 8d01-Nov-1710/23/2017Deployment

9 7d10-Nov-1711/2/2017Implementation

8-6 8-13 8-20

Figure 1.2



I.T Hub Sargodha 10

1.9 Hardware and Software Specifications: 1.9.1. Hardware Requirements: To run the application software of the system in the computer the minimum configuration required is as

below:

1. 233 MHz processor.

2. RAM: 512 MB or greater

3. Hard Disk: 20 GB or greater

4. Keyboard: 104 keys standard

5. 1.44 MB Floppy Disk Drive.

6. Monitor. [ 640 x 480 Display]

7. Mouse: 2/3 button. Optical/ Mechanical

This is the brief introduction of Hardware Configuration for the system. The system can work in news

technology also. It is just telling that system can work with old technology also but, it consist of this

minimum configuration of Hardware.

1.9.2. Software Requirement To Handel the system, Administrator requires some software. This software is used for the development

such as coding and testing. Lists are given below:

1. Front End -HTML, CSS & BOOTSTRIP

2. Back End -PHP-MySQL 5.0

3. Server -Apache Server 2.0

4. Design Tool -Macromedia Dreamweaver 8.0 and Notepad++

5. Documentation Tools -Microsoft Word -Microsoft PowerPoint and Microsoft Visio.

1.10. Tools and Technologies used with reasoning:

There are following tools and technologies that are used in our system:

Tools: 1. MS Visio Professional:

MS Visio Professional is used to make the ERD, Use case diagram, Sequence diagram, Class

diagram, State machine diagram domain model and Collaboration diagram.

2. MS Project Professional:

Gantt chart which have much importance in any project for project scheduling. MS Project

Professional is used to make gantt chart.

3. MS word:

Documentation of any project is much necessary so MS Word is used for the

documentation.

4. Notepad++ : Notepad++ is an editor which is used for coding the software.

5. Web Server: To run or execute the PHP file or code on the browser there should be must a

web server, so Apache, My SQL or any other server which have concern with PHP is used to

run the PHP code in the browser.



I.T Hub Sargodha 11

6. Web-browsing software: Google chrome, Mozilla Firefox, Internet explorer or any other

relating web browser is used to run the code or file for testing during the development.

7. XAMPP- Database is to much necessary for any software so it must be created for this

purpose XAMPP control panel is used as a localhost.

8. WAMP: - Database is to much necessary for any software so it must be created for this

purpose XAMPP control panel is used as a localhost,

Adobe Dreamweaver: Adobe dreamweaver is an editor which is used for coding the

software.

1.10.1 Front-End /Back-End technologies:

1.10.1.1. Front-End:

i. HTML HTML stands for “Hypertext Markup Language”. It is client side language for developing web pages which contain / or provide a source to show or describe the text, image, graph based information in the document containing headings, subheadings, paragraphs, lists and so on.

ii. JAVASCRIPT Java Script is a language which is used for validation of client information before sending this information to server. Because it is scripting language that’s why it is mostly used for the designing of user/client side web pages. It is a dynamic, weakly typed, prototype based language consisting a lot of functions.

iii. CSS Attraction play an important role in the success of any object. So to create attraction in the web pages CSS is used to make the attractive and user friendly web pages.

1.10.1.2. Back-End:

1. My SQL Data is stored in database so this is necessary to access that data from the database as

well as performing different operations on that data when any operation is needed so for

accessing and performing operations on data a query language is used that is My SQL. My

SQL stands for “structure query language”.

2. PHP PHP stands for “Personal Home Page” is a server side language which is used for backend

processing. This can be embedded in the HTML but not like as HTML. It is used to control

the database because round about PHP supports all databases. It receives the request from

the HTML and provide the results to HTML when the processing has done to show results.

1.10.2. Tools: 1. Adobe Dreamweaver

2. Notepad ++

3. XAMPP, WAMP

4. Google chrome



I.T Hub Sargodha 12

Chapter No 2: First Deliverable

2.1. Project/Product Feasibility Report:

There are many types of feasibilities:

1. Technical

2. Operational

3. Economic

4. Schedule

5. Specification

6. Information

7. Motivational

8. Legal and Ethical

2.1.1. Technical Feasibility: The project deals with pharmacy management system. So it is technically feasible.

2.1.2. Operational Feasibility:

The project will facilitate the pharmacist to maintain the records about the drugs, supplier and customer.

So it is technically feasible. Each operation will be assigned to specific team member according his

spatiality.

2.1.3. Economic Feasibility:

Economic feasibility describes two features. COCOMO is used to define cost estimates of our project.

We define cost estimate with the help of Function Point Analysis.

1. Benefit Estimate

2. Tangible benefit.

Those benefit which focus on reduced cost and are responsible for increase in the revenue.

1. Reduced costs

2. Increased revenue

3. Intangible benefit.

Information quality and job satisfaction are example of intangible benefits. Cost required in our project

depends upon scope of our project. When scope of project increases cost also increases. Cost depends

upon our hardware configuration, software required in our project and team member skills cost.

According to the budget the cost estimation by using COCOMO and function point’s analysis is

feasible.

2.1.4. Schedule Feasibility: Schedule feasibility is given below

1. In successful completion of project time schedule plays an important role.

2. All segments of our project are completed within time.

3. We fulfill our requirements easily



I.T Hub Sargodha 13

2.1.5. Specification Feasibility: All requirements are completed within time. All requirements are clear. We have no

confusion to understand these requirements. New requirements are implemented within time. All

Requirements are the features that our system must have or a constraint that must be accepted for end

users. Specification feasibility also included hardware and software specification required for

completion of our project.

2.1.6. Information Feasibility: All given information is completing reliable and meaningful. No confusion about requirement.

Information quality is very good and true information is given. So our software is feasible. Our project is

feasible in this context because we collected all related information about our project.

2.1.7. Motivational Feasibility: Motivational is also feasible.

2.1.8. Legal & Ethical Feasibility: We have no legal and ethical issue.

2.2. Project/Product Scope:

Following are the jobs to be done by the system:

A system is provided to the admin of pharmacy through which he can easily maintain the all the

records of medicines, he can add new medicines in the stock, delete medicine from the stock, he

can search the stored item through their id or name, generate the sales bill, purchases bill and

daily sales reports, expenses report as well as monthly or yearly reports, manage the accounts.

Customer can easily search the required items and can easily order for the prescribed medicine.

The payments of order will be received at the time of delivery.

2.3. Project/Product Costing:

2.3.1. Project Cost Estimation by Function Point Analysis: Type of

component

Low Average High Total

External Input 0*3=0 3*0=0 3*6=18 18

Internal Output 4*0=0 0*4=0 4*3=12 12

External Inquire 3*5=15 0*5=0 4*0=0 15

Internal logical

Files

0*6=0 1*18=18 0*13=0 18

External Interface

File

0*2=0 2*8=16 0*11=0 16

Total 79

Compute function points (FP), the following relation;

FPest=79*[0.65+0.01*(32)]

FPest=79*[0.65+0.01*32]

FPest=51.69



I.T Hub Sargodha 14

Serial # Complex Technology Term Scale

1 Data Communication 5

2 Distributed data processing 2

3 Performance 4

4 Heavily used configuration 2

5 Transact rate 1

6 Online data entry 2

7 End-user Efficiency 4

8 Online update 3

9 Complex Processing 3

10 Reusability 2

11 Installation ease 4

12 Operational ease 4

13 Multiple Sites 3

14 Facilitate change 3

Sum(Fi) Total complexity adjustment

value

42

2.3.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost Model)

Basic COCOMO

Type Effort Schedule

Organic PM= 2.4 (KLOC)1.05 TD= 2.5(PM)0.38

Semi-Detached PM= 3.0 (KLOC)1.12 TD= 2.5(PM)0.35

Embedded PM= 2.4 (KLOC)1.20=2.4(6)1.05=15.12

TD= 2.5(PM)0.32=2.5(15.12)0.38=14.364

PM= person-month (effort)

KLOC= lines of code, in thousands

TD= number of months estimated for software development (duration)

Intermediate COCOMO

Type Effort Organic PM= 2.4 (KLOC)1.05 x M

Semi-Detached PM= 3.0 (KLOC)1.12 x M

Embedded PM= 2.4 (KLOC)1.20 x M

PM= person-month

KLOC= lines of code, in thousands

M.- reflects 15 predictor variables, called cost drivers

The schedule is determined using the Basic COCOMO schedule equations.

People Required = 15.12/14.364=1.05263



I.T Hub Sargodha 15

2.3.3. Activity Based Costing: Activity Cost

Feasibility Report

13000

Cost Estimation by Function Point Analysis 8000

Cost Estimation by COCOMO Model 7000

Activity based Costing

6000

Critical Path Method

11000

Task Dependency and Duration

13000

Vision Document

5000

Risk List

24000

Allocate Requirement

15000

Design Interface

16000

Modeling

39000

Test and Evaluate

26000

Improve Test

35000

Show Result

18000

Total Cost 236000

2.4. Task Dependency Table:

Task# Task Dependencies

T1 Proposal None

T2 Feasibility Report T1

T3 Cost Estimation T2

T4 System Specification and

Analysis

T2

T5 Domain Model T1, T2

T6 Allocate Requirements None

T7 Application Development T4, T5

T8 User T7

T9 Processing T7, T8

T10 Testing T9

T11 Showing T7, T8,T9,T10



I.T Hub Sargodha 16

2.5. CPM - Critical Path Method:

2.5.1. Specify the Individual Activities: Individual activities are as follow:

1. Planning

2. Analysis

3. Logical design

4. Physical design

5. Testing

6. Implementation

7. Deployment

2.5.2 Determine the Sequence of the Activities: All activities are dependent on each other like, first planning and then go to second activity which is

named as Analysis. And then logical designing after it physical designing, then testing it all and then

deployment.

2.5.3. Draw the Network Diagram:

Figure 2.1

3.5.4. Estimate Activity Completion Time:

Activity Duration ES EF LS LF TS FS

Planning

(A) 5 0 5 0 5 0 0

Analysis

(B) 3 0 3 3 6 3 2

Logical

designing

(C)

8 5 13 5 13 0 0

Physical

designing 7 5 12 6 13 1 1

B C D E F A



I.T Hub Sargodha 17

(D)

Testing

(E) 7 0 7 6 13 6 6

Deploy-

ment (F) 4 13 17 13 17 0 0

2.5. 5. Identify the Critical Path: The critical path is the longest-duration path through the network. The significance of the critical path is

that the activities that lie on it cannot be delayed without delaying the project. Because of its impact on

the entire project, critical path analysis is an important aspect of project planning. Critical path is:

(A,B,C,D,E,F)

2.6. Gantt chart:

ID Task Name Start Finish DurationMay 201 7 Jun 2017 Jul 2017 Aug 2017

5-21 5-28 6-4 6-11 6-18 6-25 7-2 7-9 7-16 7-23 7-30

1 14d08-Jun-1722-May-17Proposal

2 11d23-Jun-1709-Jun-17SRS

3 13d12-Jul-1726-Jun-17Planning and Analysis

4 20d09-Aug-1713-Jul-17First Deliverable

5 20d06-Sep-1710-Aug-17Second Deliverable

6 17d29-Sep-1707-Sep-17User Interface and Design

7 15d20-Oct-1702-Oct-17Testing

8 8d01-Nov-1723-Oct-17Deployment

9 7d10-Nov-1702-Nov-17Implementation

8-6 8-13 8-20

Figure 2.2

2.7. Introduction to Team member and their skill set:

Name Roll No Skill

Muhammad Shakir 15MIT4417 • HTML, CSS,PHP,

• SQL, JAVA SCRIPT

Muhammad Nabeel 15MIT4412 • HTML, CSS,PHP,

• SQL



I.T Hub Sargodha 18

2.8. Task and Member Assignment Table:

Indication of amount of work of each member is expressed in terms of Task and its allocation by the

following given table.

Task# Task Dependencies

T1 Proposal None

T2 Feasibility Report T1

T3 Cost Estimation T2

T4 System Specification and

Analysis

T2

T5 Domain Model T1,T2

T6 Allocate Requirements None

T7 Application Development T4.T5

T8 User T7

T9 Processing T7,T8

T10 Testing T9

T11 Showing T7,T8,T9,T10

2.8.1. Allocation of People to Activities:

T1 M.Shakir

T2 M. Nabeel

T3 M.Shakir

T4 M. Nabeel

T5 M.Shakir

T6 M. Nabeel

T7 M.Shakir

T8 M. Nabeel

T9 M.Shakir

T10 M. Nabeel

T11 M.Shakir

2.9. Tools and Technology with reasoning: There are following tools and technologies that are used in our system:

Tools: 1. MS Visio Professional:

We used Visio for ERD and Sequence diagram.

2. MS Project Professional;

We used MS Project for Gantt chart.

3. MS word

For project documentation

4. Not pad++ not pad++ is an editor for coding.

5. Web Server - Apache web server or other who concern with PHP codes or scripts. It is basically

used to run the PHP code or file on browser.

6. Web-browsing software -Mozilla Firefox, Internet Explorer or other

7. XAMPP- XAMPP control panel is used as a localhost.



I.T Hub Sargodha 19

2.9.1. Technologies: PHP – It is used for back end tools for the system.

MYSQL - Used to maintain the database. So, you can call it to back-end of system.

HTML & CSS- Both are used for font end because they sport to produce good front end.

2.10. Vision Document:

2.10.1. Purpose:

This Software Requirements Specification provides a complete description of all the functions

and specifications ONLINE PHARMACY MANAGEMENT SYSTEM. With the help of this

software because it is an online pharmacy management system the admin of pharmacy can easily

handle all records about the medicines. Customer can easily view required items and can order

online. So all the processes of medicines sales, purchase and maintenance done very easily

through this system.

2.10.2. Scope:

The scope of any project much matter in its success. A system is provided to the admin of pharmacy through which he can easily maintain the all the records of medicines, he can add

new medicines in the stock, delete medicine from the stock, he can search the stored item through their name or batch number. The system will generate alerts about the expiry of

items 3 month before their expiry date and also will not allow to sale the expired items, automatically will remove those items from the stock which are expired. The system will also generate alerts about the items whose stock has reached to end. The system also will

keep the records about the manufacturer companies of medicines and also their supplier. The system will keep complete information about the customer his/her name, email

address/mobile number, gender, country, city and postal address. The system will first register the new customer before placing an order for the registration the customer will have

to provide complete information about him/her and after registration and authentication he will be able to place an order for the sake of purchasing his/her required items from our website. The client will select the category of medicines and the will search the required

medicine by its name or batch no. The system will also keep the complete information about the payments of orders weather

these payments are related to customer or supplier of the medicine, but there is not online payment method, the payments from the customer will receive at the time of delivery of

order.

2.10.3. Definition:

“ONLINE PHARMACY MANAGEMENT SYSTEM” can handle data of medicine

items and customers. This will be most useful for the pharmacist to manage the records about the

pharmacy as well as for the customers to purchase their required medicine easily by sitting in

their home.

2.11. Risk List:



I.T Hub Sargodha 20

1. It is assumed that all the users of our system have the knowledge of computer.

2. Because our system is web based so it is assumed that the all the user have internet

connection.

3. Customer can refuse or send back a delivered ordered due to not required item’s

company.

4. Willingness, cooperation, and support of all executive level management would be

required from requirement engineering to deployment phase. Lack of Willingness,

cooperation, and support of all executive level management can lead to an unfinished

system.

5. IT infrastructure with proper hardware would be required for the effective and successful

deployment and running of the system.

6. Time, technical expertise & budget constrains may introduce serious obstacles towards

the completion of the project.

7. The accuracy can not be 100%.

2.12. Product Features / Product Decomposition:

Our product features are as follows:

i. Online Pharmacy Management System.

ii. Easy to use.

iii. Online orders.

iv. Automatic special discount rate on purchased items.



I.T Hub Sargodha 21

Chapter 3: Second Deliverable for Object Oriented Approach

3.1. Existing System:

Existing pharmacy system of Abdullah medical complex is totally manual based all the work is

done on paper manually. So much of the time is wasted, a lot of effort is consumed to maintain

the records about the medicine, customers and supplier, all the reports are prepared manually on

the paper, therefore there are lot of chances of mistakes, any entry may be missed or may be a

double entry of a single unit and so on Therefore it was necessary to develop a suitable

computerized system through which the owner of pharmacy can easily handle all the activities of

pharmacy and the customer can feel easy to purchase an medicine from the pharmacy store.

3.2 Scope of the System:

The scope of any project much matter in its success. A system is provided to the admin of

pharmacy through which he can easily maintain the all the records of medicines, he can add new medicines in the stock, delete medicine from the stock, he can search the stored item

through their name or batch number. The system will generate alerts about the expiry of items 3 month before their expiry date and also will not allow to sale the expired items,

automatically will remove those items from the stock which are expired. The system will also generate alerts about the items whose stock has reached to end. The system also will keep the records about the manufacturer companies of medicines and also their supplier.

The system will keep complete information about the customer his/her name, email address/mobile number, gender, country, city and postal address. The system will first

register the new customer before placing an order for the registration the customer will have to provide complete information about him/her and after registration and authentication he

will be able to place an order for the sake of purchasing his/her required items from our website. The client will select the category of medicines and the will search the required medicine by its name or batch no.

The system will also keep the complete information about the payments of orders weather these payments are related to customer or supplier of the medicine, but there is not online

payment method, the payments from the customer will receive at the time of delivery of order.

3.3 Summary of Requirements: (Initial requirements):

This Software Requirements Specification provides a complete description of all the functions and

specifications ONLINE PHARMACY MANAGEMENT SYSTEM. With the help of this software people

can easily purchase their required medicine from the online pharmacy store. So all the processes of

medicine purchasing are done very efficiently.

3.4 Identify External Entities:

The main external entities are following:

i. Patient



I.T Hub Sargodha 22

ii. Admin

iii. Supplier

3.5 Capture “shall” Statement:

Para# Initial Requirements

1.0 Shall system be a website.

1.0 Shall system give user interface and registration and log in option too.

1.0 Shall system have a form to enter data for user registration.

1.0 Shall system have a database.

1.0 Shall system save the data entered by the user.

1.0 Shall system allow user to place an order

1.0 Shall system show notification of medicine items.

3.6 Allocate Requirements:

Para# Initial Requirements Use case name

1.0 System shall be a website. Pharmacy management system

1.0 System shall give user interface and log in option too. Pharmacy management system

1.0 System shall have a form to enter data for user. Pharmacy management system

1.0 System shall have a database. Pharmacy management system

1.0 System shall save the data entered by the user. Pharmacy management system

1.0 System shall allow user to place an order Pharmacy management system

1.0 System shall show notification of medicine items. Pharmacy management system

3.7 Priorities Requirements:

Para# Rank Initial

Requirements

Use case ID Use case Name

1.0 Highest Will system be a

website.

Uc.1 Pharmacy

management

system

1.0 Highest Will system give

user interface and

log in option too.

Uc.1 Pharmacy

management

system

1.0 Highest Will system have

a form to enter

data for user.

Uc.1 Pharmacy

management

system

1.0 Highest Will system have

a database.

Uc.1 Pharmacy

management

system

1.0 Highest Will system save

the data entered

by the user.

Uc.1 Pharmacy

management

system

1.0 Highest Will system allow

user to place an

order.

Uc.1 Pharmacy

Management

System

1.0 Highest Will system show

notification of

medicine items.

Uc.1 Pharmacy

management

system



I.T Hub Sargodha 23

3.8 Requirements Traceability Matrix:

Sr.

No

Para

no

System specification test Build Use case name

1 1.0 System will be a website. B1 Pharmacy management system

2 1.0 System will give user interface and

log in option too.

B2 Pharmacy management system

3 1.0 System will have a form to enter

data for user.


4 1.0 System will have a database. B3 Pharmacy management system

5 1.0 System will save the data entered

by the user.


6 1.0 System will allow user to place an

order.


7 1.0 System will show notification of

medicine.




I.T Hub Sargodha 24

3.9 High Level Use-case Diagrams: Pharmacy Management System:

admin

login

manage medicine

customer

select medicine

view medicines

registeration

order

Figure 3.1



I.T Hub Sargodha 25

3.10 Analysis level use-case Diagram: Pharmacy Management System:

adminlogin

manage medicine

update

add new stock

delete

customer

select medicine

view medicines

registeration

order

search

view

cancel order

customize order

<<extend>>

<<extend>>

<<extend>>

<<extend>>

<<extend>>

<<extend>>

<<extend>>

<<include>>

username

<<include>>password

Figure 3.2



I.T Hub Sargodha 26

3.11. Use case Description:

3.11.1. User Registration:

Name Description

Use case Name Registration

ID 1

Primary actor Admin

Secondary actor null

Pre-condition Admin must be visit and access home page

Assumption It is assuming that admin is in try to access

homepage

Post condition Successful registered

Basic flow 1.Access homepage

2.request for registration

3.give user personal details

4.successfully registered

Alternate flow 1.Email is not verified.

2.again request for registration

3.11.2. Log in:

Name Description

Use case Name Login

ID 2

Primary actor Admin

Secondary actor null

Pre-condition Admin must be get registration

Assumption It is assuming that admin is registered

Post condition Successfully Log in



I.T Hub Sargodha 27

Basic flow 1.Access homepage

2.request for login

3.give user name and password

4.successfully login

Alternate flow 1.User name and password incorrect

2.again request for login

3.11.3. Manage medicine:

Name Description

Use case Name Manage medicine

ID 3

Primary actor Admin

Secondary actor Null

Pre-condition admin must be successfully log in

Assumption It is assuming that admin is log in

Post condition Successfully Manage products

Basic flow 1. Admin log in

2. Select manage products option from menu

3.add medicine items in database.

4.delete medicine item from database

5. search medicine items.

6.view medicine items.

7.update items.

Alternate flow 1.Not a authorized admin



I.T Hub Sargodha 28

3.11.4. Order:

Name Description

Use case Name Order

ID 6

Primary actor Admin

Secondary actor Customer

Pre-condition Customer log in and place order

Assumption It is assuming that a patient or customer visit

the website and view medicine items and

place an order against required items

Post condition Order is placed successfully

Basic flow 1. customer visit the website.

2. search for required items

3.view items

4. place an order

Alternate flow 1.Required item is not available in the stock.



I.T Hub Sargodha 29

Chapter 4: Third Deliverable for Object Oriented Approach

4.1 Artifacts which are included in this Chapter:

1. Domain Model

2. System Sequence Diagram

3. Collaboration Diagram

4. Design Class Diagram

5. Entity Relationship Diagram

6. State Transition Diagram

4.2 Domain Model:

customer order

Admin

Items

Supplier

Figure 4.1



I.T Hub Sargodha 30

4.3. Customer’s Sequence Diagram of Pharmacy Management System:

Customer System Database

request for registeration

enter information

store information

information stored in DB

search item check availability

accknowledgement

place order

display medicane

insert order record

order confirmedorder confirmed

log in request

enter information

sucessfully registered

verify detail

accknowledgementaccknowledgement

log out

log out successfully

Figure 4.2



I.T Hub Sargodha 31

4.4 Admin Sequence Diagram:

Admin System Database

request for registeration

enter information

Store information

information store in DB

sucessfully Registered

log in request

enter name and password

verify name and password

acknowledgementacknowledgement

request to add medicine item

store item in DB


request to delete medicine item

delete item from DB


search item

check availability


request to log out

loged out sucessfully

Figure 4.3



I.T Hub Sargodha 32

4.5 System Sequence Diagram for Pharmacy Management System:

Admin Customer System Database

request for registration

enter information store info

info stored in DBsucessfully registered

log in request

enter name and password

verify name password

acknowledgmentAcknowledgement

request to add medicine

Store in DB


request to delete medicine

delete from DB


request to search medicine

check availability


request to log out

successfully log out

request for registration

enter information

store info

info stored in DBsucessfully registered

request for log in

enter name and passverify name and pass


search medicinecheck availability

acknowledgementdisplay item

place order store order record

confirm orderconfirm order

log out

sucessfully log out

Figure4.4



I.T Hub Sargodha 33

4.6 Collaboration Diagram:

customer

SystemAdmin

Database

Registration

Sign up

• Registration• Log in• Search Medicine • Select Medicine • Place order• Log out

DetailsRetrieve Data

Figure 4.5



I.T Hub Sargodha 34

4.7 Design Class Diagram:

admin

medicine item

Supplier

name: String

log in()

id: Intpassword: String

searching items()log out()

customer

C_name: String

ordering()

C_Id: Int

C_city: String

payment()

Brand-name:String

expiry date: varchargeneric name: Stirng

manufacturing date: varchar

S_name :String

recovery()

S_ID: varchar

S_mobile#: varchar

supply()

mobile no: Varchar

log in()

log out()searching ()viewing()

saling()purchasing()

dose: varchar

unit price:Int

Batch no: Intcompany name:String

S_address:varchar

S_company: varchar

Order

Order _ID: IntOrder date: varchar

ordering()

Bill

Bill_id: Int

payment()

Bill date: varchar

registered by

prepairpay

-memberName

Figure 4.6



I.T Hub Sargodha 35

4.8 Entity Relationship Diagram:

Admin

payment

Customer

Supplier

Item

User name

Password

C-id

Order no

C-Name

C-Id

mobile#

C-address

I-name

batch no

manufacturing date

Expiry date

Supplier_ID

Supplier city

Supplier name

order

amount

O_no

order date

Supplier company

company

purchase date

sale date

S-mobile#

Figure 4.7



I.T Hub Sargodha 36

4.9 State Chart Diagram for Pharmacy Management System:

registeration

Admin or user registration

Log in

verify name and password

Title

Invalid ,try again

valid

Admin

Customervalid

Search medicine

check availabilityavailable

display medicine

place order

Order is placed

order confirmation

payment

Add medicineAdd item in DB

store in DBdelete

medicine

delete from DB

search medicine

check availability

available

view medicine

Not available

Log out

Not available

Figure 4.8



I.T Hub Sargodha 37

Chapter 5: 4th Deliverable (User Interface Design)

5.1. Site Maps: Login

Admin

View Customer

Orders

View

Customer

Customer

Manage Stock

Home

Registered

Add Stock

Update Stock

Delete Stock

View Stock

Confirme

Order

View Comments

About us

Logout

Contact Us

Search

medicine

Add to cart

View Invoice

Print Invoice

Logout

Delete

Activate//Deactivate

Figure 5.1: Site Maps



I.T Hub Sargodha 38

5.2. Story boards:

5.2.1. Administrator and Customer login:

Figure 1.2 Administrator and Customer Log in:

In this interface the customer and administrator can be login. The administrator should login to manage

stock, to update, search, delete and view any data which store in the database. The customer will login to

visit the website and to place an order.



I.T Hub Sargodha 39

5.2.2. Customer registration:

Figure 5.3Customer registration:

In this interface the customer will register himself/herself. If all the registration requirements are fulfilled

then the customer will be registered.

5.2.3. Add new item to the stock:

Figure 5.4: Add new item to the Stock



I.T Hub Sargodha 40

This interface is used by the admin for the purpose of adding new item in the stock.

5.2.4. Update Stock.

Figure 5.5: Update item in the stock

In this interface the admin can update the stock in the database.

5.2.5. Order Placement:

Figure 5.6: Search medicine and add to cart.

In this interface the customer will search his/her required medicine item and will click on the add to cart

button.



I.T Hub Sargodha 41

5.2.6. Order Detail on the Admin page:

Figure 5.7 Order detail on the admin side:

This interface is showing the order details of a customer who have placed any order and the admin will

confirm or remove the order.

5.3. Navigational maps:

5.3.1. View Stock:

Figure 5.8: View Stock

In this interface administrator can also view all the stock information.



I.T Hub Sargodha 42

5.3.2. View Comments of Customers:

Figure 5.9:View comments:

In this interface administrator can see the table of comments of the visitors of the site.

5.3.3. View Customers inforamtion:

Figure 5.10: Customers Details:

In this interface administrator can also view all the customers who have been registered.

5.3.4. View Invoice:

Figure 5.11: View invoice details:



I.T Hub Sargodha 43

In this interface the customer can view the details of invoice and also can print the invoice.

5.3.5: Contact Us Page:

Figure 5.12: contact us page:

This is the contact us page through which the visitor can send a message to the admin of the

website.



I.T Hub Sargodha 44

Chapter 6: Fifth Deliverable Software Test

Document Information:

Category: Information:

Customer Cs & IT Department UOS

Project Online Pharmacy Management System

Document Test Plan

Document Version 1.0

Identifier

Status Draft

Author(s) Muhammad Shakir, Muhammad Nabeel

Approver(s) PM

Issue Date March 08 2018

Document Location

Distribution 1. Advisor

2. PM

3. Project Office

Definition of Terms, Acronyms and Abbreviations:

This section provides the definitions of all terms, acronyms, and abbreviations required to interpret the

terms used in the document properly.

Term: Description:

TL Team Leader

TP Test Plan

TM Team Member

PM Project Manager

PS Project Supervisor



I.T Hub Sargodha 45

6.1 Introduction:

This document contains the information necessary for testing, and to verify that all the functional

requirements of “Online Pharmacy Management System” are working fine without any error.

6.2 Purpose of Testing:

This portion is intended to deliver a high-level overview of “Online Pharmacy Management System”

Software Developers, System Engineers, and Testers (with a basic knowledge of software, what it is, how

it is generally tested) will benefit from this document.

6.3 Project Overview:

We are providing a platform for our customers from which they can easily place their orders online and

can easily receive their required medicines at their homes as well as on the special discount rate.

6.4 Scope of Testing:

All functional requirements should be tested in all possible ways. All possible combinations of inputs

should be given to the application to check the reliability, correctness and consistency of the system.

6.5 Test Plan Strategy:

Following tests are to be performed for testing. There should be no ambiguity about any test methodology

or other testing relevant material.

6.5.1 Unit Testing: Definition: All the functions should be independently checked first.

Participants: Team

Methodology: Test cases should be tested along with the development.

6.5.2 Integration Testing: Definition: Test the system by integrating the all modules.

Participants: Team

Methodology: After unit testing integration testing should be done properly to identify bug if any.

6.5.3 System Testing: Definition: The overall system testing.

Participants: Team, Project Manager, Supervisor.

Methodology: The overall system should be tested before the product is delivered. This is done by using

all the hardware’s and software’s involved or interacted with the system.



I.T Hub Sargodha 46

6.6 Test Environment:

The system on which the project is tested must have

• XAMPP/WAMP Server

• Notepad++ /Adobe Dreamweaver

6.7 Schedule:

Testing Activities Begin End

Designing Test Cases 15 January 2018 20 January 2018

Executing Test Cases 21 January 2108 24 January 2018

Unit testing 25 January 2018 29 January 2018

Integration testing 30 January 2018 08 February 2018

System testing 10 February 2018 18 February 2018

6.8 Control Activities:

In Case of any query or ambiguity a review meeting is called by the manager. The developers will

participate in it to overcome the issues.

6.9 Functions to be tested:

• Login

• Sign Up

• All functions of Users

• All functions of Administrator

• Update his/her profile

• Forget/ Recover Password

• Logout

6.10 Functions not to be tested:

There asre no such tools or functions which do not need testing in this project.

6.11 Test Cases:

6.11.1 Test Case 01:

Test Case ID: T01 Application Development

Team

Muhammad Shakir

Muhammad Nabeel

Test Case Version: T01 Reviewed By: Team Leader



I.T Hub Sargodha 47

Test Date: 15 January

2018

Use Case Reference: Use Case Number 01

Revision History: NO

Objective: Customer sign up or create new account.

Product: Refer to show all customer page.

Environment: Necessary and desired properties of the test environment. (hardware, software)

Assumptions: User is not already registered.

Pre-Requisite: Internet connection is required.

Step # Execution description: Procedure result:

1. Click on Sign Up. User will open sign up form.

2. After entering name, username, email, id,

password and other details click on register.

A new account is created and User is

redirected to login on his email to

active his/her account.

Comments:

No error was found during testing. All the team members are satisfied with the results.

Passed Failed Not Executed



Team:

Muhammad Shakir

Muhammad Nabeel



2018



Objective: Customer shell register his/her to log in.

Product: Refer to show all customer login page.



I.T Hub Sargodha 48


Assumptions: User is already registered.


Step # Execution description: Procedure result:

1. Click on Login. User will open a login from.

2. After entering id and password click on login. User will have redirected to his profile

page.

Comments:

No error was found during testing. All the team members are satisfied with the results




Team:

Muhammad Shakir

Muhammad Nabeel



2018

Use Case Reference: Use case 06


Objective: Customer logout his/her account.

Product: Refer to show all customer page.


Assumptions: User is already login.


Step # Execution description: Procedure Result:

1. Click on logout. User will successfully logout from



I.T Hub Sargodha 49

his/her account.

Comments:





Team:

Muhammad Shakir

Muhammad Nabeel

Test Case Version: T04 Reviewed By: Team Lead


2018



Objective: Customer can search and place order for medicine.

Product: Refer to show all medicine page.


Assumptions: Customer login and search medicine



1. Click on manage stock System will show search and place order

for medicine page

2. After editing click on update. Changes will be saved in medicine page

and user again directed to his home page

Comments:





I.T Hub Sargodha 50



Team:

Muhammad Shakir

Muhammad Shakir



2018



Objective: Customer can search products.

Product: Refer to show all products page.


Assumptions: Customer can easily search out the medicine.



1. Click in search bar. User will enter the name of medicine will

search.

2. After typing the name, click on search button

or press enter.

After entering the name, the medicine will

search all matching products.



Team:

Muhammad Shakir

Muhammad Nabeel


Test Date: 5 February Use Case Reference: Use Case Number 05



I.T Hub Sargodha 51

2018


Objective: Customer can give order for medicine.

Product: Refer to show all checkout and shipment pages.


Assumptions: Customer select the medicine to purchase.



1. Click on button add to cart. Cart will show all the medicine that are

added into cart to buy and their price and

total price.

2. Click on checkout for further proceed and give

shipment address and conform his details.

Order will placed successfully.

Comments:



Documents

Department of Computer Science & Information Technology ... · Online Pharmacy Management System Date: 15 Oct,2017 I.T Hub Sargodha 1 Department of Computer Science & Information