Pharmacy Management System Thesis | Chapter 3 – Methodology

This chapter, I discuss the Pharmacy Management System Thesis | Chapter 3 – Methodology design, System Development Life Cycle (SDLC), Extreme Programming Methodology, Use Case Model, Activity Diagram, Context Diagram, Data Flow Diagram and Entity Relationship Diagram.

Here’s the Outline of Pharmacy Management System Thesis | Chapter 3- Methodology

METHODOLOGY

  This Pharmacy Management System Thesis | Chapter 3 – Methodology presents the system design of the proponent’s system.

SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The Software Development Life Cycle (SDLC) is a framework defining tasks performed at each step in the software development process. It is a structure followed by a development team with in the software organization. It consists of a detailed plan describing how to develop, maintain and replace the specific software. The life cycle defines the methodology for improving the quality of the software and over all development process. The proponents will use the Rational Unified Process Methodology as a guide of processing the system flow.

EXTREME PROGRAMMING METHODOLOGY

Figure 1 Shows Extreme Programming the Diagram used by the proponents as their model for the system. It shows how Extreme Programming’s rules work together. A preference for effective action based on other principles so that the results aren’t harmful to the team. Extreme Programming is a software development framework that aims to produce higher quality software, and higher quality of life for the development team. XP stresses the importance of the appropriate kind of communication that is face to face discussion with the aid of a white board or other drawing mechanism. The diagram shows the team sport that relies on communication to transfer knowledge from one team member to everyone else on the team. The advantage of XP model from the other methodologies avoid waste and do only absolutely necessary things such as keep the design of the system as simple as possible so that it is easier to maintain, support, and revise.

Release Plan

In this phase, the proponents used Release Plan meeting to create a release plan, which lays out the overall project for DLT Pharmacy. They will commit themselves to the functionality that will be included and the date of the next release.

Iteration Plan

The proponents plans the activities and tasks of the developers and decides what content goes into specific iterations. The tasks will be assigned to the proponents and the time it takes to complete will be estimated. The proponents plan by selecting Stories from the team backlog and committing to execute a set of them in the upcoming iteration. The proponent’s backlog has been seeded and partially planned during the Program Increment (PI) Planning meeting. In addition, the Proponent have feedback not only from their prior iterations but from the System Demo and other proponents. That, and the natural course of changing fact patterns, provides the broader context for iteration planning.

Acceptance Test

The Proponent use acceptance tests as a complement to specification documents containing uses cases or more narrative text. Proponents write as many automated tests as much as possible, and if all of them prove to be successful, then the coding is regarded to be complete. Besides, every piece of code which is written is tested thoroughly before going ahead with the next feature. Acceptance testing is done to ascertain that the programmers understand the requirements and in turn can satisfy the actual requirements of DLT Pharmacy.

Stand Up Meeting

The Proponent report at least three things; what was accomplished yesterday, what will be attempted today, and what problems are causing delays.

Pair Negotiation

The Proponent combine two sets of skills for design and implementation to yield the best solution.

Unit Test

The Proponent take a bit of time to test virtually every line of code when it is written, what is the probability of missing a defect at that point. Proponent do unit testing, they tend to find defects much earlier, resulting in a more cost effective way to eliminate defects.

Pair Programming

The Two Proponent working together at a single computer. Effectively get a continuous code review and quicker response to nagging problems that may stop one person dead in their tracks. Proponents used pair programming to improve quality and does not actually take twice as long because they are able to work through problems quicker and they stay more focused on the task at hand, thereby creating less code to accomplish the same thing.

Code

Each pair of proponent writes their code and then integrates it together. The development team has a collective code ownership. Each proponent can change or refactor any part of the code. It ensures that no one developer becomes a bottleneck for changes and it allows proponents to reuse any functionality that might be required by multiple user stories.

Use Case Model

Figure 2 shows the use case of DLT Pharmacy-Payroll Management System and the task of every actors of the system Buy Product

Figure 3 This use case diagram is more like to purchased products. An interaction between customer and sales clerk.

Table 2: Buy Product Use Case Description of DLT Pharmacy-Payroll Management System

  Figure 4 This use case diagram includes systems that manage sales order entry processed by the sales clerk and forwarded to cashier who applies the payment to the account/invoice.

Table 3: Process Transaction Use Case Description of DLT Pharmacy-Payroll Management System.

Figure 5 This use case diagram performs by the manager towards the system which communicates information which has been compiled as a result of transactions processed.       

Table 4: Generate Report Use Case Description of DLT Pharmacy-Payroll Management System.

Figure 6 This use case diagram performs by Manager which manages the employee detail, record daily time, generate employee salary and salary pay.

Table 5: Manage Payroll Use Case Description of DLT Pharmacy-Payroll Management System.

Activity Diagram

Customer Purchasing Product

Figure 7 Activity for Customer Purchasing product show the steps of customer buying process that includes the recognition of needs and wants, information search, evaluation of choices and purchases.

Cashier Generate Report

The Figure 8 Activity for Cashier generate report shows the report generation process after the report has been submitted to run.

CONTEXT DIAGRAM

The context diagram of DLT Pharmacy-Payroll Management System represented below shows the flow of the system throughout the system process. It show what information could be input, where the data goes, and how it is stored .

