Inventory Management System.

(1)

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, users are able to work more efficiently and produce higher quality accounting 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,

(2)

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, Administrator, 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 admin to uses online Sales and Inventory Management System.

System requirement By using online Sales and Inventory Management System,

users can access online system easily and quickly with a function that should be in the system. These systems also facilitate users to:

• store the details of the inventory

• update the inventory based on the sale details

• produce receipts for sales

• generate sales and inventory reports periodically

System value 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 username and password to access the system.

• Top level security needed by project team for

protection from unauthorized users.

• The system should be built before December 2014.

(3)

4.1 USER REQUIREMENTS

The main users in this system are salespersons, sales managers, inventory managers and administrators. By using this system, users can access online Sales and Inventory Management System with some function. The system will allow them to login and key in the main requirement in the update item details and price form. Inventory managers/sales managers/administrator 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. Administrator also can add new user for the system.

4.2 FUNCTIONAL REQUIREMENTS

A requirement specifies a function that a system or component must be able to allow the user 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.

(4)

No Requirement name Requirement Description Priority

1 Log in This function will enable

salespersons/inventory managers/sales managers/administrators. to log in to the system.

Mandatory requirement

2 Change password This function will enable salesperson/

inventory managers/ sales managers/administrators to change

password.

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

Optional requirement

6 View Sold item This function will enable the

salespersons to sold an item

7 View Feedback This function will enable the

salespersons to key in feedback

8 Check stock This function will enable the

salespersons to check stock in inventory

9 Check inventory

status

This function will enable the salespersons/ inventory managers to

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.

(5)

4.3 NON FUNCTIONAL REQUIREMENTS

• The Salesperson Inventory manager Administrator must be able to access their

account 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 users. By using username and

password.

• Also system show error if the username or password is not correct

• To use the system, every user has to login by key in their username and password.

2) Performance

• The time system required to process and respond when a user key in the

Identification that is username and password

• 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

(6)

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

SOFTWARE SPECIFICATION

1 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 terms of the familiarity of the new technology used, the users have knowledge with most type of the technologies in the new system, like the databases and other internet

(7)

technologies. And for some few new unfamiliar technologies there are consultants to guide the users on how to use them.

Project Size of the system is considered medium risk. The project team consists of four people, and the business users 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

(8)

• Printer RM 100,000

• 2 servers 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 accounting 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 users 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 user’s access levels and the system will only allow privileged users, authentication, authorization and audit procedures will be facilitated to the system administrators. And data retrieval and the data presenting will be by the system, so the report generated will be automated by the system.

(9)

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 administrator wants to log in or change his password 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 users, View price/ update price, view record, also make log in, and change password, this will lead to the fast interaction among users and administrator. 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, feedback, 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 administrator 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

(10)

7.1 USE CASE DIAGRAMS (IMPROVEMENTS)

7.2 USE CASE DIAGRAMS

UpdateInformation ChangepassWord DeleteUser DeleteItems AddNewItems <<extend>> AddNewUser <<extend>> ChangePrice CheckReciepts CheckBalance CheckReturnIterms GenerateSaleTrend SelesManager GenerateReports ViewReports GenerateTrende ValidateReport CheckStatus ViewStatus CancelReceipt ProduceReceipt ViewSoldItems

Check StocketViewFeedback

SearchItem SelesPerson Login <<extend>> ViewCalendar <<extend>> BackupData Administrator MaintainDabase <<extend>> InventoryManager

(11)

ChangepassWord DeleteUser DeleteItems AddNewItems <<extend>> AddNewUser <<extend>> ChangePrice CheckReciepts CheckBalance CheckReturnIterms GenerateSaleTrend Administrator SelesManager GenerateReports ViewReports GenerateTrende ValidateReport CheckStatus InventoryManager ViewStatus CancelReceipt ProduceReceipt ViewSoldItems

Check StocketViewFeedback

