Sales and Inventory System Thesis Documentation

UPLOADED BY

Kim Ivory Santiago

Download with Google Download with Facebook

or download with email

Sales and Inventory System Thesis Documentation

DOWNLOAD

•
Maintain supplier information in the cloud
P&armac"utica- Manag"m"nt #'st"m)"atur"s
•
The system covers typical operations like receiving medication from suppliers, processi
n g departments@ medication re%uests, distributing medication to departments, returning e#piredmed
ication to suppliers.
•
The system also maintains an inventory book on stock in<out details and provides
m o n t h l y inventory report and statistics on medication consumption.
•
$harmacy )ystem keeps track of patient, doctor, drug and prescription records. !t will printreceipts of
indent, invoice, stock details, bills and others.
P&arniatra3 4P&armac' In%ormation / Manag"m"nt #'st"m5

)"atur"s
•
This system is used to seamlessly combine five distinct functions that are v ital to a pharmacy - prescription, dispensing,
billing, purchasing and inventory management.
•
This system contains item entry, purchase order and item maintenance for easy mark-up on theitems.
•
9very sales transaction is automatically deducted from the stock %uantity for automatic inventorygenerated report.
C&a$t"r 6
M"t&odo-og'
A.E3isting T&"ori"s and Id"as Associat"d
This chapter presents theories associated in obtaining necessary data, design and development of the system. !t
involves discussion on the proposed conceptual framework diagram, the methods
anda p p r o a c h e s u s e d t h e t o o l s a n d m o d e l s , b u d g e t r e % u i r e m e n t s a n d t h e s c h e d
u l e s i n v o l v i n g t h e development of the system.
Page | 12

B.Cont"3t Diagram o% t&" Pro$os"d #'st"m)igur" 1. Cont"3t Diagram o% t&" Pro$os"d #'st"m
&igure 2 shows the conte#t diagram depicting the system. This type of diagram usually pictures
thesystem at the center, with no details of its interior structure, surrounded by all its interacting
systems,environment and activities. The 'iagram e#plains the main !nput, $rocess and (utput of the
)ystemwhere the Admin from the !nput area in the left side decide to process his<her desired outcome. After it process
in the )ystem which illustrates at the center of this diagram, it barely results with an output of transaction consist of
adding items. *hen the transaction process finished, the recorded files will beseen in the inventory that
process again in the system that later develops a report back to the Admin.
C.M"t&ods and A$$roac&"s
!n the conduct of the system analysis and design, the proponents will use the agile
softwared e v e l o p m e n t m e t h o d . A g i l e s o f t w a r e d e v e l o p m e n t i s a g r o u p o f

software development methods inw h i c h s o l u t i o n s e v o l v e t h r o u g h c o l l a b o r a t i o n b e t w e e n s e l f -

o r g a n i z i n g , cross-
functional teams. !t promotes adaptive planning, evolutionary development, early delivery, continuous improvement, a
ndencourages rapid and fle#ible response to change. &urther, the use of this method brings clarity in
thesoftware development. *orking software is delivered fre%uently :weeks rather than months;. 5egular adaptation to
changing circumstances even late changes in re%uirements are welcomed in this methodwe used.
D.Too-s and Mod"-s
The proponent of this study uses the following tools and methods in the conduct of
s y s t e m analysis, as follows6E T h e
Environm"nta- Mod"-
was used to describe or show the limitations and the
interaction between our proposed system and the environment which it react. !t focuses on the events that occur outsi
de the environment and those that need a response from the system. !n doing so thus
eliminatesirrelevant stimuli that occur outside the system. !t is worthy to note the environment model is the most
Page | 13
P&armacia
7os"%a8s
Drug#tor"
Inv"ntor'#'st"mA d
m i n
T r a
n s a
c t i
o n
Inv"ntor'R"$ort
important part of making complete model, for it give a bird s eye view of the ma"or steps and processes,and enable the
user to visualize relationships, the important element and movement that e#ist in thesystem and to show
the system react with the environmentF.(n the aspect of system development, the following tools were used6
A-gorit&m.
An algorithm shows the proper se%uence of steps that should be followed in order toobtain the re%uired output.
)-o, C&art
. !t is the graphical representation of the process that involved in the system. !t has predefined graphics
that describes the process the data involved to achieved desired output.
isua- Basic 9.: D"%inition.
Nisual +asic C.G was the final edition of the software. This versionimproved the productivity an ability for web
applications, which led to the development of Nisual +asic. /9T.
Nisual +asic C.G cannot be developed on *indows Nista, *indows D or *indows )erver 4GGH.Microsoft ceased mainstream
support in 4GG?, and all support in 4GGH.
Microso%t Acc"ss +::;
, a l s o k n o w n a s M i c r o s o f t ( f f i c e A c c e s s , i s a d a t a b a s e m a n a g e m e n t system from Microsoft that
combines the relational Microsoft et 'atabase 9ngine with a graphical user interface and software-development tools, !t
is a member of the Microsoft suite of application, include inthe $rofessional and 0igher editions or sold separately.
E.Budg"t R"<uir"m"nts
The following is the hardware and software specification necessary in the implementation of thesystem and necessary in
the formulation of the essential budgetary re%uirements, as follows6
#'st"m R"<uir"m"nts
P r i = " > A m o u n t T o t a
- P r i = "
5 e c e i p t $ r
i n t e r > , ? G G
$ h p > , ? G G
$ h p ' e s k t o p
U n i t 2 4 , G G
G $ h p 2 4 , G G
G $ h p + o n d
p a p e r : 2 5
i m ; 2 ? G $ h p
2 ? G $ h p 5 e
c e i p t p a p
e r r o l l 2 G
$ h p 2 G $ h
p $ r o g r a m m
e r 2 G , G G G
$ h p 2 G , G G G
$ h p
TOTA*0
( + 9
9 9 : P
& $ ).#c&"du-ing
The calendar of activities illustrates the software pro"ect schedule through a Bantt chart. This hart
were the days we plan to make and develop our research. As being planned, we decided tostart this research on August
4G2?. !n gathering data and our survey, we will make it within twoweeks with schedule from our sub"ect class hours.
&rom 2.4 up to 2.? we agreed to make 2 task
Page | 14

per week. !n designing and building of the prototype, we discussed that we ll be creating it for t w o w e e k s a n d a
w e e k a f t e r o t h e r t a s k f o l l o w f o r t h e s a m e n u m b e r o f d a y s f r o m * + ) 4 . 'eveloping the )ystem
ode where a little bit difficult for a reason that we will work on it for =w e e k s a n d 4 d a y s . T h e * + ) 4 . = u n t i l
> . = , w e d e c i d e d t o d o i t o n t h e s a m e r e m a i n i n g d a y s . &igure 4 shows the effort estimation of the
present study.
)igur" +. ?antt C&art
C&a$t"r @
ANA* #I# DE#I?N AND DE E*OPMENT
This chapter presents the analysis, design and development of the desired system conducted bythis study.
A . # ' s t " m A n a - ' s i s
Ev"nt8s *ist1.:Proc"ss Transaction
2.2 Add Transaction !nformation2.2.2 by !tem /ame2.2.4 +y $rice2.2.= +y Luantity2.2.> +y Amount 5eceived2.4
'elete Transaction !nformation
+.: Proc"ss Pa'm"nt
Page | 15
6.: Proc"ss Inv"ntor'
Experimental Method

)igur" 6.

