ادارة المخازسن ويب

ZU LIAN INVENTORY
MANAGEMENT SYSTEM
By
LIM ZHI WEI
SCHOOL OF ARTS AND SCIENCE
TUNKU ABDUL RAHMAN COLLEGE
KUALA LUMPUR
ACADEMIC YEAR
2010/2011
Project i
ZU LIAN INVENTORY MANAGEMENT
SYSTEM
By
LIM ZHI WEI
Supervisor: Mr. Wong Yoke Seng
A project report submitted to the School of Arts and Science
in partial fulfillment of the requirement for the
Bachelor of Science, Campbell University, U.S.A,
And
Advanced Diploma in Science.
Division of Computer Science
School of Arts and Science
Tunku Abdul Rahman College
Kuala Lumpur
2010/2011
Copyright 2010 by Tunku Abdul Rahman College.
All rights served. No part of this project documentation may be reproduced,
stored in retrieval system, or transmitted in any form or by any means without
prior permission of Tunku Abdul Rahman College.
Project ii
Declaration
The project submitted herewith is a result of my own efforts in totality and in every
aspect of the project works. All information that has been obtained from other
sources had been fully acknowledged. I understand that any plagiarism, cheating or
collusion or any sorts constitutes a breach of College rules and regulations and would
be subjected to disciplinary actions.
__________________________
Student’s Name : Lim Zhi Wei
Programme : Computer Science And Computer Mathematics
Project iii
Abstract
This final year project is carried out as a partial fulfilment of the requirement for
Bachelor of Science. This final year project being develop with the purpose of
delivered a web base manufacturing inventory management system which automated
the process of manufacturing process and incorporate with sales forecasting process.
Zu Lian Inventory management will work closely with other part of the system
existed in that company such as Logistic department, R&D department, Accounting
department, Human resources as well as Machinery department by the mean of
sharing the same information in a integrated database. In short, it only covered the
inventory management processes in a supply chain management environment.
Project covered area included the ability to handle raw material purchasing, product
manufacturing processes and finish goods sold out processes as well as sales
forecasting and access control to the used of the inventory system. Covered area is
divided into five modules which are purchasing module, sales module, stock
maintenance, sales forecasting and security module.
The development platform of Zu Lian inventory was C#.NET and SQL Server 2005.
Three tier approach have being used throughout the development of the Zu Lian
inventory system which is presentation, business logic and data access layer.
In system planning stage, a project scope has being produced to define the boundary
of the project scope. In system analysis stage, system requirement specification has
being produced to define the actual user requirement. Within the system design stage,
a database structure has being defined. System implementation was actual
development of the Zu Lian Inventory. Lastly, the system testing involve testing final
product to ensure it conform to user requirement.
Project vii
The result of this project was a satisfaction. Major functionality required was present
and incorporated with forecasting ability. Although there are several weakness of this
system, after all the system are ready to be deployed.
Throughout the development of this system, the essence of each stage of system
development life cycle (SDLC) was acquired. Beside, project time management and
schedule was being practise in depth. Through the development using three tier
approach, the benefit of this implementation was realised. Lastly, the consistency of
coding practise was also developed.
Project viii
Acknowledgement
The author wishes to express his sincere gratitude to project supervisor, Mr. Wong
Yoke Seng, for his guidance, constant support and encouragement throughout the
completion of this final year project. As a supervisor, Mr Wong has done what he
could and even more then what he should in assisting the completion of this final year
project. The author would also like to convey his heartfelt appreciation to 2 Zhu Lian
company staff in providing the actual process in the manufacturing company.
The author would also like to express his appreciation on this final year project
moderator, Mr Andrew Tan for his kindness in arrange the system testing date and
time suit to the author needs.
Last, but not least, the author would also like to personally thank his family, friends in
TAR College and his/her fellow course-mates who have one way or another extended
their assistance in completing this project.
Project ix
Table of Contents
Declaration............................................................................................................................. iii
Abstract.................................................................................................................................. vii
Acknowledgement ................................................................................................................... ix
System Planning ..................................................................................................................... 13
1.1 Introduction........................................................................................................................ 13
1.2 Project Aims and Objectives.............................................................................................. 13
1.3 Company Background ........................................................................................................ 15
1.4 Project Scope ...................................................................................................................... 16
1.5 Project Schedule ................................................................................................................. 19
1.6 Methodology Used.............................................................................................................. 21
1.7 Development Environment ................................................................................................. 22
1.8 Operation Environment...................................................................................................... 23
1.9 Chapter Summary / Critical Evaluation .............................................................................. 24
Requirements Analysis .......................................................................................................... 27
2.1 Introduction........................................................................................................................ 27
2.2 Fact Gathering.................................................................................................................... 27
2.3 Fact Recording.................................................................................................................... 31
System Design......................................................................................................................... 41
3.1 Introduction........................................................................................................................ 41
3.2 Use Case ............................................................................................................................. 41
3.3 Activity Diagram ................................................................................................................ 52
3.4 Sequence Diagram .............................................................................................................. 60
3.5 State Chart Diagram........................................................................................................... 74
3.6 Final Class Diagram........................................................................................................... 77
3.7 Entity Relationship Diagram / ER Diagram ....................................................................... 79
3.8 Data Dictionary................................................................................................................... 82
3.9 Package Diagram ................................................................................................................ 90
3.10 Deployment Diagram .......................................................................................................... 93
3.11 User Interface Design/Prototype ......................................................................................... 94
3.12 Report Design..................................................................................................................... 97
Programming....................................................................................................................... 101
4.1 Introduction...................................................................................................................... 101
4.2 Feature .............................................................................................................................. 101
4.3 Algorithm Used................................................................................................................ 102
4.4 Programming Issue ........................................................................................................... 105
4.5 Chapter Summary / Critical Evaluation ............................................................................ 106
Software Testing.................................................................................................................. 108
5.1 Introduction...................................................................................................................... 108
5.2 Testing Strategies.............................................................................................................. 108
5.3 Test Plan ........................................................................................................................... 109
Project x
5.4 Chapter Summary / Critical Evaluation ............................................................................ 114
Conclusion ............................................................................................................................ 116
6.1 Link to Seminar ................................................................................................................ 116
6.2 Justification of choice of tools, technique and methodology............................................ 116
6.3 Evaluation against the Project Objective .......................................................................... 118
6.4 Project Management Issue ................................................................................................ 119
6.5 Evaluation of project......................................................................................................... 120
6.6 Future Project Improvement ............................................................................................. 120
6.7 Personal Reflection ........................................................................................................... 121
References............................................................................................................................. 122
Appendices............................................................................................................................ 123
User Guide ............................................................................................................................ 128
Project xi
Zu Lian Inventory Management System Planning
Chapter 1
System Planning
Project 12
System Planning
1.1 Introduction
In this chapter, it will discuss about the objective of the project as a whole. Content
included project aim and objective, project targeted company, project scope, project
schedule, methodology used, development environment, and operation environment.
1.2 Project Aims and Objectives
The Zu Lian inventory management system yet to be develop must solve the flaw of
current used inventory management system. There are several objectives that are to be
achieving within this project development as listed below.
1.2.1 Cross Platform
 This web based Inventory management are mean to replace the old application
that are currently use by the company which are legacy and platform dependent.
The current Inventory Manage system that used by the company is specially
design to suit the platform that being used by the company back at 1997 which is
Microsoft Windows 98 which is antique and outdated nowadays. Current
Inventory management is causing a lot of unsatisfactory of user when they
intended to update the operating system (OS) platform that being used and fail to
achieve it without perform necessary update to the application. Problem faced is
application is fail to communicate with server due to newer version of window
security which need to tune the current application to solve it. Beside, the current
application is also fail to save file to local file of the newer version of OS because
of security issue as well.
 The web based application will definitely solve this problem because it only relies
on browser and not OS dependent. It only requires a standard browser to be
installed such as Window Internet Explorer which is bundle with any version of
window. The aim of this development is to build a web based application that can
be deployed and use despite the operating system of computer using the
application.
Project 13
1.2.2 Forecasting and analysis
a) Inventory level forecasting
 The Inventory management application yet to be develop must capable to
perform prediction on the inventory level changes in the future to enable stock
reorder to be carry out in an effective way and minimize the stock over order
issue.
 It must capable to suggest a suitable of stock reorder amount after forecasting
process is carry out
b) Sales Forecasting
 Must able to keep track the sales record and use that information to forecast
the future sales amount as well as sales trend
 Must capable to maintain between customer demand and stock level to allow a
successful customer services.
1.2.3 Security and Safety
a) Authentication
 Besides providing basic authentication capability such as allow authenticated
user to access and manipulate the inventory records, it should allow
managerial role user in each department to manipulate their subordinate access
power. For instance, a new staff only allows viewing and adding new sales
instead of deleting sales until they gain more experience.
Project 14
1.3 Company Background
ABC Marketing (M) SDN BHD is establish at the mid of year 1989 as a direct sales
company with the vision to establish a full Malaysian owned direct sales enterprise.
ABC Marketing (M) SDN BHD today had extend his business boundary from a
Penang based direct selling company to a major player in the regional direct selling
market.
On top of direct selling, ABC Marketing SDN BHD is also a manufacturing company.
ABC Marketing SDN BHD today have diversify his product line from originally only
produce gold plated jewellery to Food and Beverage, Nutritional Supplement, Home
Care, Personal care, Air Treatment, water treatment and sleep enhancement product.
ABC Marketing SBD BHD have evolve from small company in 1989 until today with
an extensive network of 230 agency in the South East Asian region and had emerge as
one of the leading companies in the direct selling region for its innovative and reliable
Figure1.1ProjectScopeChart
product.
ABC had their business sited in major country around the Asia such as Malaysia,
Indonesia, Thailand and Singapore. Each of the branches consists of their own
departments including marketing, customer service, manufacturing, Accounting,
Editorial, Administration and Advertising & promotion departments which are located
with the interior of the administrative office.
(Due to request of interview was being rejected, the information of the company
is conceal for authorization reason)
Project 15
1.4 Project Scope
No. Sub Module Name Description
i. Sales Manipulation Provide functionality to handle view, add, delete and
change of sales order information
ii. Invoice Generation Capable to generate Invoice of particular sales using
information retrieved from the database
iii. Issue Work Order Capable to allow the user to issue work order to the
production department whenever the sales inventory
drop beyond certain level
iv. Shipment Arrangement Capable to arrange shipment for a particular sales which
will later then pass to shipment department
v. Sales Item Reject Capable to issue write off to product that found faulty
Handling and update the inventory database

i. Purchasing Manipulation Provide the functionality to handle view, add, delete and
change of purchasing order information as well as
vendor information
ii. Material Receiving Capable to handle receiving of stock from the vendor
Handling and keep track defect item replacement from vendor
iii. Purchasing Order Capable to generate purchase order information based
Generation on the information retrieve from the database