SearchItem SelesPerson

Login <<extend>>

(12)

1.1 BRIEF DESCRIPTION

This use case is initiated by the salesperson, inventory managers, sales managers, and administrator. This use case will enable the customer, administrator and sales person to sign in into the system

1.2 PRE-CONDITION

The user should have a username and password

1.3 PRIMARY ACTOR: Salesperson, inventory managers, sales managers, and administrator 1.4 FLOW OF EVENTS

1.4.1 BASIC FLOW

• The use case begins when the (salesperson, inventory managers, sales managers,

administrator) click on “sign in” button

• The system then display sign in page

• The user fill in username and password

• The user press “log in” button

• The system will send information to verify the username and password

• The system will allow the user to access the system if the username and Password are

valid.

• The system display user account

• The functions ends when the user logout the system.

1.4.2 ALTERNATIVE FLOW

• A1: Cancel

The system shall use message “the Login can cancelled by user demand”. 1.4.3 EXCEPTIONAL FLOW

• E1: The username you enter is not on record. Please re-enter your username

• E2: The username and password you entered are not associated with an existing

1.5 POST- CONDITION

• User will be able to login

1.6 CONSTRAINT

• The password must contain at least 15 characters.

salesperson/ inventory managers/ sales managers/administrator

(13)

USE CASE NAME: LOGIN

COLLABORATION NAME: LOGIN

: Customer

: Customer : Barnesandnoble : Barnesandnoble : Signinpage : Signinpage : Logincontroller : Logincontroller : Useraccounttable : Useraccounttable : Myaccountpage : Myaccountpage click "sign in" hyperlink

display fill in email and password

press "sign in" button

send check information E1:The Email address you enter is not... E2:The Email address and password ... verify informaton return activate account view account

(14)

USE CASE DESCRIPTION: CHANGE PASSWORD

This use case will enable the salesperson, inventory managers, sales managers, and administrators to change they password.

2.2 PRE-CONDITION

User must have old password to change the password in the system

2.3 PRIMARY ACTOR: Salesperson/ inventory managers/sales managers/administrators 2.4 FLOW OF EVENTS

2.4.1 BASIC FLOW

• The use case begin when the, salesperson, inventory managers, sales managers,

administrators press “change password” button

• The system then display account form

• The salesperson, inventory managers, sales managers, administrators. key in the

salesperson/ inventory managers/ sales managers/ administrators

Change password : Customer : Barnesandnoble : Signinpage : Logincontroller : Useraccounttable : Myaccountpage 1: click "sign in" hyperlink

2: display 3: fill in email and password

4: press "sign in" button

5: send 6: check information 7: verify informaton 8: return 9: activate account 10: view account

(15)

name, username and password

• The inventory managers, sales managers, administrators press “save change”

button

• The system send information to controller

• The system check the information and verify the information (E1: Problem with

current password)

• The system save the information and return

• The system display your profile, password has been updated

2.4.2 ALTERNATE FLOW

• A1: Cancel

The system shall use message “the change password process can cancelled by user demand”.

2.4.3 EXCEPTIONAL FLOW

• E1: Problem with current password

2.5 POST CONDITIONS

• Salesperson/ inventory managers/sales managers/administrators will be able to change

the password 2.6 CONSTRAINT

(16)

USE CASE NAME: CHANGE PASSWORD

COLLABORATION NAME: CHANGE PASSWORD : All Actors

: All Actors : Homepage : Homepage : Account Setting : Account Setting : Change Password : Change Password : Database : Database Click "Account Setting" Option

Display

Enter Current Password, New Password, Re-enter New Password

Click "Save New Password" Button

Send Information Success E1: Problem With Current Password Verify Return Display

(17)

: All Actors : Homepage

: Account Setting : Change Password

: Database 6: Success 1: Click "Account Setting" Option

3: Enter Current Password, New Password, Re-enter New Password 4: Click "Save New Password" Button

