A Business Proposal To Design A System For A Plywood Shop

Final Project Submission: System Proposal Document
A Business Proposal to design a System for a Plywood Shop
TABLE OF CONTENTS
Abstract............................................................................................................................................5
A Business Proposal to design a System for a Plywood Shop........................................................6
1. Background:.................................................................................................................................6
1.1. Problem:....................................................................................................................6
1.2. Project Audience:......................................................................................................6
1.3. Risks Involved:.........................................................................................................7
2. System Requirements..................................................................................................................7
2.1. Outputs:.....................................................................................................................7
2.2. Inputs:.......................................................................................................................7
Business Proposal to design a System for a Plywood Shop 2
2.3. Processes:..................................................................................................................8
2.4. Performance:.............................................................................................................8
2.5. Controls (i.e., security):............................................................................................8
3. Approach used.............................................................................................................................8
3.1. After Iterations:.........................................................................................................9
4. Project Plan:.................................................................................................................9
4.1. Control Plan:...........................................................................................................10
5. Work Breakdown Structure........................................................................................................11
5.1. Project Manager:.....................................................................................................12
5.2. System Analyst:......................................................................................................13
5.3. Developer:...............................................................................................................13
5.4. Tester:......................................................................................................................13
6. Gantt chart.................................................................................................................................14
6.1. Timeline:.................................................................................................................15
6.2. Resource Chart:......................................................................................................15
6.3. Cost Table:..............................................................................................................16
7. Data Process Modelling.............................................................................................................17
8. Data Flow Diagram....................................................................................................................19
9. Data Dictionary..........................................................................................................................20
10. Object Modelling.....................................................................................................................24

11. Use Case Diagram....................................................................................................................25
12. Physical Design.......................................................................................................................27
13. Data Design.............................................................................................................................29
13.1. Normal Formal Tables:.........................................................................................29
14. User Interface Design..............................................................................................................32
15. System Architecture.................................................................................................................34
15.1. ERP (Enterprise Resource Planning):...................................................................35
15.2. Total Cost of Ownership (TCO):..........................................................................35
16. Feasibility Analysis..................................................................................................................35
16.1. Operational Feasibility:........................................................................................36
16.2. Technical Feasibility:............................................................................................36
16.3. Economic Feasibility:...........................................................................................37
References......................................................................................................................................39
Abstract
The purpose of this project is to design a new application system for a plywood shop, in order to
maintain all the product information that are in the shop and in a warehouse so, that client can
manage his inventory without any hustles currently there is no software application existed in the
shop which is taking a lot of time to count the products individually to order the stock for
restocking the inventory and to deal with the customer enquiries about the product availability in
the shop by sitting in the same place instead of going and checking the inventory physically, the
proposed system can resolve these issues and can save time to run the business.
Keywords: Plywood shop, New system, Restocking, Customer enquiries, Product
availability, Resolving the issues.

A Business Proposal to design a System for a Plywood Shop
1. Background:
This paper proposes to design a new system for a plywood shop where the primary
products are plywood, glass, mirrors and few other furniture products. There is no existing
software to maintain the data of the products and this system makes the user/owner to manage
his inventory in the shop and in warehouse comfortably without going and checking them
manually.
1.1. Problem:
To maintain the whole database of the plywood sheets and other products inside the shop
and in a warehouse according to their aisle location.

It is very hard to count each and every single plywood plank and products.
During billing, the client wants to know how many plywood sheets got left in that
particular model so that they can fill the stock without running out of them.
A lot of paper work to maintain the inventory information.
To save the time in addressing the customers about the stock.
1.2. Project Audience:
For the very first time, the client/owner and employees of the shop need some training to
use the system.

Developers and hardware engineers to design and install the system.
Customers, who can get the information quickly without wasting the time.
1.3. Risks Involved:
Stock information needs to be handled carefully during the extension of a shop or while
the introduction of new products.