Add Transaction In%ormation

!n this diagram, it discussed about the Admin, Transaction, and )ystem. The Admin transact informationand it processes
on the )ystem. Moreover, it is like a cycle where after it reach at the system it responses back to the Admin.

)igur" @. Proc"ss Pa'm"nt

!n this diagram, it discussed about the Admin, $ayment, and )ystem. The Admin process payment and it proceeds to the
)ystem afterwards. *hen it reaches at the )ystem it responses back to the Admin.

)igur" . Proc"ss Inv"ntor'

Page | 16
1.1AddTransactionIn%ormation
#'st"m
Admin
Add TransactionIn%ormationTransactionIn%ormationR " s
$ o n s " R
" s $ o n s
"

+.:
Proc"ssPa'm"nt
Admin
Proc"ss Pa'm"ntProc"ss
Pa'm"ntR " s $ o
n s " R " s
$ o n s " 6.:Proc"ssInv"ntor'
Admin
Proc"ss Inv"ntor'Proc"ss
Inv"ntor'R " s $ o
n s " R " s
$ o n s "
#'st"m#'st"m
!n this diagram, it discussed about the Admin, !nventory, and )ystem. The Admin process inventory andit proceeds to
the )ystem afterwards. *hen it reaches at the )ystem it responses back to the Admin.*here the Admin can
now view the !nventory )ales.
B . A - g o r i t & m
#t"$ 10
)tart of the $rogram
#t"$ +0
!nitialize new transaction and inventory sales
#t"$ 60
'ecide to update in new transaction
#t"$ @0
!f yes8 $rint E item name, item price, %uality, amount received E
#t"$ 0
!f /o8 lick back
#t"$ 90
alculate whether item price O %uality 7 amount received
#t"$ ;0
lick submit
#t"$ 0
$rint hange
#t"$ 0
'ecide to save the transaction
#t"$ 1:0
!f Kes8 $roceed to !nventory )ales
#t"$110
!f /o8 lick back
#t"$ 1+0
'ecide to delete transaction
#t"$ 160
!f Kes8 $rint E)elect all one 5(* to 0!T deletePPF
#t"$ 1@0
!f /o8 lick to save data
#t"$ 1 0
)top the program
C . ) - o , c & a r t
The flowchart in adding a transaction.
Page | 17
)tart'ecidetoupdatein newtransaction

$rint Eitem name,item price, %uality,amount receivedF

!nitialize newtransaction andinventory sales

READ PAPER

 About
 Blog
 People
 Papers
 Job Board
 Advertise
 We're Hiring!
 Help Center

 Find new research papers in:

 Physics
 Chemistry
 Biology
 Health Sciences
 Ecology
 Earth Sciences
 Cognitive Science
 Mathematics
 Computer Science

 Terms
  Privacy
 Copyright
 Academia ©2018