2: Display

5: Send Information

7: Verify 8: Return

(18)

USE CASE DESCRIPTION: ADD NEW USER

This user cases well enable the administrator to add new user. 3.2 PRE CONDITION

The administrator must view his homepage 3.3 PRIMARY ACTOR: Administrator 3.4 FLOW OF EVENTS:

3.4.1 BASIC FLOW

• The use case begin when the administrator clicks on “Add New User” button

(19)

• The system display the new user page

• The administrator key in User information (full name, address, phone number, email)

• The administrator 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 user” messages

3.4.2 EXCEPTIONAL FLOW

• E1: Please enter full name

The system will display the messages that user should enter full name

• E2: Please enter an address

The system will display the messages that user should enter an address 3.4.13 ALTERNATIVE FLOW

• A1: cancel: The system must display a message “cancel by user demand”

3.5 POST CONDITION

The administrator will be able to add new user in the user table on the database 3.6 CONSTRAINTS

The administrator must key in new user information.

(20)

: Administrator : Main Homepage : Add New User Page : Add New User

Controller : Add New User Table

clicks on "Add New User" button

display

Key in user information (full name, address, phone number, email)

select "proceed" button

send information A1: Cancel check information reretrieve item save return sucessfully add new user

E1: Please enter full name

E2: Please enter address

COLLABORATION NAME: ADD NEW USER

: Main Homepage : Administrator

: Add New User Page

: Add New User Controller : Add New User Table

1: clicks on "Add New User" button

2: display 3: Key in user information (full name, address, phone number, email)

4: select "proceed" button

5: send information 6: check information

7: reretrieve item 8: save

9: return

(21)

A d m i n i s t r a t o r D e l e t e U s e r

USE CASE DESCRIPTION: DELETE USER

This use case will enable the administrator to delete user. 4. 2 PRE-CONDITION

The administrator must view his homepage 4.3 PRIMARY ACTOR: administrator 4.4 FLOW OF EVENTS

4.4.1 BASIC FLOW

 This use case begins when the administrator click on “delete user” button

 The system then display delete user page

 The administrator key in users information (name)

 The administrator click delete button (A1 :Cancel)

 The system send information and check the information (E1:invalid name)

 The system verify the information and return

 The system display the message of successfully deleted user

(22)

4.4 CONSTRAINT

• Administrator must key in users information (name).

USE CASE NAME: DELETE USER

: Administrator : Main Homepage : Delete user page : Delete user controller : Delete user table

clicks on "delete user" button

display

key in user information(name)

send information

check information

verify

return "sucessfully delete user" messages

A1: Cacel

E1: Invalid name

(23)

S a l e s p e r s o n V i e w I t e m

: Administrator : Main Homepage

: Delete user page

: Delete user controller : Delete user table 1: clicks on "delete user" button

2: display 3: key in user information(name)

4: select "delete" button

5: send information 6: check information

7: verify

8: return

9: "sucessfully delete user" messages

USE CASE DESCRIPTION: VIEW ITEM DETAILS

(24)

• 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

: SalePerson : Homepage : Homepage : ViewItemDetails : ViewItemDetails : ItemTable : ItemTable Click An Item Send Information Success Verify Return DisplayItemDetails

(25)

COLLABORATION NAME: VIEW ITEM DETAILS 5: Return : SalePerson : Homepage : ViewItemDetails : ItemTable 3: Success 1: Click An Item 2: Send Information 6: DisplayItemDetails 4: Verify

USE CASE DESCRIPTION: SEARCH ITEM

6.1 BRIEF DESCRIPTION:

This use case will enable the salesperson to search an item 6.2 PRE CONDITION:

• Salesperson must login to the system

(26)

• The system will verify item availability (E1: unavailable item)

• The system will display an item details

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

USE CASE NAME: SEARCH ITEM

: Homepage verify product : Search : Item details : Item details table