Client or employees must get hands-on experience on UI and options to use the system
quickly.
Extra hardware like sensors and scanners will be included to count the stock which may
increase the cost of the project.
2. System Requirements
The system requirements for the plywood system are of as follows:
2.1. Outputs:
The application should track the stock and sales from the billing counter and must
address the customer enquiries about the products.

The system must produce a weekly, monthly and yearly report on budget sales and
profits.
The system will push notifications about low stock products in the inventory.
The system will have its own barcode generator for the products to maintain its inventory.
2.2. Inputs:
Each product has its own barcode which will be scanned using a handheld device and get
registered in the product database automatically.

Products that do not have the barcode should be entered manually into the system.
Customers data and restocking information will be given to the system.
Two separate log-in screens for client/owner and employee.
2.3. Processes:
The application system will stores all the data related to products and updates newly
entered products.
The system will create a log file for every operation (updating the stock and purchases).
Generates automatic bills for the purchases to customers.
The system must calculate and count the availability of stock.
Able to display the availability of stock upon the customer requests.
2.4. Performance:
Data extraction and response time should be faster

Automatically takes back-up of the entire data in case of system crash.
Intimates the user two days in prior about the low stock products.
Able to generate the bill information while accepting the returns.
2.5. Controls (i.e., security):
Application privileges may vary from the employee to owner.

Employee will not get access to get profits and turnover of the shop.
Administrator authorization is required to enter the purchased products or update the
inventory.
3. Approach used
I used Iterative and Incremental model to complete this task because iterative model
initially uses a basic subset of requirements and iteratively upgrades to next versions by
satisfying all the requirements until the full system is implemented. Design adjustments,
enhancements and new functionalities can be added at each iteration, to use this model major
requirements must be defined in advance nevertheless, required modifications and enhancements
can be added later on. (SDLC Iterative Model (www.tutorialspoint.com))
To achieve the desired objective of a system, iterations can be useful a lot which
is a repetitive process until the final goal is achieved, this method is mainly used for the projects
which are not manageable using old-fashioned step-by-step model. (What is Project Iteration?)
3.1. After Iterations:
As per the discussion had with the client (my friend) the following changes are going to
be implemented for the system.
Sorting and searching of products.

Client needs low stock alert notifications on his desktop.
4. Project Plan:
The aim of this project is to design a new system for a plywood shop where the primary products
are plywood, glass, mirror and few other furniture products. There is no existing system to
maintain the data of the products and to address customer queries regarding the products, this
system makes the user to manage his inventory in the shop and warehouse comfortably.
The plan to design this system was started with requirement gathering by using various
approaches and after confirming the requirements from client, a technical approach has been
drawn to solve several problems like to maintain the whole database of products in the shop, in
the warehouse and to know about the low stock products and several other problems have been
addressed, the following figure 1 shows the context diagram of the plywood shop.
Figure 1: Context diagram of the plywood process system
4.1. Control Plan:
In order to execute the project without any hurdles project management unit helps to scrutinize
each and every section of the project to identify the problems some of the elements that enhance
the project are defined below.
Cost and Schedule management: This plan is used to complete the project within the
specified amount of time and in the specified budget.

Scope management: To achieve this goal we have to be careful while gathering the
requirements, if the requirements are satisfying the client we can complete the project by
keeping it on the track.

Task management: It is the process of managing a task through its life cycle, task
management can help in achieving goals of groups or individuals by collaborating and
sharing knowledge for the accomplishment of the goal.

