project proposal

21

Upload: gi-dy

Post on 22-Dec-2015

11 views

Category:

Documents


0 download

DESCRIPTION

Draft

TRANSCRIPT

Nitz Furniture Inventory System

Development Project Proposal

for

NITZ FURNITURE SHOP

Penafrancia Ave.

Naga City, Camarines Sur

Philippines

Submitted By:

DY, Gian Franco Briones

1

Contents

1 Project Summary 3

2 Proposed Project Name 3

3 Project Background 4

4 Problem De�nition 4

5 General Objective 5

6 Speci�c Objectives 5

7 Summary of Deliverables 6

8 Bene�ciaries 6

9 Proposed Solutions 7

9.1 Strengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

9.2 Weaknesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

9.3 Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

9.4 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

10 Proposed Scope and Parameters 9

11 Assessment of Existing System 10

12 Methodology 12

13 Project Plan 13

13.1 Project Kicko� . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2

13.2 Development Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

14 Appendix 14

14.1 Company Pro�le . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

14.2 Proposed Budget . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

14.3 Work Breakdown Structure . . . . . . . . . . . . . . . . . . . . . . 16

14.4 Gantt Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

14.5 Development Team Pro�le . . . . . . . . . . . . . . . . . . . . . . . 19

14.5.1 Project Manager . . . . . . . . . . . . . . . . . . . . . . . . 19

14.5.2 Programming Team . . . . . . . . . . . . . . . . . . . . . . . 19

14.6 Burn-down Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1 Project Summary

Hoping to accomplish a centralised structure of the inventory of Nitz Furniture,

we project handlers will be able to provide the �rm with the best service operation

with e�ciency and dexterity.

Amongst the projects bene�ts are the ease of use of the proposed system, the

easier facilitation, and conservation of work in terms of load out and time saving.

2 Proposed Project Name

Nitz Furniture Inventory System

3

3 Project Background

Furniture is the mass noun for the movable objects intended to support various

human activities such as seating (e.g., chairs, stools and sofas) and sleeping (e.g.,

beds). (Gray)

A single successive customer order includes processes which are:

1. Customer selects furniture or present designs to construct in sketch

2. Salesperson forwards sketches and orders to the inventory manager

3. Carpenter constructs furniture product

4. The inventory manager negotiates with the carpenter

5. The inventory manager bookkeeps all expenses of the product

6. Salesperson sets pricing and contact the customer for pickup. . .

To concur these physical independent processes in the proposed system is a good

solution. We need very responsible project holders and good �nancing to make

the project. We expect at the �nal days of the project making, the business �rm

has a centralised database repository, has software integration among business

processes, and business operation that is more agile than ever before. Producing

the amount of work for the project is a managing skill. Diagrams and charts will

help us cope with the project making with zero or less delay.

4 Problem De�nition

As the business grows and prospers in the coming �scal years, the use of these

formats shall be discontinued because these can bring information mismanage-

ment and con�dentiality risks to the business. Understanding the perturbation of

processing information in non-digitised format to its counterpart, we joined the

business to support its problem and continually question its inventory cluster to

4

make sure its needs be amenable in the proposed system software.

Integration of database systems on an aged business �rm with its neophyte users

or employees is the solution for alleviating the rigours of a �rm that has not yet

felt the new realm of the digital world.

The business �rm's primary entities are stock of wood, carpenters, �nished furni-

ture products, sales employees, inventory manager, and customers. The inventory

manager of Nitz furniture has been having inconveniences in recording inventory

transactions in non-digitized physical formats such as a 200-page record book, OR

slips, document processor written product tags, and etc.

5 General Objective

Providing up the business with a newly serviced system that makes information

processing easier is the aim of this project. Having a centralised and data reposi-

tories amongst departments of the �rm will integrate unity and interconnectivity.

The project should �uidly handle information of the business �rm with accuracy.

Reduction of paper works is part of the project's environment-friendly setup.

6 Speci�c Objectives

1. Ability to provide the �rm's inventory and sales department the best software

service they can obtain from the new system.

2. The presence of a centralised database repository, computer networks, and

inventory software is established.

3. A novice employee of Nitz furniture should be able to learn to use and

5

operate the system with little to no unfamiliarity.

4. Have the capability to con�dently store and display past customer record if

a situation arises.

7 Summary of Deliverables

A release candidate of the proposed software and software documentation will

be presented. A sample end-user of the business �rm will use the program to

faithfully validate its nature and use. This documentation will be presented to

check if the contents are very realistic.