i. Production Material Capable to keep track the material level purchasing
Manipulate from vendor and alert for reordering.
ii. Production Material Capable to keep track all material batch using in
Usage Monitoring production
iii. Finish goods Provide the functionality to manipulate the stock level
Management such as view, add, delete, and alter the stock
information produce from production department
Project 16
1.4.1 Sales Maintenance Module
1.4.2 Purchasing Module
1.4.3 Stock Maintenance
Project 17
iv. Finish goods sales Capable to keep track which batch of finish goods sold
monitoring in each sales transaction
i. Authentication Allow authenticated user to login to the inventory
system to perform their related job
ii. Access Privilege Allow managerial position staff to manipulate their
Manipulation respective subordinate access power to the system
iii. Add New User Allow managerial position staff to add new subordinate
to access to the system
iv. Update User Allow user to change and update their information
v. Delete User Allow managerial position staff to delete user no longer
have access to the system
1.4.4 Security Module
i. Sales Forecasting Capable to forecast sales of 3 month ahead
ii. Graph Capable to present sales forecast result in line graph
format
1.4.5 Forecast Module
Figure1.2aProjectScheduleGant
Project 18
1.5 Project Schedule
Figure1.2bProjectScheduleGant
Project 19
Project 20
1.6 Methodology Used
Methodology used throughout the system development life cycle is Prototype modal.
Prototyping
Initial Design Customer

Requirement Evaluation
Review and
Update
Maintain Test Deployment
Figure 1.3 Prototype Modal
Project commences with initial requirement which produce the project scope
document to define the actual size of the project and user requirement was recorded
into the system requirement specification.
As project development proceeds, new requirement was realize and the new user
requirement was incorporated into the design, each of the module developed was go
through the cycle until user satisfaction was achieved.
After each of the module development was completed and review by user. A final
integration of each module was done and the system develop was put through a series
of testing. After the testing was done, a user acceptance test (Final Testing) was
carried out to validate the final product. After the user acceptance was passed, the
system was ready to be deployed and used.
Project 21
1.7 Development Environment
To develop an up-to-date web based application the following development platform is being
use:
1.7.1 Hardware
A. Personal computer
a. Server (installed with Window server 2005)
 Served as data storage of inventory data and handle request from user
 CPU
o Pentium 4 1Ghz
o 512 MB ram
o 80 GB Hard disk
b. Client
 Serve as client to simulate real life application environment and carry out the
development of the project
1.7.1 Software
A. ASP.net with C# in Microsoft Visual 2008
 To develop a successful and up-to-date web based application, selection of a
suitable and latest development tools is an important step. The ASP.net is a latest
development technology that promotes integration between various programming
platforms.
B. Microsoft SQL 2005 Express
 Used to manipulate the data within the database easily with the feature supported.
C. Adobe Flash Professional CS5
 Use develop animation feature in presenting the result to user typically in
producing forecasting result through flash animation.
Project 22
1.8 Operation Environment
The following is the operation structure of the intended Inventory Management
System
Figure 1.4 Deployment Chart
The Operation environment of the new Inventory management system will allow staff
inside the company as well as outside company to log into the system to perform their
job.
There will be an application server which will be responsible to handle user request as
well as serve as data storage of the inventory system. Any of the company staff will
have to login first before any action can be performs. The company will also provide
wireless access point to allow user to access the inventory wirelessly.
Project 23
1.9 Chapter Summary / Critical Evaluation
Within the initial state of the project varies problems and obstacles has being face. For
instance, finding a suitable company as the survey subject in order to gain more
understanding on the actual functionality required by an inventory management
system. It is essential in order to develop a up to standard inventory management
system. Although information is acquired from two staff from a manufacturing
company which from purchasing and sales department, information collected is not
sufficient due to manufacturing department interview request to the company has
being rejected with reason of private and confidentiality of their business flow.
Due to unfamiliar to actual inventory management system functionality, defining the
project scope would become tough job as inappropriate project scope could lead to
final system to be out of functionality scope or project failure. To counter this
problem, a thorough research on the inventory management is carried out to research
on current demanding functionality requirement on an inventory system. Functionality
such as forecasting on the sales and stock demand is priority over others because if
would reduce stacking stock problem and promote just in time (JIT) production to
reduce over manufacturing problem.
Next, the development methodology of the system development life cycle (SDLC) is
also an essential element towards delivered a satisfaction final system. Various
methodologies had being research thoroughly, for example Spiral modal, Waterfall
modal and Prototype modal. Each of them carries along their pros and cons
throughout the development cycle, for instance waterfall modal would reduce the cost
of the development but it might lead to unsatisfied system or even project failure. As
for Spiral modal, it is more suitable to develop a highly sophisticated system but will
incurred extra cost. Prototype modal are more suitable to develop a medium size
system and incurred only decent cost. At the end of the research the prototype modal
is chosen as the development methodology.
To develop a system rapidly and efficiently, the choice over the integrated
development environment (IDE) tools and development platform played a vital role.
Within this project, ASP.net framework 3.5 was selected. ASP.net 3.5 was much more
robust as it upgrade from 2.0. Backend classes support for dealing with the database
and client side was significantly efficient. A proper IDE with development support
Project 24
feature was essential to allow rapids system development which in return reduce the

development cost and increase customer satisfaction. IDE used was Microsoft visual
2008 which bundle Microsoft SQL 2005 Express along.
Project 25
Zu Lian Inventory Management Requirements Analysis
Chapter 2
Requirements Analysis
Project 26
Requirements Analysis
2.1 Introduction
In this chapter, the technique used to acquire the information regarding the system
requirement will be discussed in detail. It will be included the fact gathering technique
and fact recording. In the fact gathering, it will discuss about the process of
interviewing 2 Zhu Lian Company staff about their job flow. In the fact recording, the
information collected will be recorded in words as well as activity diagram. The
overall system requirement will show in use case format in subsequence chapter.
2.2 Fact Gathering
a. Interview
In order to gain more understanding on the Inventory management flow of an actual
manufacturing company, a face to face interview and phone interview had being
carried out with 2 existing employees of the ABC company which from purchasing
department and sales department respectively. In the process of interview both
employee had being ask to describe the existing flow of the actual transaction
between request of raw material from supplier and purchase request from the
customer. The detail flow of both transactions is described in figure 1.1 and figure 1.2.
As in figure 1.1 Purchase raw material activity, when the manufacturing company
want to purchase raw material from the supplier, they are require to filled in a
preorder form which state the actual amount of raw material of each type, the
negotiate price and the due date. If the supplier is not agreed with the offer receive
the process is repeat until an agreement of both party achieved. After agreement is
settled, the manufacturing company will issue a formal purchase order to supplier.
The supplier will acquire the material requested and send it before or on time to the
manufacturing company. Upon receiving, the manufacturing company’s purchasing
staff will check the raw material for defect. If no defect found, supplier will receive
acknowledgement and send invoice to the company purchasing staff which will be
passes to finance department. If a defect unit is found, the manufacturing company
will filled in a Vendor Corrective Action Request (VCAR) form which attached
together with photo which described the status of defect unit, the original stock unit
Project 27
receive will be key in to system with extra note attach to the delivery order receive.

The supplier will having a internal investigation carry out to investigate cause of
defect and will return a solution to manufacturing company based on defect unit
amount. If the amount of defect is small, supplier will inform the manufacturing
company to dispose the defect unit and will issue a credit note to the company. In a
formal approach, the ABC Company will issue a Good Return to Vendor (GRTV)
form to supplier form and signed by supplier before the dispose action will be taken
by the manufacturing company. If the defect amount is large, the supplier will resend
the raw material tie to the defect amount to manufacturing company. The supplier
company will update the stock delivery status (remove the extra note). After the
delivery process is complete, the supplier will send the invoice to the company’s
finance company to make payment in a given duration and the raw material
purchasing flow is consider complete.
Right before a sales process can begin, both ABC Company and customer will had a
Minimum Order Quantity agreement signed which specify the minimum order
quantity of a particular product on a set of duration. The customer must at least order
the minimum quantity in the duration agree by both party, and the customer will order
the product on the monthly basis. As in figure 1.2 Sales flow, the customer will send
the ABC Manufacturing company a purchase order, the sales department staff will
create a sales order. The amount of the particular product will be checked. If the
amount is sufficient, shipment will be arrange and the Delivery order will be
generated and send to the customer. If the amount is not sufficient, the sales
department will issue a work to the manufacturing department for production. After
the production is done and the stock level is sufficient, the sales staff will arrange
shipment send to the customer company together with the delivery order.
Upon the receiving, if no defect is found the manufacturing company will receive the
acknowledgement and an invoice will send to customer and the flow is completed. If
a defect is found, the customer will fill in the defect status form and inform the
company. The company will verify the defect status and send back a write off
response to the customer to dispose the defect unit and another shipment will be
arrange to replace the defect unit.
Beside the main flow, the functional requirement and non functional requirement is

also being enquire which will be specify at the later part.
Project 28
Figure 2.1 Purchase Material Flow Activity Diagram
Project 29
Figure 2.2 Sales Flow Activity Diagram
Project 30
2.3 Fact Recording
2.3.1 General Description
1. Product Function
This Web based Inventory management system which yet to be developed will have
the basic functionality as below:
i. Sales transaction Processing
- Capable to handle sales processes such as create sales order, generate invoice,
keep track purchase order, issue work order, defect unit tracking, arrange
shipment
ii. Raw material management
- Capable to provide functionality to manage the raw material such as generate
raw material purchase order, stock tracking, handling receiving, defect unit
tracking.
iii. Stock Maintenance
- Capable to manage the stock of raw material as well as finish good such as stock
level control between the production and sales such as the purchase of raw
material, production of finish goods, keep track production efficiency, inform
stock level replenish, and finish goods sold out process.
iv. Staff info Maintenance
- Capable to control the access power of the company user base on the access
power and allow authenticated staff to perform process within his job area.
v. Forecasting
Capable to provide analytical capability to predict future demand of the sales
demand and production amount.
Project 31
2. Relationship to other information system

a. Finance management system
This Zu Lian inventory management system will work closely with the ABC
Company Finance department finance management system. It will responsible
to carry out all the function of the inventory management regarding the
product sold to their customer and raw material purchased from their supplier.
It would not participate or interrupt the flow of the money transaction incur
within the sales and material purchasing.
b. Research and Development information system
Zu Lian inventory management system will only govern the process of
product production based on the information of each product material
proportion stored in the database. It will not handling the process new product
invention and development process.
c. Logistic management system
Zu Lian inventory management system will responsible to record down the
shipment detail for particular sales. It would not responsible for the shipment
arrangement and schedule of those sales as it will be handled by the company
logistic department management system instead.
d. Human resources and Machinery information system
Zu Lian inventory management system will carried out all production schedule
including production staff schedule and production machinery scheduling. It
would not interfere or participate in the management of those property as it
will be handled by the company human resources and machinery information
system.
3. User Problem Statement
i. Stock level unbalance with demand
- inventory shortage and overstock often happen cause the company to
suffer lost of good will and unsalable stock
- due to current system does not incorporate with forecasting ability,
overwhelm demand often occur that require the manufacturing to issue
work order which incur extra cost such as overtime wages and extend
production machine operation time
Project 32
ii. Does not provide proper tracing of defective item
- Manual record of defective shipment is require on unsatisfied shipment
causing extra refer back process require to trace back defective shipment
ID
iii. Separated User Interface
- When purchasing clerk want to simultaneously handling the receiving and
purchasing order, the clerk are require to minimize the current interface
and open another user interface to do cross referencing
iv. Manual tracing of shipment arrival date
- Current system does now provide tracing mechanism to trace the shipment
arrival date which require the clerk to manually trace the shipment arrival
4. User Objectives
i. Provide extension of current Inventory system
- Provide all current system functionality and incorporate new functionality that
enhance worker and manufacture company productivity
ii. Incorporate Forecasting ability
- Provide forecasting ability to predict future inventory demand as well as
product manufacture amount to reduce lost in good will and unsalable
inventory
(Will be further discuss in functional and non functional requirement section)
5. General Constraint
Newly develop system must meet the following condition
i. Hardware Platform
- must reuse the current hardware with the mean of minimal enhancement in
hardware
ii. Software Platform
- Must capable to work with other IS currently use by the company such as
Finance management system
- OS Platform : Microsoft XP SP3 and Microsoft server 2003
iii. Language
Project 33
- All language must in standard English with no technical jargon
2.3.2 External Interface Requirement
1. User Interface
a) Menu Bar
 The menu bar of all functionality related to the user must be appearing