The Figure 9 DLT Pharmacy-Payroll Management System Context Diagram

Show the product purchased, process transaction, manage inventory and manage

payroll.

DATA FLOW DIAGRAM

             Data Flow Diagram of proposed solution shows all the concept and flows of each entity that shows all the process in proposed system solution showing this flow may help to the reader for identity which the process begins. It often used as a preliminary step to create an overview of pharmacy without going into great detail, which can later be elaborated. It normally consist of overall application dataflow and processes of the pharmacy process. It contains all of the user flow and their entities such as all the flows of pharmacy

The Figure 10 Level 1 Data Flow Diagram of Pharmacy-Payroll Management System shows customer the order and payment received by the sales clerk.

The Figure 11 Level 1 Data Flow Diagram of Pharmacy-Payroll Management System shows the product has been processed.

The Figure 12 Level 1 Data Flow Diagram of Pharmacy-Payroll Management System Shows the order and inventory of product in the pharmacy

The Figure 13 Payroll Data Flow Diagram of Pharmacy-Payroll Management

System shows the time worked calculated payroll and the pay of employee.

ENTITY RELATIONSHIP DIAGRAM

     The Entity Relationship Diagram of Pharmacy-Payroll Management System shows the relationship of entity sets stored in a database. It indicates the logical structures of each database.

Figure 14 Shows the relationship of entity sets stored in a database of DLT Pharmacy-Payroll Management System.

Data Dictionaries

These tables below provide the entire database tables details such as Field Name, Descriptions, data types, character lengths.

Table 6: Table Customer

Table 6 This table shows the attributes of entity of Customer

Table 7: Table User       

Table 7 This table shows the attributes of entity of User

Table 8: Table Supplier

Table 8 This table shows the attributes of entity of Supplier

Table 9: Table Items

Table 9 This table shows the attributes of entity of Items

Table 10: Table Category

Table 10 This table shows the attributes of entity of Category

Table 11: Table Auto Number

Table 11 This table shows the attributes of entity of Auto Number

Table 12: Table Generic

Table 12 This table shows the attributes of entity of Generic

Table 13: Table Shelves

Table 13 This table shows the attributes of entity of Shelves

Table 14: Table Transaction

Table 14 This table shows the attributes of entity of Transaction

Table 15: Table Employee

Table 14 This table shows the attributes of entity of Employee

Table 16: Table Salary

Table 16 This table shows the attributes of entity of Salary

Table 17: Table Payroll

Table 17 This table shows the attributes of entity of Payroll

Table 18: Table Deduction

Table 18 This table shows the attributes of entity of Deduction

Architectural Diagram

Architectural diagram of DLT Pharmacy-Payroll Management System. The manager will be the admin that will manage to add staff and products, update and delete records for the database after adding the staff. Cashier will manage his unit for the sales; he will record all the sales report and store it in the database to generate report to the manager for the printing.

Screen Design

Main Dashboard

The figure 16 Main Dashboard shows the main interface design of the system.

 List of Category

The figure 17 List of Category shows the interface design which display the category name of the product.

List of Generic

The figure 18 List of Generic shows the interface design which display the Generic name of the product.

List of shelves

The figure 19 List of Shelves shows the interface design which displays the shelves name of the product.

List of User

The figure 20 List of User shows the interface design which display the employee name.

List of Supplier

The figure 21 List of Supplier shows the interface design which display the name and details of the supplier.

List of Item

The figure 22 List of Item shows the interface design which displays the name of the product.

List of Customer

The figure 23 List of Customer shows the interface design which display the name and details of the customer.

List of Transaction

The figure 24 List of Transaction shows the interface design which display details of the transaction.

Point of Sale

The figure 25 Point of sale shows the interface design which display the cashiering and details of every transaction

System Requirements

Developing “DLT Pharmacy-Payroll Management System ” is not an easy task. It all started from the requirement gathering and passes through so many other stages before it will be implemented.

 Based on the benefits of this system and tremendous value it will add to customer-user satisfaction, the below recommendation will be considered.

It is recommended that the new system should be used with the necessary specifications of the system requirements and provision for an uninterrupted power supply should be made available throughout the hours of operation of the pharmacy to avoid power outage.

There should also be basic computer knowledge for the users of the developed system.

The following is the list of hardware and software that was used in the development and the recommended software and hardware for deployment for the system to run smoothly. (Pharmacy Management System Thesis | Chapter 3 – Methodology)

Hardware Requirements

Recommended Hardware Requirement for Development:

Processor: Intel® Celeron® CPU N3060 @ 1.60GHz 1.60GHz

RAM: 4GB DDR4 2133Mhz

OS: Windows 10

System Type: 64 bit operating system , x64-based processor

Mouse 2 button with scroll

Laptop LCD 14”

Keyboard

Software Requirements

Software Requirement for Development:

XAMPP v3.2.2 (32/64-bit)

VB. NET 201

Download the Full Source Code of this project

Here’s the complete Source code Pharmacy management System project

Related Article

• Pharmacy Management System Thesis Chapter 1
• Pharmacy Management System Thesis Chapter 2

Inquiries

if you have any questions or suggestions about Pharmacy Management System Thesis | Chapter 3 – Methodology, please let’s me know by dropping your comment below.