Risk management: Risk management defines the assessment, identification and
prioritization of risks to maximize the realization of opportunities by coordinating with
application resources to control and to monitor the impact of unfortunate events. The
main objective of risk management is to promise the business goal is not deviating.
Quality management: Quality management has four main aspects quality control, quality
management, quality improvement and quality assurance for the project. To achieve more
consistent quality, quality management not only uses quality assurance but also control
processes, the main goal of quality management is to ensure the product, organization or
service is reliable. (Project Management Institute, 2004).
5. Work Breakdown Structure
Work has been distributed among various departments in order to complete the project in the
given timeline and budget as shown in the following figure 2, each and every one involved in the
has their own roles and responsibilities which are discussed below.
Figure 2: WBS of the proposed project
The following are the different people who are involved in this system development:
5.1. Project Manager:
Project manager is the person who has the responsibility for the successful completion of project,
the following are the duties of a project manager.
The main roles of a project manager are communicating and coordinating with clients,
arranging meetings, making schedules and prioritizing tasks.
If any potential issues arises in the middle of the project, project manager takes the
responsibility to find the solution.

5.2. System Analyst:
System analyst plays an important role in designing and analysing the system, some of his duties
are of as follows:
System analyst gather the requirements from clients by studying the current business
requirements.
He is solely responsible for whole system design and architecture and to make sure the
future changes will not affect the current system.
5.3. Developer:
Developer is responsible to develop the code by studying the functional requirements of the
project.
Developer is the responsible person for developing the code and sometime he needs to
perform the unit testing without any bugs.
He involves in installing the system along with the project manager to ensure that the
system got deployed and working fine without any issues.
5.4. Tester:
In order to test the developed application tester plays an important role to check that the
application is working fine and satisfying the client.
Mainly testers will design the test cases and as per the test cases they will test the
application and if they find and bugs they will inform to the developer.
Testing will be done based up on different aspects and different techniques will be used in
testing to carry out the application test until it satisfies the client. (Singh, I. 2010)
6. Gantt chart
The following figure 3 gives the detailed information of the project which requires 91 days
starting date is 27-SEP-2015 and finish date is 1-MAR-2016 involving numerous stages like
project planning, requirement gathering, designing, developing, testing and installing the system
which is a step-by-step procedure.
In this project requirement gathering, developing and testing stages takes a long time compared
to other stages.
Figure 3: Gantt chart for the proposed project

6.1. Timeline:
The following figure 4 shows the timeline of the project from starting date to end date which is
comprised with different stages specifying time for each stage.
Figure 4: Timeline of the proposed project
6.2. Resource Chart:
The resource sheet gives us the information about the resources which are working for the
project with their standard rate per hour. For developer and tester the hourly rate is $35.00 and
for project manager and system analyst it is $50.00. The following figure 4 represents the
resource sheet for the proposed project.

Figure 5: Resource Sheet for the proposed project
6.3. Cost Table:
The cost table of the project shows in the table 1, the total budget and duration of the project is
depending up on the resources assigned to the project which is $33,120 for 91 days and
744hours, the detailed cost for the project is been categorized for individual section shown in the
table 2, the highest cost is allocated for requirement gathering $14,000 which is an important
stage of the project in order to satisfy the client requirements.
Table 1: Cost table of the project

Fixed Cost
Task Name Fixed Cost Total Cost Baseline Variance Actual Remaining
Accrual
System for Plywood Shop $0.00 Prorated $33,120.00 $0.00 $33,120.00 $0.00 $33,120.00
Project Plan $0.00 Prorated $3,200.00 $0.00 $3,200.00 $0.00 $3,200.00
Requirements $0.00 Prorated $14,000.00 $0.00 $14,000.00 $0.00 $14,000.00
Design $0.00 Prorated $5,200.00 $0.00 $5,200.00 $0.00 $5,200.00
Development $0.00 Prorated $4,060.00 $0.00 $4,060.00 $0.00 $4,060.00
Testing $0.00 Prorated $4,620.00 $0.00 $4,620.00 $0.00 $4,620.00
Installation $0.00 Prorated $2,040.00 $0.00 $2,040.00 $0.00 $2,040.00
Table 2: Detailed layout of the project cost
7. Data Process Modelling
Data process modelling is a set of analysis and design technique used to understand the
business data environment to logical data models and to physical data and physical structure, for
planning and designing of the system in an effective way data process modelling procedures
catch and make transformation of complex system requirements into actual representation of the
system. The following figure 6 shows the data process model of a plywood shop which gives a
brief idea about the business operation where the input of the system are customer related data
i.e., enquiries about product, billing information and product information such as design,
patterns, availability, size and many more. (Data Modelling and Process Modelling, n.d.)
Figure 6: Data Process Modelling
The following figure 7 depicts the detailed process of the current system in detail and
their relationship between each entity, here the primary keys are customer-ID, product-ID,
administrator-ID, employee-ID, picking-ID and the foreign keys are customer-ID, and product
description which are in the billing entity.