at every page throughout the whole inventory management system (e.g.
Sales, Shipment, Defect tracking for sales staff). Every staff will only
see menu bar item related to their job area as well as access power(e.g.
purchasing clerk can only see material management related processes).
 The menu bar must be consistent throughout the navigation of the user
when performing their job transaction
b) Tool Tips
 Suitable amount of reminder should be display to user to allow them to
understand what they should do (e.g. display input format to user when
user key in information).
c) Color
 The number of color used should be limited to 4-5 colors to avoid
dazzle. Appropriate color and consistence usage should be prioritize
(e.g. using red color to display warning message only throughout the
whole system).
d) Appropriate Inform message
 Message use to inform the user within the system should be free from
technical jargon as well as error code(e.g. “Runtime error orcur at
storing sale information” or “Error code:2345”)
e) Feedback
 appropriate response should be display to user to allow the user to
know that processing in progress (e.g. Progress bar).
f) Help
Project 34
 Provide a help session within the system to guild the user step by step
to complete the transaction process
g) Standardize Graphic User Interface(GUI) Component
 all GUI component should be consistent in form of shape and size(e.g.
button should be same size and shape(e.g. ractangle))
 use same representation throughout the system. For example the save
button should display either only a diskette icon or save word to avoid
user confuse.
h) Screen size
 screen size should be fix in any of the pc/mac which run the software.
This could increase the user familiarize thus increase productivity.
i) Font
 all font use should be same throughout the software develop to reduce
user frustration and confusion(except for title and informational
message)
2. Hardware Interface
a) Keyboard
 Allow the user to key in text based data to the system.
b) Mouse
 Allow the user to make selection such as radio button and check box as
well as navigation through the whole system.
c) Printer
 Allow user to print out transaction related document.
3. Software Interface
a) SQL Server Express
 The database use by the system must be SQL Server Express to
store data related to the whole system operation and business
information.
b) Operation System(OS)
Project 35
 New web based inventory management(client) must be capable
to run at any OS platform
 New web based inventory management(client) must be capable
to run at any OS platform
4. Communication Interfaces
a) Client will interact with the server through the local LAN as well as internet
to exchange data as well as carry out business function such as update
information, add new sales, cancel sales, and etc. The changes will take
effect immediately after the transaction being commit. All client will
connect and do transaction with that server only.
2.3.3 System Requirement
A. Functional Requirement
1. Sales Maintenance Module
i. must able to allow the user to create a new sales order, insert sales
information and save to database
ii. shall allow the user to check for stock level before create new sales order
iii. will allow the user to arrange shipment and generate delivery order
iv. must able to generate invoice for received shipment
v. shall provide functionality to keep track defect item receive by customer
vi. should automatically reduce the stock level and provide appropriate
message regarding the current stock status
2. Purchasing
i. must allow the user to generate purchase order
ii. must provide functionality to handle material receiving
iii. must provide functionality to handle defect item receive and return
processes
iv. must capable to generate vendor corrective action response(VCAR) form
and Goods return to vendor form(GRTV)
3. Forecasting Module
i. must provide graphical report regard the forecast result for both sales and
demand
Project 36
ii. must provide a provision of at least 3 month of sales based on passed sales
and stock demand level data
iii. forecasting result shall be display in graph format as well as table format
iv. must allow user to print the forecasting result as a report with proper
format
4. Security Module
i. Must provide functionality to allow managerial position staff to add, delete,
and update staff info
ii. Must provide authentication functionality to provide access control to user
on the system
iii. Must allow the user themselves to update their personal information
iv. must allow the managerial position staff to change the access power of
each user
5. Stock Maintenance
i. must allow purchasing clerk to update the material information and
material level
ii. must allow purchasing clerk to update the finish goods information and
goods level
iii. must provide functionality to allow the user to keep track each
manufacture batch material usage and quantity of goods produce to
calculate the cost of production
iv. must allow the user to keep track the manufacture lost if manufacture fault
occur.
B. Non Functional Requirement
a. Reliability
i. The failing rate of the system must be keep as low as possible
which is lower than 1% would be preferred.
b. Portability
i. Must able to be use in any platform regardless of what OS platform
user currently use such as Windows XP, Linux and etc.
c. Usability
i. User friendliness should be prioritize, it must be easy to use with
litter or no training required where possible. There should be a help
session to allow user to refer to wherever they are doubt about
Project 37
something. Response given by the system to user must be clear
enough to allow user to know that the process is carry out. Any
critical activity like delete a record should be ask the user second
confirmation before deleting is perform.
d. Efficiency
i. Processing Requirement
 The new software delivered shall be capable to run in a
standard personal computer with atom processor without
extensive processing power
ii. Performance Requirement
 Each transition of GUI to GUI must not taken more than 2
seconds. Processing such as retrieve information should be
done within 4 seconds and must not more than that.
C. Organization requirement
a. Implementation requirement
i. The new system shall not require the company to buy any third
party library or software which will incur extra operation cost of
the new system. The system main data storage should be capable to
store in the current server with only minimum upgrade as possible
to reduce transition cost from replacing the old system to the new
system.
b. Delivery requirement
i. The new System should be deliver as soon as possible without
affecting the system quality.
D. External Requirement
a. Legislative Requirement
i. newly develop system shall comply with copyright with the mean
of no copyright issue. New system shall not cause any legal issue
to arise.
b. Interoperability Requirement
i. Since the system will work closely with the finance system
currently company have. It must be able to share database finance
info with the finance system(only for limited access) without cause
any changes with the finance database structure.
Project 38
Within the process of collecting user requirement, varies difficulty have being faced.
First of all, the communication gap between a business and technical personnel was a
major difficulty face during the process of interview. For instance, in the process of
telephone interview to the survey company employee, business jargon was used by
the employee in describe the flow of the system. A series of question and answer to
allow thorough understanding of the business flow.
Next, in enquiring about the extra functionality that they intended to incorporate to
their system, the user tend to express using their own word and even not clear with
their needs. Similarly, in depth questioning is require to clear out the intention of the
user.
Project 39
Zu Lian Inventory Management System Design
Chapter 3
System Design
Project 40
System Design
3.1 Introduction
In this chapter it will mainly cover the system design phase of the SDLC processed. It
will document the actual implementation of the developed system. Sub chapter
included sequence diagram for all system modules, final class diagram, database
design included the entity relationship and data dictionary, user interface design or
prototype and report design.
3.2 Use Case
1. Overview Use case diagram of new system
Figure 3.1 Overview use case diagram
Project 41
2. Sale Maintenance Use case
Use Case: Sales Maintenance
Description of Feature
 Provide essential function to support daily sales transaction like manage
sales, shipment arrangement, defect maintenance as well as produce
related transaction report
Actor Involve: Sales Clerk
Main Flow:
Actor Action System Response
1. Sales Staff log into system
2. Staff select Sales Maintenance
3. Display Sales sub menu: add,
delete and update sales, arrange
4. Staff select add new Sales
shipment, defect maintenance
6. filled up new sales detail 5. Prompt adding new sales user
Project 42
Figure 3.2 Sales Maintenance Use Case Diagram
interface
7. Save to database
Alternative flow:
A1. Step 4:
4. Staff select update sales 5. request for invoice id
6. Staff input Invoice ID 7. Locate and display sales info
8. Change/update sales info and
9. save to database
summit
A2. Step 4:
4. Staff select delete sales 5. request for invoice id
6. Staff input invoice ID 7. Locate, display sales info and display
8. press delete button
9. prompt for confirmation
10. select ok
11. information delete from database
A3. Step 4:
4. Staff select arrange shipment 5. prompt adding new shipment UI
6. Staff fill in shipment information 8. save information to database
A4. Step 4:
4. Staff Select Defect Management 5. request for batch number
6. Staff input batch number 7. display batch defect information
8. Staff update defect information and
9. save to database
summit
Project 43
3. Staff Info Maintenance Use case
Use Case: Staff Info Maintenance
 Provide essential function to allow human resource and managerial
staff to maintain information about the worker including their login
access ability
Actor Involve: Manager, Human Resource staff
Main Flow 1(Manager):
1. Manager login to system 3.System display out Staff
maintenance menu
2. Manager select Staff Maintenance
4. Manager select Access control 5.System display out Access control
menu
6. Manager input the staff id
7. System display staff access ability
8. Manager change the staff access
power and click save 9.System save changes to database
and display message of changes
Figure 3.3 Staff Info Maintenance Use Case Diagram
Project 44
saving status
Alternative flow:
A1. Step 4:
4. Manager select Delete staff 5. System prompt for staff ID
6. Manger staff search for staff and 7. System prompt for confirmation
click ok
8. Manger click ok
9. System update database and display
update status
Main Flow 2(Human resource staff):
1. HR staff login to system 2. System display out staff maintenance
menu
4. System display staff details form
3. HR staff select add new staff
6. System save staff detail and prompt
5. HR staff fill in staff detail and click
save status
save
Alternative flow:
A1. Step 3:
3. HR staff select update staff 4. System prompt for staff id
5. HR staff search for staff 6. System display out the staff detail
according to staff access power
8. System update database and display
7. HR staff make changes to staff info
update status
Project 45
4 Purchasing Use case
Use Case: Purchasing
 Provide essential function to support daily material ordering start with
placing order to receiving.
Actor Involve: Purchasing Clerk
Main Flow:
1. Purchasing Staff log into system
2. Staff select Purchasing 3. Display Purchasing sub menu: new
order, receiving, defect tracing
shipment, defect maintenance
4. Staff select place new order 5. Display new material form
6. Staff fill in new material purchase 7. Generate and print out purchase
order
info and click summit
Alternative flow:
A1. Step 4:
4. Staff select receiving 5. Prompt for order id
6. Staff input the purchase order id 7. display order receiving form
8.Staff input the receiving information 9. System save to database and prompt

saving status.
A1.1. Step 8:
8. Staff input the receiving information 9. System display vendor corrective
with defect action request form
10. Staff fill up VCAR form 11. System print VCAR form.
Figure 3.4 Purchasing Use Case Diagram
Project 46
Use Case: Forecasting
 Provide forecasting ability to managerial position staff such as purchasing