4. send information 5. verify product 6. retrieve details 7. return details E 1: Unavailable item 8. Display : Sales Person

1. key in initial letters of the item

2. select particular product

3. select "search" button

(27)

COLLABORATION NAME: SEARCH ITEM

USE CASE DESCRIPTION: ADD NEW ITEM

This use case will enable the administrator to add new item in inventory.

: Sales Person : Homepage

verify product : Search

: Item details table : Item details

1: 1. key in initial letters of the item 2: 2. select particular product

3: 3. select "search" button

4: 4. send information5: 5. verify product

6: 6. retrieve details 7: 7. return details

8: 8. Display

Add new item Administrator

(28)

• Then, Administrator 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)

• Administrator will save the information

• A1: Cancel

• 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 user should enter item name

7.5 POST CONDITION

• Administrator will be able to add new item information

7.6 CONSTRAINT

• Administrator must key in the lecturer information

(29)

: Administrator : Main Homepage : Add new item page : Add new item controller : 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

5.send information 7.retrieve item 6.check information 9.return 8.save A1: cancel 10. display E1: please enter item ID E2: please enter item name

COLLABORATION NAME: ADD NEW ITEM

: Administrator : Main Homepage

2: 2.display 1: 1. select "add new item" button

3: 3.key in item information 4: 4.select "proceed" button

(30)

USE CASE DESCRIPTION: CHECK INVENTORY STATUS

This user 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 user 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

• A1: Cancel

(31)

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

: Check Inventory Status Page : Check Inventory Status Control

: Check Inventory Status Table : Homepage

click on "check inventory status" button

display

key in item information (item ID)

send information

check information

retrieve item

return

display "sucessfully" message A1: Cancel

E1: Invalid item ID

(32)

: SalesPerson/Sales Manager

: Check Inventory Status Page : Check Inventory Status Control

: Check Inventory Status Table

: Homepage 1: click on "check inventory status" button

2: display 3: key in item information (item ID)

4: select "proceed" button 5: send information

6: check information

7: retrieve item 8: return

9: display "sucessfully" message

USE CASE DESCRIPTION: CHANGE PRICE

This use case will enable the administrator to change item price 9.2 PRE CONDITION:

• Administrator must login to the system

• The item details must be stored in database

9.3 PRIMARY ACTOR: Administrator 9.4 FLOW OF EVENTS:

9.4 .1 BASIC FLOWS:

• The use case begin when the administrator key in the price on the administrator

homepage.

• The administrator will select “change price” button. (A1: Cancel)

Change price Administrator

(33)

• The system will verify 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:

• Administrator will be able to view item details

9.6 CONSTRAINT:

• Administrator must key in the item price

USE CASE NAME: CHANGE PRICE

: Administrator : Administrator Homepage : Change Price

Controlller : Change Price Details : Change Price Table

1. key in price number of the item 2. select "change price" button

3. send information 4. verify 5. retrieve details A1: Cancel AE1: value is required

(34)

: Administrator

: Administrator Homepage

: Change Price Controlller

: Change Price Details : Change Price Table

4: 4. verify

1: 1. key in price number of the item

2: 2. select "change price" button 3: 3. send information

5: 5. retrieve details 6: 6. return details

7: 7. save 8: 8. display

USE CASE DESCRIPTION: PRODUCE A RECEIPT

This use case will enable the salesperson to produce a receipt 10.2 PRE CONDITION:

Salesperson must login 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)

(35)

• The system will display “successfully” message 10.4.2 ALTERNATIVE FLOW

• A1: Cancel

• 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 : Produce receipt table

controller clicks on "produce a receipt" button

display

key in item information (item name, item price)

send information A1: Cancel E1: Inavalid item name E2: Invalid item price

(36)

Check Balance Administrator

(from Logical View)

Administrator (from Logical View)

Inventory Manager

: Main Homepage

: Salesperson : Produce a receipt page