Figure 7: Logical Data Process Modelling
8. Data Flow Diagram
Data flow diagrams describes the process flow from one system to another along with its
local storage, the plan to design this system was started with requirement gathering by using
various approaches and after confirming the requirements from client, a technical approach has
been drawn to solve several problems like to maintain the whole database of products in the
shop, in the warehouse and to know about the low stock products and several other problems
have been addressed, the following figure 8 shows the context diagram of the plywood shop.
Figure 8: Data Flow Diagram of Plywood shop
9. Data Dictionary
A logical model of the system is produced by set of DFDs on the other hand the details in
the DFDs are acknowledged separately by the data dictionary. A data dictionary also known as
data repository which is the second component of structured analysis, the data dictionary also
defines and describes all data elements and meaningful combinations of data elements.
In this particular project there are various data elements such as customer, billing, product
inventory, management/administrator, employee and warehouse, the following tables shows the
data which that is associated with the various elements.

Table 3: Customer Table
Field Name Character Length Data Type
Customer ID 5 to 10 Characters Alpha-Numeric
Customer Name 25 Characters Only Alphabets
Customer Contact 10 Characters Only Numeric
Customer Address 100 Characters Alpha-Numeric
Customer table contains the information about the customer name, contact, address and a
unique ID which will be generated by the system during billing all other details should be
entered manually by the user.
Table 4: Management/Administrator Table
Administrator ID 5 to 10 Characters Alpha-Numeric
Administrator Username 25 Characters Alphabetic
Administrator Password 25 Characters Alpha-Numeric
The administrator/management table gives the information about the type of user who
logged into the application with full privileges.

Table 5: Employee Table

Alpha-
Employee ID 5 to 10 Characters Numeric
Employee
Username 25 Characters Alphabetic
Alpha-
Employee Password 25 Characters Numeric
The employee table gives the information about the type of user logged into the
application with employee ID and username having minimum privileges.
Table 6: Billing Table
Billing ID 5 to 10 Characters Alpha-Numeric
Product Name 25 Characters Alphabetic
Customer ID 5 to 10 Characters Alpha-Numeric
Product Description 25 Characters Alphabetic
The billing table contains information about the billing ID which is a unique ID generated
by the system and consists of product name, customer ID and product description.
Table 7: Product Inventory Table

Alpha-
Product ID 5 to 10 Characters Numeric
Product Count 3 to 5 Characters Numeric
The product inventory table consists of all the information about the products in the shop
with unique product IDs for every single product.
Table 8: Warehouse Table
Picking ID 5 to 10 Characters Numeric
Product Count 3 to 5 Characters Numeric
The warehouse table consists of unique picking ID generated by the system when the
orders are placed by the customers and based on the orders the billing will be generated.
10. Object Modelling
The representation of information system with identification of things such as objects is
known as object modelling which can be used to view the system interaction with objects and
working of the system an object can be a person, user, transaction or an action, the below figure
9 shows the object modelling for a plywood with various objects such as customers, employees
and with different transactions like placing and order, enquiring about products.
Figure 9: Object modelling diagram for a plywood shop

11. Use Case Diagram
The use case diagram comprises of actors and use cases of this project the below figure
10 shows the use case diagram of the plywood processing system, the actors involved in this
project are of as follows:
Administrator
Employee
Customer
The use cases of this project are of as follows:
Queries about the product
Order processing system
Product inventory
Picking process
Prepare invoice
Figure 10: Use case diagram of plywood processing system