department Manager, sale department manager, and CEO. Some manager
only can see trend and forecasting according to their power
Actor Involve: Managerial Position staff
Main Flow:
1. Manager log into system and select 2. display forecasting sub menu: sale
forecasting forecast, demand forecast, trend
analysis
3. Manager select trend analysis 4. prompt for duration
5. Manager input date 6. Process and display total Sales and
demand of the period, and trend
information
8. print trend analysis with format
7. Manager select print as report
Project 47
5 Forecasting
Project 48
Alternative flow:
A1. Step 3:
3. Manager select sales forecasting 4. System display the current trend and
display a 3 month provision forecasting
6. System generate forecasting report
A2. Step 3:
3. Manager select demands forecasting 4. System display the current trend and
display a 3 month provision forecasting
Figure 3.5 Forecasting Use Case Diagram
6. System generate forecasting report
Project 49
6 Stock Maintenance Use case
Use Case: Stock Maintenance
 Provide forecasting ability to managerial position staff such as purchasing
department Manager, sale department manager, and CEO. Some manager
only can see trend and forecasting according to their power
Actor Involve: Warehouse Staff
Main Flow:
1. Warehouse Staff log into system 2. display Warehouse sub menu:
and select forecasting Material, Finish Goods, Defect,
Manufacturing
3. Warehouse Staff select material 4. display material list
5. Warehouse Staff select require to 6. save to database(purchasing will
order and click summit receive this info) and prompt for save
status
Alternative flow:
A1. Step 3:
3. Warehouse Staff select finish goods 4. display finish goods list
5. Warehouse Staff select require to 6. save to database(production
produce and click summit department will receive this info) and
display for save status
A2. Step 3:
3. Warehouse Staff select defect 4. display defect form
5. fill in defect information and 6. save to database and display save
summit status
Figure 3.6 Stock Maintenance Use Case Diagram
Project 50
Project 51
3.3 Activity Diagram
3.3.1 New User
Figure 3.7 New User Activity Diagram
3.3.2 Update User
Figure 3.8 Update User Activity Diagram
3.3.3 Delete User
Figure 3.9 Delete User Activity Diagram
Project 52
3.3.4 Access Privilege Control
Figure 3.10 Access Privilege Control Activity Diagram
3.3.5 New Sales Order
Figure 3.11 New Sales Order Activity Diagram
Project 53
3.3.6 Sales Receiving
Figure 3.12 Sales Receiving Activity Diagram
Project 54
3.3.7 New Work Order
Figure 3.13 New Work Order Activity Diagram
Project 55
3.3.8 Sales Forecasting
Figure 3.14 Sales Forecasting Activity Diagram
Project 56
3.3.9 New Purchase Order
Figure 3.15 New Purchase Order Activity Diagram
Project 57
3.3.10 New Supplier
Figure 3.16 New Supplier Activity Diagram
3.3.11 New Material
Figure 3.17 New Material Activity Diagram
Project 58
3.3.12 Purchasing Receiving
Figure 3.18 Purchasing Receiving
Project 59
Zu Lian Inventory Management
3.4 Sequence Diagram
3.4.1 Create User
Figure 3.19 Create User Sequence Diagram
Project 60
3.4.2 Delete User
Figure 3.20 Delete User Sequence Diagram
Project 61
3.4.3 Update User
Figure 3.21 Update User Sequence Diagram
Project 62
3.4.4 Access Privilege Control
Figure 3.22 Access Privilege Control Sequence Diagra
m
Project 63
3.4.5 New Sales Order
Figure 3.23 New Sales Order Sequence Diagram
Project 64
3.4.6 Sales Receiving
Figure 3.24 Sales Receiving Sequence Diagram
Project 65
3.4.7 New Work Order
Figure 3.25 New Work Order Sequence Diagram
Project 66
3.4.8 Sales Forecast
Figure 3.26 Sales Forecast Sequence Diagram
Project 67
3.4.9 New Material
Figure 3.27 New Material Sequence Diagram
Project 68
3.4.10 New Supplier
Figure 3.28 New Supplier Sequence Diagram
Project 69
3.4.11 New Purchase Order
Figure 3.29 New Purchase Order Sequence Diagram
Project 70
3.4.12 Purchasing Receiving
Figure 3.30 Purchasing Receiving Sequence Diagra
m
Project 71
3.4.13 New Production Order
Figure 3.31 New Production Order Sequence Diagra
m
Project 72
3.4.14 Verify Production (3.1.13 Sub process)
Figure 3.32 Verify Production Sequence Diagram
Project 73
3.5 State Chart Diagram
3.5.1 Sales Order
Figure 3.33 Sales Order State Chart
3.5.2 Sales Order Item
Figure 3.34 Sales Order Item State Chart
3.5.3 Product
Figure 3.35 Product State Chart
Project 74
3.5.4 Work Order
Figure 3.36 Work Order State Chart
3.5.5 Production
Figure 3.37 Production State Chart
3.5.6 Purchase Order
Figure 3.38 Purchase Order
Project 75
3.5.7 Purchase Order Item
Figure 3.39 Purchase Order Item State Chart
3.5.8 Purchase Order Defect Item
Figure 3.40 Purchase Order Defect Item State Chart
Project 76
3.6 Final Class Diagram
Figure 3.41a Final Class Diagram
Project 77
Figure 3.41b Final Class Diagram
Project 78
3.7 Entity Relationship Diagram / ER Diagram
Figure 3.42a Entity Relationship Diagram
Project 79
Figure 3.42b Entity Relationship Diagram
Project 80
Figure 3.42c Entity Relationship Diagram
Project 81
Field Description Data Type Size Null Key
Agency_Id Agency record identifier Int 4 NO PK
Address Company Address Varchar MAX NO
Postcode Company Postcode Int 4 NO
State Company State Varchar 50 NO
Country Company Country Varchar 50 NO
Telephone Company Telephone Varchar 50 NO
Contact_Name Contact name Varchar 50 NO
Fax Company Fax Number Varchar 50 NO
Email Company contact email address Varchar 50 NO
Remark Additional information regarding Varchar MAX YES
agency
Role_Id Access privilege record identifier Int 4 No PK
Department Access by which department varchar 50 No
Type Categories of service provide by varchar 50 No
web page. Eg. Maintenance
Page Web page access name varchar 50 NO
Type Name Categories name display in main varchar 50 NO
menu
Display Name Web page display name in sub varchar 50 NO
menu
ER_Id Employee access privilege record Int 4 NO PK
identifier
Emp_Id Associated employee id Int 4 NO FK,
FYP_EMPLOYE
1. FYP_ACCESS_PRIVILEGE E
Role_Id Associated access privilege id Int 4 NO FK,
FYP_ACCESS_
PRIVILEGE
3.8 Data Dictionary
2. FYP_AGENCY
Project 82
MB_Id Material batch record identifier Int 4 NO PK
Batch_Date Date of material batch receive Datetime 8 NO
from supplier
Manufacture_D Material batch’s manufacture Datetime 8 YES
3. FYP_EMP_AP
ate date
Expire_Date Material batch’s expire date Datetime 8 NO
Total_Quantity Material batch receive quantity Int 4 NO
Current_Quanti Material batch current quantity Int 4 No
ty
Supplier_Batch Supplier’s material batch id Varchar 50 NO
_Id
Material_Id Material batch associated FK,
material id FYP_MATERIA
L
Emp_Id Employee access privilege record Int 4 NO PK
identifier
Firstname Employee’s first name Varchar 50 NO
Lastname Employee’s last name Varchar 50 NO
Address Employee’s home address Varchar 50 NO
Postcode Employee’s home postcode Varchar 50 NO
State Employee’s home state Varchar 50 NO
Country Employee’s home country Varchar 50 NO
Telephone Employee’s contact number Varchar 50 NO
4. FYP_EMPLOYEE
Email Employee’s email address Varchar 50 NO
Remark Employee’s additional 50 NO YES
information
Material_Id Material record identifier Int 4 NO PK
Name Material’s Name Varchar 50 NO
Description Material’s description Varchar MAX NO
Unit_of_Measu Material’s basic measurement Varchar 10 NO
rement unit
Composition Material’s compound listing Varchar MAX YES
Supplier_Id Material supplier id Int 4 NO FK,
FYP_SUPPLIER
5. FYP_MATERIAL
Project 83
MT_Id Material transaction record Int 4 NO PK
6. FYP_MATERIAL_BATCH
identifier
MT_Date Material transaction date Datetime 8 NO
Type Material transfer to which table Varchar 50 NO
Reference_Id Transaction reference table id Bigint 8 NO FK,
FYP_PRODUCT
ION
MB_Id Association material batch Int 4 NO FK,
FYP_MATERIA
L_BATCH
Amount Material batch amount transfer Int 4 NO
OPM_Id On production machinery record Int 4 NO PK
identifier
Mac_Id Associated machinery record Int 4 NO FK,
identifier FYP_MACHINE
RY
Production_Id Associated production record Int 4 NO FK,
identifier FYP_PRODUCT
ION
OPS_Id On production staff record Int 4 NO PK
identifier
Production _Id Associated production identifier Int 4 NO FK,
7. FYP_MATERIAL_TRANSACTION FYP_PRODUCT
ION
PStaff_Id Associated production staff Int 4 No FK,
FYP_PRODUCT
ION_STAFF
POM_Id Purchase order’s material record Int 4 NO PK
identifier
PO_Id Associated purchase order id Bigint 8 NO FK,
FYP_PURCHAS
E_ORDER
Material_Id Associated material id Int 4 NO FK,
FYP_MATERIA
8. FYP_ON_PRODUCTION_MACHINERY
Project
9. FYP_ON_PRODUCTION_STAFF 84
Product_Id Product record identifier Int 4 NO PK
Name Product’s name Varchar 50 NO
Desciption Product’s description Varchar MAX NO
Unit_of_Measu Product’s basic measurement Varchar 10 NO
rement unit
Bar_Code Product’s barcode Varchar 20 NO
Min_Order_Qu Minimum unit of order Int 4 NO
antity
Price_per_Unit Product unit price Money 8 NO
10. FYP_PO_MATERIAL
Expire_Duratio Product expired duration from Int 4 NO
n date of production
Weight Product weight measure in Decimal(18,4 5 No
Kilogram/KG )
PB_Id Product batch record identifier Int 4 NO PK
PB_Date Date of product batch transfer Datetime 8 NO
from production to product
batch
Expire_Date Product expire date. Datetime 8 NO
Expire date = production date +
product expire duration
Total_Amount Product batch total unit Int 4 NO
Production_Id Product batch associated Int 4 NO FK,
production batch FYP_PRODUCT
ION
Product_Id Product batch associated product Int 4 NO FK,
id FYP_PRODUCT
L
Amount Material order amount Int 4 NO
Receive_Amoun Material receive amount Int 4 NO
t
Price Material purchase price Money 8 NO
Status Purchase order’s material status. Varchar 10 NO
Eg, Pending, Received
11. FYP_PRODUCT
12. FYP_PRODUCT_BATCH
Project 85
Production_Id Production record identifier Int 4 NO PK
Status Production status. Eg. Varchar 50 NO
OnProgress, Complete, Transfer
Production_Dat Production start date Datetime 8 NO
e
Current_Progre Production progress in percent Decimal(18,2 5 NO
ss )
Workorder_Id Associated workorder identifier Int 4 NO FK,
FYP_WORKOR
DER
Finished_Unit Current produce unit Int 4 NO
Total_Unit Total production unit issued by Int 4 NO
workorder
UOM Product UOM Varchar 4 NO
Last_Update Last update date of production Dateitme 8 NO
progress
PT_Id Product transaction record Int 4 NO PK
identifier
PT_Date Product transaction record date Datetime 8 NO
Type Varchar 8 NO
Amount Product transaction amount Int 4 NO
Status Status of product transaction. Eg. Varchar 50 NO
Pending, Receive
Remark Additional information regarding Varchar MAX YES
product transaction
PB_Id Product transaction associated Int 4 NO FK,
product batch id FYP_PRODUCT
_BATCH
Reference_Id Product transaction credit to Int 4 NO FK,
which table FYP_SALES_O
RDER
Mac_Id Machinery record identifier Int 4 NO PK
Name Machinery name Varchar MAX NO
Watt Electricity used measure in watt Decimal(18,2 5 NO
)
14. FYP_PRODUCTION
13. FYP_PRODUCT_TRANSACTION
Project 86
PStaff_Id Production record identifier Int 4 NO PK
Name Name of production staff Varchar MAX NO
Title Tile of production staff Varchar 5 NO
Type Type of production staff. Eg, F = Char 1 NO
Full time, T = Temporary staff
Salary Salary for production staff Decimal(18,2 5 NO
)
15. FYP_PRODUCTION_MACHINERY
Recipe_Id Product recipe record identifier Int 4 NO PK
Product_Id Associated product record Int 4 NO FK,
identifier FYP_PRODUCT
Material_Id Associated material Id Int 4 NO FK,
FYP_Material
Proportion Weight of material used respect Decimal(18,4 5 NO
to material unit of measurement )
PO_Id Purchase order record identifier Int 4 NO PK
PO_Date Purchase order record date Datetime 8 NO
Status Purchase order status. Eg, Varchar 5 NO
Pending, Complete
Total Purchase order total amount of Decimal(18,2 5 NO
money due )
Productivity Machinery productivity measure Decimal(18,2 5 NO
in minute )
Product_Id Associated product product by Int 4 NO FK,
this machine
16. FYP_PRODUCTION_STAFF FYP_PRODUCT
Max_Staff_Allo Number of staff require for this Int 4 NO
catable machinery to operate
SO_Id Sales order record identifier Int 4 NO PK
Sales_Date Sales order record creation date Datetime 8 NO
Status Sales order status. Eg. Pending, Varchar 10 NO
Complete
17. FYP_PURCHASE_ORDER
18. FYP_RECIPE
Project 87
SOP_Id Sales order product record Int 4 NO PK
identifier
SO_Id Associated sales order identifier Bigint 8 NO FK,
FYP_SALES_O
RDER
Product_Id Associated product identifier Int 4 NO FK,
FYP_PRODUCT
Amount Product order amount Int 4 NO
19. FYP_SALES_ORDER
Total Sales order subtotal Decimal(18,2 5
)
Supplier_Id Supplier record identifier Int 4 NO PK
Name Supplier company name Varchar MAX NO
Address Suppler company address Varchar MAX NO
Country Supplier Company country Varchar 50 NO
Telephone Supplier contact number Varchar 50 NO
Contact_Name Supplier agent contact name Varchar 50 NO
Fax Supplier agent fax number Varchar 50 NO
Email Supplier email address Varchar 50 NO
Remark Supplier additional information Varchar MAX NO
Shipment_Id Shipment record identifier Int 4 NO PK
20. FYP_SHIPMENT
Address Address to ship to Varchar MAX NO
Status Status of shipment. Eg. Pending, Varchar 8 NO
Complete
SO_Id Associated sales order identifier Bigint 8 NO FK,
FYP_SALES_O
RDER
Contact_Name Shipment receiver name Varchar MAX NO
Contact_Num Sipment receiver contact number Varchar MAX NO
Agency_Id Associated agency id for this sales Int 4 NO FK,
order FYP_AGENCY
Total Sales order total amount due Decimal(18,2 5 NO
)
21. FYP_SO_PRODUCT
Project
22. FYP_SUPPLIER 88
Workorder_Id workorder record identifier Int 4 NO PK
Amount Amount of unit require to Int 4 NO
product
Due_Date Due date for the production to Datetime 8 NO
complete
Product_Id Associated product identifier Int 4 NO FK,
FYP_PRODUCT
Emp_Id Associated employee issee this Int 4 NO FK,
workorder FYP_EMPLOYE
E
Status Status or workorder. Eg. Pending, Varchar 20 NO
Admited, Completed
Start_Date Production start date Datetime 8 NO
OT_Amount OT amount require for each day Int 4 NO
through the duration of
production
Duration Duration of production from start Int 4 NO
date to completion date measure
23. FYP_WORKORDER in days
PStaff_OT_Rate Amount of permenant staff OT decimal(18, 5 NO
pay rate measure in hours 2)
TStaff_OT_Rate Amount of temporary staff OT decimal(18, 5 NO
pay rate measure in hours 2)
TStaff_Basic_Ra Amount of temporary basic pay decimal(18, 5 NO
te rate measure in hours 2)
Electricity_Rate Amount pay rate for a single of decimal(18, 5 NO
unit of electricity measure in watt 2)
Project 89
3.9 Package Diagram
Project 90
Figure 3.43 Package Diagram
Project 91
Project 92
3.10 Deployment Diagram
Figure 3.44 Deployment Diagram
Project 93
3.11 User Interface Design/Prototype
User interface for Zu Lian Inventory is intentionally to be simple and clear cut. Since
the system is design to be use by back end user to carry out business process which is more
residing on functionality over appearance attractiveness. As compare to an e-commence
application which the user interface is more priority over the functionality due to
attractiveness is the key of success to an e-commence.
1
Figure 3.45 System User Interface Prototype - Main Page
In section 1, it contains all categories main menu item which can be select. The side menu
(section 2) which will be change according to the categories selected in the main menu. All
menu items are pulled and inserted into the html table row from the database. Any changes in
database will be change the menu item accordingly. For instance, if a new functionality is to
be included to the system, it only need to be update the database to reflect the change to the
user interface without incur any changes to the user interface code. If a new category of
functionality is to be included to the system, similar step can be taken.
Project 94
Common user interface component that assist in user input such as drop down list, radio
button, check box, date picker and etc are used to reduce the chance of inputting error or
improper format data to the system.
Figure 3.46 System User Interface Feature - Date Picture
Figure 3.47 System User Interface - Drop Down List
Project 95
Advance user interface component such as grid view, detail view are also used to display a
record as well as a list of record retrieve from database.
Figure 3.48 System User Interface - Grid View
Popup pages are also used to display report and business document such as purchase order,
invoice, and etc.
Figure 3.49 System User Interface - Pop Up Page
Project 96
3.12 Report Design
1. Sales forecasting report
Display all the passed sales and provide a 3 time frame provision to the future
according to the user selection. For instance, monthly, quarterly and yearly.
Figure 3.50 Forecasting Report
Note: Yearly and quarterly forecasting report is included in appendix
Project 97
Production Report
Calculate the cost of production of a selected production including production detail
such as workmanship, material cost, electricity cost and etc.
Figure 3.51 Production Report
Project 98
Within the system design stage, varies diagram are require to be drawn to capture the
user requirement and system architecture. At the beginning of this stage, the actual
purpose of each diagram is not clear. To counter this problem, a thorough study of the
actual usage in the internet is require to enhance the understanding of the purpose of
each diagramming in capturing and retain the architecture information. This is
essential to allow the diagram drawn to be 100% clear without the present of any
ambiguity, this will allow developer in the future to maintain the system much more
easily.
Next, the requirement of the system may not be fully realize during this stage, some
of the process of diagramming such as class diagram and sequence diagram have to be
revise to incorporate newly realize functionality. This significantly increase the time
needed in completing this system design stage.
Last but not least, the user interface design and report design was unsatisfied by the