: Produce receipt table : Produce a receipt controller 6: check information

1: clicks on "produce a receipt" button 3: key in item information (item name, item price)

4: select "proceed" button

2: display

5: send information

7: verify 8: return

9: display "sucessfully" message

USE CASE NAME: CHECK BALANCE.

This use case will enable the administrator and inventory manager to check Balance. 11.2 PRE-CONDITION

The admin and inventory manager should have a user ID and password 11.4 FLOW OF EVENTS

11.4.1 BASIC FLOW

• This use case begins when the administrator and inventory manager clicks on “Check

Balance” Button.

• The system then display check balance page

• The Admin press check balance button.

(37)

• The system will allow the user to access the system if the user I.D and password are valid

• The system displays the Balance.

• The functions ends when the Admin/Inventory manager logout of the system.

ALTERNATIVE FLOW Not applicable

EXCEPTIONAL FLOW

The user ID or password you entered does not match please re-enter again.

USE CASE NAME: CHECK BALANCE

:

Admin/InventoryManager :

Admin/InventoryManager : Homepage : Homepage _:

BalanceController : BalanceController : BalanceTable. : BalanceTable.

Click on "Check Balance" Button

Send Info ( )

Verify ( )

Check Balance ( ) Return ( ) Display "Balance"

Enter User ID And Password

User name or Password is incorrect. Pls re-enter again.

(38)

COLLABORATION NAME: CHECK BALANCE BRIEF DESCRIPTION Administrator InventoryManager Generate Report : Administrator : Homepage : BalanceController : BalanceTable. 1: Click on "Check Balance" Button

2: Send Info ( ) 3: Verify ( )

4: Enter User ID And Password

5: Check Balance ( )

6: Return ( ) 7: Display "Balance"

(39)

This use case is initiated by the administrator and inventory manager. This use case will enable the administrator and inventory manager to generate all the report in the system.

PRE-CONDITION

The Admin and Inventory Manager should have a user I.D and password FLOW OF EVENTS

BASIC FLOW