12. Physical Design
The physical design of a system represents the logical data of the project which is
collected during the requirement gathering phase in order to build a system. The physical design
is used to review the external and internal entities of a system and to know how the data is flows
into and out of the entities. In other terms, how data is given as input, how it is authenticated and
how it is processed and how it is displayed as output can be studied using physical design
diagrams.
The requirements are gathered to design a new system for a plywood shop where the
primary products are plywood, glass, mirrors and few other furniture products. There is no
existing software to maintain the data of the products and this system makes the user/owner to
manage his inventory in the shop and in a warehouse comfortably without going and checking
them manually and to maintain the whole database of the plywood sheets and other products
inside the shop and in a warehouse according to their location.
Once the products are ordered and during the billing the client wants to know the count of
the plywood so that they can restock the items in the inventory. The following figure 11 shows
the physical diagram for the specified requirements where there are several entities like
customer, owner, employee, products, product inventory, billing and reports generate.
igure 11: Physical design of the requirements

13. Data Design
The data design of the plywood system is showed in the below figure 12 and the entities
used in the system are customer, administrator, employee, products which are represented by
rectangle shapes and the relationship between the entities are placing order, verifying order,
checking for stock which are represented by diamond shape.
Figure 12: Entity Relationship Diagram for a plywood shop
13.1. Normal Formal Tables:
The first normal form (1NF) for plywood system with sample data is shown in the below
table 9 where there are no repeating groups

Table 9: 1NF of Plywood System with Sample Data
1 NORMAL FORM
Order
Customer Numbe Product Descriptio Quantit Shippin Payment
Date Name r Number n y g Method
11/18/1 James Red Home
5 Thorley 9784 7654 plywood 10 Delivery Cash
11/19/1 Justine Film faced Credit
5 Wright 9785 8954 plywood 6 Pickup Card
11/20/1 Ginny Dining Home Credit
5 Hughes 9786 5695 chairs 4 Delivery Card
11/21/1 Charmaine Debit
5 Cox 9787 5454 Mirror 1 In Store Card
11/22/1 Adam Meranti Home
5 Lewis 9788 6885 Plywood 7 Delivery Cash
11/23/1 Block
5 Paul Usher 9789 6884 Board 2 Pickup Cash
The 2NF is shown in the below table 10 where the primary key is order line which is a
combination of two primary keys product number and order number as shown in the table 11.
Table 10: 2NF of a plywood system
2 NORMAL FORM
Order Product Descriptio Customer Payment
Date Number Number n Name Shipping Method
Charmaine
11/18/15 9784 5454 Mirror Cox In Store Debit Card
Meranti Adam Home
11/19/15 9785 6885 Plywood Lewis Delivery Cash
Block
11/20/15 9786 6884 Board Paul Usher Pickup Cash
Table 11: 2NF of a plywood system with primary order number
Product
Order Number Number Quantity
9784 7654 10
9785 8954 6
9786 5695 4
9787 5454 1
9788 6885 7
9789 6884 2
The 3NF of a plywood is shown in the following table 12 where the second normal form
table is transformed in which the primary key is order number the 3NF will consists of product
and customer including the customer name.
Table 12: 3NF of a plywood system
3 NORMAL FORM
Product Customer Payment
Number Description Name Shipping Method
5454 Mirror Charmaine Cox In Store Debit Card

Meranti Home
6885 Plywood Adam Lewis Delivery Cash
6884 Block Board Paul Usher Pickup Cash

Product in 3NF
Product Number Description Customer Name
5454 Mirror Charmaine Cox
6885 Meranti Plywood Adam Lewis
6884 Block Board Paul Usher
Customer in 3 NORMAL FORM
Customer Name Shipping Payment Method
Charmaine Cox In Store Debit Card
Adam Lewis Home Delivery Cash
Paul Usher Pickup Cash
14. User Interface Design
In this particular system there are two separate logins for administrator/management and
for employee having restrictions to certain functions, the following figure 13 shows the user
interface for the employee and the following figure 14 shows the user interface for
administrator/owner of the shop.