user. A series of redesigning was required to achieve user satisfaction. Problem rise
by the user included the ease of user to input data. The use of the drop down list was
requested by the user to allow them to select from the list instead of key in by
themselves. Beside, the use of date picker was also requested to allow them to select
the date without entering them manually and require remembering the format of the
date. User complain that the presentation of the report was not clear enough, user
suggest that the use of different color to allow the different part of the report to
improve the readability, particularly in the material drawn page.
Project 99
Zu Lian Inventory Management Programming
Chapter 4
Programming
Project 100
Programming
In this chapter, it will be discuss about the algorithm applied as well as the methodology used
in the project.
4.1 Introduction
The project is developed on the ASP.net framework 3.5 with C#. It combined with html to
deliver a powerful server side web application. As for the database, SQL Server 2005 was
selected due to it was bundle along with visual studio 2008. Other than ASP.net, Flash was
also used to develop animated line graph for the purpose of displaying forecasting report. Sub
topic covered include system feature, algorithm used, programming issue, and extra personal
reflection on the coding stage of the system.
4.2 Feature
1. Barcode
In order to provide a more efficient way of handling the purchase order and sales
order, barcode was implemented. Barcode EAN 13 standard was selected as the
format of the barcode implemented.
As for the generation of the barcode, open source external library was used.
ITextSharp was a library written in C# customise for .Net platform. To allow
reusability of the barcode generation code, it has being written as a HTTP request.
Below is the code for the HTTP request.
Figure 4.1 Barcode Http Request Code
Project 101
4.3 Algorithm Used
i. Forecasting Module
To provide a forecasting with decent accuracy, the selection of forecasting was a
crucial step. As for the data collected from the database are respected in time frame,
time series forecasting was selected as the forecasting methodology. There are several
common and heavily used method such as moving average, exponential smoothing,
linear smoothing and etc, exponential smoothing was selected as the forecasting
algorithm. Exponential smoothing weighted the pass data respected to their time
frame. A more recent observation will be given more weight compared to older
observation; it is based on the assumption that recent observation carried more
information regarding the future trend. Below are the pseudo codes of the algorithm
implemented.
Begin forecasting
Initialize result to new List<ForecastDataStruct>
Add data[1] to result list
Initialize length = data.Length - 1
Initialize count = 1
While count < length
Value = (data[count] - data[count-1]) * weight
+ data[count - 1]
Add value to result list
End While
Initialize forecastRange = data.Lenght +
forecastInterval -1
Initialize count2 = data.Lenght - 1
While count2 < forecastRange
Value = (result[count - 2] - result[count-1]) *
weight + result[count - 1]
Add value to result list
count = count + 1
End While
Return result list
End forecast
Project 102
ii. Verify Production
Advance user in production department such as production manager having to
authority to issue a production work order to start a new production line. Prior to the
initialization of the approval, production can run the verify production functionality to
verify the cost of production and estimate production revenue and profit. Below is the
algorithm used.
Begin VerifyProduction
Initialize verifyProductionResult = new instance
availableMachineList = retrieve idle machinery from
database
availableStaffList = retrieve idle staff from
database
initialize maxProductivity = 0
initialize maxStaffRequire = 0
foreach i in availableMachineList
maxProductivity = maxProductivity +
i.productivity
maxStaffRequire = maxStaffRequire +
i.staffCount
End foreach
Initialize days = endDuration - startDuration
Initialize maxProductionAmount = days * (normalHour
+ maxOTAmount * 60) * maxProductivity
If maxProductionAmount < workorder.amount
verifyProductionResult.isProductable = false
verifyProductionResult.productableAmount =
maxProductionAmount
return verifyProductionResult
Else If maxProductionAmount < workorder.amount
Initialize currentProductableAmount = 0
Initialize currentProductivity = 0
Initialize manPowerRequired = 0
Initialize macInvolve = new instance of list
Initialize count = 0
For count < availableMachineList.Length
If currentProductableAmount <
workorder.amount
Project 103
currentProductivity +=
availableMachineList[count].productiv
ity
manPowerRequired +=
availableMachineList[count].staffCoun
t
currentProductableAmount = days *
(normalHour + maxOTAmount * 60) *
currentProductivity
Add availableMachineList[count] to
verifyProductResult
else
end loop
End If
End For Loop
If manPowerRequired > availableStaffList.count
verifyProductionResult.isManPowerSufficien
t = false
verifyProductionResult.lackManPowerAmount
= manPowerRequired -
availableStaffList.count
End If
Else
verifyProductResult.macList = availableMacList
End IF Else
Initialize materiaList = get product material list
from database
Foreach i in materialList
If material i not enough
verifyProductionResult.isMaterialSufficient =
false
End If
End Foreach
End Verify Production
Project 104
4.4 Programming Issue
1) Flash External Interface on Internet Explorer and ASP.net Bug
In the forecasting report, I developed a line graph using Flash. It requires retrieve data
from server side for displaying out the information. Flash contain a communication
interface called external interface. It allow flash to be integrated with various platform
such as Java, web page through JavaScript and etc.
Problem :
Everything work fined in fire fox and Google chrome browser. When flash is
embedded in the asp.net form, internet explorer implementation will look for
“window.objName” rather than “document.form[x].objName”. This cause the java
script embedded in the web page by server side code failed to connect the actual flash
object.
Solution :
After some in-depth research over the internet, I try several way suggested and it does
not work out. At the end I found a neat solution for the problem. It is a form fix
written by SteveKamerman (SWFFormFix). It will auto correct the reference code of
the internet explorer to the correct implementation. Below is the usage of the form fix.
By attach the SWFFormFix to the web page, and some minor changes to the object
tag used to embed the page and it work on the internet explorer.
Project 105
Within this development stage, it took almost 40% or the overall system development
life cycle. Varies problem arise in the coding stage, due to the development team of
this project is solo based, every problem faced was require to solve by me
independently. There is no communication and exchange of idea can be took place, I
has to do the research on the net to find the answer. The most serious problem faced
was the internet explorer and flash external interface problem. I spend quite a lot of
time to finding the solution and at the end a form fix provided by the SteveKamerman
solve the problem. I only require to include the java script file in the page and do
some adjustment on the flash embed code and it work like a charm.
Beside, the request of the use to include the bar code to improve the office automation
require me to search for appropriate ASP.net external class to implement the bar code.
At the end the ITextSharp library was chosen due to it is a free open source library
and ease of using it. To allow the bar code implementation code to be used by all
document, the code was written in the form of http request. Any page require bar code
only require to do a http request, and a image of the bar code will be return.
With in the development of this project, there is a significant grow in my
programming skill. First of all I gain more understanding on the server side
application over the web platform. Unlike in studying in the Internet Programming
course, hands on a project give more practical experience rather than just learning it in
theory. Besides, I have gain more knowledge with C# language. In the pass I am more
preferring with java programming, but after stick with the C# in the final year project
I much more prefer to develop with C# right now. The features of the C# such as IN
and OUT keyword give more flexibility in returning multiple arguments with a single
method. Beside the DELEGATE feature in C# eliminate the need of written a
interface to do the standardization in communication. In any method, I can pass a
method as an argument which allows us to pass in a callback function. With this, the
coupling of methods can be done much more efficiently and increase maintainability
over the code.
Next, I gain more realization on programming. The need of designing and
implementing an algorithm efficiently is a crucial step in programming. To achieve
this, mathematic played vital role. A mathematics formula can substitute several lines
of code or perhaps hundreds of them.
Project 106
Zu Lian Inventory Management Software Testing
Chapter 5
Software Testing
Project 107
Software Testing
5.1 Introduction
In this chapter will cover the final system testing strategies which including unit
testing, integration testing, black box, and final system testing. The test plan is prepare in the
end of the chapter to show the expected output from the final system functionality in order to
validate it completeness, logic correctness as well as bug free.
5.2 Testing Strategies
In the development process of Zu Lian Inventory, various testing was carried out in order to
develop a product that suit the need of the user. Various testing strategies will be discuss in
detail separately below.
5.2.1 Unit Testing
Unit testing is the most fundamental testing method in the initial stage of the system
development. Its responsibility is to validate behaviour correctness of each sub module. Unit
testing is carried out on every sub module to ensure that the portion develop was confront to
the business logic and free from bugs.
5.2.2 Integration Testing
Integration Testing was carried out to ensure each module developed can be work together as
a whole to support the business operation. It main responsibility is to validate any process
perform in the system affect other module correctly and the database integration is ensure.
When all of the system modules are developed, all of the modules need to be check for its
integrity in working as a whole. Bug fix has taken place to fix the communication problem as
well as database integrity.
5.2.3 System Testing
After the integration testing is passed, System testing will take place. System testing is the
final testing of the entire system. Its responsible is to ensure that every expect of the system is
tailor to the user specification. In the final testing, each module, sub module and validation
checking of the system s tested thoroughly.
Project 108
Function Test Data Expected Result Actual Result Remark
Randomly A message “Incorrect
insert user id A message “Incorrect user Pass
user id or password”
and user id or password” appear
appear
password
Enter Sales
Manager User Redirect user to Sales Redirect user to Sales Pass
Id and Manager Page Manager Page
Password
Enter
Purchasing Redirect user to Redirect user to Purchasing
Login Page Manager User Purchasing Manager Pass
Manager Page
Id and Page
Password
Enter
Production Redirect user to Redirect user to Production
Manager User Production Manager Pass
Manager Page
Id and Page
Password
Enter any Redirect user to related Redirect user to related
Function : Login clerk user id Pass
department Page department Page
and password
List of user in the
Select an User
department manage by List of Department user
User List List in the Pass
this user will be listed in listed in table format
submenu
the table format
Insert New All input component get
All input component get
User detail empty and a message
Create User empty and a message “Add Pass
into proper “Add User successful”
User successful” appear
column appear
Update any
A Message “Update A Message “Update User
Update User field of user Pass
User Successful appear” Successful appear”
detail
Select a user
A Message “Delete User A Message “Delete User
Delete User id and click Pass
Successful appear” Successful appear”
delete
Function : User Maintenance Software Testing
5.3 Test Plan
5.3.1 Security Module
Project 109
User Detail was display User Detail was display in
Select a user in table format and table format and related
Display User
Id from related user access user access privilege is Pass
Detail
dropdown list privilege is display in display in checkbox list
checkbox list
A Message “Update
A Message “Update User
Check access User Access Privilege
Function : Access Privilege Access Privilege Successful”
privilege that Successful” was display
was display and login into
does not and login into user Pass
user account selected
belong to account selected
privilege display in sub
selected user privilege display in sub
Update User menu
menu
Access
A Message “Update
Privilege A Message “Update User
Uncheck User Access Privilege
Access Privilege Successful”
access Successful” was display
was display and login into
privilege that and login into user Pass
user account uncheck
belong to account uncheck
privilege disappear in sub
selected user privilege disappear in
menu
sub menu
Project 110
Select A Sales Sales Order with
List Sales Sales Order with selected
Order ID from selected ID appear in Pass
Order ID appear in table format
dropdown list table format
Select A
Product Detail with Product Detail with
Product ID
List Product selected ID appear in selected ID appear in table Pass
from
5.3.2 Sales Maintenance table format format
dropdown list
Insert new
A Message “New Sales A Message “New Sales
New Sales sales order
Order Update Order Update Successful” Pass
Order and press
Successful” was display was display
Done
Enter Sales Sales order detail and Sales order detail and sales
order ID and sales order item appear order item appear in table Pass
press OK in table format format
Sales Select a sales Selected Sales Item
Selected Sales Item
Receiving order item disappear from the list
disappear from the list and
and enter and a message Pass
a message “Receiving
item receiving “Receiving Successful”
Successful” was appear
detail was appear
Enter the
product id, All input field is clear All input field is clear and a
New Work
amount and and a message “New message “New Order Pass
order
due date and Order Created” appear Created” appear
press Done
Select work List of current pending List of current pending
Work Order
order status in work order appear in work order appear in table Pass
Status
sub menu table format format
Project 111
Select A
Purchase Order with Purchase Order with
List Purchase Purchase
selected ID appear in selected ID appear in table Pass
Order Order ID from
table format format
dropdown list
Insert new
A Message “New A Message “New Purchase
New Purchase Purchase
Purchase Order Update Order Update Successful” Pass
Order order and
press Done
Insert new
A Message “New A Message “New Material
Material detail
New Material Material detail Update detail Update Successful” Pass
and press
Done
Insert new
A Message “New A Message “New Supplier
Supplier detail
New Supplier Supplier detail Update detail Update Successful” Pass
and press
Done
Enter Purchase order detail
Purchase order detail and
Purchase and Purchase order
Purchase order item Pass
order ID and item appear in table
appear in table format
press OK format
Select a
Receiving Selected Purchase Item
Purchase Selected Purchase Item
disappear from the list
order item disappear from the list and
and a message Pass
and enter a message “Receiving
“Receiving Successful”
item receiving Successful” was appear
was appear
detail
Enter Purchase order detail
Purchase order detail and
Purchase and Purchase order
Purchase order item Pass
order ID and item appear in table
appear in table format
press OK format
Select a
Selected Purchase Item
Purchase Selected Purchase Item
disappear from the list
order item disappear from the list and
and a message Pass
and enter a message “Receiving
“Receiving Successful”
item receiving Successful” was appear
was appear
detail
Project 112
5.3.3 Purchasing Maintenance
Select All Current in progress
All Current in progress and
List Production list and completed
completed production Pass
Production from the sub production show in 2
show in 2 separate table
menu separate table
Insert A Popup of production
A Popup of production
New production report regarding the
report regarding the Pass
Production Detail and production cost is
production cost is display
press verify display
A popup of infeasible
Insert product A popup of infeasible
production is display
amount over production is display with
with related scarce Pass
the material related scarce material
material information
resource information display
Verify display
Production A popup of infeasible
Select a due A popup of infeasible
production is display
date which is production is display with
with man power Pass
man power man power insufficient
insufficient information
infeasible information display
display
Select work All current pending All current pending work
List Work
order from work order is show in order is show in table Pass
order
the sub menu table format format
Select
monthly A popup page displaying A popup page displaying
Monthly
forecasting the monthly report with the monthly report with Pass
Forecasting
and select selected duration show selected duration show
duration
Select
A popup page displaying
quarterly A popup page displaying
Quarterly the quarterly report
forecasting the quarterly report with Pass
forecasting with selected duration
and select selected duration show
show
duration
Select yearly
A popup page displaying A popup page displaying
Yearly forecasting
the yearly report with the yearly report with Pass
Forecasting and select
selected duration show selected duration show
duration
Project 113
5.3.4 Stock Maintenance
Within the system testing stage, varies testing was took place such as unit testing,
integration testing and final system testing.
First of all, within the unit testing, varies bug encounter which require a decent
amount of time to solve them which is essential to allow the integration of different
module to be more smoother. Most of the problem faces was logic bug during the
coding stage which require some adjustment to counter it.
Next, the integration testing, majorly problem face was the data type and format
passing between module which thrown an exception. Some of the data type are
required to change do cater this problem. For instance, the use of DateTime class was
require the date time pattern to be exact in order to parse them into DateTime object.
If the date was presented in different format, a InvalidFormatException will be
thrown by the application engine. Extra validation code was require to prevent the
invalid code from casting.
Lastly, in the final system testing, the system testing took place without any bug
shown which could consider a major success. The flow of the system was presented
5.3.5 Sales Forecasting
with a series of question and answering. No significant problem arise in the final
system testing.
Project 114
Zu Lian Inventory Management Conclusion
Chapter 6
Conclusion
Project 115
Conclusion
6.1 Link to Seminar
Within my seminar study, it is related to the forecasting method current used in the
mathematic field. It includes 2 main types of forecasting technique which is time
series forecasting method and causal / econometric forecasting method. The method
applied in my final year project is exponential smoothing in time series forecasting.
Each of the method was discussed in detail. In the time series forecasting contain 3
main forecasting techniques which is moving average, exponential and linear
forecasting.
Exponential smoothing is selected because it is implementation feasible and with
decent accuracy in showing the trend line. Beside, as compared to moving average
and linear technique, it clearly showed a better accuracy.
It has being elegantly implemented in my sales forecasting module. It was used to
provide 3 forecasting duration up ahead. There 3 type of forecasting included in my
project which is monthly, quarterly and yearly forecasting. User can select one of the
types of forecasting suit to their need and select the duration of the data require use in
the forecasting. A sales forecasting report will be generated and display.
6.2 Justification of choice of tools, technique and
methodology
Methodology
Within this final year project, the programming style use was Object-Oriented (OO)
approach. 3 tiers implementation consist of user interface (UI), controller and data
access was implemented. UI consist of web form and it’s behind code. Controller
consists of business logic which responsible in handling the input receiving from the
UI and update the database confront to the business logic. Data access tier provide the
interface to the controller tier to manipulate the database. Within my project, there are
5 controllers and 5 data access objects corresponding to my five modules which are
sales, purchasing, production, security and forecasting module. Each controller will
only interact with their corresponding data access tier.
Project 116
Tools
Several tools were used to assist me to complete this project. Most of it provide
functionality and feature that speed up the development of my final year project. Used
tools will be discussed in detail below
Visual Studio 2008
The leading integrated development editor (IDE) for Dot Net 3.5 platform
programming. The main editor I used throughout my project development. Beside
standard functionality such as coding keyword highlighting, code auto complete and
debug utility and etc, advance feature such as code script inserting, SQL server
database viewer was very helpful in the development processes.
SQL Server Management Studio Express
As compare to visual studio 2008 SQL server database viewer, this management
studio included better functionality such as database tuning, structure definition
language (SDL) generation and etc. It allow database maintenance to be much more
efficient and less time consuming.
Flash CS5
The latest IDE for flash development. It was used to develop the flash line graph
implemented in my sales forecasting report. As compare to Flash CS4, major
improvement can be clearly seemed. For instance, the auto complete by Adobe Flash
CS5 was much more accurate and precise.
Photoshop CS5
Latest picture utility by adobe. Added extra functionality on picture editing. It used on
editing and picture creation for the user interface design.
Rational Software Architecture
Majorly used in UML diagram creation in project system design. Sequence diagram,
use case and activity diagram was drawn by this tools. As compare to Microsoft Visio,
it was much easier to use. It’s connection point between each component relationship
can be easily connected without any distortion.
Project 117
6.3 Evaluation against the Project Objective
When completed of this Zu Lian inventory management system, it is
successfully accomplish the project objective stated in chapter 1: Project Aims and
Objective. Below are the evaluations against the project objective.
As compare to previous inventory management system used by the company,
it can be clearly seen that the efficiency of the working was improve significantly. For
instance, the use of barcode in handling the purchase order and sales order increase
the efficiency in handling the receiving process. Sales or Purchasing worker only
requires to scanned the bar code and the sales order and purchase order information
and detail will be show in the system. As compare to the manual entering, it will be
much more time efficient. Beside the automated process such as GRTV form
generation in purchasing department will reduce the user effort in handling the
receiving processes. User only require to do the receiving, once a purchase order was
mark as partially received, it will automatically save in the database and the GRTV
form will be printed upon user activation.
Compare to previous system, newly develop Zu Lian Inventory was
incorporated with forecasting ability. It can show the trend line of the sales which can
help the sales manager to predict the upcoming sales amount which in turn allow the
purchasing department and production department to produce sufficient amount of
product and purchase enough of material to handle the sales demand. As compare to
previous system, it relied on the sales manager instinct to do the forecasting which in
turn cause stacking product stock as well as the material stock.
Next, the enhanced of security module allow the managerial position staff to
manipulate the user access privilege according to their experiences to avoid any
serious mistake done by newly recruited staff. When a new user was created in the
system by the manager, the manager is require to grant the permission to the user
account to allow the user to access to the page granted otherwise they will not be able
to access to the system. This allow the managerial staff to limit the ability of new user
activity within the system. As the user gain more experience, managerial can grant
them more access privilege. This in return increase the maintainability of the system
security.
Project 118
6.4 Project Management Issue
As compare to the team development, working alone on the project contain its pros
and cons.
The benefit in working alone are it does not require to having regular meeting