• This use case begins when the (administrator and inventory Manager clicks on

“Generate report” Button.

• The system then display Generate report in page

• The Admin/Inventory Manager enter his user ID and password

• The Admin press generate report button

• The system will send information to verify the user I.D and password

• The system will allow the user to access the system of the user I.D and password are

valid

• The system display the generated report

• The functions ends when the Admin/Inventory manager logout of the system.

ALTERNATIVE FLOW Not applicable

EXCEPTIONAL FLOW

The user ID or password you entered does not match please re-enter again. USE CASE NAME: GENERATE REPORT

(40)

: Inventory manager

: Generate inventory report page

: Main Homepage : Generate inventory

report table : Generate inventory

report controller clicks on"generate report inventory" button

display

click "proceed" button

send information

check information

save information

return

display inventory report key in inventory reports information (items category, price)

COLLABORATION NAME: GENERATE REPORT

: Generate inventory report table

: Inventory manager : Generate inventory report page : Main Homepage

: Generate inventory report controller 2: display 5: send information 6: check information 7: save information 8: return

9: display inventory report 1: clicks on"generate report inventory" button

3: key in inventory reports information (items category, price) 4: click "proceed" button

(41)

7.3 CLASS DIAGRAM Item Item No Types of item Price Quantity Add New Item()

Login Form Username Password Login() Cancel() user Profile Name Phone no Address Zip code Add New User()... update() Cancel() Delete User Name Delete User() View Salesperson UsaerName Password First Name Last Name DOB SEX ID Email Phone Number View status() View sold item() View feedback() Search item() Produce a receipt() Cancel a receipt() Check stock() Check inventory status() ...

Sales Manager Username password First name Last name DOB SEX ID Email Phone Number Check exception() Check a receipt() Check balance() Check return item() Generate sales trend()...

Price Page Item No Price Change Price() View Price() Inventory Manager User Name Password First name Last Name DOB SEX ID Email Phone Number View reports() Check inventory status() ... Validate report() Generate reports() Generate trends() Login Administrator Admin Name() Password() Admin ID DOB SEX Email Phone No. Add new item()... Delete item() Add new user()... Delete user() Change price() Change Password form Username Password Submit() Cancel() Change Passwod Change Price Login Login Login Add

View Chance Price Dalete

(42)

7.4 ACTIVITY DIAGRAM

➢ View item details

Click On "View Item" Button

Enter (Enter the name of Item)

Click "Search" Button

View The Item

Searching The Item [No Result] Display The Item Details [Success] View Item Salesperson

(43)

➢ Search item Click Go Button Key Search word DisplaySearch Item VerifySearchIte m Corect InCorect searchItem Salesperson

(44)

Click "Add User" Button Key in "User Information" Click On "Save " Button Select New User Verify the Information (Valid) Sussecceful add or Fail Display Amid page (Invalid) System Administrator

(45)

➢ Add new item

Click "Add Item" button

key in "Item name"price

Click "Save" Button Check and Verify Sussecceful Added ADD ITEM Admid

(46)

7.5 STATECHART DIAGRAM ➢ Search item Verify Iten name Search Item Salesperson key in the name of the search Item Pending Comformation Requesting search Relessed

View the list of the Item by Salsperson

(47)

Add new item page

Pending for add new item

Filled the page

Clicks on "add new item" page

Requests for add new item page

key in the add new item information

information approach

check confirmation

save the information

Success or fail

will appear the message on screen and return to homepager

(48)

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 ground up as an object oriented and will be very useful for coding inventory management system.

PHP is based on Perl, it is a

general-purpose scripting

language initially designed for web development to generate dynamic web pages and PHP code is embedded into the HTML source document.

Visual Basic is a

third-generation event driven

programming language and

associated development

surroundings from Microsoft for its COM programming model.

Java applications are normally compiled to byte code that is able to run on any Java virtual machine (JVM) regardless of computer architecture.

PHP is an interpreted scripting language almost always run on a server for the primary function of responding to clients

Scripting languages such as VBA and VBScript are syntactically similar to Visual Basic, but perform differently.

Advantages:

1) Easy to use object-oriented programming language when compared to the popular programming language.

2) Java is interpreted to run Java programs

3) The compiler, interpreter,

and Java-compatible browsers include some levels of security

Advantages:

1) It runs fast and doesn't tend to slow other processes down 2) PHP uses a modular system of extensions to interface with a variety of libraries.

3) PHP community is willing to share

4) PHP can run on both Windows servers and UNIX

Advantages:

1) User friendly and interface 2) Simple and easy to use 3) Powerful front end tool 4) Low cost

5) It is reachable with documentation in most tools

(49)

Disadvantages: 1) Low speed

2) It runs slowly compared to other programs

3) The programs do not always work properly even if they are written correctly

Disadvantages:

1) Web programming tools is freely accessible to protection flaws.

2) Need to control the variables coming and accessible between pages. 3) Need to add java or java code other client-side tools in the output

Disadvantages:

1) Does not support side-by-side execution

2) Large talent pool of competition

3) Cannot handle pointers directly

(50)

The group Assignment consists of four (4) members. The Assignment is to develop an online inventory Management system. We have meeting with all the group members 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.

(51)

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.

(52)

➢ 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

e-business 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 support systems: an organizational perspective.

Reading, Mass., Addison-Wesley Pub. Co.

➢ Efraim Turban, Jay E. Aronson, Ting-Peng Liang (2008). Decision Support Systems

and Intelligent System

➢ Holsapple, C.W., and A. B. Whinston. (1996). Decision Support 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,

(53)

➢ Designs Playground, 2006, viewed 20 November 2011, The Advantages of PHP

http://www.designersplayground.com/articles/118/1/The-Advantages-of-PHP/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