Figure 13: User Interface for Employee
Figure 14: User Interface for Administrator/Owner

15. System Architecture
The system architecture for plywood shop is shown in the following figure 15 which
gives a basic idea about the functionality of the system where the plywood planks or the new
products of the shop are get scanned by a handheld scanner which will be registered in the
central inventory database, whenever the customer places for the order users will fetch the data
from database and generate the bill payable by the customer.
Figure 15: System Architecture of a plywood shop

15.1. ERP (Enterprise Resource Planning):
ERP can be used to complete many business needs. An example within manufacturing
would be if a company manufactures chairs. The ERP would keep an eye on how many raw
products the company has in stock. If it notices that the stock of one particular item needed to
make a chair is running low, it will automatically re order that product. This helps the
manufacturing process to run smoothly.
15.2. Total Cost of Ownership (TCO):
Total cost of ownership can be defined based upon several cost factors like:
Development of the application

Hardware
Operating system
Training
Back-ups
Down time.
16. Feasibility Analysis
The clients plywood shop has more than 1000 varieties of plywood designs and some
other furniture products, there is no previously existed system to maintain all the products in a
centralized location and stock is checked manually and maintained in books. Every time it is
hard to refer the books to check the stock with the proposed project client can save a lot of time
in addressing the customers and to maintain the inventory without getting the products out of
stock so, the proposed system can bring a better change in the business.
16.1. Operational Feasibility:
Operational feasibility is mainly concerned with issues like whether the system will be
used if it is developed and implemented. Whether there will be resistance from users that will
affect the possible application benefits? The essential questions that help in the operational
feasibility of a system are following.
Does management support the project?

Are the users not happy with current business practices? Will it reduce the time
(operation) considerably? If yes, then they will welcome the change and the new system.
Have the users been involved in the planning and development of the project? Early
involvement reduces the probability of resistance towards the new system.

Will the proposed system really benefit the organization? Does the overall response
increase? Will accessibility of information be lost? Will the system affect the customers
in considerable way?
Proposed project is beneficial only if it can be turned into information systems that will
meet the organizations operating requirements. Simply stated, this test of feasibility asks if the
system will work when it is developed and installed. Are there major barriers to Implementation?
Here are questions that will help test the operational feasibility of a project:
Is there sufficient support for the project from management from users? If the current
system is well liked and used to the extent that persons will not be able to see reasons for change,
there may be resistance.
16.2. Technical Feasibility:
In technical feasibility the following issues are taken into consideration.
Whether the required technology is available or not

Whether the required resources are available
Once the technical feasibility is established, it is important to consider the monetary
factors also. Since it might happen that developing a particular system may be technically
possible but it may require huge investments and benefits may be less. For evaluating this,
economic feasibility of the proposed system is carried out.

Evaluating the technical feasibility is the trickiest part of a feasibility study. This is
because, at this point in time, not too many detailed design of the system, making it difficult to
access issues like performance, costs on (on account of the kind of technology to be deployed)
etc. A number of issues have to be considered while doing a technical analysis.
Understand the different technologies involved in the proposed system before
commencing the project we have to be very clear about what are the technologies that are to be
required for the development of the new system. Find out whether the organization currently
possesses the required technologies. Is the required technology available with the organization?
16.3. Economic Feasibility:
For any system if the expected benefits equal or exceed the expected costs, the system
can be judged to be economically feasible. In economic feasibility, cost benefit analysis is done
in which expected costs and benefits are evaluated. Economic analysis is used for evaluating the
effectiveness of the proposed system.
In economic feasibility, the most important is cost benefit analysis. As the name suggests,
it is an analysis of the costs to be incurred in the system and benefits derivable out of the system
A simple economic analysis which gives the actual comparison of costs and benefits are
much more meaningful in this case. In addition, this proves to be a useful point of reference to
compare actual costs as the project progresses. There could be various types of intangible
benefits on account of automation. These could include increased customer satisfaction,
improvement in product quality better decision making timeliness of information, expediting
activities, improved accuracy of operations, better documentation and record keeping, faster
retrieval of information, better employee morale.