between team member which require time scheduling on meeting to took place which
will increase the project development time. Besides misunderstanding between team
members in the process of development can be avoid which will allow system
development process to be smoother rather than stuck in redesign as well as repeat the
development of affected module. Next, the consistency of programming style can be
ensured, to allow the system maintain by next developers easier. Last but not least, the
process of module integration can be more quickly. This is cause by different develop
programming style as well as programming practice will be significant different.
Integration can be done rapidly in solo development because developers know each
module flow in detail.
The major disadvantage in solo development is the lack of idea exchanging. A

system develop by a programming might not be capable to cover every condition.
Within the development of the system, majorly idea was thought by myself and
research on my own in the internet, which might cause extra requirement to be
realized on the development phases which would increase development time in tuning
and refining the new requirement. Beside, in team development, the individual
motivation is clearly more important. A lack of self motivation in development phases
will cause the development to progress slowly than expected in schedule. Next, the
teamwork practicing in solo development is none. In any application development,
there will always be a team responsible for various component of the system. The
actual teamwork experience cannot be gain in solo development.
In a nut shell, I would more prefer in team development. It will be nice if any
major difficulty face by the system development can be bring out in progress meeting
between member. It can be bring out and discussed, problem faced can be solve with
a solution by a team rather than a single people.
Project 119
6.5 Evaluation of project
6.5.1 Strength of Project
The strength of this project is that it incorporated with forecasting ability and
automated business process compare to previous system. Beside, the enhance security
feature included in the system allow the managerial staff to having their control over
the accessing and manipulation in the system.
6.5.2 Weaknesses of Project
The major weakness of the system is that the actual lead time management between
the material purchasing and production schedule does not thorough. This would cause
the material management to be more difficult which it relies on the production and
purchasing manager experience.
6.6 Future Project Improvement
As state in section 6.5.2 weaknesses of project, the system should be enhancing in the
aspect of the lead time management between the purchasing of the material and the
production schedule. Beside, the user interface of the system still can be enhance to
allow it to be more attractive, although it is not necessary for a back end system to be
attractive but a more attractive appearance can increase the motivation of the worker
in working which in return increase the job efficiency.
Although it does not included in the project requirement, some office communication

