Inventory Management System. 1p6333
This document was ed by and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this report form. Report 3i3n4
Overview 26281t
& View Inventory Management System. as PDF for free.
More details 6y5l6z
- Words: 6,982
- Pages: 53
10 INTRODUCTION Inventory Management System is fully integrated, which means when you update information in the system, all other related areas will be instantly updated in the system. By using this system, s are able to work more efficiently and produce higher quality ing data for management decision making. 20 PROBLEMS The management use manually to keeping they record of the store, but the system is difficult to maintain due to the cost of material, human errors, less data integrity, difficulty in searching and retrieving product and feasible loss of records and retrieving files. 30 OBJECTIVES •
To increase sale and production
•
To maintain the complete inventory records of stock, receipt, details of purchasers and sellers for a departmental store.
•
To Create an easy to use system for an illiterate workforce
•
To prepare a secure and reliable system to protect the store data from man-made and natural disasters
•
To spend less time in searching and retrieving of information
•
To create a back up of files in every successful operation
•
To increase alternatives to manual handling of data of the store inventory
•
To produce simple not complexity system
•
To tend to present flexibility in the ways data and information are inputted, processes, retrieved and stored
10 SYSTEM REQUEST
1
The system is to develop online Sale and Inventory Management system. This system should be used to store information the Store sales and price their various functions, salesperson and their various functions, , management and their various functions. Project sponsor
AbdulKareem, project manager
Project need
The main objective of this project is to increase sales by creating the complete inventory records of stock, receipt, details of purchasers and sellers at departmental store and also to facilitate the salespersons, sales manager’s inventory managers and the to uses online Sales and Inventory Management System.
System requirement
By using online Sales and Inventory Management System, s can access online system easily and quickly with a function that should be in the system. These systems also facilitate s to:
System value
•
store the details of the inventory
•
update the inventory based on the sale details
•
produce receipts for sales
•
generate sales and inventory reports periodically
We hope that the system will increase sales by developing an online Sales and Inventory Management System for a departmental store. Reduction in customer’s complaint, Reduction in inventory cost, Reduction in staff salary, Reduction IT cost We hope that it helps to control and balance the flow of incoming and outgoing inventory items.
Special issues/Constraints
•
Before accessing the system, we need to key in the information such as name and to access the system.
•
Top level security needed by project team for protection from unauthorized s.
•
The system should be built before December 2014.
2
4.1 REQUIREMENTS The main s in this system are salespersons, sales managers, inventory managers and s. By using this system, s can access online Sales and Inventory Management System with some function. The system will allow them to and key in the main requirement in the update item details and price form. Inventory managers/sales managers/ can check a receipt and print out the bill as reference of items purchased. Inventory managers can generate inventory reports of the items category-wise and see the reports from salespersons about items not available a d need to keep in the inventory. also can add new for the system. 4.2 FUNCTIONAL REQUIREMENTS A requirement specifies a function that a system or component must be able to
allow the
to perform some kind of function. (Thomas Andrew 2009) The main purpose of the system is to increase sales by creating the complete inventory records of stock, receipt, details of purchasers and sellers at departmental store.
3
No
Requirement name
Requirement Description
Priority
1
This function will enable
Mandatory
salespersons/inventory
requirement
managers/sales managers/s. to to the system. 2
Change
This function will enable salesperson/ inventory managers/ sales
Mandatory requirement
managers/s to change . 2
View status
This function will enable salespersons to view status.
3
Cancel a receipt
This function will enable the salespersons to check a receipt
4
Produce a receipt
This function will enable the salespersons to check a receipt
5
Search item
This function will enable the salespersons to search an item
6
View Sold item
This function will enable the salespersons to sold an item
7
View
This function will enable the salespersons to key in
8
Check stock
This function will enable the salespersons to check stock in
Mandatory requirement Mandatory requirement Mandatory requirement Optional requirement Mandatory requirement Mandatory requirement Mandatory requirement
inventory 9
Check inventory status
This function will enable the salespersons/ inventory managers to
Mandatory requirement
check details 10
Validate report
This function will enable the inventory managers to validate report
11
Generate trend
This function will enable the inventory managers to generate trend
12
View reports
This function will enable the inventory managers to view reports.
Mandatory requirement Mandatory requirement Mandatory requirement 4
4.3 NON FUNCTIONAL REQUIREMENTS •
The Salesperson Inventory manager must be able to access their 24 hours a day, seven days a week.
•
The non functional requirements of the Sale and Inventory Management systems are as described below.
1) Security •
The system must have protection from unauthorized s. By using name and .
•
Also system show error if the name or is not correct
•
To use the system, every has to by key in their name and .
2) Performance •
The time system required to process and respond when a key in the Identification that is name and
•
The system is supposed to respond in less than 2 seconds.
3) Availability •
Sale and Inventory Management system is a standalone system which has four to five (4 – 5) s and s must have to use it during operating hours
4.4 HADWARE AND SOFTWARE REQUEREMENTS HADWARE REQUEREMENTS
1 2
HARDWARE
SPECIFICATION
Processor
Intel Pentium4 Processor 1,600GHz
Keyboard
Standard key board 5
3
Hard Drive
80GB 5400RPM /8M/PATA)
4
Network Adapter
PCI 10/100 Ethernet Adapter
5
Printer
Ink jet printer attached in wireless
SOFTWARE REQUEREMENTS
1
SOFTWARE
SPECIFICATION
Operating System
Windows 7 Professional and Windows Server 2008 R2
2
Anti-Virus Software
Norton antivirus software
3
Spread Sheet
Tool Microsoft Excel
4
Internet Tool
Microsoft Internet Explorer version 6.0
5
Programming Tool
Asp.net, SQL
6
Backup Software
CD-R/CD-RW Disk and Data tape/hard disk
7
File Utilities
Win Rar 8.1/7-zip for extracting a files
4.5 NETWORK REQUIREMENTS 5.0 FEASIBILITY STUDY a) TECHNICAL The inventory management system the system is going to be developed using php and sql server as database linkage. The system is technically feasible, even though there are some risks. Regarding the familiarity with the newly developed system, the organization has little experience with the new inventory system because the previous system and the new one has some features alike, but the new system has more functions than the previous one. Also in of the familiarity of the new technology used, the s have knowledge with most type of the technologies in the new system, like the databases and other internet
6
technologies. And for some few new unfamiliar technologies there are consultants to guide the s on how to use them. Project Size of the system is considered medium risk. The project team consists of four people, and the business s will also be involved. The development is going to last for approximately three 3 months. The System compatibility with the current technical infrastructure is good and will be compatible with all the organizational situations. b) ECONOMICAL From the analysis stage the system analyst conducted a survey base on the amount that will be needed to purchase all the necessary components that will be use in the system development. Buying the components is going to cost the organization a lot of money, but compared to the amount that the organization used in building the current system, paying the employees monthly salary and allowances is compared nothing to the one time expense for the new project. In the long run, the company is going to gain the profit above the previous one from the current system. COST AND BENEFITS FOR ECONOMIC FEASIBILITY STUDY: OPERATIONAL COST: Sometimes referred to as revenue or running cost these are the cost resulting from day-to-day running of an operation: •
Staff cost
RM 50,000
•
Hard ware
RM 25,000
•
Maintenance
RM 30,000
•
Electricity
RM 15,000
•
Operational labour
RM 100,000 TOTAL=RM 220,000
DEVELOPMEN COST: This is the expected amount of money that the organization will spend in developing the system which includes the following: •
Development labour
RM 1,246,252
•
Server software
RM 10,976
•
Software licenses
RM 34,875 7
•
Printer
•
2 servers
RM 100,000 RM 125,000 TOTAL= RM 1,517,103
TANGIBLE BENEFITS: Regarding the tangible benefits when the organizations business process is automated, the system analyst carry out an observation with other organizations on how they generate more benefits using the online services to satisfy their customers want like amazon.com The benefit is seen as the profit that the organization is going to obtain after the system is automated: •
Increase in sales
RM 349,000
•
Reduction in inventory cost
RM 68,000
•
Reduction in customer’s complaint
RM 70,000
•
Reduction in staff salary
RM 321,000
•
Reduction IT cost
RM 20,000 TOTAL=RM 828,000
INTANGIBLE BENEFITS: Also called soft benefits, are the gains attributable to your improvement in project that are not reportable for formal ing purposes. These benefits are not included in the financial calculations because they are not nonmonetary or they are difficult to measure: •
Increased in market share
RM 25,000
•
Increased Brand recognition
RM 15,000
•
Better supplier relation
RM 10,000
•
Improved customer service
RM 20,000
•
High quality product
RM 5,000 TOTAL=RM 75,000
c) ORGANIZATIONAL FEASIBILITY From the organizational viewpoint, the system has low risk, because the system is well accepted by the top management of the organization, and other s have strong interest in it, because it solved most of the problems and it satisfies all the requirements needed by them, such as the security issues: in which ’s access levels and the system will only allow privileged s, authentication, authorization and audit procedures will be facilitated to the system s. And data retrieval and the data presenting will be by the system, so the report generated will be automated by the system. 8
6.0 ANALYSIS STRATEGY A) ANALYSIS OF AS IS SYSTEM Currently, most of the Store still using normal or manual system to manage their transaction and day to day activities, the normal system that they are using still using paper base system to enter the transaction. Which the movement of our technologies, some of the store are interested in make an evolution by changing the methods on how to managing a store. As we familiar with the current system which based on paper base always has problem in time consuming, man errors to do the entire duty. For instance, if the wants to or change his or the file of the salesperson can see clearly, change price. We lead to files or records that having high probability to lost either by natural disaster or human error. b) IMPROVEMENTS The new system will have some unique functionality of add new s, View price/ update price, view record, also make , and change , this will lead to the fast interaction among s and . The system is powerful secured, in the sense that the performance and standard of security on the system will be so tight to keep data safe from an unauthorized access from outsiders. The system is fully computerizing system. The improvement of the new system is view calendar, view staff information, , maintain database, and backup. c) PROPOSED TO BE SYSTEM By using this system, most problems faced in the store will be eliminated. This is done by the means of the Online Sale and Inventory Management System, which allows salesperson, Inventory manager, sale manager, and to use the system immediately once they fill the record of the sale. Now, there is no need to the Salesperson and Inventory manager to make paper record Sale and Inventory system which it will give benefit of cost savings by reducing their salesperson, Inventory manager services, and communication. Almost salesperson, Inventory manager complain about the inconsistence in the manual record of transaction procedure. Sales person and Inventory manager can save their time by using the online Sales and Inventory Management system as an alternative of going to the departmental Store. 7.0 UML DIAGRAMS
9
7.1 USE CASE DIAGRAMS (IMPROVEMENTS)
ViewStatus CancelReceipt
CheckReciepts
ProduceReceipt Change SelesPerson CheckBalance SearchItem
<<extend>>
ViewSoldItems
Check Stocket
View
SelesManager CheckReturnI
<<extend>>
GenerateSaleTrend ViewCalendar
<<extend>>
UpdateInformation
MaintainDabase
BackupData CheckStatus
ValidateReport
<<extend>>
AddNewItems
DeleteItems AddNew <<extend>>
InventoryManager GenerateTrende
Delete ViewReports ChangePrice
GenerateReports
7.2 USE CASE DIAGRAMS 10
ViewStatus CancelReceipt
CheckReciepts
ProduceReceipt Change SelesPerson CheckBalance SearchItem
<<extend>>
ViewSoldItems
SelesManager CheckReturnI
Check Stocket
View GenerateSaleTrend
<<extend>>
CheckStatus
AddNewItems
ValidateReport
DeleteItems AddNew <<extend>>
InventoryManager GenerateTrende
Delete ViewReports ChangePrice
GenerateReports
USE CASE DESCRIPTION: 11
salesperson/ inventory managers/ sales managers/
in
1.1 BRIEF DESCRIPTION This use case is initiated by the salesperson, inventory managers, sales managers, and . This use case will enable the customer, and sales person to sign in into the system 1.2 PRE-CONDITION The should have a name and 1.3 PRIMARY ACTOR: Salesperson, inventory managers, sales managers, and 1.4 FLOW OF EVENTS 1.4.1 BASIC FLOW •
The use case begins when the (salesperson, inventory managers, sales managers, ) click on “sign in” button
•
The system then display sign in page
•
The fill in name and
•
The press “” button
•
The system will send information to the name and
•
The system will allow the to access the system if the name and are valid.
•
The system display
•
The functions ends when the the system.
1.4.2 ALTERNATIVE FLOW •
A1: Cancel The system shall use message “the can cancelled by demand”.
1.4.3 EXCEPTIONAL FLOW •
E1: The name you enter is not on record. Please re-enter your name
•
E2: The name and you entered are not associated with an existing
1.5 POST- CONDITION • will be able to
1.6 CONSTRAINT •
The must contain at least 15 characters. 12
USE CASE NAME:
: Customer
: Barnesandnoble
: controller
: page
: table
: Mypage
click "sign in" hyperlink display
E1:The Email address you enter is not...
fill in email and
E2:The Email address and ...
press "sign in" button send check information informaton return activate view
COLLABORATION NAME:
13
3: fill in email and 4: press "sign in" button
2: display
: Customer
: page
1: click "sign in" hyperlink
10: view
: Barnesandnoble 5: send
6: check information 9: activate : Mypage 7: informaton
: controller
8: return : table
USE CASE DESCRIPTION: CHANGE
salesperson/ inventory managers/ sales managers/ s
Change
2.1 BRIEF DESCRIPTION This use case will enable the salesperson, inventory managers, sales managers, and s to change they . 2.2 PRE-CONDITION must have old to change the in the system 2.3 PRIMARY ACTOR: Salesperson/ inventory managers/sales managers/s 2.4 FLOW OF EVENTS 2.4.1 BASIC FLOW •
The use case begin when the, salesperson, inventory managers, sales managers, s press “change ” button
•
The system then display form
•
The salesperson, inventory managers, sales managers, s. key in the 14
name, name and •
The inventory managers, sales managers, s press “save change” button
•
The system send information to controller
•
The system check the information and the information (E1: Problem with current )
•
The system save the information and return
•
The system display your profile, has been updated
2.4.2 ALTERNATE FLOW •
A1: Cancel The system shall use message “the change process can cancelled by demand”.
2.4.3 EXCEPTIONAL FLOW •
E1: Problem with current
2.5 POST CONDITIONS •
Salesperson/ inventory managers/sales managers/s will be able to change the
2.6 CONSTRAINT • The must contain at least 15 characters.
15
USE CASE NAME: CHANGE
: All Actors
: Homepage
: Setting
: Change
: Database
Click " Setting" Option Display
Enter Current , New , Re-enter New
E1: Problem With Current
Click "Save New " Button
Send Information
Success
Return Display
COLLABORATION NAME: CHANGE
16
1: Click " Setting" Option
: Homepage
: All Actors
3: Enter Current , New , Re-enter New 4: Click "Save New " Button 9: Display 2: Display 6: Success
5: Send Information
: Setting
: Change
8: Return 7:
: Database
17
USE CASE DESCRIPTION: ADD NEW
A dm inis trator
A dd new us er
3.1 BRIEF DESCRIPTION This cases well enable the to add new . 3.2 PRE CONDITION The must view his homepage 3.3 PRIMARY ACTOR: 3.4 FLOW OF EVENTS: 3.4.1 BASIC FLOW •
The use case begin when the clicks on “Add New ” button 18
•
The system display the new page
•
The key in information (full name, address, phone number, email)
•
The click on “Proceed” button (A1: Cancel)
•
The system check the information (E1: Please enter full name) (E2: Please enter address)
•
The system save information
•
The system display “successfully added a new ” messages
3.4.2 EXCEPTIONAL FLOW • E1: Please enter full name
The system will display the messages that should enter full name • E2: Please enter an address The system will display the messages that should enter an address 3.4.13 ALTERNATIVE FLOW • A1: cancel: The system must display a message “cancel by demand” 3.5 POST CONDITION The will be able to add new in the table on the database 3.6 CONSTRAINTS The must key in new information.
USE CASE NAME: ADD NEW
19
:
: Main Homepage
: Add New Controller
: Add New Page
: Add New Table
clicks on "Add New " button display
Key in information (full name, address, phone number, email)
select "proceed" button A1: Cancel
E2: Please enter address
E1: Please enter full name
send information
check information
reretrieve item
save
return sucessfully add new
COLLABORATION NAME: ADD NEW 1: clicks on "Add New " button
: 3: Key in information (full name, address, phone number, email) 4: select "proceed" button
: Main Homepage
2: display
10: sucessfully add new : Add New Page
5: send information 6: check information
7: reretrieve item 8: save
9: return : Add New Controller
: Add New Table
20
USE CASE DESCRIPTION: DELETE D A d e lm i e tn i e s t U sr a e rt o r
4.1 BRIEF DESCRIPTION This use case will enable the to delete . 4. 2 PRE-CONDITION The must view his homepage 4.3 PRIMARY ACTOR: 4.4 FLOW OF EVENTS 4.4.1 BASIC FLOW
This use case begins when the click on “delete ” button
The system then display delete page
The key in s information (name)
The click delete button (A1 :Cancel)
The system send information and check the information (E1:invalid name)
The system the information and return
The system display the message of successfully deleted
4.4.2 ALTERNATE FLOW •
A1: Cancel The system will display the message that “the process has been cancelled”
4.4.3 •
EXCEPTIONAL FLOW E1: invalid name The system will display the messages that name do not match
4.4 POST CONDITION •
will be able to delete in the system
21
4.4 CONSTRAINT •
must key in s information (name).
USE CASE NAME: DELETE
:
: Main Homepage
: Delete controller
: Delete page
: Delete table
clicks on "delete " button display
key in information(name)
select "proceed" button A1: Cacel
send information E1: Invalid name check information
return "sucessfully delete " messages
COLLABORATION NAME: DELETE
22
1: clicks on "delete " button
:
3: key in information(name) : Main Homepage 4: select "delete" button 2: display
9: "sucessfully delete " messages
: Delete page
6: check information
5: send information 7:
8: return : Delete controller
: Delete table
USE CASE DESCRIPTION: V S ia l e e w s Ip te r e s m o n
VIEW ITEM DETAILS
5.1 BRIEF DESCRIPTION This use case will enable the
salesperson to view item 5.2 PRE-CONDITION
The products must be stored in database 5.3 PRIMARY ACTOR: Salesperson 5.4 FLOW OF EVENTS 5.4.1 BASIC FLOW 23
•
This uses case begins when the salesperson clicks on “view Item” button
•
The system shall send information and retrieved the information from the Item
•
The system return the information
5.4.2 ALTERNATINE FLOW Not Applicable 5.4.3 EXCEPTIONAL FLOW Not Applicable 5.5 POST CONDITION •
Salesperson will be able to view details of an item
5.6 CONSTRAINT •
Salesperson must key in letters of an item.
USE CASE NAME: VIEW ITEM DETAILS
: SalePerson
: Homepage
: ViewItemDetails
: ItemTable
Click An Item Send Information
Success
Return
DisplayItemDetails
24
COLLABORATION NAME: VIEW ITEM DETAILS 1: Click An Item
: Homepage
: SalePerson 6: DisplayItemDetails 3: Success 2: Send Information
4:
5: Return : ViewItemDetails
: ItemTable
USE CASE DESCRIPTION: SEARCH ITEM
Sales Person
Search item
6.1 BRIEF DESCRIPTION: This use case will enable the salesperson to search an item 6.2 PRE CONDITION: •
Salesperson must to the system
•
The products must be stored in database
6.3 PRIMARY ACTOR: Salesperson 6.4 FLOW OF EVENTS: 6.4.1 BASIC FLOW •
The use case begin when the salesperson key in the first letter of an item in the search function on the main homepage.
•
The salesperson will select an item that you want and select “search” button. (A1: Cancel) 25
•
The system will item availability (E1: unavailable item)
•
The system will display an item details
6.4.2 ALTERNATIVE FLOW •
A1: Cancel The system will display the message that the process has been cancelled
6.4.3 EXCEPTIONAL FLOW •
E1: Unavailable item The system will display the messages that item are unavailable
6.5 POST CONDITION •
Salesperson will be able to view details of an item
6.5 CONSTRAINT •
Salesperson must key in letters of an item.
: Sales Person
: Homepage
product : Search
: Item details
: Item details table
1. key in initial letters of the item
2. select particular product
3. select "search" button
A 1: Cancel
4. send information E 1: Unavailable item 5. product
6. retrieve details
7. return details
8. Display
USE CASE NAME: SEARCH ITEM
26
COLLABORATION NAME: SEARCH ITEM
1: 1. key in initial letters of the item 2: 2. select particular product 3: 3. select "search" button
: Homepage
: Sales Person
4: 4. send information5: 5. product
7: 7. return details
: Item details table
: Item details
8: 8. Display 6: 6. retrieve details product : Search
USE CASE DESCRIPTION: ADD NEW ITEM
Add new item
7.1 BRIEF DESCRIPTION: This use case will enable the to add new item in inventory. 7.2 PRE CONDITION: must to the system 7.3 PRIMARY ACTOR: 7.4 FLOW OF EVENTS: 7.4.1 BASIC FLOW •
The use case begin when the click on “add item” button.
•
The system will display add new item page.
•
will key in the item information (item ID, item name, item price) 27
•
Then, will select “proceed“ button.(Alternative1: Cancel)
•
The system will check information (item ID, item name, item price) (E1: please enter item ID) (E2: please enter item name) (E3: please enter item price)
•
will save the information
7.4.2 ALTERNATIVE FLOW •
A1: Cancel The system will display the message that the process has been cancelled
7.4.3 EXCEPTIONAL FLOW •
E1: Please enter item ID The system will display the message that item ID are invalid
•
E2: Please enter item name
•
The system will display the message that should enter item name
7.5 POST CONDITION •
will be able to add new item information
7.6 CONSTRAINT •
must key in the lecturer information USE CASE NAME: ADD NEW ITEM
28
:
: Main Homepage
: Add new item controller
: Add new item page
: Add new item table
1. select "add new item" button 2.display
3.key in item information (item ID, item name, item price)
4.select "proceed" button E1: please enter item ID
5.send information A1: cancel
E2: please enter item name
6.check information
7.retrieve item
8.save
9.return
10. display
COLLABORATION NAME: ADD NEW ITEM 1: 1. select "add new item" button
: Main Homepage
:
3: 3.key in item information 4: 4.select "proceed" button 2: 2.display 6: 6.check information 7: 7. information 8: 8.save
9: 9.return
: Add new item table
: Add new item controller 5: 5.send information : Add new item form
29
USE CASE DESCRIPTION: CHECK INVENTORY STATUS
S alespers on/sales m anager
Chec k inventory ststus
8.1 BRIEF DESCRIPTION: This case will enable the sales person and sales manager to check the inventory status. 8.2 PRE-CONDITION: The sales person and the sales manager must key in item information 8.3 PRIMARY ACTOR: Salesperson and sales manager 8.4 FLOW OF EVENTS: 8.4.1 BASIC FLOW: •
This case begins when sales person and sales manager clicks on “check inventory status” button
•
The system will display check inventory status page
•
Sales person and sales manager must key in item information (item ID) and select “proceed” button
•
The system will retrieve item. •
The system display “successfully” message
7.4.2 ALTERNATIVE FLOW •
A1: Cancel The system will display the message that the process has been cancelled
7.4.3 EXCEPTIONAL FLOW 30
•
E1: Invalid item ID The system will display the message that item ID are invalid
8.5 POST CONDITION: •
The sales person and the sales manager will be able to check inventory status.
8.6 CONSTRAINTS: •
The sales person and the sales manager must key in item ID information
USE CASE NAME: CHECK INVENTORY STATUS
: SalesPerson/Sal...
: Homepage
: Check Inventory Status Page
: Check Inventory Status Control
: Check Inventory Status Table
click on "check inventory status" button display
key in item information (item ID)
select "proceed" button A1: Cancel
send information E1: Invalid item ID check information
retrieve item
return
display "sucessfully" message
COLLABORATION NAME: CHECK INVENTORY STATUS
31
6: check information
3: key in item information (item ID) 4: select "proceed" button
: SalesPerson/Sales Manager
5: send information
: Check Inventory Status Page 8: return
: Check Inventory Status Control
1: click on "check inventory status" button 7: retrieve item 2: display 9: display "sucessfully" message
: Check Inventory Status Table
: Homepage
USE CASE DESCRIPTION: CHANGE PRICE
Change price
9.1 BRIEF DESCRIPTION: This use case will enable the to change item price 9.2 PRE CONDITION: •
must to the system
•
The item details must be stored in database
9.3 PRIMARY ACTOR: 9.4 FLOW OF EVENTS: 9.4 .1 BASIC FLOWS: •
The use case begin when the key in the price on the homepage.
•
The will select “change price” button. (A1: Cancel) 32
•
The system will item price availability (E1: A value is required)
•
The system will display change price details
9.4.2 ALTERNATIVE FLOW: •
A1: Cancel The system will display the message that the process has been cancelled
9.4.3 EXCEPTIONAL FLOW : •
E1: A value is required The system will display the message that a price value is required
9.5 POST CONDITION: •
will be able to view item details
9.6 CONSTRAINT: •
must key in the item price
USE CASE NAME: CHANGE PRICE
:
: Homepage
: Change Price Controlller
: Change Price Details
: Change Price Table
1. key in price number of the item 2. select "change price" button A1: Cancel 3. send information AE1: value is required 4.
5. retrieve details
6. return details
7. save
8. display
COLLABORATION NAME: CHANGE PRICE 33
4: 4.
:
1: 1. key in price number of the item 2: 2. select "change price" button 3: 3. send information
: Change Price Controlller
5: 5. retrieve details 6: 6. return details : Homepage
: Change Price Table
7: 7. save 8: 8. display
: Change Price Details
USE CASE DESCRIPTION: PRODUCE A RECEIPT
Salesperson
Produce a receipt
10.1 BRIEF DESCRIPTION: This use case will enable the salesperson to produce a receipt 10.2 PRE CONDITION: Salesperson must to the system 10.3 PRIMARY ACTOR: Salesperson 10.4 FLOW OF EVENTS: 10.4.1 BASIC FLOW •
The use case begin when the clicks on “produce a receipt” button.
•
It will display produce a receipt page
•
The salesperson will key in item information (item name, item price)
•
The salesperson will select “proceed” button (A1: Cancel)
•
The system will check information (E1: invalid item name) (E1: invalid item price) 34
•
The system will display “successfully” message
10.4.2 ALTERNATIVE FLOW •
A1: Cancel The system will display the message that the process has been cancelled
10.4.3 EXCEPTIONAL FLOW •
E1: invalid item name The system will display the messages that item are invalid
10.5 POST CONDITION •
Salesperson will be able to produce a receipt
10.5 CONSTRAINT •
Salesperson must key in item information
USE CASE NAME: PRODUCE A RECIEPT
: Salesperson
: Main Homepage
: Produce a receipt page
: Produce a receipt controller
: Produce receipt table
clicks on "produce a receipt" button display
key in item information (item name, item price)
select "proceed" button A1: Cancel
send information
E1: Inavalid item name
E2: Invalid item price
check information
return
display "sucessfully" message
COLLABORATION NAME: PRODUCE A RECIEPT 35
3: key in item information (item name, item price) 4: select "proceed" button
: Salesperson
1: clicks on "produce a receipt" button
: Produce a receipt page 2: display
6: check information
5: send information 9: display "sucessfully" message : Main Homepage
8: return
: Produce receipt table
7: : Produce a receipt controller
(from Logical View)
USE CASE NAME: CHECK BALANCE.
(from Logical View)
Check Balance
Inventory Manager
11.1 BRIEF DESCRIPTION This use case will enable the and inventory manager to check Balance. 11.2 PRE-CONDITION The and inventory manager should have a ID and 11.4 FLOW OF EVENTS 11.4.1 BASIC FLOW •
This use case begins when the and inventory manager clicks on “Check Balance” Button.
•
The system then display check balance page
•
The press check balance button.
•
The system will send information to the I.D and 36
•
The system will allow the to access the system if the I.D and are valid
•
The system displays the Balance.
•
The functions ends when the /Inventory manager of the system.
ALTERNATIVE FLOW Not applicable EXCEPTIONAL FLOW The ID or you entered does not match please re-enter again.
USE CASE NAME: CHECK BALANCE
: /InventoryManager
: Homepage
: BalanceController
Click on "Check Balance" Button
: BalanceTable. name or is incorrect. Pls re-enter again.
Send Info ( ) ( ) Enter ID And Check Balance ( ) Return ( ) Display "Balance"
37
COLLABORATION NAME: CHECK BALANCE
1: Click on"Check Balance" Button 4: Enter IDAnd :
: Homepage 3: ( )
7: Display "Balance"
2: SendInfo( ) 5: Check Balance( )
6: Return( )
: BalanceController
: BalanceTable.
Generate Report
InventoryManager
BRIEF DESCRIPTION
38
This use case is initiated by the and inventory manager. This use case will enable the and inventory manager to generate all the report in the system. PRE-CONDITION The and Inventory Manager should have a I.D and FLOW OF EVENTS BASIC FLOW •
This use case begins when the ( and inventory Manager clicks on “Generate report” Button.
•
The system then display Generate report in page
•
The /Inventory Manager enter his ID and
•
The press generate report button
•
The system will send information to the I.D and
•
The system will allow the to access the system of the I.D and are valid
•
The system display the generated report
•
The functions ends when the /Inventory manager of the system.
ALTERNATIVE FLOW Not applicable EXCEPTIONAL FLOW The ID or you entered does not match please re-enter again. USE CASE NAME: GENERATE REPORT
39
: Inventory manager
: Main Homepage
: Generate inventory report page
: Generate inventory report controller
: Generate inventory report table
clicks on"generate report inventory" button display
key in inventory reports information (items category, price)
click "proceed" button send information
check information
save information
return
display inventory report
COLLABORATION NAME: GENERATE REPORT 3: key in inventory reports information (items category, price) 4: click "proceed" button 1: clicks on"generate report inventory" button
: Inventory manager
2: display : Generate inventory report page
: Main Homepage
5: send information 9: display inventory report 6: check information
8: return
: Generate inventory report table
7: save information : Generate inventory report controller
40
7.3 CLASS DIAGRAM
Form name
Item Item No Types of item Price Quantity
Profile Name Phone no Address Zip code
View
() Cancel()
Add New Item()
Add New ()... update() Cancel()
Add
Name() () ID DOB SEX Email Phone No. Add new item()... Delete item() Add new ()... Delete () Change price() Dalete Change wod
Salesperson UsaerName First Name Last Name DOB SEX ID Email Phone Number
Sales Manager name First name Last name DOB SEX ID Email Phone Number
View status() View sold item() View () Search item() Produce a receipt() Cancel a receipt() Check stock() Check inventory status() ...
Check exception() Check a receipt() Check balance() Check return item() Generate sales trend()...
Inventory Manager Name First name Last Name DOB SEX ID Email Phone Number View reports() Check inventory status() ... Validate report() Generate reports() Generate trends() Change Price
View
Chance Price
Delete Name Delete ()
Change form name Submit() Cancel()
Price Page Item No Price Change Price() View Price()
41
7.4 ACTIVITY DIAGRAM ➢ View item details
Salesperson
View Item
Click On "View Item" Button
Enter (Enter the name of Item)
Click "Search" Button
[No Result]
Searching The Item
[Success]
View The Item
Display The Item Details
42
➢ Search item
Salesperson
searchItem
Key Search word
InCorect
Click Go Button
DisplaySearch Item
SearchIte m
Corect
➢ Add new 43
Click "Add " Button
System
Display Amid page
Select New Key in " Information" (Invalid) the Information
(Valid) Click On "Save " Button
Sussecceful add or Fail
44
➢ Add new item
id
ADD ITEM
Click "Add Item" button
key in "Item name"price
Check and
Click "Save" Button
Sussecceful Added
45
7.5 STATECHART DIAGRAM ➢ Search item
Salesperson key in the name of the search Item Search Item
Pending Comformation
Requesting search
Iten name Relessed View the list of the Item by Salsperson
➢ Add new item 46
Clicks on "add new item" page Add new item page Requests for add new item page Pending for add new item key in the add new item information Filled the page information approach
check confirmation save the information
Success or fail will appear the message on screen and return to homepager
47
8.0 DESIGN AND IMPLEMENTATION Differentiation between various programming languages In every stage of implementation system the web developers or system analyst will need to decide and choose which programming language the propose system will be use. When making decision on programming languages some important issues will consider such as: What database does the system working with : 1. JAVA 2. PHP 3. VISUAL BASIC JAVA
PHP
VISUAL BASIC
Java has been built from the PHP is based on Perl, it is a Visual ground
up
as
an
object general-purpose
Basic
scripting generation
oriented and will be very language initially designed for programming useful for coding inventory web development to generate associated management system.
is
a
event
thirddriven
language
and
development
dynamic web pages and PHP surroundings from Microsoft code is embedded into the for its COM programming HTML source document.
model.
Java applications are normally PHP is an interpreted scripting Scripting languages such as compiled to byte code that is language almost always run on VBA able to run on any Java virtual a
server
machine (JVM) regardless of function
for of
computer architecture.
clients
Advantages:
Advantages:
the
and
VBScript
are
primary syntactically similar to Visual
responding
to Basic, but perform differently.
Advantages:
1) Easy to use object-oriented 1) It runs fast and doesn't tend 1) friendly and interface programming language when to slow other processes down compared
to
the
2) Simple and easy to use
popular 2) PHP uses a modular system 3) Powerful front end tool
programming language.
of extensions to interface with 4) Low cost
2) Java is interpreted to run a variety of libraries. Java programs
5) It is reachable with
3) PHP community is willing documentation in most tools
3) The compiler, interpreter, to share and Java-compatible browsers 4) PHP can run on both include some levels of security
Windows servers and UNIX 48
Disadvantages:
Disadvantages:
Disadvantages:
1) Low speed
1) Web programming tools is 1) Does not side-by-
2) It runs slowly compared to freely accessible to protection side execution other programs
flaws.
3) The programs do not always 2)
Need
work properly even if they are variables written correctly
2) Large talent to
control
coming
pool of
the competition and 3) Cannot handle pointers
accessible between pages.
directly
3) Need to add java or java code other client-side tools in the output
INVIDIVIDUAL REPORT
49
The group Assignment consists of four (4) . The Assignment is to develop an online inventory Management system. We have meeting with all the group normally three times in a week, and the Assignment task was distributed for each of the group member. My task in the Assignment is to analyze the feasibility of the system, Four (4) use case diagrams and their description each and sequence diagram. Another task done by me is the Drawing of the Class diagram. After finishing the individual task given to each member of the group, we later on compile all together and we check and edit some errors together before printing the work.
10.0 CONCLUSION
50
In conclusion, an online Sales and Inventory Management System is a perfect solution for the keeping they record of the store. The system can be used as a tool to maintain due to the cost of material, human errors, less data integrity, difficulty in searching and retrieving product and feasible loss of records and retrieving files. We were following SDLC phases such as planning, analysis, design and implementation of system to come out with a full documentation. Then, we also discussed the advantages of programming languages as you see in the documentation.
REFERENCES
51
➢ Bell, D. Morrey, I. and Pugh, J. (1987-1993). Software Engineering : A Programming
Approach. 2nd ed. Britain: Prentice Hall. p32-56. ➢ Champeaux, D. D. Lea, D. and Faure, P. (1994). Object-Oriented System
Development. Canada: Addison-Wesley. p25-60. ➢ Quatrani, T (1998). Visual Modeling with Rational Rose 2000 and UML. United
States of America: Addison-Wesley. p34-50. ➢ Shammas, C. N. (1954). Visual C++ Generic Programming. United States of
America: McGraw Hill. p1-20. ➢ Wilkie, G (1994). Object-Oriented Software Engineering : The Professional
Developer's Guide. United States of America: Addison-Wesley. p1-200. ➢ Hentzen, W. (1995). Programming Visual FoxPro 3.0. Ziff-Davis Publishing: United
States of America. p1-200. ➢ O’Brien, J (1999). Management Information Systems – Managing Information
Technology in the Internetworked Enterprise. Boston: Irwin McGraw-Hill. ➢
Kroenke, D M. (2008). Experiencing MIS. Prentice-Hall, Upper Saddle River, NJ
➢ O'Brien, J A. (2003). Introduction to information systems: essentials for the ebusiness enterprise. McGraw-Hill, Boston, MA ➢ Alter, S. The Work System Method: Connecting People, Processes, and IT for Business Results. Works System Press, CA ➢ Beynon-Davies P. (2009). The ‘language’ of informatics: the nature of information
systems. International Journal of Information Management. ➢ Beynon-Davies P. (2009). Business Information Systems. Palgrave, Basingstoke ➢ Kotler, Philip; Keller, Kevin Lane (2006). Marketing Management (12 ed.). Pearson
Education ➢ Keen, P. G. W. (1978). Decision systems: an organizational perspective.
Reading, Mass., Addison-Wesley Pub. Co. ➢ Efraim Turban, Jay E. Aronson, Ting-Peng Liang (2008). Decision Systems
and Intelligent System ➢ Holsapple, C.W., and A. B. Whinston. (1996). Decision Systems: A
Knowledge-Based Approach. St. Paul: West Publishing. ➢ MS, 2007, Java Advantages and Disadvantages, viewed 17 November 2011,
http://www.webdotdev.com/nvd/content/view/1042/204/ ➢ Webodia, n.d., programming language, viewed 17 November 2011,
http://www.webopedia.com/TERM/P/programming_language.html
52
➢ Designs Playground, 2006, viewed 20 November 2011, The Advantages of PHP
http://www.designersplayground.com/articles/118/1/The-Advantages-ofPHP/Page1.html ➢ GSLOGIX, 2011, viewed 20 November 2011, Advantages and disadvantages of
PHP , http://www.gslogix.com/blog/2011/10/advantages-and-disadvantages-of-php/ ➢ Voegele, J. (2004), Last viewed 20 September1 2011.Programming Languange
Comparison. Available: http://www.jvoegele.com/software/langcomp.html.
53
To increase sale and production
•
To maintain the complete inventory records of stock, receipt, details of purchasers and sellers for a departmental store.
•
To Create an easy to use system for an illiterate workforce
•
To prepare a secure and reliable system to protect the store data from man-made and natural disasters
•
To spend less time in searching and retrieving of information
•
To create a back up of files in every successful operation
•
To increase alternatives to manual handling of data of the store inventory
•
To produce simple not complexity system
•
To tend to present flexibility in the ways data and information are inputted, processes, retrieved and stored
10 SYSTEM REQUEST
1
The system is to develop online Sale and Inventory Management system. This system should be used to store information the Store sales and price their various functions, salesperson and their various functions, , management and their various functions. Project sponsor
AbdulKareem, project manager
Project need
The main objective of this project is to increase sales by creating the complete inventory records of stock, receipt, details of purchasers and sellers at departmental store and also to facilitate the salespersons, sales manager’s inventory managers and the to uses online Sales and Inventory Management System.
System requirement
By using online Sales and Inventory Management System, s can access online system easily and quickly with a function that should be in the system. These systems also facilitate s to:
System value
•
store the details of the inventory
•
update the inventory based on the sale details
•
produce receipts for sales
•
generate sales and inventory reports periodically
We hope that the system will increase sales by developing an online Sales and Inventory Management System for a departmental store. Reduction in customer’s complaint, Reduction in inventory cost, Reduction in staff salary, Reduction IT cost We hope that it helps to control and balance the flow of incoming and outgoing inventory items.
Special issues/Constraints
•
Before accessing the system, we need to key in the information such as name and to access the system.
•
Top level security needed by project team for protection from unauthorized s.
•
The system should be built before December 2014.
2
4.1 REQUIREMENTS The main s in this system are salespersons, sales managers, inventory managers and s. By using this system, s can access online Sales and Inventory Management System with some function. The system will allow them to and key in the main requirement in the update item details and price form. Inventory managers/sales managers/ can check a receipt and print out the bill as reference of items purchased. Inventory managers can generate inventory reports of the items category-wise and see the reports from salespersons about items not available a d need to keep in the inventory. also can add new for the system. 4.2 FUNCTIONAL REQUIREMENTS A requirement specifies a function that a system or component must be able to
allow the
to perform some kind of function. (Thomas Andrew 2009) The main purpose of the system is to increase sales by creating the complete inventory records of stock, receipt, details of purchasers and sellers at departmental store.
3
No
Requirement name
Requirement Description
Priority
1
This function will enable
Mandatory
salespersons/inventory
requirement
managers/sales managers/s. to to the system. 2
Change
This function will enable salesperson/ inventory managers/ sales
Mandatory requirement
managers/s to change . 2
View status
This function will enable salespersons to view status.
3
Cancel a receipt
This function will enable the salespersons to check a receipt
4
Produce a receipt
This function will enable the salespersons to check a receipt
5
Search item
This function will enable the salespersons to search an item
6
View Sold item
This function will enable the salespersons to sold an item
7
View
This function will enable the salespersons to key in
8
Check stock
This function will enable the salespersons to check stock in
Mandatory requirement Mandatory requirement Mandatory requirement Optional requirement Mandatory requirement Mandatory requirement Mandatory requirement
inventory 9
Check inventory status
This function will enable the salespersons/ inventory managers to
Mandatory requirement
check details 10
Validate report
This function will enable the inventory managers to validate report
11
Generate trend
This function will enable the inventory managers to generate trend
12
View reports
This function will enable the inventory managers to view reports.
Mandatory requirement Mandatory requirement Mandatory requirement 4
4.3 NON FUNCTIONAL REQUIREMENTS •
The Salesperson Inventory manager must be able to access their 24 hours a day, seven days a week.
•
The non functional requirements of the Sale and Inventory Management systems are as described below.
1) Security •
The system must have protection from unauthorized s. By using name and .
•
Also system show error if the name or is not correct
•
To use the system, every has to by key in their name and .
2) Performance •
The time system required to process and respond when a key in the Identification that is name and
•
The system is supposed to respond in less than 2 seconds.
3) Availability •
Sale and Inventory Management system is a standalone system which has four to five (4 – 5) s and s must have to use it during operating hours
4.4 HADWARE AND SOFTWARE REQUEREMENTS HADWARE REQUEREMENTS
1 2
HARDWARE
SPECIFICATION
Processor
Intel Pentium4 Processor 1,600GHz
Keyboard
Standard key board 5
3
Hard Drive
80GB 5400RPM /8M/PATA)
4
Network Adapter
PCI 10/100 Ethernet Adapter
5
Printer
Ink jet printer attached in wireless
SOFTWARE REQUEREMENTS
1
SOFTWARE
SPECIFICATION
Operating System
Windows 7 Professional and Windows Server 2008 R2
2
Anti-Virus Software
Norton antivirus software
3
Spread Sheet
Tool Microsoft Excel
4
Internet Tool
Microsoft Internet Explorer version 6.0
5
Programming Tool
Asp.net, SQL
6
Backup Software
CD-R/CD-RW Disk and Data tape/hard disk
7
File Utilities
Win Rar 8.1/7-zip for extracting a files
4.5 NETWORK REQUIREMENTS 5.0 FEASIBILITY STUDY a) TECHNICAL The inventory management system the system is going to be developed using php and sql server as database linkage. The system is technically feasible, even though there are some risks. Regarding the familiarity with the newly developed system, the organization has little experience with the new inventory system because the previous system and the new one has some features alike, but the new system has more functions than the previous one. Also in of the familiarity of the new technology used, the s have knowledge with most type of the technologies in the new system, like the databases and other internet
6
technologies. And for some few new unfamiliar technologies there are consultants to guide the s on how to use them. Project Size of the system is considered medium risk. The project team consists of four people, and the business s will also be involved. The development is going to last for approximately three 3 months. The System compatibility with the current technical infrastructure is good and will be compatible with all the organizational situations. b) ECONOMICAL From the analysis stage the system analyst conducted a survey base on the amount that will be needed to purchase all the necessary components that will be use in the system development. Buying the components is going to cost the organization a lot of money, but compared to the amount that the organization used in building the current system, paying the employees monthly salary and allowances is compared nothing to the one time expense for the new project. In the long run, the company is going to gain the profit above the previous one from the current system. COST AND BENEFITS FOR ECONOMIC FEASIBILITY STUDY: OPERATIONAL COST: Sometimes referred to as revenue or running cost these are the cost resulting from day-to-day running of an operation: •
Staff cost
RM 50,000
•
Hard ware
RM 25,000
•
Maintenance
RM 30,000
•
Electricity
RM 15,000
•
Operational labour
RM 100,000 TOTAL=RM 220,000
DEVELOPMEN COST: This is the expected amount of money that the organization will spend in developing the system which includes the following: •
Development labour
RM 1,246,252
•
Server software
RM 10,976
•
Software licenses
RM 34,875 7
•
Printer
•
2 servers
RM 100,000 RM 125,000 TOTAL= RM 1,517,103
TANGIBLE BENEFITS: Regarding the tangible benefits when the organizations business process is automated, the system analyst carry out an observation with other organizations on how they generate more benefits using the online services to satisfy their customers want like amazon.com The benefit is seen as the profit that the organization is going to obtain after the system is automated: •
Increase in sales
RM 349,000
•
Reduction in inventory cost
RM 68,000
•
Reduction in customer’s complaint
RM 70,000
•
Reduction in staff salary
RM 321,000
•
Reduction IT cost
RM 20,000 TOTAL=RM 828,000
INTANGIBLE BENEFITS: Also called soft benefits, are the gains attributable to your improvement in project that are not reportable for formal ing purposes. These benefits are not included in the financial calculations because they are not nonmonetary or they are difficult to measure: •
Increased in market share
RM 25,000
•
Increased Brand recognition
RM 15,000
•
Better supplier relation
RM 10,000
•
Improved customer service
RM 20,000
•
High quality product
RM 5,000 TOTAL=RM 75,000
c) ORGANIZATIONAL FEASIBILITY From the organizational viewpoint, the system has low risk, because the system is well accepted by the top management of the organization, and other s have strong interest in it, because it solved most of the problems and it satisfies all the requirements needed by them, such as the security issues: in which ’s access levels and the system will only allow privileged s, authentication, authorization and audit procedures will be facilitated to the system s. And data retrieval and the data presenting will be by the system, so the report generated will be automated by the system. 8
6.0 ANALYSIS STRATEGY A) ANALYSIS OF AS IS SYSTEM Currently, most of the Store still using normal or manual system to manage their transaction and day to day activities, the normal system that they are using still using paper base system to enter the transaction. Which the movement of our technologies, some of the store are interested in make an evolution by changing the methods on how to managing a store. As we familiar with the current system which based on paper base always has problem in time consuming, man errors to do the entire duty. For instance, if the wants to or change his or the file of the salesperson can see clearly, change price. We lead to files or records that having high probability to lost either by natural disaster or human error. b) IMPROVEMENTS The new system will have some unique functionality of add new s, View price/ update price, view record, also make , and change , this will lead to the fast interaction among s and . The system is powerful secured, in the sense that the performance and standard of security on the system will be so tight to keep data safe from an unauthorized access from outsiders. The system is fully computerizing system. The improvement of the new system is view calendar, view staff information, , maintain database, and backup. c) PROPOSED TO BE SYSTEM By using this system, most problems faced in the store will be eliminated. This is done by the means of the Online Sale and Inventory Management System, which allows salesperson, Inventory manager, sale manager, and to use the system immediately once they fill the record of the sale. Now, there is no need to the Salesperson and Inventory manager to make paper record Sale and Inventory system which it will give benefit of cost savings by reducing their salesperson, Inventory manager services, and communication. Almost salesperson, Inventory manager complain about the inconsistence in the manual record of transaction procedure. Sales person and Inventory manager can save their time by using the online Sales and Inventory Management system as an alternative of going to the departmental Store. 7.0 UML DIAGRAMS
9
7.1 USE CASE DIAGRAMS (IMPROVEMENTS)
ViewStatus CancelReceipt
CheckReciepts
ProduceReceipt Change SelesPerson CheckBalance SearchItem
<<extend>>
ViewSoldItems
Check Stocket
View
SelesManager CheckReturnI
<<extend>>
GenerateSaleTrend ViewCalendar
<<extend>>
UpdateInformation
MaintainDabase
BackupData CheckStatus
ValidateReport
<<extend>>
AddNewItems
DeleteItems AddNew <<extend>>
InventoryManager GenerateTrende
Delete ViewReports ChangePrice
GenerateReports
7.2 USE CASE DIAGRAMS 10
ViewStatus CancelReceipt
CheckReciepts
ProduceReceipt Change SelesPerson CheckBalance SearchItem
<<extend>>
ViewSoldItems
SelesManager CheckReturnI
Check Stocket
View GenerateSaleTrend
<<extend>>
CheckStatus
AddNewItems
ValidateReport
DeleteItems AddNew <<extend>>
InventoryManager GenerateTrende
Delete ViewReports ChangePrice
GenerateReports
USE CASE DESCRIPTION: 11
salesperson/ inventory managers/ sales managers/
in
1.1 BRIEF DESCRIPTION This use case is initiated by the salesperson, inventory managers, sales managers, and . This use case will enable the customer, and sales person to sign in into the system 1.2 PRE-CONDITION The should have a name and 1.3 PRIMARY ACTOR: Salesperson, inventory managers, sales managers, and 1.4 FLOW OF EVENTS 1.4.1 BASIC FLOW •
The use case begins when the (salesperson, inventory managers, sales managers, ) click on “sign in” button
•
The system then display sign in page
•
The fill in name and
•
The press “” button
•
The system will send information to the name and
•
The system will allow the to access the system if the name and are valid.
•
The system display
•
The functions ends when the the system.
1.4.2 ALTERNATIVE FLOW •
A1: Cancel The system shall use message “the can cancelled by demand”.
1.4.3 EXCEPTIONAL FLOW •
E1: The name you enter is not on record. Please re-enter your name
•
E2: The name and you entered are not associated with an existing
1.5 POST- CONDITION • will be able to
1.6 CONSTRAINT •
The must contain at least 15 characters. 12
USE CASE NAME:
: Customer
: Barnesandnoble
: controller
: page
: table
: Mypage
click "sign in" hyperlink display
E1:The Email address you enter is not...
fill in email and
E2:The Email address and ...
press "sign in" button send check information informaton return activate view
COLLABORATION NAME:
13
3: fill in email and 4: press "sign in" button
2: display
: Customer
: page
1: click "sign in" hyperlink
10: view
: Barnesandnoble 5: send
6: check information 9: activate : Mypage 7: informaton
: controller
8: return : table
USE CASE DESCRIPTION: CHANGE
salesperson/ inventory managers/ sales managers/ s
Change
2.1 BRIEF DESCRIPTION This use case will enable the salesperson, inventory managers, sales managers, and s to change they . 2.2 PRE-CONDITION must have old to change the in the system 2.3 PRIMARY ACTOR: Salesperson/ inventory managers/sales managers/s 2.4 FLOW OF EVENTS 2.4.1 BASIC FLOW •
The use case begin when the, salesperson, inventory managers, sales managers, s press “change ” button
•
The system then display form
•
The salesperson, inventory managers, sales managers, s. key in the 14
name, name and •
The inventory managers, sales managers, s press “save change” button
•
The system send information to controller
•
The system check the information and the information (E1: Problem with current )
•
The system save the information and return
•
The system display your profile, has been updated
2.4.2 ALTERNATE FLOW •
A1: Cancel The system shall use message “the change process can cancelled by demand”.
2.4.3 EXCEPTIONAL FLOW •
E1: Problem with current
2.5 POST CONDITIONS •
Salesperson/ inventory managers/sales managers/s will be able to change the
2.6 CONSTRAINT • The must contain at least 15 characters.
15
USE CASE NAME: CHANGE
: All Actors
: Homepage
: Setting
: Change
: Database
Click " Setting" Option Display
Enter Current , New , Re-enter New
E1: Problem With Current
Click "Save New " Button
Send Information
Success
Return Display
COLLABORATION NAME: CHANGE
16
1: Click " Setting" Option
: Homepage
: All Actors
3: Enter Current , New , Re-enter New 4: Click "Save New " Button 9: Display 2: Display 6: Success
5: Send Information
: Setting
: Change
8: Return 7:
: Database
17
USE CASE DESCRIPTION: ADD NEW
A dm inis trator
A dd new us er
3.1 BRIEF DESCRIPTION This cases well enable the to add new . 3.2 PRE CONDITION The must view his homepage 3.3 PRIMARY ACTOR: 3.4 FLOW OF EVENTS: 3.4.1 BASIC FLOW •
The use case begin when the clicks on “Add New ” button 18
•
The system display the new page
•
The key in information (full name, address, phone number, email)
•
The click on “Proceed” button (A1: Cancel)
•
The system check the information (E1: Please enter full name) (E2: Please enter address)
•
The system save information
•
The system display “successfully added a new ” messages
3.4.2 EXCEPTIONAL FLOW • E1: Please enter full name
The system will display the messages that should enter full name • E2: Please enter an address The system will display the messages that should enter an address 3.4.13 ALTERNATIVE FLOW • A1: cancel: The system must display a message “cancel by demand” 3.5 POST CONDITION The will be able to add new in the table on the database 3.6 CONSTRAINTS The must key in new information.
USE CASE NAME: ADD NEW
19
:
: Main Homepage
: Add New Controller
: Add New Page
: Add New Table
clicks on "Add New " button display
Key in information (full name, address, phone number, email)
select "proceed" button A1: Cancel
E2: Please enter address
E1: Please enter full name
send information
check information
reretrieve item
save
return sucessfully add new
COLLABORATION NAME: ADD NEW 1: clicks on "Add New " button
: 3: Key in information (full name, address, phone number, email) 4: select "proceed" button
: Main Homepage
2: display
10: sucessfully add new : Add New Page
5: send information 6: check information
7: reretrieve item 8: save
9: return : Add New Controller
: Add New Table
20
USE CASE DESCRIPTION: DELETE D A d e lm i e tn i e s t U sr a e rt o r
4.1 BRIEF DESCRIPTION This use case will enable the to delete . 4. 2 PRE-CONDITION The must view his homepage 4.3 PRIMARY ACTOR: 4.4 FLOW OF EVENTS 4.4.1 BASIC FLOW
This use case begins when the click on “delete ” button
The system then display delete page
The key in s information (name)
The click delete button (A1 :Cancel)
The system send information and check the information (E1:invalid name)
The system the information and return
The system display the message of successfully deleted
4.4.2 ALTERNATE FLOW •
A1: Cancel The system will display the message that “the process has been cancelled”
4.4.3 •
EXCEPTIONAL FLOW E1: invalid name The system will display the messages that name do not match
4.4 POST CONDITION •
will be able to delete in the system
21
4.4 CONSTRAINT •
must key in s information (name).
USE CASE NAME: DELETE
:
: Main Homepage
: Delete controller
: Delete page
: Delete table
clicks on "delete " button display
key in information(name)
select "proceed" button A1: Cacel
send information E1: Invalid name check information
return "sucessfully delete " messages
COLLABORATION NAME: DELETE
22
1: clicks on "delete " button
:
3: key in information(name) : Main Homepage 4: select "delete" button 2: display
9: "sucessfully delete " messages
: Delete page
6: check information
5: send information 7:
8: return : Delete controller
: Delete table
USE CASE DESCRIPTION: V S ia l e e w s Ip te r e s m o n
VIEW ITEM DETAILS
5.1 BRIEF DESCRIPTION This use case will enable the
salesperson to view item 5.2 PRE-CONDITION
The products must be stored in database 5.3 PRIMARY ACTOR: Salesperson 5.4 FLOW OF EVENTS 5.4.1 BASIC FLOW 23
•
This uses case begins when the salesperson clicks on “view Item” button
•
The system shall send information and retrieved the information from the Item
•
The system return the information
5.4.2 ALTERNATINE FLOW Not Applicable 5.4.3 EXCEPTIONAL FLOW Not Applicable 5.5 POST CONDITION •
Salesperson will be able to view details of an item
5.6 CONSTRAINT •
Salesperson must key in letters of an item.
USE CASE NAME: VIEW ITEM DETAILS
: SalePerson
: Homepage
: ViewItemDetails
: ItemTable
Click An Item Send Information
Success
Return
DisplayItemDetails
24
COLLABORATION NAME: VIEW ITEM DETAILS 1: Click An Item
: Homepage
: SalePerson 6: DisplayItemDetails 3: Success 2: Send Information
4:
5: Return : ViewItemDetails
: ItemTable
USE CASE DESCRIPTION: SEARCH ITEM
Sales Person
Search item
6.1 BRIEF DESCRIPTION: This use case will enable the salesperson to search an item 6.2 PRE CONDITION: •
Salesperson must to the system
•
The products must be stored in database
6.3 PRIMARY ACTOR: Salesperson 6.4 FLOW OF EVENTS: 6.4.1 BASIC FLOW •
The use case begin when the salesperson key in the first letter of an item in the search function on the main homepage.
•
The salesperson will select an item that you want and select “search” button. (A1: Cancel) 25
•
The system will item availability (E1: unavailable item)
•
The system will display an item details
6.4.2 ALTERNATIVE FLOW •
A1: Cancel The system will display the message that the process has been cancelled
6.4.3 EXCEPTIONAL FLOW •
E1: Unavailable item The system will display the messages that item are unavailable
6.5 POST CONDITION •
Salesperson will be able to view details of an item
6.5 CONSTRAINT •
Salesperson must key in letters of an item.
: Sales Person
: Homepage
product : Search
: Item details
: Item details table
1. key in initial letters of the item
2. select particular product
3. select "search" button
A 1: Cancel
4. send information E 1: Unavailable item 5. product
6. retrieve details
7. return details
8. Display
USE CASE NAME: SEARCH ITEM
26
COLLABORATION NAME: SEARCH ITEM
1: 1. key in initial letters of the item 2: 2. select particular product 3: 3. select "search" button
: Homepage
: Sales Person
4: 4. send information5: 5. product
7: 7. return details
: Item details table
: Item details
8: 8. Display 6: 6. retrieve details product : Search
USE CASE DESCRIPTION: ADD NEW ITEM
Add new item
7.1 BRIEF DESCRIPTION: This use case will enable the to add new item in inventory. 7.2 PRE CONDITION: must to the system 7.3 PRIMARY ACTOR: 7.4 FLOW OF EVENTS: 7.4.1 BASIC FLOW •
The use case begin when the click on “add item” button.
•
The system will display add new item page.
•
will key in the item information (item ID, item name, item price) 27
•
Then, will select “proceed“ button.(Alternative1: Cancel)
•
The system will check information (item ID, item name, item price) (E1: please enter item ID) (E2: please enter item name) (E3: please enter item price)
•
will save the information
7.4.2 ALTERNATIVE FLOW •
A1: Cancel The system will display the message that the process has been cancelled
7.4.3 EXCEPTIONAL FLOW •
E1: Please enter item ID The system will display the message that item ID are invalid
•
E2: Please enter item name
•
The system will display the message that should enter item name
7.5 POST CONDITION •
will be able to add new item information
7.6 CONSTRAINT •
must key in the lecturer information USE CASE NAME: ADD NEW ITEM
28
:
: Main Homepage
: Add new item controller
: Add new item page
: Add new item table
1. select "add new item" button 2.display
3.key in item information (item ID, item name, item price)
4.select "proceed" button E1: please enter item ID
5.send information A1: cancel
E2: please enter item name
6.check information
7.retrieve item
8.save
9.return
10. display
COLLABORATION NAME: ADD NEW ITEM 1: 1. select "add new item" button
: Main Homepage
:
3: 3.key in item information 4: 4.select "proceed" button 2: 2.display 6: 6.check information 7: 7. information 8: 8.save
9: 9.return
: Add new item table
: Add new item controller 5: 5.send information : Add new item form
29
USE CASE DESCRIPTION: CHECK INVENTORY STATUS
S alespers on/sales m anager
Chec k inventory ststus
8.1 BRIEF DESCRIPTION: This case will enable the sales person and sales manager to check the inventory status. 8.2 PRE-CONDITION: The sales person and the sales manager must key in item information 8.3 PRIMARY ACTOR: Salesperson and sales manager 8.4 FLOW OF EVENTS: 8.4.1 BASIC FLOW: •
This case begins when sales person and sales manager clicks on “check inventory status” button
•
The system will display check inventory status page
•
Sales person and sales manager must key in item information (item ID) and select “proceed” button
•
The system will retrieve item. •
The system display “successfully” message
7.4.2 ALTERNATIVE FLOW •
A1: Cancel The system will display the message that the process has been cancelled
7.4.3 EXCEPTIONAL FLOW 30
•
E1: Invalid item ID The system will display the message that item ID are invalid
8.5 POST CONDITION: •
The sales person and the sales manager will be able to check inventory status.
8.6 CONSTRAINTS: •
The sales person and the sales manager must key in item ID information
USE CASE NAME: CHECK INVENTORY STATUS
: SalesPerson/Sal...
: Homepage
: Check Inventory Status Page
: Check Inventory Status Control
: Check Inventory Status Table
click on "check inventory status" button display
key in item information (item ID)
select "proceed" button A1: Cancel
send information E1: Invalid item ID check information
retrieve item
return
display "sucessfully" message
COLLABORATION NAME: CHECK INVENTORY STATUS
31
6: check information
3: key in item information (item ID) 4: select "proceed" button
: SalesPerson/Sales Manager
5: send information
: Check Inventory Status Page 8: return
: Check Inventory Status Control
1: click on "check inventory status" button 7: retrieve item 2: display 9: display "sucessfully" message
: Check Inventory Status Table
: Homepage
USE CASE DESCRIPTION: CHANGE PRICE
Change price
9.1 BRIEF DESCRIPTION: This use case will enable the to change item price 9.2 PRE CONDITION: •
must to the system
•
The item details must be stored in database
9.3 PRIMARY ACTOR: 9.4 FLOW OF EVENTS: 9.4 .1 BASIC FLOWS: •
The use case begin when the key in the price on the homepage.
•
The will select “change price” button. (A1: Cancel) 32
•
The system will item price availability (E1: A value is required)
•
The system will display change price details
9.4.2 ALTERNATIVE FLOW: •
A1: Cancel The system will display the message that the process has been cancelled
9.4.3 EXCEPTIONAL FLOW : •
E1: A value is required The system will display the message that a price value is required
9.5 POST CONDITION: •
will be able to view item details
9.6 CONSTRAINT: •
must key in the item price
USE CASE NAME: CHANGE PRICE
:
: Homepage
: Change Price Controlller
: Change Price Details
: Change Price Table
1. key in price number of the item 2. select "change price" button A1: Cancel 3. send information AE1: value is required 4.
5. retrieve details
6. return details
7. save
8. display
COLLABORATION NAME: CHANGE PRICE 33
4: 4.
:
1: 1. key in price number of the item 2: 2. select "change price" button 3: 3. send information
: Change Price Controlller
5: 5. retrieve details 6: 6. return details : Homepage
: Change Price Table
7: 7. save 8: 8. display
: Change Price Details
USE CASE DESCRIPTION: PRODUCE A RECEIPT
Salesperson
Produce a receipt
10.1 BRIEF DESCRIPTION: This use case will enable the salesperson to produce a receipt 10.2 PRE CONDITION: Salesperson must to the system 10.3 PRIMARY ACTOR: Salesperson 10.4 FLOW OF EVENTS: 10.4.1 BASIC FLOW •
The use case begin when the clicks on “produce a receipt” button.
•
It will display produce a receipt page
•
The salesperson will key in item information (item name, item price)
•
The salesperson will select “proceed” button (A1: Cancel)
•
The system will check information (E1: invalid item name) (E1: invalid item price) 34
•
The system will display “successfully” message
10.4.2 ALTERNATIVE FLOW •
A1: Cancel The system will display the message that the process has been cancelled
10.4.3 EXCEPTIONAL FLOW •
E1: invalid item name The system will display the messages that item are invalid
10.5 POST CONDITION •
Salesperson will be able to produce a receipt
10.5 CONSTRAINT •
Salesperson must key in item information
USE CASE NAME: PRODUCE A RECIEPT
: Salesperson
: Main Homepage
: Produce a receipt page
: Produce a receipt controller
: Produce receipt table
clicks on "produce a receipt" button display
key in item information (item name, item price)
select "proceed" button A1: Cancel
send information
E1: Inavalid item name
E2: Invalid item price
check information
return
display "sucessfully" message
COLLABORATION NAME: PRODUCE A RECIEPT 35
3: key in item information (item name, item price) 4: select "proceed" button
: Salesperson
1: clicks on "produce a receipt" button
: Produce a receipt page 2: display
6: check information
5: send information 9: display "sucessfully" message : Main Homepage
8: return
: Produce receipt table
7: : Produce a receipt controller
(from Logical View)
USE CASE NAME: CHECK BALANCE.
(from Logical View)
Check Balance
Inventory Manager
11.1 BRIEF DESCRIPTION This use case will enable the and inventory manager to check Balance. 11.2 PRE-CONDITION The and inventory manager should have a ID and 11.4 FLOW OF EVENTS 11.4.1 BASIC FLOW •
This use case begins when the and inventory manager clicks on “Check Balance” Button.
•
The system then display check balance page
•
The press check balance button.
•
The system will send information to the I.D and 36
•
The system will allow the to access the system if the I.D and are valid
•
The system displays the Balance.
•
The functions ends when the /Inventory manager of the system.
ALTERNATIVE FLOW Not applicable EXCEPTIONAL FLOW The ID or you entered does not match please re-enter again.
USE CASE NAME: CHECK BALANCE
: /InventoryManager
: Homepage
: BalanceController
Click on "Check Balance" Button
: BalanceTable. name or is incorrect. Pls re-enter again.
Send Info ( ) ( ) Enter ID And Check Balance ( ) Return ( ) Display "Balance"
37
COLLABORATION NAME: CHECK BALANCE
1: Click on"Check Balance" Button 4: Enter IDAnd :
: Homepage 3: ( )
7: Display "Balance"
2: SendInfo( ) 5: Check Balance( )
6: Return( )
: BalanceController
: BalanceTable.
Generate Report
InventoryManager
BRIEF DESCRIPTION
38
This use case is initiated by the and inventory manager. This use case will enable the and inventory manager to generate all the report in the system. PRE-CONDITION The and Inventory Manager should have a I.D and FLOW OF EVENTS BASIC FLOW •
This use case begins when the ( and inventory Manager clicks on “Generate report” Button.
•
The system then display Generate report in page
•
The /Inventory Manager enter his ID and
•
The press generate report button
•
The system will send information to the I.D and
•
The system will allow the to access the system of the I.D and are valid
•
The system display the generated report
•
The functions ends when the /Inventory manager of the system.
ALTERNATIVE FLOW Not applicable EXCEPTIONAL FLOW The ID or you entered does not match please re-enter again. USE CASE NAME: GENERATE REPORT
39
: Inventory manager
: Main Homepage
: Generate inventory report page
: Generate inventory report controller
: Generate inventory report table
clicks on"generate report inventory" button display
key in inventory reports information (items category, price)
click "proceed" button send information
check information
save information
return
display inventory report
COLLABORATION NAME: GENERATE REPORT 3: key in inventory reports information (items category, price) 4: click "proceed" button 1: clicks on"generate report inventory" button
: Inventory manager
2: display : Generate inventory report page
: Main Homepage
5: send information 9: display inventory report 6: check information
8: return
: Generate inventory report table
7: save information : Generate inventory report controller
40
7.3 CLASS DIAGRAM
Form name
Item Item No Types of item Price Quantity
Profile Name Phone no Address Zip code
View
() Cancel()
Add New Item()
Add New ()... update() Cancel()
Add
Name() () ID DOB SEX Email Phone No. Add new item()... Delete item() Add new ()... Delete () Change price() Dalete Change wod
Salesperson UsaerName First Name Last Name DOB SEX ID Email Phone Number
Sales Manager name First name Last name DOB SEX ID Email Phone Number
View status() View sold item() View () Search item() Produce a receipt() Cancel a receipt() Check stock() Check inventory status() ...
Check exception() Check a receipt() Check balance() Check return item() Generate sales trend()...
Inventory Manager Name First name Last Name DOB SEX ID Email Phone Number View reports() Check inventory status() ... Validate report() Generate reports() Generate trends() Change Price
View
Chance Price
Delete Name Delete ()
Change form name Submit() Cancel()
Price Page Item No Price Change Price() View Price()
41
7.4 ACTIVITY DIAGRAM ➢ View item details
Salesperson
View Item
Click On "View Item" Button
Enter (Enter the name of Item)
Click "Search" Button
[No Result]
Searching The Item
[Success]
View The Item
Display The Item Details
42
➢ Search item
Salesperson
searchItem
Key Search word
InCorect
Click Go Button
DisplaySearch Item
SearchIte m
Corect
➢ Add new 43
Click "Add " Button
System
Display Amid page
Select New Key in " Information" (Invalid) the Information
(Valid) Click On "Save " Button
Sussecceful add or Fail
44
➢ Add new item
id
ADD ITEM
Click "Add Item" button
key in "Item name"price
Check and
Click "Save" Button
Sussecceful Added
45
7.5 STATECHART DIAGRAM ➢ Search item
Salesperson key in the name of the search Item Search Item
Pending Comformation
Requesting search
Iten name Relessed View the list of the Item by Salsperson
➢ Add new item 46
Clicks on "add new item" page Add new item page Requests for add new item page Pending for add new item key in the add new item information Filled the page information approach
check confirmation save the information
Success or fail will appear the message on screen and return to homepager
47
8.0 DESIGN AND IMPLEMENTATION Differentiation between various programming languages In every stage of implementation system the web developers or system analyst will need to decide and choose which programming language the propose system will be use. When making decision on programming languages some important issues will consider such as: What database does the system working with : 1. JAVA 2. PHP 3. VISUAL BASIC JAVA
PHP
VISUAL BASIC
Java has been built from the PHP is based on Perl, it is a Visual ground
up
as
an
object general-purpose
Basic
scripting generation
oriented and will be very language initially designed for programming useful for coding inventory web development to generate associated management system.
is
a
event
thirddriven
language
and
development
dynamic web pages and PHP surroundings from Microsoft code is embedded into the for its COM programming HTML source document.
model.
Java applications are normally PHP is an interpreted scripting Scripting languages such as compiled to byte code that is language almost always run on VBA able to run on any Java virtual a
server
machine (JVM) regardless of function
for of
computer architecture.
clients
Advantages:
Advantages:
the
and
VBScript
are
primary syntactically similar to Visual
responding
to Basic, but perform differently.
Advantages:
1) Easy to use object-oriented 1) It runs fast and doesn't tend 1) friendly and interface programming language when to slow other processes down compared
to
the
2) Simple and easy to use
popular 2) PHP uses a modular system 3) Powerful front end tool
programming language.
of extensions to interface with 4) Low cost
2) Java is interpreted to run a variety of libraries. Java programs
5) It is reachable with
3) PHP community is willing documentation in most tools
3) The compiler, interpreter, to share and Java-compatible browsers 4) PHP can run on both include some levels of security
Windows servers and UNIX 48
Disadvantages:
Disadvantages:
Disadvantages:
1) Low speed
1) Web programming tools is 1) Does not side-by-
2) It runs slowly compared to freely accessible to protection side execution other programs
flaws.
3) The programs do not always 2)
Need
work properly even if they are variables written correctly
2) Large talent to
control
coming
pool of
the competition and 3) Cannot handle pointers
accessible between pages.
directly
3) Need to add java or java code other client-side tools in the output
INVIDIVIDUAL REPORT
49
The group Assignment consists of four (4) . The Assignment is to develop an online inventory Management system. We have meeting with all the group normally three times in a week, and the Assignment task was distributed for each of the group member. My task in the Assignment is to analyze the feasibility of the system, Four (4) use case diagrams and their description each and sequence diagram. Another task done by me is the Drawing of the Class diagram. After finishing the individual task given to each member of the group, we later on compile all together and we check and edit some errors together before printing the work.
10.0 CONCLUSION
50
In conclusion, an online Sales and Inventory Management System is a perfect solution for the keeping they record of the store. The system can be used as a tool to maintain due to the cost of material, human errors, less data integrity, difficulty in searching and retrieving product and feasible loss of records and retrieving files. We were following SDLC phases such as planning, analysis, design and implementation of system to come out with a full documentation. Then, we also discussed the advantages of programming languages as you see in the documentation.
REFERENCES
51
➢ Bell, D. Morrey, I. and Pugh, J. (1987-1993). Software Engineering : A Programming
Approach. 2nd ed. Britain: Prentice Hall. p32-56. ➢ Champeaux, D. D. Lea, D. and Faure, P. (1994). Object-Oriented System
Development. Canada: Addison-Wesley. p25-60. ➢ Quatrani, T (1998). Visual Modeling with Rational Rose 2000 and UML. United
States of America: Addison-Wesley. p34-50. ➢ Shammas, C. N. (1954). Visual C++ Generic Programming. United States of
America: McGraw Hill. p1-20. ➢ Wilkie, G (1994). Object-Oriented Software Engineering : The Professional
Developer's Guide. United States of America: Addison-Wesley. p1-200. ➢ Hentzen, W. (1995). Programming Visual FoxPro 3.0. Ziff-Davis Publishing: United
States of America. p1-200. ➢ O’Brien, J (1999). Management Information Systems – Managing Information
Technology in the Internetworked Enterprise. Boston: Irwin McGraw-Hill. ➢
Kroenke, D M. (2008). Experiencing MIS. Prentice-Hall, Upper Saddle River, NJ
➢ O'Brien, J A. (2003). Introduction to information systems: essentials for the ebusiness enterprise. McGraw-Hill, Boston, MA ➢ Alter, S. The Work System Method: Connecting People, Processes, and IT for Business Results. Works System Press, CA ➢ Beynon-Davies P. (2009). The ‘language’ of informatics: the nature of information
systems. International Journal of Information Management. ➢ Beynon-Davies P. (2009). Business Information Systems. Palgrave, Basingstoke ➢ Kotler, Philip; Keller, Kevin Lane (2006). Marketing Management (12 ed.). Pearson
Education ➢ Keen, P. G. W. (1978). Decision systems: an organizational perspective.
Reading, Mass., Addison-Wesley Pub. Co. ➢ Efraim Turban, Jay E. Aronson, Ting-Peng Liang (2008). Decision Systems
and Intelligent System ➢ Holsapple, C.W., and A. B. Whinston. (1996). Decision Systems: A
Knowledge-Based Approach. St. Paul: West Publishing. ➢ MS, 2007, Java Advantages and Disadvantages, viewed 17 November 2011,
http://www.webdotdev.com/nvd/content/view/1042/204/ ➢ Webodia, n.d., programming language, viewed 17 November 2011,
http://www.webopedia.com/TERM/P/programming_language.html
52
➢ Designs Playground, 2006, viewed 20 November 2011, The Advantages of PHP
http://www.designersplayground.com/articles/118/1/The-Advantages-ofPHP/Page1.html ➢ GSLOGIX, 2011, viewed 20 November 2011, Advantages and disadvantages of
PHP , http://www.gslogix.com/blog/2011/10/advantages-and-disadvantages-of-php/ ➢ Voegele, J. (2004), Last viewed 20 September1 2011.Programming Languange
Comparison. Available: http://www.jvoegele.com/software/langcomp.html.
53
Related Documents 3h463d
Smart Inventory Management System 5i3t4w
December 2019 47
Online Inventory Management System 4g196q
November 2019 60
Inventory Management System. 1p6333
April 2020 29
Inventory Management System 6v296n
April 2020 15
Inventory Management System Documentation 32po
November 2022 0