8 Bene�ciaries

The following are the common bene�ts that a beni�ciary can obtain:

� Flexible user interface

� Ease of use

� Reducing time and cost

� Easy locating of previous records

� Compare with previous condition graphically

� Huge data recording

� Faster data retrieval

� Ease of �nding out information

Mainly the employees of Nitz Furniture are the bene�ciaries.

Interactivity amongst departments of the business �rm should be realised.

6

9 Proposed Solutions

We want the �rm be integrated with a typical database system and computer

network systems. We want Nitz furniture employees have a glimpse of information

processing in software. We want the business activities be rendered with software

capabilities.

9.1 Strengths

We project managers have con�dence because of the rapid secure and reliable

technologies ready to be given at �rst hand. The best selected methodology com-

plements a good work and energy outputs from project managers.

9.2 Weaknesses

The usage of the existing methodologies may cause delay and waste work and

power, hindering the project manager to do the project on time as expected. Ef-

fects of the ine�ciency of the methodology lead the project to immense instability

and project delay. Selection and implementation of the best proposed methodol-

ogy can mitigate delays and instability.

9.3 Scalability

Interminable updates and support to the project should be established. As the �-

nal product has been released, support continues throughout the proposed service

life span. Accommodation of the growth of the business �rm in its coming business

years, the system should have the ability resize. A change in data storage quantity

is not a problem. But a change in the �rm's structure such as appendage or modi-

7

�cation of a department due to changes in the �rm is a di�erent view. The existing

entity relationships may be deprecated. An existing deprecated system between of

the the project and that of the business �rm in terms of variation is manageable

for the project manager who had done the project or a newly appointed project

manager who would dismantle the project to apply changes. There can be oc-

currences where the project is �xedly sized due to its scope and limitations. The

support for the expansion complies with the scope.

Hence, this project may be constantly sized because its concern is solely for the

inventory department. Other expanding entities within the business �rm that may

need a new project would mean another distinct project.

9.4 Security

Security is one of the most integral aspects that the project should characterise.

The defence of the system to unauthorised access is probably the utmost ability

of the project.

Data security features amongst Windows 6.1+ operating systems are implemented

in the proposed software. The database uses Oracle platforms. We chose the top

of the line database servers. Oracle's powerful preventive and detective security

controls include database activity monitoring and blocking, privileged user and

multifactor access control, data classi�cation and discovery, transparent data en-

cryption, consolidated auditing and reporting, secure con�guration management,

and data masking. With Oracle, users can deploy reliable data security solu-

tions that require no changes to existing applications, saving time and money.

8

From the outset, Oracle has delivered the industry's most advanced technol-

ogy to safeguard data at the source of the database. Oracle provides a com-

prehensive portfolio of security solutions to ensure data privacy, protect against

insider threats, and enable regulatory compliance for both Oracle and non-Oracle