tools such as email, broadcast board, notice and etc can be implemented in the system
to increase the functional commutation efficiency between departments.
Project 120
6.7 Personal Reflection
As an undergraduate student, I totally agree that it is a must for every student in
computer science to get involved in developing a system that confront to real working
world requirement. On the past, we only develop mini system which confront to the
need to particular course scope. For instance, in the course AACS4014 Data
Structures and Algorithms, the scope was to introduce to us the way of organising the
data in a proper format as well as sets of methods in manipulating the data structure.
The assignment was solely tested us on the usage of the data structure which is lack of
the actual practise of data structure application. Similarly, in the subject of
AACS4264 Object-Oriented Analysis and Design (OOAD), the scope of the subject is
to introduce to us the implementation using object base. It is actually refer to tier
implementation, but most of us do not really realize the truth of the actual intention at
that time.
But in the development of the final year project, those small pieces I learn from
various subject have be apply into it. It gave me a clearer picture of what I actually
gone through in the past 2 year of study in this degree. Data structure actual intention
was to allow a standard communication between each sub component in a big system.
Of course it also shown as that a good algorithm implemented can tremendously
increase the efficiency of the system compare to static logic which increase the
complexity of the system. Tier implementation learns form OOAD was actually
increased the maintainability of the system.
Through the system development life cycle (SDLC) I have being through. I gain more
understanding on the various stage of development compare to study it literally. I
have applied most of the knowledge I learn from the Computer science and Computer
mathematic course into this final year project. I realize that the scope of our course as
compared to other course are actually more side on programming side. The learning
of mathematic is to increase our programming efficiency and solving problem
creatively. Beside it increase the analytical skill of us in processing the problem we
faced.
Last but not least, the course structure of our course still has its room of improvement.
A properly constructed course structure can increase the learning curve of the student
and also the connectivity of the course as a whole package.
Project 121
Zu Lian Inventory Management References
References
1. Package diagram - Wikipedia, the free encyclopedia. [Online]
Available at : http://en.wikipedia.org/wiki/Package_diagram [Accessed On March 16,
2011]
2. UML Package Diagrams - Overview of Graphical Notation [Online]
Available at : http://www.uml-diagrams.org/package-diagrams.html [Accessed On
March 16, 2011]
3. Create a UML statechart diagram - Visio - Microsoft Office [Online]
Available at : http://office.microsoft.com/en-us/visio-help/create-a-uml-statechart-
diagram-HP001208872.aspx [Accessed On March 16, 2011]
4. Deployment Diagram - UML 2 Diagrams - UML Modeling Tool [Online]
Available at : http://www.visualparadigm.com/VPGallery/diagrams/Deployment.html
[Accessed On March 16, 2011]
5. Activity diagram - Wikipedia, the free encyclopedia [Online]
Available at : http://en.wikipedia.org/wiki/Activity_diagram [Accessed On March 16,
2011]
6. Prototype Modal - Blogspot
Available at : http://csebrules.blogspot.com/2011/01/assignment-2-task-2-
prototyping-model.html [Accessed On March 10, 2011]
7. A fix for Flash 8’s ExternalInterface - Steve Kamerman.com
Available at : http://www.stevekamerman.com/2006/12/a-fix-for-flash-8s-
externalinterface-in-a-form/ [Accessed On March 8, 2011]
Project 122
Zu Lian Inventory Management Appendices
Appendices
Document generated by the system will be attach as appendices list below
1. Good Return To Vendor From
2. Sales Forecast Report
3. Invoice
4. Puchase Order
Project 123
No:
Vendor Liew Trading
ZU LIAN INDUSTRIES SDN. BHD
GOOD RETURN TO VENDOR
1008
Date: 17/03/2011
Return Item KG 500 Reason And Action To Be