References
What is Project Iteration? (What is Project Iteration)? Retrieved from
http://www.taskmanagementguide.com/glossary/what-is-project-iteration-.php
SDLC-Iterative Model (www.tutorialspoint.com) Retrieved from
http://www.tutorialspoint.com/sdlc/sdlc_iterative_model.htm
Project Management Institute. (2004). A guide to the project management body of knowledge
(PMBOK guide) (3rd ED.). Newton Square, PA: Author.
Singh, I. (2010, February 8). Responsibilities. Retrieved October 30, 2015, from
http://inderpsingh.blogspot.com/2010/02/what-are-responsibilities-of-software.html
Data modelling. (n.d.). Retrieved November 11, 2015, from
https://www.pesg.com/seminars /data_ modelling

A Business Proposal To Design A System For A Plywood Shop

Uploaded by

Copyright:

Available Formats

A Business Proposal To Design A System For A Plywood Shop

Uploaded by

Document Information

Original Description:

Original Title

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

A Business Proposal To Design A System For A Plywood Shop

Uploaded by

Copyright:

Available Formats

What are the main sections covered in the document?

What are the main sections covered in the document?

What are the main components of the system requirements section?

What are the main components of the system requirements section?

Final Project Submission: System Proposal Document

A Business Proposal to design a System for a Plywood Shop

A Business Proposal to design a System for a Plywood Shop........................................................6

1.2. Project Audience:......................................................................................................6

1.3. Risks Involved:.........................................................................................................7

2.5. Controls (i.e., security):............................................................................................8

3.1. After Iterations:.........................................................................................................9

4.1. Control Plan:...........................................................................................................10

5. Work Breakdown Structure........................................................................................................11

5.1. Project Manager:.....................................................................................................12

5.2. System Analyst:......................................................................................................13

6.2. Resource Chart:......................................................................................................15

6.3. Cost Table:..............................................................................................................16

7. Data Process Modelling.............................................................................................................17

8. Data Flow Diagram....................................................................................................................19

10. Object Modelling.....................................................................................................................24

11. Use Case Diagram....................................................................................................................25

12. Physical Design.......................................................................................................................27

13. Data Design.............................................................................................................................29

13.1. Normal Formal Tables:.........................................................................................29

14. User Interface Design..............................................................................................................32

15. System Architecture.................................................................................................................34

15.1. ERP (Enterprise Resource Planning):...................................................................35

15.2. Total Cost of Ownership (TCO):..........................................................................35

16. Feasibility Analysis..................................................................................................................35

16.1. Operational Feasibility:........................................................................................36

16.2. Technical Feasibility:............................................................................................36

16.3. Economic Feasibility:...........................................................................................37

Keywords: Plywood shop, New system, Restocking, Customer enquiries, Product

availability, Resolving the issues.

A Business Proposal to design a System for a Plywood Shop

and in a warehouse according to their aisle location.

1.2. Project Audience:

use the system.

1.3. Risks Involved:

the introduction of new products.

increase the cost of the project.

The system requirements for the plywood system are of as follows:

address the customer enquiries about the products.

registered in the product database automatically.

Data extraction and response time should be faster

2.5. Controls (i.e., security):

Application privileges may vary from the employee to owner.

requirements must be defined in advance nevertheless, required modifications and enhancements

can be added later on. (SDLC Iterative Model (www.tutorialspoint.com))

3.1. After Iterations:

be implemented for the system.

Sorting and searching of products.

Figure 1: Context diagram of the plywood process system

4.1. Control Plan:

the project are defined below.

specified amount of time and in the specified budget.

keeping it on the track.

management can help in achieving goals of groups or individuals by collaborating and