databases. (http://www.oracle.com/)

10 Proposed Scope and Parameters

The usability of the proposed system should be considered for intrinsic use solely

for Nitz Furniture, ensuring the integrity and constancy of the proposed system.

Ability to make the proposed system solely for the business �rm is an integral

concern. Uniqueness of the actual system to the proposed system should both be

congruent with each other. To make the proposed system look and feel as genuine

as possible, use of proper nouns in the system will be inevitable. Title and logos

will be inscribed in the software as well. Spanning the demands and needs of

the business �rm, its inventory system is the only concern of the project holders.

Earlier mentioned that the main �rm's entities are stock of wood, carpenters,

�nished furniture products, sales employees, inventory manager, and customers.

Our scope is to cover the customer, inventory manager, and �nished furniture

products.

The system does not include the salary setting of the �rm's employees such as the

carpenters and expenses like tools, adhesive supplies, and electricity consumed by

a planer, wood cutter, and etc. The system's primary concern with is with the

project title itself, the inventory system.

9

11 Assessment of Existing System

:Customer :Salesperson :Inventory Manager :Carpenters

order()

arrange()

partiallyPay()

OR-N/P

giveTask()

giveTask()

doTask()

askForSupplies()

recieve()

turnOver()

recieveWage()

CarpentryCarpentry

bookeepExpenses()

Furniture ConstructionFurniture Construction

queueProductInventory()

acquireFinishedProduct()

contact()

fullyPay()

ORdeliver()

Finishing EventsFinishing Events

Order ProcessOrder Process Events

10

ExistingSystem

1..*

1..*

1..*

1..*

1..*

1..1

Customer

+Name

+customer_no

-address

-city

-state

#contact_no

order(dow

npay)

fullyPay()

submitDesign()

SalesPeople

+sales_

person

+name

-hire_

date

#bill()

#authorise()

#sendTask()

#contact()

#recievePayment()

InventoryItem

+product_no

+unit_price

-supplier_id

+category_id

-quantity_per_unit

-units_

in_stock

-units_

on_order

Invoice

+invoice_

no

+date

+customer_no

+sales_

person

+product_no

-unitprice

-quantity

#amount

+authorizer

Accounts

Recievable

+acc_rec

-date

-customer_no

#amount

+invoice_

no

InventoryManager

+name

hire_

date

#sendOrder()

#giveItem()

#giveW

age()

#giveSupplies()

#bookkeepExpense()

#giveTask()

#queueProductInventory()

#record()

Carpenter

+sales_

person

#construct()

11

Customer

Place Order

Check Item

Canvass Design

Get Payment Info

Get Product

Sales Person

Record

Get Product

Authorise

Contact

Send Order

Inventory Manager

Give Supplies

Give Wage

Authorise

Queue Product in Inventory

Bookkeep Expenses

Deliver

Carpenter

Construct

Recieve Order

12 Methodology

Scrum is a type of Agile methodology that focuses around 30-day "sprints" and

monthly "scrum sessions" where project deliverables are broken down into 30-day

intervals. When teams switch to scrum, those previously paralysed by heavy "pro-

cess" or di�culty in prioritizing work, can see great gains in productivity. Scrum

12

is applicable only in certain types of environments - mainly those with collocated,

100% dedicated team members (not working of multiple projects), with unlimited

support for the project team (not a heavily constrained time and materials bud-

get).(http://www.successfulprojects.com/) A meeting place was conducted and

the Scrum device is �xed in the meeting area. The project manager will faithfully

control the development of the project using the methodology device.

13 Project Plan

Conferring standards from the client, we project managers should consider his

standard and give the best client satisfaction. Delivering the intended scope of

the project creates limits and saving power. We need to integrate software capa-

bility in the business �rm to achieve secure and e�cient data handling. We will

painstakingly perform technical and programming tasks. We will be responsible

and always be involved in project activities. We plan to �nish the project on or a

few days before 31 April 2016.

13.1 Project Kicko�

Meetings are done every end of the working week. The project manager and

holders should always be present in meetings. We should be able to develop good

personalities and understanding with each other. This is where we share and

exchange ideas to develop a more intuitive project making skill.

13

13.2 Development Plan

All the work load and knowledge abilities of the team are the primary inputs and

initiating power, making it through the project development. Project handlers

should give themselves a refresh and review of technical principles of Visual Basic

programming and mySQL querying. Proprietor interview is an integral part of

the development plan. Questioning skills should be honed to precisely let the

client expect a good project output. Interview and midterm project reports are

scheduled to maintain stability of the project, evident on the Gantt chart. (see

appendix) Every answers will be answered and implemented in the project making

processes. Having the best chosen methodology and expert judgement amongst

team members, we will be able to produce a good output.

14 Appendix

14.1 Company Pro�le

Nitz Furniture o�ers a�ordable furniture pieces that would surely �t your budget.

Having eliminated the overhead cost of a showroom, we o�er much lower prices

than most retailers in the Philippine market. We understand that each customer

is unique and has their own taste especially when it comes to the decor for their

home or o�ce. That's why we work closely with you to understand your individ-

ual needs, with regards to style, colour or theme. We will help you match your

furniture pieces together. Just contact us and one of our knowledgeable associates

will be more than happy to provide you with the best advice possible. If there is

something you don't see, ask. We have a network of some of the best manufac-

14

Proprietor

Employees

Sales People

Inventory Manager

Carpenters

Figure 1: A simple organizationalstructure of Nitz Furniture. Salespeople and inventory manager aresalaried while the carpenters arewaged by the proprietor.

turers in the world and can usually �nd the perfect piece for you.

� Business Type: Furniture and Houseware

� Address: 144 PENAFRANCIA AVENUE Naga City Camarines Sur

� Tel: (054) 473 2262 / (054) 811 5134

� Fax: (054) 811 5134

14.2 Proposed Budget

� BUDGET STATEMENT �For the year ended 30 April 2016

� �

w/o Labor w/ laborEquipmentOracle Database SystemComputer Unit ×3 95,850.00 99,350.00Genuine Windows 8.1 EnterpriseIntel Core i5-240017" LCD Monitor

Database Server 17,000.00 19,500.00Sub Total 112,850.00 118,850.00

Labor at �44.53/hr × 8hrs× 15da× 17moGian Franco Dy +12% 101,742.14Rosselle Corporal 90,841.20Eden Villamante 90,841.20Joss Aragones 90,841.20

Sub Total 0.00 374,265.74

Total 493,115.74

15

The team will require �493,115.74 to cover the cost of the project, as well as an

estimated �600.00 to cover the cost of any printed reference material that would

be bene�cial to developing the software. All software development tools will be

available through open sources.

14.3 Work Breakdown Structure

A WBS (Work Breakdown Structure) is a hierarchical and incremental decom-

position of the project into phases, deliverables and work packages. It is a tree

structure, which shows a subdivision of e�ort required to achieve an objective; for

example a program, project, and contract.(2011, Booz)

16

Inventory

System

1

1.1

1.2

1.2.1

1.2.2

1.3

1.4

2

2.1

2.2

2.3

2.4

2.4.1

2.4.2

2.4.3

3

3.1

3.2

3.3

1Plan

1.1InterviewProprietor

1.2Datagathering

1.2.1Researchaboutfurniture

productionanditstransac-

tions

1.2.2Survey

NitzFurniture

employees

1.3Queuenecessary

equipmentforproject

making

1.4Makemeetingand�nancingarrangementswiththeclientand

theprogram

mingteam

2Develop

2.1Investigategathered

data

2.2CanvassGUI

2.3Haveameeting

2.3.1Thoroughly

discusstheplan

2.3.2Schedule

future

bi-weekly

orweekly

meetingwiththe

team

2.3.3Accordwithprogram

mingteam

2.4Program

2.4.1Proposetheoreticalalgorithmsof

theproblem

2.4.2Accordwithproject

manager

andhewilldotoowith

theclient

2.4.3CodethealgorithmsinVisualBasicandprovideappro-

priatequeriesfortheOracledatabaseplatform

3Assure

SoftwareQuality

3.1Provideprogressreportsto

theclientandproject

manager

3.2Spendamonth

ofdebuggingandtesting

3.3Sam

pleaNitzFurniture

employeeareleasecandidateof

the

software

17

14.4

Gantt

Chart

2015

2016

Jan

Feb

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

Nov

Dec

Jan

Feb

MarApr

Planning

Project

Proposal

Proprietor

Interview

DataGathering

Finance

Acquisition

SoftwareDocumenting

Development

ProgressReport1

FrontEnd

BackEnd

ProgressReport2

EndBridging

Quality

Assurance

EthicsTest

Debugging

FinalReport

Dem

onstration

Figure

2:GanttChart

18

14.5 Development Team Pro�le

Client

Project Advisor

Project Manager

Programming Team

14.5.1 Project Manager

Gian Franco Dy is a professional in the �eld of project management. Project

managers can have the responsibility of the planning, execution and closing of any

project, typically relating to construction industry, architecture, aerospace and

defense, computer networking, telecommunications or software development.

14.5.2 Programming Team

Herewith are the members of the programming team and their characteristic:

1. Rosselle Corporal � earned units in Bachelor of Science in Electronics and

Communications Engineering at University of the Nueva Caceres She is pro-

�cient in programming in Python, C++ and Visual Basic. She has a good

queriying background in MySQL.

2. Joss Aragones � earned units in Bachelor of Science in Computer Science

at University of the Nueva Caceres. Also, She is pro�cient in programming

in C, C#, and Visual Basic. She had experienced database-related seminars

of Oracle then earned the reputation as one of the most leading professionals

who manages database.

19

3. Gian Franco Dy � earned units in Bachelor of Science in Marketing Man-

agement at University of the Nueva Caceres.

4. Eden Villamante � earned units in Bachelor of Science in Information Man-

agement at Ateneo de Naga University. She has the skills of managing infor-

mations in databases. She is also good in programming in C++ and Visual

Basic.

The team are professionals who have a minimum attainment of a bachelor degree

in computer science or information technology. These people have professional

programming skills pro�cient in Visual Basic and Oracle database which are the

foundations of the GUI and database of this project. They work according to

the methodologies presented in this document. Most have three or more years of

experience with the chosen programming languages for quali�cations to join this

team.

20

14.6

Burn-downChart

−2

02

46

810

1214

1618

2022

2426

2830

3234

024681012

IterationTimeline(days)

SumofTasksEstimates(days)

Burndow

nChart)

IdealTasksRem

aining

ActualTasksRem

aining

21