1.

INTRODUCTION
Sales and 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. The management use manually to keep their
record to the store, but the system is difficult to maintain due to the cost of materials, human
errors, less data integrity, difficulty in searching and retrieving product and feasible loss of
records and retrieving files.

Video rental system is a system specialized in managing the rental transaction between
the business owner and the customer. It includes sales and inventory for the video rental shop.
The system is developed due to some issue existing by using manual system followed by this
shop. In this case, the user or member was easy to rent or register because of this system. And it
also helps the video shop to make their business more efficient in terms of rent.

By combining these two systems it will create

1.1 Goals and Objective

The main objective of inventory management is to maintain inventory at appropriate level to

avoid excessive or shortage of inventory because both the cases are undesirable for business.
Thus, management is faced with the following conflicting objectives:

1. To gather data and information.

2. To plan the flow of creating the system using the gathered data information.

3. To design the system GUI.

4. To create an easy to use system for an illiterate workface with database.

5. To develop overall system.

6. To test for any system errors and for its functions to be evaluated by its effectiveness and
efficiency.

7. To implement the system for the user to get their opinion and reactions.
1.2 Statement of scope

The scope of this project is to develop and implement a computer parts inventory system that
performs all of the tasks necessary to track orders from the customer and deliver it to the
customer. The project consists of inventory management, consuming, purchasing, and bill of
materials.

Account module contains user information records such as personal information. The
user can add, update, and delete an account if it is no longer a customer of the company or if the
manager would no longer need the information. The manager can also view the account of every
customer. The customer can view and edit their own personal information. The user can also
create new password of different account if it was forgotten.

Inventory module will be designed to control the inventory on hand. In this module, the
user will be able to assign a status to each item. The status will be good stock, reserve stock,
waiting for quality approval.

Sale module the requisitioned may specify if substitutions are allowed or not and include
a required by date. The system will be able to notify the requisitioned that the purchase order has
been processed, allow the ability to send a group of unsent purchase orders at one time and
individual resend purchase orders, and keep track of order history. The order history will contain
when sent, resent, modified, etc. In addition, it will provide a list of open requisitions by buyer
responsible and allow the buyer to check the requisitions and convert them to purchase orders. In
addition, users can enter, update or delete buyers.

The record module

The reserve module

The rent module

User Requirements for Sales and Inventory Management System

Req. No. Requirements Priority Description

 name

1 Log in Admin This function will enable user to log in to

the system

2 Change Admin This function will enable user to change the

password password

3 Create Account Admin This function will allow the user to create
an account

4 View inventory Admin This function will enable user to view

stocks availability

5 Add and update Admin This function will enable the user to add
video and update information and copy of the
information and video
video copy

6 Remove Admin This function will enable the user to

overused video remove overused video

7 Search video Admin This function will enable user to search

video

8 Add customer Customer This function will enable the user to add
customer account

8 View customer Admin/Customer This function will enable the user to view
profile the customer profile

9 View Admin/Customer This function will enable the user to view

transactions transaction in the inventory

9 View sold item Admin This function will enable the user to view
sold items

10 View rent items Admin This function will enable the user to view
the rent items

11 View reserve Admin This function will enable user to view the
item reserve items

12 Check inventory Admin This function will enable user to check

status stock in inventory

13 Check sales Admin This function will enable user to check

status stock inventory
 14 Check sales Admin This function will enable user to check
status stock in inventory

2. Usage scenario

2.1 User profiles

The following definitions describe the actors in the system.

Admin The admin has the responsibility for the whole system. They have unrestricted
access to the Sales and Inventory Management system including viewing and
changing passwords.

Customer The customer is the one who consumes the item. They are responsible for
transactions for buying, renting, and reserving.

System The system refers to the computer hardware and software that controls the
application. It accepts user input, displays user output.
Database Server The Web server is a remote computer system that maintains the database and
serves Web pages to the System.

2.2 Use-cases

The following use-cases are typical interactions between the external environment and the
internal software system. Each use-case is described in section 2.2.2.
1. Log onto system
2. Create account
3. Change password
 4. Display System activity
5. View inventory activity information
6. Search video
7. Add video stock
8. Add video copy
9. Update video stocks information
10. View rented video limit
11. Remove overuse videos
12. Add customer account
13. Input data
14. View costumer profile
15. Update customer profile
16. Choose transaction for customer
17. View reservation information
18. Update reservation
19. Check reserve status
20. View rent information
21. Update video renting
22. Check video rented record
23. View sales record
24. Update sales
25. Check sales record
26. Log out system Validate report

