Đồ án Kỳ 2 Aptech: Quản lý Kho hàng

Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


1






This is to certify that

Mr./Ms:
Bach Ngoc Toan, Nguyen Van Khoi,Luong
Hoang Manh,Lam Thi Phuong Loan.

Has successfully Designed & Developed:
Inventory Management

Submitted by: Lai Duc Chung

Date of Issue: May 19, 2009

Authorized Signature:


Bui Viet Son


Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech

2

Chapter 1: Problem Definition
Form No.1/eProjects/Version 1.0

I. Description about Inventory Management System

To day, applications to life more than. And computing and informatics is being
developed so fast. Management a shop or a inventory with a large amount data stored.
Management bills, Tran tract and information of customer in a day will very difficult if
you done by hand.
That is objectives of Inventory Management System, which we provided here.
This is application software has functional help sales, inventory manager, sales manager
and administrator easy view, validate and manipulation information of customer, bills
and categories product. Beyond, systems support administrator statistics numeric about
Functional of application has been developed to provide a lot of benefit to user.
Help to management inventory easier. All business process faster and correctly.
Base Java programming language can run on any platform. Your application can execute
even on many platform difference if they setup Java Runtime Environment .Therefore
system will implemented widely and reality higher.

II. Goals of project

Inventory Management System has been developed to achieve these goals:
 Management easier information of product and customers.
 Management bills details, Tran tract and generate report to administrator and sales
manager.
System built with functions below:
 Store information abound administrator, sales, inventory manager in database.

 Sales person:
Login to the system through the initial screen of the system
Change the password after logging into the system
See status of the inventory, i.e., whether a particular item is available or
not etc
Search for a particular item by typing the initial.
Enter the items purchased by a customer and produce a bill for the same
Cancel the produced bill, in case of error in entering the details, and
produce a new one
Take back an already sold Items that is not satisfactory to the
customer (the shop allows that) and produce a receipt for the same
Inform the inventory manager about the Items that are not available,
so that they can be stocked
Inform the sales manager about any exceptions (such as an
Items are being purchased, but it is not available in the system.
Get help about the system on how to use the different features
of the system

Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


3

 Inventory manager

Login to the system/change his password after logging in etc check the
status of the inventory
Veer the reports from sales people about items that are not available
and need to be kept in the inventory
Validate the inventory against the sales done in the previous day (whether

the items that are sold and the change in the inventory for the
corresponding items match etc)
Generate inventory reports of the items category-wise, price-wise etc
Generate inventory-trends (like how is coffee powder stock changing
over the month)

 Sales Manager

Login to the system/change his password after logging in etc

Check how many bills have been generated in the day so far

Check how much money is transacted in the day so far

Check how many bills have been cancelled so far in the day(due to wrong
entry by the sales persons)

Check how many items have been returned so far in the day

Check for any exception reports from the sales persons and correct it by
contacting the inventory manager

Generate sales-trend graphs for each of the item (like how is apple selling
in the last one month)

 Administrator

Login to the system and change his password after logging in

Add new users to the system

Add new items/categories to the inventory (‘grape’ may be added to
the category ‘fruits’ or a new category such as ‘vegetables’ may be
added)

Change the price of an item



Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


4

Chapter 2: Customer Requirement
Specification (CRS)
Form No.2/eProjects/CRS/Version1.0
Client: User

Business/Project Objective

Camp connection is general stores selling various fast moving consumer
goods (FMCG). The store is existence from almost 5 years and is situated in the
heart of the city.

Since last 2 – 3 years is has been doing exceptionally well because of the
huge complex built around the area and people prefer to visit the nearest place to
buy various FMCG.

The store is able to cater to the need of people but at the same time finding

it difficult to manage the sales and stock details and to manage the large amount of
transaction which is causing discrepancies in the data.

Now a day use of computer is the best way to manage the large amount of
data easily and effectively so the owner of the store has decided make use of
computer to maintain the data. He has thought of development of Sales and
Inventory Management System (SIMS) which will store all the information and
required data can be retrieved with ease. SIMS is the proposed solution for his
store problems.

Create a database for the store. Add tables to store information about the
different Inventory, Sales and Users. The client-server application authenticates
the existing user by his username and password. The application has a registration
page where a new user can enter his personal details in the given fields. The user
details get stored in the database containing details of existing user gets updated.
After the user is authenticated, the user can perform the task of sales or inventory
manage or sales manage operation which the user has permission.

Input provided by the Client:

• Inputs for the application :
 The information of users
 The information of products.
 The information of bills.

Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


5

• Outputs from the application :
 The information of goods when a user searches with their input
information.
 Status of the inventory
 Produce bills.
 Reports about the inventory problems

• Process Involved in the application :
 Log in or log out the system :
 Add a new record
 Update records
 Search for a particular item in the store
 Generate a bill
 Manage bills
 Generate reports

Hardware Requirements:
• A minimum computer system that will help you access the entire tool in the
course is a Pentium 200 or a higher capability CPU.
• 256 Megabyte of RAM or Higher.

Software Requirements:
• Any platform you can have (window, Linux…).
• jdk 1.4_02 or later.
• Net Bean 6.5.
• MS SQL Server 2005.

Scope of the Work (in brief):

Depending on the decision taken by the store owner, Sale and Inventory

Management System need to be developed with the following requirements:
Registration of new client and authentication of existing client.
Provide a user friendly interface to the user to work with application
Allow user to search for item information in the store, user information.
Add new goods and manage the entire item in the store.
Generation of reports related to all the store problems.
Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


6





Chapter 3: Architecture and Design of the
Project
Form No.3/eProjects/Design/Version1



Tow-Tier Architecture of the Project

Tier 2
Database Tier
User interface – GUI Components
Database Access
Tier 1
Presentation Tier

Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


7

Design Flowcharts
• Administrator Login:







Input user
Name and

password

Check user
name and
password

Display
window main

Status =0

Start
Stop
Check status the
user name on the
database
No

Yes

Registr
ation
No
Display error
Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


8

Input

information
a = account
record added
Stop
Insert
successful
Yes
No
A > 0
Display successful
Yes
No Display
error
Validation of information
And insert to database
Validate
successful
Yes
No
Start

• Function Add:

Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


9

• Function Edit


Start
Stop
Input information
Validate
successful
Display
successful
Display error
Yes
No
Validation data on
the form
Update
successful
a = count record
updated
A > 0

No
Yes
Yes
No
Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


10

• Function Delete

Stop
a = count record
deleted
a > 0
Display
successful
Yes
Yes
No
No
No
Yes
Start
Input information
Display error
Validation data on
the form
Validate
successful

Update
successful
Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


11

• Function Search






Stop
Display
information
No
Yes
Start
Input information
Validation data on
the form
Validate
successful
Display error
Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


12

Chapter 4: Data Flow Diagram
Form No.4/eProjects/DFD/Version1.0

Define: Data Flows Diagram (DFD) describes the information flow in the
system. The next step of system analysis is to consider in detail the
information necessary for the implementation for functions discussed above
and the one necessary for the improvement of the functions. Modeling tool
frequently used for this purpose is DFD. DFD will support 4 main
activities:
Analysis: DFD is used to determine requirement of users.
Design: DFD is used to map out plan and illustrate solution to analysis and
users while designing a new system.
Communication: one of the strength of DFD is its simplicity and ease to
understand to analysts and users;
Document: DFD is used to provide special description of requirement and
system design. DFD provide an overview of key functional components of
the system but it does not provide any detail on these components. We have
to use other tools like database dictionary, process specification to get an
idea of which information will be exchanged and how.
The main components of Context Diagram:

The process: Shows the common function of system
External

Data store

Process

Data flow

Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


13

The external factors: External factors can be a person, a group of persons or
an organization that are sources of information for the systems and are where
system products are transferred to.

The data flow: Describe the movement of information from one part of the
system to another.

The data store: The Data Store is used to model a collection of data packets at rest.
A store is represented graphically by two parallel lines. The name of a Data Store
that identifies the store is the plural of the name of the packets that are carried by
flows into and out of the Data Store

Sales

Manage
Sales and
inventory
Feedback
Inventory detail
Feedback
Inventory
Manager
Admin

Sales Manager

Transaction
Inventory
report

Feedback
Feedback
Account details
Feedback
Feedback
Authentication
details

Transaction
checking

Feedback
Feedback

Figure 2: Level 0 Context Diagram
Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


14


Sales
3.
Transaction
details
Figure: DFD Level 1 For Sale
4.
Create bill
Products
Bills
Require bills
Feedback
1.
Account
process
User
User id, pass
Relay
information
Check, change
pass, id
feedback
Input bills
Relay

information
Require
Relay id, date, time,
Item/quantity/price

Require
Relay
information
2.
Check
information
Feedback Require
Products
Check
Relay
information
Inventory
manager
Report
Sales
manager
Report
Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


15


Admin
1.

Account
management
Figure 3: DFD Level 1 for Administrator
2.
Authentification
User
Roles
Require
permission
Feedback
Input
show
Require
Retrieve
information
Saving
account
Retrieve
information
3.
Change
price
Products
Save
Retrieve
information
Require
show
4.
Input

categories
& products
Categories
Input
show
Require
Show
Products
show
Input
Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


16


Inventory
manager
2.
Check
status
Figure 4: DFD Level 1 For Inventory management
3.
Create
report
Products
1.
Account
process
User

User id, pass
relay
information
g

Check, change
pass, id
feedback Require
Relay information


Require
Relay
4.
Make
inventory
trends

Require
Retrieve
information
5.
Validate sale
Products
require
Retrieve

bills
Require
Retrieve

Require
Relay information


Retriev
e

Require
Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


17


Sales manager
2.
Check
transaction
Figure 5: DFD Level 1 for Sale Manager
Bills
3.
Check
exception
Require trends
Feedback
4.
Create
Sale-trends
Check

exception
Feedback
Feedback
Require bills Show
Distingue
1.
Account
process
User
User id, pass
relay
information
g

Check, change
pass, id
feedback
Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


18

Chapter 5: Entity Relationships(ER) Diagram

Form No.5/eProjects/ERD/Version1.0:

Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


19

Chapter 6: Database Design/Structure

Form No.6/eProjects/TAB/Version1.0

Table: Administrator
Field Name Date Type Null Key Description
AdminID Varchar(5) No PK Identifier of administrator
Username Varchar(30) No Username for login of admin
Password Varchar(20) No Password for login of admin
Phone Nvarchar(20) Yes Phone number of admin
Email Nvarchar(50) Yes Email of admin
RoleID Varchar(5) No Role ID of admin

Status
Bit Yes Status of admin

Table: Roles
Field Name Data Type Null Key Description
RollID Varchar(5) No PK Stores the RollId of User
RollName Nvarchar(30) No Stores RollName of User


Table: Categories
Field Name Data Type Null Key Description
CategoryID Varchar(5) No PK
Stores the CategoryId of
Item
CategoryName Nvarchar(30) No
Stores the CategoryName of
the ITem





Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


20

Table: Items
Field Name Data Type Null Key Description
ItemID Varchar(5) No PK Stores ItemId of the Items
ItemName Nvarchar(25) No
Stores Item Name of the

Items
Unit Nvarchar(20) No Stores unit of the Items
Quantity
Available Int No CHK Stores quantity of items
Price Float No Stores price of Items
DateImport Datetime No Stores Date import of Items
Manufacture Nvarchar(50) No
Stores Manufacture of
Items
Descript Nvarchar(200)

No Store descript of Items
CategoryID Varchar(5) No FK Stores Category Id of Items
Status Bit No Stores status of items
Sold Int Yes Quantity sold of item



Table: Customer
Field Name Data Type Null Key Description
CustomerID Varchar(5) No PK Stores Customer Id
CustomerName Nvarchar(50) No Stores customer Name
Address Nvarchar(200)

No Store address of customer
IdentityCard Varchar(20) No
Stores Identity Card of
customer
DateImport Datetime No
Stores date import of

customer
Status Bit No Stores status of customer
Purchased Float Yes
Store amount money this
customer purchased




Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


21






Table: Bills
Field Name Data Type Null Key Description
BillId Int No PK Stores ID of bill
AdminID Varchar(5) No FK Id of sales
CustomerID Varchar(5) No FK Stores customer ID
Date Datetime Yes Stores date bill
Discount Float Yes Stores discount of bill
VAT Float Yes Stores VAT of bill
Payment Nvarchar(20) No Stores payment of bill
Total Float Yes Stores total bill
Status Bit Yes Stores status of bill

Table: BillDetails
Field Name Data Type Null Key Description
BillID Int No FK Stores bill id
ItemID Varchar(5) No FK Stores Item ID of item
Quantity Int Yes Store quantity of bill
Price Float No Stores float of bill
Primary(BillID,ItemID)

Int, varchar(5) PK
Stores primary key of
Bill ID and Item ID





Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


22





Chapter 7: Task sheet
Form No.7/eProjects/TAB/Version1.0

Project Ref No.: Date of Preparation of Activity Plan:
Sr.
No
.
Task
Project
Title:
Activity
Plan
Prepare
By:
Actual
Start
Date
Actual
Days
Team
Member
Names
Status
1

Project
Definition
Sales and
Inventory
Management
System
11/05/09 1 Bach
Ngoc

Toan
Completed

2

Customer
Requirement
Specificatio
n (CRS)
Sales and
Inventory
Management
System
12/05/09 1 Nguyen
Van
Khoi
Completed

3

Architecture
& Design of
the Project
Sales and
Inventory
Management
System
13/05/09 2 Luong
Hoang
Manh

Completed

4

Data Flow
Diagram
Sales and
Inventory
Management
System
15/05/09 3 Bach
Ngoc
Toan
Completed

5

Entity
Relationship
(ER)
Diagram
Sales and
Inventory
Management
System
18/05/09 1 Lam Thi
Phuong
Loan
Completed

6

Database
Design/Stru
cture
Sales and
Inventory
Management
System
19/05/09 1 Luong
Hoang
Manh
Completed

8 Design
Snapshot
Sales and
Inventory
Management
System
20/5/09 1 Bach
Ngoc
Toan
Completed

Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


23

Chapter 8: Checklist of Validations
Form No.8/eProjects/Tab/ver1.0

Checklist of Validations

Option Validated
Can a new user who gets registered, enter the application after
logging in?
Yes
Do all the options present in the application display the correct
result?
Yes
Does the application’s functionality resolve the user problem, and
satisfy their needs?
Yes
Has the hardware and software been correctly chosen? Yes

Inventory Managemenet Group 1-C0809J1-Bach Khoa-Aptech


24

Chapter 9: Submission Checklist
Form No.9/eProjects/Tab/Ver1.0

Sr.
No.
Particular Yes

No NA Comments
1. Are the users able to log in to the
application after validation is
performed on the user name and
password?
Yes


2. Are the users able to modify their
details after getting registered?
Yes


3. Are all the screen contents devoid of
spelling mistakes?
Yes


4. Is the user able to trade on fund
which has been selected?
Yes

5. Is the application user-friendly?
Yes