Compur UOM
Quantity Defect
Taken By
Stock Id Description Complaint Vendor
Milo Mix 24
ACAC 788
Material
Appendices 1 Good Return to Vendor Form
Project 124
Appendices 2 Sales Forecasting Report
Project 125
Purchase Order
Zu Lian Industrial SDN.BHD.
PO Number:
Plot 41, Bayan Lepas Industrial Estate, 1001
Phase IV, 11900 Penang, Malaysia.
PO Date: 23/2/2011
Vendor Id:
Purchase From Ship To:
Liew Trading Zu Lian Industrial SDN.BHD.
Plot 41, Bayan Lepas Industrial
10-11 jalan pahang, 11500, Penang,Malaysia
Estate,
Phase IV, 11900 Penang,
Malaysia.
Contact: Contact Name:
04-2323623 Yeoh Shang Fan
012-4565741
Require By Date:
Name UOM Amount Price(RM) SubTotal(RM)
KOPI 24 Campur KG 50000 5 250000

Milo Mix 24 Compur KG 50000 4.7 235000
Total(RM): 485000.00
Appendices 3 Purchase Order
Project 126
Zu Lian Industrial
SDN.BHD. Invoice
Best Service To Bravo Customer Date: 17/03/2011
Invoice Num:
1000000000034
Plot 41, Bayan Lepas Industrial Estate,
Phase IV, 11900 Penang, Malaysia.
Bill To: Lee Chong Han
Lee Health Care
A 18-18, Kampung Melayu
11500 , Pulau Pinang
04-8282822
Milk Shake
1002
Product Id Description Quantity Unit Price UOM SubTotal
1001 Coco Plus 2000 9.9 KG 19800

400 12.5 pack 5000
Powder Plus
Total 24800
Appendices 4 Invoice
Project 127
Zu Lian Inventory Management User Guide
User Guide
I. System Document
Set up a ASP.NET web site with IIS
1. Start the IIS Manager, it can be open by select Setting -> Control Panel ->
Administrative Tools Internet Services Manager from start menu.
2. Next, create a virtual directory for an existing physical directory. For this step
please expend the web sites item in the IIS tree, right click the Default WebSite
item and choose New -> virtual Directory from the menu (See Figure 1).
Figure 1. Createing a Virtual Directory
3. The first step in the wizard responsible with the virtual directory creation is to
choose an alias (Name of the application). The alias is the name which will be use
in the URL to access the files in this virtual directory. For our case, the alias will be
Zu Lian Inventory
Figure 2. Choosing an alias
4. Click Next
5. The next step in this wizard is to provide existing physical directory to which the
virtual directory will point to (see Figure 3). So, this physical directory will be
exposed as virtual directory through the alias.
Figure 3. Choosing a physical directory
Project 129
6. The final step is to choose your permission for the virtual directory(see figure
4). Usually, to host an ASP.NET application, read and execute permissions
will be sufficient.
Figure 4. Setting permissions
7. Click Next and then finish the creation of the virtual directory.
8. Copy the entire site (including all subdirectories) to the virtual directory
Testing the Web site
1. Since the application having the login as the default web page, we can testing
the deployment by open the browser and try to access the link :
http://localhost/ZuLianInventory/Login.aspx
2. If the Login.aspx was appears correctly that mean everything went OK.
3. If you receive the below result, which mean ASP.Net or Network Service
account does not have appropriate windows permission on the directory
Project 130
Figure 5. Server Application Unavailable
4. If you receive the result below, that mean that IUSR_MachineName account

or the windows account under which you authenticate yourself does not have
appropriate windows right on the virtual directory. This depends on the IIS
authentication mode you have chosen to use
Figure 6. Access denied by ACL
Project 131
II. Operation Document
Login
1. Enter your user Id - refer to your employee number (only number are allow)
2. Enter your password (If you are new user then please refer to your departmental
manager for the password set upon the creation of your account. Dedault if “1000”)
3. Press login after you had enter the user id and password.
a. If wrong password or user ID was enter, system will prompt notification upon
login failed, please re-verify your login detail
b. Once the system verify your identity as valid user, you will be redirect to your
main page
Sample of login fail is as below
Project 132
Add New User
1. Select Maintenance in the main menu (Section 1)
2. Select Create user in the sub menu(Section 2)
3. Fill in the Staff detail in section 3
4. Press done once all detail have being filled in.
a. If any information does not fill in or incorrect format, error message will be
shown in the right side of section 3 respect to field with problem
b. If all field was filled correctly a confirmation message “Staff Create
successful” will be show below section 3
Project 133
Update User
1
2
3
1. Select Maintenance from the main menu
2. Select Update User from the sub menu
3. Update user detail field in section 3 accordingly
4. Press done once all field require update is change
a. If any information does not fill in or incorrect format, error message will be
shown in the right side of section 3 respect to field with problem
b. If all field was filled correctly a confirmation message “Update staff
successful” will be show below section 3
Project 134
Delete User
1
3
2
2. Select Update User from the sub menu
3. Select User Id which to be delete
4. User Detail will be display on table form which the user id is selected
5. Press Delete to delete the user and a confirmation box will appear, press ok to
continue or press cancel to abort the deletion
6. If ok is press, a confirmation message “Delete Successful” will appear as below
Project 135
User Listing
2. Select User List from sub menu
3. List of user will appeal in table form
Access Privilege Control
2
3
2. Select Access Privilege control in the sub menu
3. Select an user Id from dropdown list
4. User detail of the selected ID will appear
5. Check the appropriate access privilege wanted to grant to the user
6. Press Update once the access privilege selection was done
a. A Confirmation message “Update successful” will appear
Project 136
New Sales Order
1. Select Sales tap in the main menu
2. Select the New sales in the sub menu
3. Enter the agency search detail in appropriate field (Note : multiple search condition
are allow) and press search, list of agency will appear in table format as below
4. Select the agency from the list but pressing the select button. The agency Id will
appear in the label
Project 137
5. Press add button to start adding sales order product
6. A product search will appear as shown below
7. Enter the product search detail in appropriate field (Note : multiple search condition
are allow) and press search, list of product will appear in table format as below
Project 138
8. Select a product by press the select button in the table and input the amount and press
insert. Result as shown in below
9. Press Done button once all product item have added.
a. A confirmation message “Sales added successful” will be shown as below
Project 139
Sales Receiving
1. Select the sales tab in the main menu
2. Select Receiving in the sub menu
3. Scan or input the sales order id in thd text field
4. Sales order detail will be show as above
5. Press receiving on the sales item table to do the sales receiving process
6. A receiving view will appear as below
7. Select no radio button indicate sales item received by customer without any defect. If
defect was present select the yes radio button and select the reason from the drop
down list and press done.
Project 140
8. A confirmation message will appear as shown in diagram above
New Work Order
1. Select Sales tab in the main menu
2. Select New work order from the sub menu
3. Select a product id from the drop down list
4. Fill in the amount and due date of the workorder
5. Press Done once fill in required information, a confirmation message will appear as
below.
Project 141
New Pending Work Order
1 3
1. Login into the production manager account
2. In the main page newly added pending work order by the sales manager will be listed
in the main page.
3. Select accept will bring up a view to fill in the reason or remark. (Optional to fill in)
4. Select reject will bring up a view to fill in the reason or remark. (Must be fill in)
Project 142
5. After insert the remark, press update to reject the sales order
a. A confirmation message will be display as below
6. Press verify will redirect the user to new production page as below
Project 143
New Production Work Order
3
4
1. Fill in the start date of the production
2. Fill in the overtime rate of the permanent staff
3. Fill in the basic for the temporary staff (RM per hour)
4. Fill in the overtime rate for the temporary staff (RM per hour)
5. Fill in the unit price of the electricity (RM per unit)
6. Press verify button to calculate the cost of the production
a. Production cost report will be show as a popup if the all criteria is sufficient
such as workmanship, material.
b. Production infeasible page will be shown if the criteria are not sufficient.
Project 144
7. Press Start Production button to start the production.
Project 145
View Production List
1
4 5 6
1. Select Production tab in the main menu
2. Select Production List in the sub menu
3. Production List will be show as above.
4. Press Detail to view the detail of the production as figure below
5. Press work order button to view the detail as figure below
Project 146
6. Press Schedule button to update the production progress and view the detail schedule
7. Insert the amount of completion each day into the text box and press ok. (Note: Each
day can only update once).
Project 147
New Purchase Order
1
1. Select Purchasing tab from the main menu
2. Select New PO from submenu
3. Fill in the criteria of the supplier and press search
4. Supplier detail match criteria given will be listed as figure below
5. Press Select button at the side to select the criteria
Project 148
7
6. After the supplier is selected, a list of material list will be shown as figure above.
7. Press select button to insert production item.
8. Key in the amount of the material and unit purchase price and press add
Project 149
9. After Adding all purchase order, press done to create the purchasing order.
10. A Confirmation message “Purchase order successful created” will be shown
Purchasing receiving
2
1
1. Select Receiving from the sub menu
2. Key in the purchase order id and press search.
3. Purchase order detail will be shown as figure below
Project 150
4. Press the receive button to switch to item receiving view
5. Key in the supplier batch id, manufactured date (Optional) and expire date.
6. If material received contain defect, check the partial radio button and key in the amount
receive, and remark and press done.
7. If material receive does not contain defect, check the Full radio button and press done.
8. A confirmation message “Item successful received” will shown.
New Material
1. Fill in the Supplier search criteria and press search
2. List of supplier match the search criteria will be shown as below
Project 151
3
3. Press Select to choose the supplier
4. Enter new material information as shown below
5. Press Ok Upon confirm material insertion
6. A successful message “Material Insertion Successful” will be shown
Project 152
New Supplier
1. Select Purchasing in the main menu
2. Select New Supplier in the sub menu
3. Insert all supplier detail
4. Press Add Upon confirmation supplier insertion
5. A successful confirmation message “Insertion Successful” will show.
Defect Receiving
3 5
1. Select Receiving Defect From the sub menu
2. Defect item receive in the material receiving will be shown here
3. Select receiving to do second receiving (Note: No partial receiving can be done)
Project 153
4. Insert material receiving information and press done
a. A confirmation message “Receiving Successful” will be show upon
succession
5. Select Credit upon receiving vendor credit note to update the defect material as
credited
6. Press GRTV button to generate the vendor corrective action form.
Project 154

ادارة المخازسن ويب

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ادارة المخازسن ويب

Uploaded by

Copyright:

Available Formats

ZU LIAN INVENTORY

Supervisor: Mr. Wong Yoke Seng

No. Sub Module Name Description

No. Sub Module Name Description

Initial Design Customer

Maintain Test Deployment

feature was essential to allow rapids system development which in return reduce the

receive will be key in to system with extra note attach to the delivery order receive.

Beside the main flow, the functional requirement and non functional requirement is

2. Relationship to other information system

8.Staff input the receiving information 9. System save to database and prompt

Last but not least, the user interface design and report design was unsatisfied by the

The benefit in working alone are it does not require to having regular meeting

The major disadvantage in solo development is the lack of idea exchanging. A

Although it does not included in the project requirement, some office communication

Return Item KG 500 Reason And Action To Be

KOPI 24 Campur KG 50000 5 250000

Product Id Description Quantity Unit Price UOM SubTotal

1001 Coco Plus 2000 9.9 KG 19800

4. If you receive the result below, that mean that IUSR_MachineName account

You might also like