2.2.1 Use-Case Diagram

Generate trend
The use-case diagram in
Administrator
Figure 1 shows three actors that were described in section 2.1. In order to minimize the
complexity of this diagramViewseveral
reportconnections were left out. For instance, every use-case will
Customer
typically involve an interaction with the System and database Server.
<<uses>>
Create Account Log on to system
Change password

For the whole technical operation system

Database System

<<uses>>
 ``

Figure 1: Use- Case Diagram of Sales and Inventory Management System

2.2.2 Use-Case Descriptions

Use Case ID: Log on to System

Primary Actor: User
Secondary Actor: User
Trigger: This function will enable user to log in to the system.
Goal in context: To gain access to the System
Preconditions: The user is logged into the system.
Post conditions: A new account has been created.
Scenario: 1. The user selects "Create account" button.
2. The user enters the information into the provided form.
 3. The user selects "Enter" button.
4. The system validates the information provided.
5. The system creates a new account.

Use Case ID: Change password

Primary Actor User
Secondary Actor: User
Trigger: This function will enable user to change the password
Goal in context: To secure the system in Video rental
Preconditions: The user is changing the password.
Post conditions: A new password has been created.
Scenario: 1. The user selects "Change password" button.
2. The user enters old password and input a new password.
3. The user selects "Enter" button.
4. The system validates the information provided.
5. The system creates a new password.

Use Case ID: Create account

Primary Actor User
Secondary Actor: User
Trigger: This function will allow the user to create an account
Goal in context: To provide an account in the system
Preconditions: The user is creating an account
Post conditions: A new account has been created.
Scenario: 1. The user selects "Create account" button.
2. The user inputs data.
3. The user selects "Enter" button.
4. The system validates the information provided.
5. The system creates a new account.

Use Case ID: Search video

Primary Actor: User
Trigger: This function will enable user to search video
Goal in context: To be able to find video easily
Preconditions: The user search video in the system
Post conditions: The video has been searched.
Scenario: 1. The user input video in the search bar.
2. The system will display the inputted video information.
Use Case ID: View video stock
Primary Actor: User
Trigger: This function will enable user to view video stocks availability
Goal in context: To view the current stocks availability
Preconditions: The user view the video stock in the system
Post conditions: The video stock has been view.
Scenario: 1. The user selects inventory button in the main menu of the system
2. The system will show the video stock in the system.

Use Case ID: View sold item

Primary Actor: User
Trigger: This function will enable user to view sold an item
Goal in context: To view the sold items
Preconditions: The user views the sold item.
Post conditions: The sold item has been view.
Scenario: 1. The user selects the "check record" button.
3. The system will show the sold item.

Use Case ID: View rent video

Primary Actor: User
Trigger: This function will enable user to view rent video
Goal in context: To view the rented video
Preconditions: The users view the rent video.
Post conditions: The rent video has been view.
Scenario: 1. The user select rent" button
3. The system will show the rent video.

Use Case ID: View reserve video

Primary Actor: User
Trigger: This function will enable user to view reserve video
Goal in context: To view the reserved video
Preconditions: The user views the reserve video
Post conditions: Reserve video has been view.
Scenario: 1. The user selects the "reserve" button.
2. The system will show the reserve video.
Use Case ID: Check inventory status
Primary Actor: User
Trigger: This function will enable the user to check stock in inventory
Goal in context: To monitor the inventorys availability
Preconditions: The user checks the stock of the inventory status.
Post conditions: The Inventory status has been checked.
Scenario: 1. The user selects the Inventory" button.
2. The system will show the stock of the inventory status.

Use Case ID: Check sales status

Primary Actor: User
Trigger: This function will enable salesperson to check stock in inventory
Goal in context: To monitor the sales status
Preconditions: The user checks the sales status.
Post conditions: The sales status has been checked.
Scenario: 1. The user selects the "buy" button.
2. The system will show the sales status.

2.3 Special usage considerations

Every transaction that is relevant is unchangeable.

2.4 Activity Diagrams

The following activity diagrams show the actions that occur during a particular use-case.
Figure 2 shows the steps taken as the user logs on to the computer system. Access is only granted
if the correct user ID / password combination is entered within the first three attempts. After a
third attempt the user ID will be locked out and an administrator will need to issue a new
password. Once access is granted the employee can use the system according to their level of
authorization.

