This action might not be possible to undo. Are you sure you want to continue?
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, retrieved and stored
• • •
10 SYSTEM REQUEST
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 Project need AbdulKareem, project manager 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: • • • • 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. •
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.
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.
Requirement name Log in
Requirement Description This function will enable salespersons/inventory managers/sales managers/administrators. to log in to the system.
Priority Mandatory requirement
This function will enable salesperson/ inventory managers/ sales managers/administrators to change password.
This function will enable salespersons to view status.
Mandatory requirement Mandatory requirement Mandatory requirement Optional requirement Mandatory requirement Mandatory requirement Mandatory requirement Mandatory requirement Mandatory requirement Mandatory requirement Mandatory requirement
Cancel a receipt
This function will enable the salespersons to check a receipt
Produce a receipt
This function will enable the salespersons to check a receipt
This function will enable the salespersons to search an item
View Sold item
This function will enable the salespersons to sold an item
This function will enable the salespersons to key in feedback
This function will enable the salespersons to check stock in inventory
Check inventory status
This function will enable the salespersons/ inventory managers to check details This function will enable the inventory managers to validate report
This function will enable the inventory managers to generate trend
This function will enable the inventory managers to view reports.
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. Sale and Inventory Management system is a standalone system which has four to five (4 – 5) users and users must have to use it during operating hours 3) Availability
4.4 HADWARE AND SOFTWARE REQUEREMENTS HADWARE REQUEREMENTS HARDWARE 1 2 Processor Keyboard SPECIFICATION Intel Pentium4 Processor 1,600GHz Standard key board
the organization has little experience with the new inventory system because the previous system and the new one has some features alike.0 FEASIBILITY STUDY a) TECHNICAL The inventory management system the system is going to be developed using php and sql server as database linkage. like the databases and other internet 6 . Also in terms of the familiarity of the new technology used. The system is technically feasible. even though there are some risks.5 NETWORK REQUIREMENTS 5.0 Asp. the users have knowledge with most type of the technologies in the new system.1/7-zip for extracting a files 4.net.3 4 5 Hard Drive Network Adapter Printer 80GB 5400RPM /8M/PATA) PCI 10/100 Ethernet Adapter Ink jet printer attached in wireless SOFTWARE REQUEREMENTS SOFTWARE 1 Operating System SPECIFICATION Windows 7 Professional and Windows Server 2008 R2 2 Anti-Virus Software Norton antivirus software 3 4 5 6 7 Spread Sheet Internet Tool Programming Tool Backup Software File Utilities Tool Microsoft Excel Microsoft Internet Explorer version 6. SQL CD-R/CD-RW Disk and Data tape/hard disk Win Rar 8. Regarding the familiarity with the newly developed system. but the new system has more functions than the previous one.
000 RM 25.000 TOTAL=RM 220. The development is going to last for approximately three 3 months.875 7 . the company is going to gain the profit above the previous one from the current system.000 RM 30. Buying the components is going to cost the organization a lot of money.000 RM 100. 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. Project Size of the system is considered medium risk. 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 Hard ware Maintenance Electricity Operational labour RM 50. but compared to the amount that the organization used in building the current system.252 RM 10. In the long run.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 Server software Software licenses RM 1.246. and the business users will also be involved.976 RM 34. The project team consists of four people. The System compatibility with the current technical infrastructure is good and will be compatible with all the organizational situations. And for some few new unfamiliar technologies there are consultants to guide the users on how to use them.000 RM 15.technologies. paying the employees monthly salary and allowances is compared nothing to the one time expense for the new project.
000 INTANGIBLE BENEFITS: Also called soft benefits. authorization and audit procedures will be facilitated to the system administrators.000 TOTAL=RM 75. such as the security issues: in which user’s access levels and the system will only allow privileged users. because the system is well accepted by the top management of the organization.000 RM 10.000 TOTAL= RM 1. And data retrieval and the data presenting will be by the system. because it solved most of the problems and it satisfies all the requirements needed by them.000 RM 20.000 RM 5.103 TANGIBLE BENEFITS: Regarding the tangible benefits when the organizations business process is automated.000 TOTAL=RM 828. so the report generated will be automated by the system. the system has low risk.517. and other users have strong interest in it. are the gains attributable to your improvement in project that are not reportable for formal accounting purposes.000 RM 321.000 RM 125.000 RM 15.000 RM 70.000 RM 68. 8 . authentication.000 RM 20.000 c) ORGANIZATIONAL FEASIBILITY From the organizational viewpoint. 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.• • Printer 2 servers RM 100. These benefits are not included in the financial calculations because they are not nonmonetary or they are difficult to measure: • • • • • Increased in market share Increased Brand recognition Better supplier relation Improved customer service High quality product RM 25.com The benefit is seen as the profit that the organization is going to obtain after the system is automated: • • • • • Increase in sales Reduction in inventory cost Reduction in customer’s complaint Reduction in staff salary Reduction IT cost RM 349.
6. the normal system that they are using still using paper base system to enter the transaction. Inventory manager services.0 UML DIAGRAMS 9 . The system is fully computerizing system. and change password. 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. and communication.0 ANALYSIS STRATEGY A) ANALYSIS OF AS IS SYSTEM Currently. The improvement of the new system is view calendar. Which the movement of our technologies. change price. c) PROPOSED TO BE SYSTEM By using this system. View price/ update price. Inventory manager complain about the inconsistence in the manual record of transaction procedure. maintain database. We lead to files or records that having high probability to lost either by natural disaster or human error. view staff information. As we familiar with the current system which based on paper base always has problem in time consuming. b) IMPROVEMENTS The new system will have some unique functionality of add new users. Inventory manager. For instance. most of the Store still using normal or manual system to manage their transaction and day to day activities. 7. some of the store are interested in make an evolution by changing the methods on how to managing a store. which allows salesperson. this will lead to the fast interaction among users and administrator. most problems faced in the store will be eliminated. This is done by the means of the Online Sale and Inventory Management System. man errors to do the entire duty. and backup. Now. view record. Almost salesperson. and administrator to use the system immediately once they fill the record of the sale. also make log in. sale manager. 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. 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. feedback. if the administrator wants to log in or change his password or the file of the salesperson can see clearly.
7.2 USE CASE DIAGRAMS 10 .1 USE CASE DIAGRAMS (IMPROVEMENTS) ViewStatus CancelReceipt CheckReciepts ProduceReceipt ChangepassWord SelesPerson CheckBalance SearchItem <<extend>> ViewSoldItems Login SelesManager CheckReturnIterms Check Stocket ViewFeedback <<extend>> GenerateSaleTrend ViewCalendar UpdateInformation <<extend>> MaintainDabase BackupData CheckStatus <<extend>> AddNewItems Administrator ValidateReport DeleteItems AddNewUser InventoryManager GenerateTrende <<extend>> DeleteUser ViewReports ChangePrice GenerateReports 7.
ViewStatus CancelReceipt CheckReciepts ProduceReceipt ChangepassWord SelesPerson CheckBalance SearchItem <<extend>> ViewSoldItems Login SelesManager CheckReturnIterms Check Stocket ViewFeedback GenerateSaleTrend CheckStatus <<extend>> AddNewItems Administrator ValidateReport DeleteItems AddNewUser InventoryManager GenerateTrende <<extend>> DeleteUser ViewReports ChangePrice GenerateReports USE CASE DESCRIPTION: LOG IN 11 .
sales managers.CONDITION • User will be able to login 1.salesperson/ inventory managers/ sales managers/administrator Login in 1.5 POST.4 FLOW OF EVENTS 1. Please re-enter your username E2: The username and password you entered are not associated with an existing 1. inventory managers.2 ALTERNATIVE FLOW 1. and administrator. This use case will enable the customer.4.1 BASIC FLOW • The use case begins when the (salesperson. 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.2 PRE-CONDITION The user should have a username and password 1. A1: Cancel The system shall use message “the Login can cancelled by user demand”. administrator and sales person to sign in into the system 1. sales managers. and administrator 1. inventory managers. • • • • • • • • 1.4. 12 .3 EXCEPTIONAL FLOW • • E1: The username you enter is not on record.3 PRIMARY ACTOR: Salesperson.1 BRIEF DESCRIPTION This use case is initiated by the salesperson.6 CONSTRAINT • The password must contain at least 15 characters. inventory managers. The system display user account The functions ends when the user logout the system. sales managers.4.
. E2:The Email address and password .USE CASE NAME: LOGIN : Customer : Barnesandnoble : Signinpage : Logincontroller : Useraccounttable : Myaccountpage click "sign in" hyperlink display fill in email and password press "sign in" button send check information verify informaton return activate account view account E1:The Email address you enter is not. COLLABORATION NAME: LOGIN 13 ....
4 FLOW OF EVENTS 2.2 PRE-CONDITION User must have old password to change the password in the system 2. sales managers. sales managers. inventory managers.4. and administrators to change they password. administrators.1 BASIC FLOW • The use case begin when the. salesperson. inventory managers. administrators press “change password” button The system then display account form The salesperson. key in the 14 • • .3: fill in email and password 4: press "sign in" button : Customer 1: click "sign in" hyperlink 2: display : Signinpage 10: view account : Barnesandnoble 5: send 6: check information 9: activate account : Myaccountpage 7: verify informaton : Logincontroller 8: return : Useraccounttable USE CASE DESCRIPTION: CHANGE PASSWORD salesperson/ inventory managers/ sales managers/ administrators Change password 2. inventory managers. sales managers.1 BRIEF DESCRIPTION This use case will enable the salesperson.3 PRIMARY ACTOR: Salesperson/ inventory managers/sales managers/administrators 2. 2.
5 POST CONDITIONS • Salesperson/ inventory managers/sales managers/administrators will be able to change the password 2.3 EXCEPTIONAL FLOW • E1: Problem with current password 2. username and password • The inventory managers.2 ALTERNATE FLOW A1: Cancel The system shall use message “the change password process can cancelled by user demand”.name. password has been updated • • • • • 2.4. 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.6 CONSTRAINT • The password must contain at least 15 characters.4. sales managers. 15 . 2.
USE CASE NAME: CHANGE PASSWORD : All Actors : Homepage : Account Setting : Change Password : Database Click "Account Setting" Option Display Enter Current Password. Re-enter New Password Click "Save New Password" Button E1: Problem With Current Password Send Information Success Verify Return Display COLLABORATION NAME: CHANGE PASSWORD 16 . New Password.
Re-enter New Password 4: Click "Save New Password" Button 9: Display 2: Display 6: Success 5: Send Information : Account Setting : Change Password 8: Return 7: Verify : Database 17 .1: Click "Account Setting" Option : All Actors : Homepage 3: Enter Current Password. New Password.
USE CASE DESCRIPTION: ADD NEW USER A dm inis trator A dd new us er 3.4 FLOW OF EVENTS: 3.1 BRIEF DESCRIPTION This user cases well enable the administrator to add new user.1 BASIC FLOW • The use case begin when the administrator clicks on “Add New User” button 18 .4.2 PRE CONDITION The administrator must view his homepage 3.3 PRIMARY ACTOR: Administrator 3. 3.
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 • E1: Please enter full name 3.13 ALTERNATIVE FLOW • A1: cancel: The system must display a message “cancel by user demand” 3.4. phone number. USE CASE NAME: ADD NEW USER 19 .5 POST CONDITION The administrator will be able to add new user in the user table on the database 3.• • • • • • The system display the new user page The administrator key in User information (full name.2 EXCEPTIONAL FLOW 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.6 CONSTRAINTS The administrator must key in new user information. address.4.
address. phone number. email) select "proceed" button A1: Cancel send information E1: Please enter full name check information E2: Please enter address reretrieve item save return sucessfully add new user COLLABORATION NAME: ADD NEW USER 1: clicks on "Add New User" button : Administrator 3: Key in user information (full name. email) 4: select "proceed" button 2: display : Main Homepage 10: sucessfully add new user : Add New User Page 5: send information 6: check information 7: reretrieve item 8: save 9: return : Add New User Controller : Add New User Table 20 . address. phone number.: 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.
4.3 • A1: Cancel The system will display the message that “the process has been cancelled” EXCEPTIONAL FLOW E1: invalid name The system will display the messages that name do not match 4.4. 4.4 FLOW OF EVENTS 4.1 BRIEF DESCRIPTION This use case will enable the administrator to delete user.2 ALTERNATE FLOW • 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 display the message of successfully deleted user The system verify the information and return 4.USE CASE DESCRIPTION: DELETE USER D A e d l m e i t n e i s U t s r e a r t o r 4.4 POST CONDITION • Administrator will be able to delete user in the system 21 .3 PRIMARY ACTOR: administrator 4. 2 PRE-CONDITION The administrator must view his homepage 4.
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) select "proceed" button A1: Cacel send information E1: Invalid name check information verify return "sucessfully delete user" messages COLLABORATION NAME: DELETE USER 22 .
1 BASIC FLOW 23 .4 FLOW OF EVENTS 5.1 BRIEF DESCRIPTION This use case will enable the salesperson to view item 5.1: clicks on "delete user" button : Administrator 3: key in user information(name) : Main Homepage 4: select "delete" button 2: display 9: "sucessfully delete user" messages 6: check information : Delete user page 5: send information 7: verify 8: return : Delete user controller : Delete user table USE CASE DESCRIPTION: V S i a e l w e s I p t e e r m s o n VIEW ITEM DETAILS 5.4.3 PRIMARY ACTOR: Salesperson 5.2 PRE-CONDITION The products must be stored in database 5.
5 POST CONDITION • • Salesperson will be able to view details of an item Salesperson must key in letters of an item.4.3 EXCEPTIONAL FLOW Not Applicable 5. 5.4.6 CONSTRAINT USE CASE NAME: VIEW ITEM DETAILS : SalePerson Click An Item : Homepage : ViewItemDetails : ItemTable Send Information Success Verify Return DisplayItemDetails 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 Not Applicable • • 5.2 ALTERNATINE FLOW 5.
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.4.1 BRIEF DESCRIPTION: This use case will enable the salesperson to search an item 6.3 PRIMARY ACTOR: Salesperson 6. The salesperson will select an item that you want and select “search” button.COLLABORATION NAME: VIEW ITEM DETAILS 1: Click An Item : SalePerson 6: DisplayItemDetails 3: Success 2: Send Information : Homepage 4: Verify 5: Return : ViewItemDetails : ItemTable USE CASE DESCRIPTION: SEARCH ITEM Sales Person Search item 6. (A1: Cancel) 25 .4 FLOW OF EVENTS: 6.2 PRE CONDITION: • • Salesperson must login to the system The products must be stored in database 6.
select "search" button 4. key in initial letters of the item 2. retrieve details 7. return details 8. send information E 1: Unavailable item 5.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 Salesperson must key in letters of an item. Display USE CASE NAME: SEARCH ITEM 26 .2 ALTERNATIVE FLOW 6. select particular product 3.4.4. 6. verify product A 1: Cancel 6.• 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.5 CONSTRAINT : Sales Person : Homepage verify product : Search : Item details : Item details table 1.
item name. return details : Item details table : Item details 8: 8. retrieve details verify product : Search USE CASE DESCRIPTION: ADD NEW ITEM Administrator Add new item 7. Display 6: 6. verify product 5: 7: 7. key in initial letters of the item 2: 2. select "search" button : Sales Person : Homepage 4: 4.1 BRIEF DESCRIPTION: This use case will enable the administrator to add new item in inventory. 7. item price) 27 • .1 BASIC FLOW • • The use case begin when the admin click on “add item” button. select particular product 3: 3. The system will display add new item page.4 FLOW OF EVENTS: 7.COLLABORATION NAME: SEARCH ITEM 1: 1.3 PRIMARY ACTOR: Administrator 7.4. send information 5. Administrator will key in the item information (item ID.2 PRE CONDITION: Admin must login to the system 7.
4.5 POST CONDITION • • 7.6 CONSTRAINT 28 .• • Then.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 user should enter item name Administrator will be able to add new item information Administrator must key in the lecturer information USE CASE NAME: ADD NEW ITEM 7. item name. Administrator will select “proceed“ button. item price) (E1: please enter item ID) (E2: please enter item name) (E3: please enter item price) • • Administrator will save the information A1: Cancel The system will display the message that the process has been cancelled 7.(Alternative1: Cancel) The system will check information (item ID.2 ALTERNATIVE FLOW 7.
save 9: 9.return 10.key in item information (item ID. select "add new item" button : Administrator : Main Homepage 3: 3.return : Add new item controller : Add new item table 5: 5.retrieve item 8. display COLLABORATION NAME: ADD NEW ITEM 1: 1.display 3. select "add new item" button 2. item price) 4.verify information 8: 8. item name.display 6: 6.select "proceed" button 5.select "proceed" button 2: 2.send information A1: cancel 6.: Administrator : Main Homepage : Add new item page : Add new item controller : Add new item table 1.send information : Add new item form 29 .save 9.check information E1: please enter item ID E2: please enter item name 7.key in item information 4: 4.check information 7: 7.
4.3 EXCEPTIONAL FLOW 30 .3 PRIMARY ACTOR: Salesperson and sales manager 8. 8.1 BRIEF DESCRIPTION: This user case will enable the sales person and sales manager to check the inventory status.2 PRE-CONDITION: The sales person and the sales manager must key in item information 8.4.2 ALTERNATIVE FLOW • • • • A1: Cancel The system will display the message that the process has been cancelled 7.USE CASE DESCRIPTION: CHECK INVENTORY STATUS S alespers on/sales m anager Chec k inventory ststus 8.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.4. • The system display “successfully” message 7.4 FLOW OF EVENTS: 8.
• E1: Invalid item ID The system will display the message that item ID are invalid 8.. : 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 CONSTRAINTS: USE CASE NAME: CHECK INVENTORY STATUS : SalesPerson/Sal. The sales person and the sales manager must key in item ID information 8.5 POST CONDITION: • • The sales person and the sales manager will be able to check inventory status.
3 PRIMARY ACTOR: Administrator 9. (A1: Cancel) 32 .1 BASIC FLOWS: • • The use case begin when the administrator key in the price on the administrator homepage.1 BRIEF DESCRIPTION: 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.4 FLOW OF EVENTS: 9.4 . The administrator will select “change price” button.6: check information 3: key in item information (item ID) 4: select "proceed" button 5: send information : SalesPerson/Sales Manager : 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 Administrator Change price 9.
verify 5.6 CONSTRAINT: USE CASE NAME: CHANGE PRICE : Administrator : Administrator Homepage : Change Price Controlller : Change Price Details : Change Price Table 1. select "change price" button A1: Cancel 3. key in price number of the item 2.4.2 ALTERNATIVE FLOW: • 9.4.• • The system will verify item price availability (E1: A value is required) The system will display change price details A1: Cancel The system will display the message that the process has been cancelled 9. send information AE1: value is required 4. retrieve details 6. save 8.3 EXCEPTIONAL FLOW : • E1: A value is required The system will display the message that a price value is required 9. display COLLABORATION NAME: CHANGE PRICE 33 . return details 7.5 POST CONDITION: • • Administrator will be able to view item details Administrator must key in the item price 9.
4.4: 4. save 8: 8. 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 • • • • . select "change price" button 3: 3.1 BASIC FLOW • The use case begin when the clicks on “produce a receipt” button. verify : Administrator 1: 1.1 BRIEF DESCRIPTION: This use case will enable the salesperson to produce a receipt 10. send information : Change Price Controlller 5: 5. return details : Administrator Homepage : Change Price Table 7: 7. display : Change Price Details USE CASE DESCRIPTION: PRODUCE A RECEIPT Salesperson Produce a receipt 10.3 PRIMARY ACTOR: Salesperson 10. key in price number of the item 2: 2.4 FLOW OF EVENTS: 10.2 PRE CONDITION: Salesperson must login to the system 10. retrieve details 6: 6.
item price) select "proceed" button A1: Cancel send information E1: Inavalid item name check information verify E2: Invalid item price return display "sucessfully" message COLLABORATION NAME: PRODUCE A RECIEPT 35 .5 CONSTRAINT 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.3 EXCEPTIONAL FLOW • E1: invalid item name The system will display the messages that item are invalid 10.4.2 ALTERNATIVE FLOW • 10.4.5 POST CONDITION • • Salesperson will be able to produce a receipt Salesperson must key in item information 10.• The system will display “successfully” message A1: Cancel The system will display the message that the process has been cancelled 10.
1 BRIEF DESCRIPTION This use case will enable the administrator and inventory manager to check Balance. Administrator (from Logical View) Check Balance Inv entory Manager 11.4 FLOW OF EVENTS 11.3: key in item information (item name.1 BASIC FLOW • • This use case begins when the administrator and inventory manager clicks on “Check Balance” Button. 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 8: return : Main Homepage : Produce receipt table 7: verify : Produce a receipt controller Administrator (from Logical View) USE CASE NAME: CHECK BALANCE. The system then display check balance page The Admin press check balance button. 11.4. The system will send information to verify the user I.D and password 36 • • .2 PRE-CONDITION The admin and inventory manager should have a user ID and password 11.
• • • The system will allow the user to access the system if the user I. Pls re-enter again. Click on "Check Balance" Button Send Info ( ) Verify ( ) Enter User ID And Password Check Balance ( ) Return ( ) Display "Balance" 37 . User name or Password is incorrect. USE CASE NAME: CHECK BALANCE : Admin/InventoryManager : Homepage : BalanceController : BalanceTable.D and password are valid The system displays the Balance. ALTERNATIVE FLOW Not applicable EXCEPTIONAL FLOW The user ID or password you entered does not match please re-enter again. The functions ends when the Admin/Inventory manager logout of the system.
a n e a le Administrator Generate Report InventoryManager BRIEF DESCRIPTION 38 .COLLABORATION NAME: CHECK BALANCE 1 C k o "C e k B la c " B tto : lic n h c a n e u n 4 E te U e IDA dP s w rd : n r sr n as o : A m is a r d in tr to : Hmp g o eae 3 V r () : eify 7 D p y "B la c " : is la a ne 2 S n In ( ) : e d fo 5 C e k B la c ( ) : hc a ne : B la c C n o r a n e o tr lle 6 R tu ( ) : e rn : B la c T b .
D and password are valid The system display the generated report The functions ends when the Admin/Inventory manager logout of the system.This use case is initiated by the administrator and inventory manager. USE CASE NAME: GENERATE REPORT 39 . 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. ALTERNATIVE FLOW Not applicable EXCEPTIONAL FLOW The user ID or password you entered does not match please re-enter again.D and password The system will allow the user to access the system of the user I.
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 .: 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.
... Delete user() Change price() Dalete Change Passwod Delete User Name Delete User() Change Password form Username Password Submit() Cancel() 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() .3 CLASS DIAGRAM Item Item No Types of item Price Quantity Add New Item() Login Form Username Password Login() Cancel() View user Profile Name Phone no Address Zip code Add New User() . Change Price View Chance Price Inventory Manager User Name Password First name Last Name DOB SEX ID Email Phone Number View reports() Check inventory status() . Add new item().. .... . Validate report() Generate reports() Generate trends() Price Page Item No Price Change Price() View Price() 41 . Delete item() Add new user().7.. update() Cancel() Login Add Login Login Login Administrator Admin Name() Password() Admin ID DOB SEX Email Phone No.. 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()..
7.4 ACTIVITY DIAGRAM ➢ View item details Salesperson View Item Click On "View Item" Button Enter (Enter the name of Item) [No Result] Click "Search" Button Searching The Item [Success] View The Item Display The Item Details 42 .
➢ Search item Salesperson searchItem Key Search word InCorect Click Go Button VerifySearchIte m DisplaySearch Item Corect ➢ Add new user 43 .
Administrator System Click "Add User" Button Display Amid page Select New User Key in "User Information" (Invalid) Verify the Information (Valid) Click On "Save " Button Sussecceful add or Fail 44 .
➢ Add new item Admid ADD ITEM Click "Add Item" button key in "Item name"price Check and Verify Click "Save" Button Sussecceful Added 45 .
5 STATECHART DIAGRAM ➢ Search item Salesperson key in the name of the search Item Search Item Requesting search Pending Comformation Verify Iten name Relessed View the list of the Item by Salsperson ➢ Add new item 46 .7.
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 .
When making decision on programming languages some important issues will consider such as: What database does the system working with : 1. to share and Java-compatible browsers 4) PHP can run on both include some levels of security Windows servers and UNIX 48 . Advantages: server for of the machine (JVM) regardless of function clients Advantages: Advantages: 2) Simple and easy to use responding and VBScript are primary syntactically similar to Visual to Basic. JAVA 2. language development dynamic web pages and PHP surroundings from Microsoft code is embedded into the for its COM programming HTML source document. 1) Easy to use object-oriented 1) It runs fast and doesn't tend 1) User friendly and interface programming language when to slow other processes down compared to the programming language. VISUAL BASIC JAVA PHP VISUAL BASIC Basic is event a thirddriven and Java has been built from the PHP is based on Perl. Java programs popular 2) PHP uses a modular system 3) Powerful front end tool of extensions to interface with 4) Low cost 5) It is reachable with 3) PHP community is willing documentation in most tools 2) Java is interpreted to run a variety of libraries. PHP 3.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. it is a Visual ground up as an object general-purpose scripting generation oriented and will be very language initially designed for programming useful for coding inventory web development to generate associated management system. interpreter. model. but perform differently. 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 computer architecture. 3) The compiler.
Disadvantages: 1) Low speed other programs Disadvantages: Disadvantages: 1) Web programming tools is 1) Does not support side-byflaws. Need to control coming 2) Large talent the competition and 3) Cannot handle pointers directly pool of 2) It runs slowly compared to freely accessible to protection side execution 3) The programs do not always 2) written correctly work properly even if they are variables accessible between pages. 3) Need to add java or java code other client-side tools in the output INVIDIVIDUAL REPORT 49 .
Another task done by me is the Drawing of the Class diagram. The Assignment is to develop an online inventory Management system. we later on compile all together and we check and edit some errors together before printing the work. After finishing the individual task given to each member of the group. 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.The group Assignment consists of four (4) members. 10.0 CONCLUSION 50 . Four (4) use case diagrams and their description each and sequence diagram. We have meeting with all the group members normally three times in a week.
an online Sales and Inventory Management System is a perfect solution for the keeping they record of the store. design and implementation of system to come out with a full documentation. We were following SDLC phases such as planning. The system can be used as a tool to maintain due to the cost of material. Then. human errors. difficulty in searching and retrieving product and feasible loss of records and retrieving files.In conclusion. we also discussed the advantages of programming languages as you see in the documentation. less data integrity. analysis. REFERENCES 51 .
International Journal of Information Management. p1-20. Ziff-Davis Publishing: United States of America. P.webdotdev. (1987-1993). ➢ Efraim Turban. Software Engineering : A Programming Approach. Java Advantages and Disadvantages. Paul: West Publishing. ➢ Shammas. United States of America: McGraw Hill. Programming Visual FoxPro 3. (2009). Co. http://www. ➢ Beynon-Davies P. and IT for Business Results. G. D M. and Pugh. (1994). Visual C++ Generic Programming. Experiencing MIS. C. United States of America: Addison-Wesley. Lea. ➢ Quatrani. Prentice-Hall. D.W. Addison-Wesley Pub. P. p34-50. Kevin Lane (2006). viewed 17 November 2011. ➢ O’Brien. 2nd ed.d. Boston. Decision support systems: an organizational perspective. Philip. The Work System Method: Connecting People. Business Information Systems.. Works System Press. Processes. ➢ Hentzen. J. G (1994). T (1998). (1996). Object-Oriented System Development. Mass. Aronson.webopedia. D. MA ➢ O'Brien. B.0. Keller. Visual Modeling with Rational Rose 2000 and UML. (1978). and Faure. I. p25-60. and A. McGraw-Hill. N. p32-56. Upper Saddle River. J (1999). ➢ Champeaux. ➢ Wilkie. Canada: Addison-Wesley. (2003). CA ➢ Beynon-Davies P. Decision Support Systems and Intelligent System ➢ Holsapple. ➢ MS. W. (1954). p1-200. Object-Oriented Software Engineering : The Professional Developer's Guide. 2007. viewed 17 November 2011. (1995).). (2009).➢ Bell. W. programming language. St. United States of America: Addison-Wesley. http://www. Basingstoke ➢ Kotler.com/TERM/P/programming_language. S.. Palgrave. Pearson Education ➢ Keen. Boston: Irwin McGraw-Hill. Morrey. NJ business enterprise.com/nvd/content/view/1042/204/ ➢ Webodia.html 52 . Introduction to information systems: essentials for the e➢ Alter. Britain: Prentice Hall. Ting-Peng Liang (2008). D.. Whinston. ➢ Kroenke. Decision Support Systems: A Knowledge-Based Approach. J A. D. Marketing Management (12 ed. n. The ‘language’ of informatics: the nature of information systems. C. Management Information Systems – Managing Information Technology in the Internetworked Enterprise. Reading. Jay E. p1-200. (2008).
Programming Languange Comparison.html ➢ GSLOGIX.com/articles/118/1/The-Advantages-ofPHP/Page1.html. Advantages and disadvantages of PHP . Last viewed 20 September1 2011. viewed 20 November 2011. 2006.➢ Designs Playground.com/software/langcomp. (2004). http://www.designersplayground. 2011.jvoegele. J.com/blog/2011/10/advantages-and-disadvantages-of-php/ ➢ Voegele.gslogix. Available: http://www. 53 . viewed 20 November 2011. The Advantages of PHP http://www.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.