Figure 1 - Activity diagram for Account Management module

 Account Module

Create Account

Input User Data

Enter

Validate

[incorrec
Check Data

[correct]

New account created

Figure 2 - Activity diagram for Inventory Module

 Inventory Module

Figure 3 - Activity diagram for Sale Module

 Sale Module

Figure 4 - Activity diagram for record module

Record Module
Figure 5 - Activity diagram for reserve module Reserve Module
Figure 5 - Activity diagram for rent module Rent Module
2. Data Model and Description

3.1 Data objects

Video Data object

3.2 Relationships

The user may add multiple account in the system so one-to-many relationship exists. Since the
user may not need to be reminded of anything it is possible for an employee to exist without a
daily reminder, but a daily reminder must be assigned to a specific employee.
Each time the user edits a record it will be recorded in the change data object. Most customer
will make multiple changes so there is a one-to-many relationship between customer and change
data objects. Customer may not make any changes and can therefore exist alone. However, a
change object must be associated with an employee and therefore cannot exist alone.

3.3 Complete data model

4. Functional Model and Description

4.1 Class diagrams

4.2 Software Interface Description

4.2.1 External machine interfaces

The software will be capable of printing invoices and reports on a local or network printer.

4.2.2 External system interfaces

The Sales and Inventory Management system ...

4.2.3 Human interface

The Web pages shall permit complete navigation using the keyboard alone, in addition to using
mouse and keyboard combinations.

5. Behavioral Model and Description

5.1 Description for software behavior

5.1.1 Events

5.1.2 States

Admin States Description

Registering The admin is setting up a new account.
On Line The admin has logged on to the system.
Checking/Updating The admin is checking or updating the inventory activity
Off Line The admin has logged off the system

Customer States Description

Registering The customer is creating an account.

On Line The employee has logged on to the system.

Off Line The employee has logged off the system.
Terminated The employee has been terminated and must be blocked from using the
system.

Stocks States Description

Viewing

5.2 State chart Diagram

The system is to develop Sale and Inventory Management system. This systems 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.

Figure 14 contains statecharts for the manager,sales activity, and employee. After a child reaches
the age of 6 they will no longer be allowed to enroll in child care. A parent may decide to enroll
another child in which case they will need to enter the registering state again so that the new
childs information can be recorded. If an employee is promoted their access privileges will
change so they will need to log out then log on to the system for the new changes to take effect.

The various states for ae classroom, waiting list and immunization objects are shown in Figure
15. The statechart for the classroom is identical to that for the waiting list except for the guard
conditions. Either object can be at capacity or below. It is expected that a classroom will close if
its enrollment drops too low. Likewise a waiting list is eliminated if there are fewer than 20
children in a classroom

Overall system statechart diagram

statechart diagrams

6. Restrictions, Limitations, and Constraints

The system shall integrate within the existing LAN structure and with the existing
systems, such as the database management systems.
All HTML code shall conform to the HTML 4.0 standard.
All server side code shall be written in ASP.NET.
Netscape 7.0x or Microsoft Internet Explorer 5.x (or more recent versions of either)

7. Validation Criteria

Software validation will ensure that the system responds according to the users expectations;
therefore, it is important that the end users be involved in some phases of the test procedure. All
tests will be traced back to the requirements in section 1.2.

7.1 Classes of tests

Unit testing will be conducted on all of software subsystems including
1. Logging on to the system
2. Viewing and editing information
3. Viewing Sales reports
4. Logging off to the system

Test cases for black box testing will be based on equivalence categories. These categories
will include values that lie on and around the boundary values of a function. For example,
if a function can accept values from 0 to 100 then the test cases will include the values -1,
0, 1, 99, 100, and 101.
 Acceptance testing will be conducted at the customers site.

7.2 Expected software response

The software should display an appropriate error message when a value outside the
accepted limits is entered.

The software should not be capable of deleting a customer record even if they withdraw
from the Care Center.

7.3 Performance Bounds

The system shall support up to 100 simultaneous users against the Database Server at any
given time.
The system will provide access to the database management system with a latency of no
more than 20 seconds.

Appendix A: Glossary
Account a reference for all of the information related to User and customer.
Administrator A person on the administrative staff of the Sales and Inventory system.
Inventory a complete list of the things that are in a place.
Module a computer program that does a particular job.
Transaction the act of process of doing business with another person or company.