Ps1finaldoocuments Final Na Po To2

Project Charter
Project Name: Material Management (Procurement and Warehousing)
Date:
Version 1
Author:
Bentor, John Roland H.
Tamesis, Kristian Ian T.
Survida, Jeric S.
Laurio, John Stephen A.
Dayag, Mhark John Paul E.
Procurement and Warehousing System Page 1

Chapter 1
1. Project Background
1.1 Problem/Opportunity Description
 Accuracy - exact quantity of items

 Miscomputation - sometimes the personnel made a wrong
computation of the remaining and used products.
 Data loss - high security of data when it comes in corrupt files.
 Maintenance – repair of items in case the item have damage.
1.2 Benefits
 Generate daily reports.
 Product monitoring.
 Product computation.
 Requesting of item.
 Returning of item.
1.3 Goals
 The inventory process of other restaurant is just a manual

operation that’s why the proponents are proposing a system that
will transform their inventory process of the said company into a
computerized inventory process employees encounter some
problems with regards to their inventory processing such as the
security, losing of item’s data, manual checking and storing of
files proponents will develop a system that will make the

product’s data to be secured and only the authorized user could
access and changed it.
1.4 Stakeholders and Clients

 Owners- are stakeholders because a fast food restaurant brings
them their profits.
 Costumers- are stakeholders because they can satisfy their
demand for food of the restaurants.
 Suppliers- are stakeholders because they provide restaurants
with raw material and get their revenues.
2. Project Scope
WORK BREAKDOWN STRUCTURE
2.1 Objectives
MATERIAL MANAGEMENT (PROCUREMENT AND WAREHOUSING)
PROCUREMENT SUPPLIER WAREHOUSING
RELEASE STOCK OF
OF ITEMS ITEMS
DELIVER
ITEMS
ORDERING MAINTAINANCE
OF STOCKS / REPAIRING
OF ITEMS
SEARCH FOR Biding
SUPPLIERS

The inventory process of other restaurant is just a
manual operation that’s why the proponents are proposing a
system that will transform their inventory process of the said
company into a computerized inventory process employees
encounter some problems with regards to their inventory
processing such as the security, losing of item’s data,
manual checking and storing of files proponents will develop
a system that will make the product’s data to be secured and
only the authorized user could access it to provide
manageable records, lessen the paper works, lessen and
identify the usage and spoilage.
2.2 Deliverables
Objective 1- Accuracy
Project deliverables Work Products/Description

Accuracy exact quantity of items
Objective 2 - Miscomputation

Miscomputation sometimes the personnel made a wrong
computation of the remaining and used
Products.

Objective 3 - Data loss

Data loss high security of data when it comes in
corrupt files
Objective 4 - Maintenance

Maintenance repair of items in case it have damage
2.3 Out of Scope
 The storing of goods

 All about P.O.S and Billing
3. Project Plan
3.1 Approach and Methodology
 Project Planning. List down the particular tasks of
the proponents that should have to be done according
to the scheduled time of compliance of the project
development.

 Brainstorming. Sharing of thoughts and knowledge
to come up with a great idea on how to improve the
existing system. Knowing the root why the existing
system encounters a particular problem on the flow of
process.
 Re-interview. Gathering of facts to form an efficient
and reliable source of information that will be needed
to develop a much better system.
 Surfing in the Internet. Another source of data
gathering. Comparison and contrast of existing
system to know what are the things to do and not to
do, to be able to prevent unnecessary process that
will become a constraint on the developing system.
 Consultation. Asking advice to meet the satisfaction
and requirements of an effective information system.
3.2 Project Timeline
ID TASK NAME START FINISH DURATION

1 Do research 07/10/2014 07/13/2014 4 days
2 Project Planning 07/11/2014 07/12/2014 2 days
3 Brainstorming 07/11/2014 07/12/2014 2 days
4 Interview 07/14/2014 07/14/2014 1 day
5 Arranging the 07/16/2014 07/20/2014 5 days
chapter 1
6 Revising the 07/ 22/ 2014 07/24/2014 2 days
chapter 1
7 Searching for local 07/27/2014 07/31/14 5 days
literature
8 Searching for 08/01/14 08/05/14 5 days

foreign literature
9 Combining the local 08/06/14 08/06/14 1 days
study and the
synthesis
10 Do the Chapter 3 08/15/14 08/31/14 16 days
3.2 Success Criteria

 Accuracy of monitoring
 Organized records of Items.
 Tenable flow of schedule
 Reliable source of information
 Security of records
 Satisfaction or contentment
 Updated records
3.3 Issues and Policy Implications

It not may depend to other but it can't be affect any
subsystem and other task to the process

3.4 Risk Management Plan
RISK PROBABILITY IMPACT RISK
FACTOR (H-M-L) (H-M-L) MANAGEMENT
ACTION
Technical Risk M L Secure a backup for
every documents
Project H H Allotted time should be
management considered
Risk
Financial risk H M Ask a sponsor
Compliance H H Make it before the

Risk appointed time
Service Transition
A. Corrupted files- unable to open the files

B. Block-out System/Electricity Shutdown
3.5 Options Analysis

 create two or more back-up files
 provide a generator as other source of electricity
3.6 Technical Features

 User-Friendly- easy to operate and to understand
 Level of Security- highly security of files
 Complete and simple- it contains all important facts
that are needs.

Project Organizations and Staffing
ROLE NAMES & CONTACT RESPONSIBILITIES TIME

INFORMATION
Project Manager  Manage, review,
and prioritize
project work plans.
 Provide status
report.
 Manage project
team.
 Recommend
changes, escalate
issues, and
mitigate risk.
System Analyst  Participate in
project activities,
including planning,
implementation of
deliverables, and
quality control.
 Provide worthy
ideas in developing
a system.
Business  Participate in
Analyst project activities,
including planning
and quality control.
 Provide worthy
intelligent ideas in
developing

documentation.
Document  Participate in
Specialist project activities.
 Creating the
documentation.
 Studying the
conduct interview
information.
Programmer  Participate in
project activities,
programmed the
system,
maintaining the
system.
Advisors and  Participate in

Resources project activities.
Project Budget
Budget Item: Description: Budget Cost:
One-Time Costs:
One-Time item 1: Description:
Total One-Time Costs
Ongoing Costs:
Ongoing item 1: Description:
Total Ongoing Costs

Chapter 2
System features
 Generating daily reports.
 Product monitoring.
 Product computation.
 Requesting of item.
 Returning of item.
2.1 Foreign studies
Bob Evans Restaurant
Bob Evans Farms, Inc. is a food service, processing, and

retailing company based in the Columbus, Ohio suburb of New
Albany. The company is named after its founder, Bob Evans
(1918–2007). It operates Bob Evans Restaurants. Its food
processing and retail enterprise products are manufactured and
sold under the Bob Evans and Owens Country Sausage brand
names. The Bob Evans Restaurant chain started from a single
truck stop diner near the Bob Evans Farm in Rio Grande, Ohio
in 1946. The chain has grown to nearly 570 locations in 23
states, primarily in the Mid-Atlantic, Midwestern, and upper
Southern states. All locations are corporately owned, not
franchised. The restaurant chain started after Bob Evans began
slaughtering and packaging his own sausage for his diner.
Truck drivers and other patrons began telling him that his
sausage was superior. However, but did not have the capacity

to fill large orders. He contracted with his cousin Tim Evans of
Evans Packing Co. to package Bob Evans Sausage products. In
the early years of The Bob Evans History, Bob was known to
have made his way across the Southern Ohio Hills seeking
some of the best cuts of meat. He was very well known in a little
town along the Ohio River by the name of Coal Grove, Ohio,
where at the local Meat Market & Grocery Store he and Earl
Nance created sausage recipes. Evans tried to sell his sausage
to area restaurants, but they turned him down, saying that
customers wouldn't pay more for quality. Evans felt differently,
and opened his own restaurant on his farm in Rio Grande in
1962. Another relative, Dan Evans, served as CEO until his
retirement in 2000. The company also offers pork products to
the retail grocery market, as well as other prepared food
products to the grocery and food service segments. The primary
theme is one of country living: "Breakfast is served all day". The
bob Evans restaurant have procurement and warehousing
system their system can generate reports weekly monthly or
daily also can generate graphed timeline of your sales, profits,
or inventory levels , multi user like admin or employee, monitor
warehouse stock, in and out or item, quantity and unit
measurement of the item is monitored, also the time and date
item receive the purchase orders status report spoilage and
item expiry date is notified , barcode scanners to manage your
inventory more quickly and accurately, compatible with most
barcode scanners you can plug into your computer, multiple
Units of measurement, can determine the product cost tracking
and multiple Currencies and Languages.

Portillo Restaurant
Portillo's, which is the main entity within The Portillo

Restaurant Group is a chain of restaurants that specialize in
serving Chicago-style food. Portillo's is located primarily
throughout the Chicago metropolitan area, with two locations in
southern California and one in Scottsdale, Arizona. Dick Portillo
was born at 1330 West Van Buren in Chicago, Illinois. His family
then moved to government-subsidized row houses on Mohawk
Street, called the Mother Frances Cabrini Housing Project. After
his father started earning enough money, they were prompted to
leave and moved to 1617 South Central Park. His family later
moved to the southwest suburbs. He was a 1957 graduate of
Argo Community High School at 63rd and Harlem. After high
school, he served a tour with the Marine Corps. The first
Portillo’s hot dog stand known as “The Dog House” opened in
1963 on North Avenue in Villa Park. Owner and founder Dick
Portillo invested $1,100 into a 6’ x 12’ trailer without a bathroom
or running water. To get the water he needed, he ran 250 feet of
garden hose from a nearby building into the trailer. The Portillo
restaurant have procurement and warehousing system their
system can generate reports weekly monthly or daily also can
generate graphed timeline of your sales, profits, or inventory
levels , multi user like admin or employee, monitor warehouse
stock, in and out or item, quantity and unit measurement of the
item is monitored, also the time and date item receive the
purchase orders status report spoilage and item expiry date is
notified , barcode scanners to manage your inventory more
quickly and accurately, compatible with most barcode scanners
you can plug into your computer, multiple Units of
measurement, can determine the product cost tracking and

multiple Currencies and Languages, warehouse summary,
warehouse stock layout and inward tally / outward tally details of
items.
Spangles restaurant
Spangles is a family-owned fast food chain based in Wichita,

Kansas. It serves 1/3-poundburgers, flatbread pita wraps,
French fries, onion rings, Lactose free milkshakes and other
soft-serve ice cream desserts, cinnamon rolls of which are
made in Yoder, Kansas and are named after the town, and
breakfast sandwiches. Breakfast specialties include sourdough
sandwiches, Pitas and Breakfast Bowls. Lunch specialties
include the 1/3-pound Gourmet Supreme burger, 1/3-pound
Western Burger, 1/3 pound Mushroom Swiss Burger,
Sourdough Bacon Swiss, Sourdough Turkey bacon Ranch
Sandwich and Grilled Chicken on Pita. Some of the promotional
food items that Spangles have served are a Guacamole Bacon
Swiss Burger, Asian Chicken Pita, Seafood Krab Pita (a Lenten
offering), a Parmesan chicken pita, and a Frito Chili Cheese
Bowl. The chain is known for its bizarre, kitschy TV
commercials. Unlike restaurants like McDonalds, Spangles
offers its full menu until 11:00 a.m. and offers six popular
breakfast items the rest of the day. The spangles restaurant
have procurement and warehousing system their system can
generate reports weekly monthly or daily also can generate
graphed timeline of your sales, profits, or inventory levels , multi
user like admin or employee, monitor warehouse stock, in and
out or item, quantity and unit measurement of the item is
monitored, also the time and date item receive the purchase

orders status report spoilage and item expiry date is notified ,
barcode scanners to manage your inventory more quickly and
accurately, compatible with most barcode scanners you can
plug into your computer, multiple Units of measurement, can
determine the product cost tracking and multiple Currencies
and Languages, warehouse summary, warehouse stock layout
and inward tally / outward tally details of items, stock list and
stock report of item is reported.
Fatbugger
Fatburger was founded by Lovie Yancey in Los Angeles,

California in 1947. It was originally named "Mr. Fatburger" (on
behalf of Lovie’s boyfriend), until the “Mr.” was removed by
Yancey in 1952. At that time, she bought out her start-up
partners and retained sole ownership of the Fatburger brand
until 1990, keeping and operating only the original store on
Western Avenue for herself. Fatburger remained mostly a
California chain until the late 1990s, when it began an
expansion in North America. On August 15, 2003, Fog Cutter
Capital Group completed a $7 million investment and financing
package for the company. As of 2014 Fatburger operates or
franchises over 150 Fatburger restaurants worldwide with over
300 more planned for future development. For several months
in 2006, the company was barred from selling additional
franchises in California.Fatburger has achieved near cult status
in California culture, thanks to references in popular hip hop
music. Ice Cube mentions the restaurant chain in his 1993 hit "It
Was A Good Day," as did Tupac Shakur in "Late Night," a track

off his posthumous 2002 album "Better Dayz .In 2008,
Fatburger opened its first restaurant in a sports stadium, the
Arizona Diamondbacks' Chase Field.Fatburger also opened its
first location in the Dubai, U.A.E., (today there are eight).In
January 2013, Fatburger opened its first branch in Karachi,
Pakistan. Owing to the success of the burgers and positive
response by Pakistanis, Fat burger opened its biggest flagship
outlet globally on June, 2013 in Lahore. The fatburger
restaurant have procurement and warehousing system their
system can generate reports weekly monthly or daily also can
generate graphed timeline of your sales, profits, or inventory
levels , multi user like admin or employee, monitor warehouse
stock, in and out or item, quantity and unit measurement of the
item is monitored, also the time and date item
Receive the purchase orders status report spoilage and item
expiry date is notified , multiple Units of measurement,
warehouse summary, warehouse stock layout and inward tally /
outward tally details of items, stock list and stock report.
Perkins Restaurant and Bakery
The Perkins chain was established in 1958, when Matt and

Ivan Perkins opened Perkins Pancake House in Cincinnati,
Ohio. Throughout the Sixties, the chain expanded as a
franchise. One franchisee in Minnesota, Wyman Nelson,
introduced an expanded menu and an aggressive advertising
campaign in 1967.Between 1969 and 1978 Nelson consolidated
Perkins and another chain, Smitty's, into Perkins 'Cake & Steak'.
Nelson assumed nationwide development control of the
company, and focused on opening over 220 Perkins Cake &

Steak House restaurants. In 1979, Matt and Ivan Perkins
retired, and sold their remaining interest in the company,
including all trademark and distribution rights. In August 1979,
Perkins became a wholly owned subsidiary of Memphis-based
Holiday Inns, Inc. corporate headquarters were established in
Memphis, Tennessee. Matt Perkins died of heart disease in
1991 at age 79.Ivan Perkins died on February 11, 1998, and his
wife Cecilia died February 25, 2013, at the age of 97.In 1985
restaurant entrepreneur Donald N. Smith, who then served on
the Board of Directors of Holiday Inns, purchased an ownership
interest in Perkins and became Chairman of the Board and the
company's CEO. Smith remodeled buildings, and introduced in-
store bakeries, and distinctive brand imagery and standardized
signage. The company became focused on table-service family
dining. The company was renamed Perkins Family Restaurants
in 1987, and was organized into a master limited partnership
with interests publicly traded on the New York Stock Exchange.
Perkins also expanded internationally, opening a restaurant in
Thunder Bay, Ontario, Canada. In 1990, the company began its
philanthropic relationship with Give Kids the World, contributing
money and meals to the Florida-based charity for terminally ill
children from around the world. In 1992 the company introduced
a new building design, with the prototype restaurant opening in
Springfield, Illinois, with an arched exterior façade with neon
lights and an interior design with a central kitchen and baking
with separate dining wings. In the 2000s Perkins underwent
business changes. In 2000 it merged with a wholly owned
subsidiary of The Restaurant Company. In 2005 the parent
company, TRC, was acquired by Castle Harlan, a New York-
based private equity investment firm, for approximately US$245
million. In May 2006 TRC also acquired Marie Callender's, a

chain of casual dining restaurants also known for their freshly
baked pies. By 2011 the company, now more than 50 years old,
was in financial trouble. In June 2011 many restaurants were
closed across the country with no notice given to customers and
staff. There were closures in Colorado, Kansas, Illinois,
Tennessee, Florida, Michigan, and Minnesota. Later that month,
Perkins & Marie Callender's Inc. filed for Chapter 11
Bankruptcy. The company closed about 65 restaurants and laid
off 2,500 workers. In the bankruptcy proceedings the company
listed assets of $290 million and liabilities of $441 million. The
company emerged from bankruptcy at the end of November,
2011, but continued to experience difficulties: in May 2012 it
was announced that all Western New York area Perkins
restaurants would close. The Portillo restaurants have
procurement and warehousing system their system can
generate reports weekly monthly or daily also can generate
graphed timeline of your sales, profits, or inventory levels , multi
user like admin or employee, monitor warehouse stock, in and
out or item, quantity and unit measurement of the item is
monitored, also the time and date item receive the purchase
orders status report spoilage and item expiry date is notified ,
barcode scanners to manage your inventory more quickly and
accurately, compatible with most barcode scanners you can
plug into your computer, multiple Units of measurement, can
determine the product cost tracking and multiple Currencies
and Languages, warehouse summary, warehouse stock layout
and inward tally / outward tally details of items, stock list and
stock report of item is notified.

2.2 Local Studies
Congo Grille
Congo Grille is a chain of family restaurants in the

Philippines named for its African jungle-themed interiors. In
contrast to the decor, the cuisine is predominantly Filipino with a
smidgen of Western and Chinese foods. The award-winning
restaurant is also popularly known as The Sisig King for its
recent achievements in a food feast celebrating the favorite
Filipino dish. The chain has plans to build stores overseas,
especially in the United States. Congo Grille was established in
1999 by Kenneth Sytin and his brothers. That year, the business
had as many as 13,000 customers a month and was dubbed
"the fastest growing grill in town." In 2006, Congo Grill
participated in the Annual Sisig Festival held in Angeles City,
Pampanga. Their pork sisig and two other sisig dishes won first
prizes in the major categories. The restaurant operates based
on three concepts; a Philippine restaurant in an air conditioned
environment, food without monosodium glutamate, and a
mascot (an ape in safari outfit) for entertaining youngsters.
Congo Grille was opened for franchising in 2008.The Congo
Grille is have procurement and warehousing system their
system can generate reports weekly monthly or daily, multi user
like admin or employee, monitor warehouse stock, in and out or
item, quantity and unit measurement of the item is monitored,
also the time and date receive the item, purchase orders status
report, spoilage and item expiry date of the item is recorded
notified.

Gerry’s Grill
Gerry’s Grill is a group of restaurants based in the

Philippines. It is also among the largest restaurant chains in the
country, having 47 stores (44 in the Philippines and 3 in the
United States). Gerardo B. Apolinario had a way of enjoying
delicious food with friends and relatives. In this, he dreamed of a
place of such pleasant ambience which he would share with
them. After gathering his folks for organizing, Gerry's Grill was
opened on Valentine Day in 1997. Since then, the restaurant
business rapidly expanded. Apolinario's explanation regarding
how he founded the chain was: “When we were in college, I was
always the designated cook of the group whenever we had out-
of-town trips. I eventually mastered it.” During the opening of a
branch in Cebu, Apolinario once quoted: “You should be
consistent with your food and service. That is the secret. The
Gerry's Grill have procurement and warehousing system their
also the time and date item receive the purchase orders status
report spoilage and item expiry date is notified . The database
holding the information of their system is Microsoft access.

Bacolod Chicken Inasal
Bacolod Chicken Inasal is a Philippine restaurant chain. It

is among the best known in the country for serving inasal, a kind
of roast chicken served on skewers that originated in the
Visayas. It is also a sponsor for a number of television sitcoms
on ABS-CBN. The chain was established in 1993 by the
Tanalgo siblings; Rose, Bing and JM. It began as a small take-
out stall in Mandaluyong where customers purchased their food
then ate them at their convenience. A year later, a full-fledged
store was built to allow patrons to sit and dine. Soon, their
specialties gained attention among the denizens of Metro
Manila and, five years after it was founded, a second outlet was
built in Makati.
On May 30, 2009, the first-ever Inasal Festival was held in
Bacolod City. For their efforts in promoting inasal nationwide,
BCI was commended by the city's mayor, Evelio Leonardia, who
presented them a trophy. The mascot of the chain is a
caricature boy named Toto. His name, according to the website,
is a Visayan customary way in which men are sometimes called.
On ads or banners, the character talks in a Visayan dialect
(subtitled in Tagalog). Portraits of local actress Judy Ann
Santos, holding an inasal, are often seen on ads that promote
the restaurant chain. She was selected to be an endorser of the
business because they were inspired by a dish called Ysabella
Chicken that appeared in a TV sitcom called Ysabella which
stars Santos. Despite this, Rose Tanalgo said the recipe for
their chicken is rather different from what was seen in the TV
series. The bacolod chicken inasal have procurement and
warehousing system their system can generate reports weekly
monthly or daily, multi user like admin or employee, monitor

item expiry date is notified. The database holding the
information of their system is Microsoft access.
Mang Inasal
Mang Inasal Chicken BBQ is the Philippine's fastest growing

barbeque fast food chain, serving chicken, pork barbeque and other
Filipino favorites, was first established on December 12, 2003 in Iloilo
City. Currently, there were 445 branches nationwide and with over
10,000 employees system wide. Mang Inasal is doing its share in
alleviating the unemployment burden of the country. The presence of
every Mang Inasal in a certain area provides not only employment but
also opportunities to community members including suppliers of
kalamansi, charcoal, banana leaves, vegetables, bamboo sticks, and
other ingredients. It also indirectly gives income-generating activities
to many. In keeping with the mission to consistently provide its
customers a great Pinoy dining experience, Mang Inasal, the
Philippines’ fastest growing barbecue fast food chain branches out
again, this time in Turbina, Calamba, Laguna adding to its more than
300 branches nationwide. Marco Sison and Nonoy Zuñiga graced the
opening last Nov. 19. The Brothers Band provided the entertainment
and back up. First established in Iloilo City on December 12, 2003 by
Edgar “Injap” Sia serving grilled chicken, pork barbecue and other
Filipino favorites, Mang Inasal Turbina in Calamba is a franchise
owned by Ikemada Resources, Inc., a holding company, which aims
to have ownership of different outlets/branches in the food industry.
Ikemada’s choice of Turbina in Calamba as the next site for Mang
Inasal is its strategic location which is between the two bus terminals

ferrying passengers from Manila to the southern provinces of Quezon,
Batangas, Bicol and Mindoro. Turbina is just 30-minutes’ drive from
Makati. This is also in line with Mang Inasal’s vision to be the
preferred quick service restaurant of every Pinoy everywhere. The
mang inasal have procurement and warehousing system their
also the time and date item receive the purchase orders status
report spoilage and item expiry date is notified.
Master Siomai
Master Siomai is a food cart franchising business developed

by Masterrific Foods, an 11-year-old company specializing in
the production and distribution of processed meat such as ham,
bacon, burger patties and siomai to its diverse clientele ranging
from hotels, restaurants and market places. Still going strong
seven years after it was established, the success and
experience of Masterrific led it to another highly-promising
venture in 2007 – a Food Cart Franchising. This gave birth to
Master Siomai which grew to 550 outlets and counting to date.
The company also has branches in major malls like SM,
Robinson’s, Gaisano, Ayala, Gotesco, NCCC, Puregold,
Waltermart and Savemore. Its rapid growth can be attributed to
its very efficient system, high product quality, and exceptional
personnel. One of the keys to Master Siomai’s sensational
success is credited to its very own distinctive Japanese siomai –
pork siomai wrapped in genuine Japanese seaweed specially
topped with crab. To complement this feature product, our

signature Japanese-inspired food cart is designed in a way that
will contribute to the light and pleasant atmosphere that our
patrons deserve. Aside from these, we also take pride in our
delicious and flavorful beef, pork and shrimp siomai plus a thirst-
quenching gulaman pandan drink to serve as refreshment.
Other new and exciting products will be rolled in the future not
only for the market to embrace, but for our customers to
enjoy. The primary motivation of Master Siomai is to be
approachable. We are driven to satisfy both the taste buds and
pockets of the modern Pinoy with only the best products made
from the best ingredients using innovated technology and a
skilled workforce. The master siomai have procurement and
warehousing system their system can generate reports weekly
monthly or daily, multi user like admin or employee, monitor
item expiry date is notified.
3.1 Synthesis and significance of the studies

Reviewing of studies about procurement and warehousing
system is important. The proponents can get some ideas and
knowledge that will help to them in making the project.
Literature is about the study of some know people who studies

about the procurement and warehousing system that was done
by the foreign people and local are the studies that was done by
the local studies.
Foreign literature, procurement and warehousing system helps

us to meet the profit goals, shorter the cash cycle, avoid
inventory shortage improve business profits, to manage the

stock in the warehouse and the most important work for any
manufacturing unit. It explains that by managing the process it
becomes easier for the organization to meet the profit goals,
shorter the cash cycle, avoid inventory shortage.
The study of literature we search for is have the same process

like are develop system like Generating report, Product
monitoring and computation, Requesting and Returning of items
and they database can't handle large data otherwise our system
can’t have an authorized in spoiled goods and its expiry date.
Features Congo Gerry’ Bacolod Mang Mast Bob Portillo' Spangl Fatbu The Propos
Grille s Grill Chicken Inasal er Eva s es rger Perkin e
Inasal Siom ns s System
ai
Generat / / / / / / / / / / /
e report
Weekly/
Daily
Monitori / / / / / / / / / / /
ng of
Product
Comput / / / / / / / / / / /
ation of
Product
Reques / / / / / / / / / / /
ting and
Returni
ng of
Items

stock / / / / / / / / / / /
layout
and
inward
/outwar
d tally
Features Cong Gerry’ Bacolod Mang Maste Bob Portillo' Spangl Fatburg The Propos
o s Grill Chicken Inasal r Eva s es er Perki e
Grille Inasal Siom ns ns System
ai
Warehous / / / / / / / / / / /
e
summary
Multi User / / / / / / / / / / /
Admin
and
Employee
Stock List / / / / / / / / / / /
Time and / / / / / / / / / / /
Date
Status
In/Out

RISKMITIGATION,MONITORING, AND MANGEMENT
PLAN
1.0 Introduction
The Proponent do the risk mitigation, monitoring and management plan

process to developed plan, enhance and reduce the risk by indentifying the
new risk and plan effectiveness in the project .As part of an iterative process,
the risks will identify and record the results of risk prioritization analysis that
provides input to both risk mitigation and risk impact assessment .
1.1 Scope and intend of RRMM activities
The goal of the risk mitigation, monitoring and management plan is to

identify as many potential risks as possible. To help determine what the
potential risks. The development team will consistently be monitoring their
progress and project status as to identify present and future risks as quickly
and accurately as possible. With this said, the members who are involved
with the implementation of the product will also need to keep their eyes open
for any possible risks that the development team did not spot.
1.2 Risk Management organizational role
Each member will undertake risk management. The development team will
consistently be monitoring their progress and project status as to identify
present and future risks as quickly and accurately as possible. With this said,
the members who are not directly involved with the implementation of the
product will also need to keep their eyes open for any possible risks.
2.0 Risk description
The Proponent will identify the possible risk to avoid error and to
developed plan, .As part of an iterative process, the risks will identify and
record the results of risk prioritization analysis that provides input to both
risk mitigation and risk impact assessment.
 Technology risk
 Development risk
 Business risk
 User risk
 Employee Risk
 Process Risk
2.1 Risk Table
Category Risk
Technology risk Out dated hardware
Development risk Insufficient resources
Business risk Delay Delivered goods and materials
Employee Risk Lack of training and experience
2.1.1 Description of risk Mitigation, Monitoring and Management

Plan
Technology risk

Technology risk involves of using technology that outdated .the software
will not function correctly from the outdated hardware technology .Since the
technology change rapidly the technology risk is important .
Development risk
If client fails to provide all necessary information and equipment due to
company privacy the development and execution of the system will fail .The
client shall provide all necessary things to do the project.
Business risk
This is the risk where concern is that the proponent is the being able to
produce client need that will impact on their business .If the software does not
achieve its goals or if the system does not work.
Employee Risk
The risk is in the user or person’s ability, experience and willingness to
create a team who develop the system. IF someone in the team does not have
enough experience to use application for developing the system ,and others
member of the team is do his job or task given in late, and if one of the members
is not exerting effort to do the system the project will fail .
2.1.2 Probability and impact for Risk Mitigation, Monitoring

and management plan
Category Risk Probability Impact

Technology risk Outdated 30% 2
Development Insufficient 50% 3

risk resources
Business impact Late delivering of 30% 1

good and
materials
Employee Risk Lack of training 40% 3
and experience
Impact Values Description
1 Catastrophic
2 Critical
3 Marginal
4 Negligible
Above is the table that categorizes the risk involved in software

development .It gives brief description of the risk in the Risk column and
also provides the probability of the risk accruing in percentage in
probability column and also the impact of the risk in the impact column.
The impacts values assigned to the each risk are described in the section
below the risk table. It is very convenient way to look at the risk and
describe the information of the risk.
3.0 Risk Mitigation, Monitoring and Management
Risk mitigation, Monitoring and management is the process of

developing options and actions to enhance opportunities and reduce
threats to the project . Risk mitigation progress monitoring includes
tracking identified risks, identifying new risks, and evaluating risk .

3.1. Risk Mitigation for Risk Monitoring and Management
Risk management is all about understanding risks that can impact

your system, and implementing strategies to mitigate and manage
those risks. A plan will be created avoid the risk and keep the software
development process to reach their objectives.
3.1.1 Product Size
Product size is the computation of the system a little

miscomputation or overestimating of the system will affects the
the product quantity and also the system.
3.1.2 Business impact
In this risk the software quality is concerned .To meet the high
software quality the team will spend more time to understand needs of
the user and costumer to gather information to provide software
requirements.
3.1.3 Customer risk
Customer risk is about the customer problem with the system ,

this will help us in the right product at right price for the costumer.
3.1.4 Process Risk
Process risk is about the quality of the system to be as high as

possible the user will achieve their need in our system.

3.1.15 Technology risk
The technology will affect the system developed to able to run

the system properly will need also a proper hardware to avoid
errors and bugs and latest hardware and equipment will provide
good service.
3.1.16 Development risk
Development risk is all about the tools ,recourses team

members and cost or budget needed .The tools is the software
,resources is like the laptop and human resource or the team will
developed the system.
3.1.17 Employee Risk
Employee risk is about the skills, knowledge and their

willingness of the team members to make the project ,and also the
employee or the people will use the system .
3.2 Risk Monitoring for Risk Mitigation ,Monitoring and Management

Plan
The technology change rapidly the risk monitoring for risk

mitigation, monitoring and management plan is about the changing of
technology.
3.2.1 Product Size
Product size is about the monitoring of functions necessary for the

program and help us in monitoring the size of the product.

Business impact is about costumer and client request to determine

change will make also the work progress of the team will monitor.
3.2.3 Customer Risk(User)
To monitor the risk of meeting our clients to get some

information and to help us to solve the problem to able to achiev
better product quality
3.2.4 Process Risk
To monitor the risk and review work to find the problems in the
system process in order to achieve better product quality.
The technology risk is in about rapid changes of the

technology the hardware will be use to run the system ,this will
help the team to see the future technology.
3.2.6 Development risk
Development risk in monitoring is about the operation of the

system, the accurate warehousing and procurering of item that will
affect in the developing the system to meet the quality or the
software and understand the needs of the user and to provide
system requirement
3.2.6 Employee Risk
Employee risk is about in the team members and their skills

some member has difficulties in performing their task or the tools are
not use properly by the member.

3.3 Risk Management for Risk Mitigation, Monitoring and
Management Plan
In this section we will identify several different software

development risk encountered and will try to create a plan to manage
this risk.
3.3.1 Product Size
Monitoring of process in the system and still looking for a erors this
is our way to in managing the risk
We have done many discussions about the software to reach

clients needs and to clear the misunderstanding between the team and to
change to get the clients suggestions to fit their business process .
3.3.3 Customer Risk (User)
Meetings in our clients and gather information and discuss

regarding in the system .
3.3.4 Process Risk
If the Problem exist within the system the team will fix the problems
to meet the quality standards of the clients
For this phase during the development of the software a new

technology will encountered , we spot the new techniques how to improve

the software without major change and also include techniques to develop
our project and the technologies will affect our project .
In this phase technology and tools are not enough or not suitable to
make our project properly , and also provide the software information ,
hardware and software specification to run the software .
Monitoring and manage of the risk will include looking for each team
member is having difficulties in performing some task or using particular
tools or techniques or lack of capability to use particular tools and spend
time for help each team member to learn certain tools using.
4.0 Special Condition
Special condition that are associated with the software are the followings.
Saving Check-list :
We need to make sure that as an inspector goes through the facility to be

inspecting he or she will automatically save data after every entry or change
occurred save button will be used only to finalize the reports.
Login:
Since we are using modular login we need to make sure that the person
login will only have access to certain part of the application ,this depend on the
rights granted to the user. We have to explain to each user why he or she is not
able to use that certain application .We also need to make sure that users with
read only.

Software Configuration Management Plan
1.0 Introduction
Software Configuration Management (SCM) is to identify and

control major software changes, ensure that change is being
properly implemented, and report changes to any other
personnel or clients who may have an interest. The objective of
SCM is to limit the impact changes may have on the
entire system. This will help to eliminate unnecessary changes,
and to monitor and control any necessary changes. This allows
software development to continue, despite large and/or
insignificant changes without significant backtracking, lessening
development time and resulting in a higher-quality product.
1.1 Scope and intent of Software Configuration

Management
Activities
The Software Configuration Management Plan is used to

establish the overall approach for the Software Configuration
Management required for this system. The scope of this plan in
Software Management Configuration is to developed or
implemented for the system, to maximize productivity by
minimizing mistakes in the member of the team.SCM activities
are identifying change .control change, ensure that the change is
being implemented properly and also have a way to document
the change to less the time consuming work to be successful in
doing our system.

1.2 Software Configuration Management
Organization role
The Software configuration management team will work

closely in the project, cross-examining many of the future errors
and software change requests. Programmer will submit change
requests directly to the SCM team for their inspection and
approval. The leader will be appointed to oversee all SCM
activities. He will receive all change requests, and will make any
final decisions regarding those changes, including which
Programmer will carry out approved changes. The SCM leader
also keeps a library of all submitted requests, even those that
have been denied.
2.0 Software Configuration Management Task
The SCM leader will analyze all current design specifications

and breakdown the software into subsystems. All subsystems
will consist of major software functions or interface components.
Any submitted changes will be connected to its corresponding
subsystem, which will be traced
backwards though the system to determine its impact. The
leader assign task for each member any changes will be
discussed with team and client.
2.1 Identification
The Software Configuration Management process applied to

this project identifies many types of error, each item has specific
identification rule and minimum verification characteristics.

2.1.1 Description
 Identify change
If some change or suggestion is implemented on the system
the team will analyze the change to figure it if the change is
necessary and justify
 Approve change
All change and suggestion of team mates or client must be
necessary and justify and all change must know of all team
members this determines which change requests approve or
deny.
 Ensure the change is being properly

Implemented
We ensure the finalize change is being implement properly
with helping of each team member to implement the change.
 Document the change

The change will be document to gives as reference in the
implemented change. This document serves us a guide and
reference.
2.1.2 Work products and documentation
 Identify change

If the change is identified all of the team members
must know.
 Control change
After the change is identified the members of the team
decides if the change is valid and reasonable to implement.
Ensure the change is being implemented properly.
 Document the change

The change will be document to gives as reference in the
implemented change. This document serves us a guide and
reference.
2.2 Configuration Control
The project design, document, and the current prototype of

the software .the will be used to track the impact through
the corresponding subsystem, and eventually the entire
system.The original design document will be consulted to
ensure that the requested change remains within
requirement specifications and the overall spirit of the
project. The leader may consult the current prototype if he is
unsure any change is required. This is imperative for
cosmetic changes to the interface. He will base his decision
on how severely the change will impact the entire system
and, more importantly, on the corresponding subsystem.

2.2.1 Description
Change will be controlled by using human procedures and

automated tools. Here are the steps, which will be taken in order
to control change
 Request change
 Software developer will evaluate the change request
 The result of the evaluation will be presented as
change report
 Final decision on change will be made
If the change is approved
1. Define constraint
2. Check out items for change
3. Make necessary change
4. Apply SQA activities
5. Check in items
6. Apply testing activities
7. Rebuilt the software
8. Distribute the software
2.3 Version Control

It is important that you have the latest version. Having the
latest version reduces the chance of a conflict, when the system
have a minor and major update the version control by number
scheme ,when the update is minor the version will be increase by
.1 but if major update like adding a new functionality in the
system the version number is increasing by 1. example 1 is the
current version, minor update it becomes 1.0 and if major
update it becomes version 2 .

2.3.1 Description
As a result of the change, the version number of various
modules will be increased .We will be using a universal version
number system for all modules. We will also have a final version
of the entire product
2.3.2 Increasing Version Number
When a change request is filed a change report will be

created. After the change is finalized it will be documented. We
will be using a decimal point version number system
Bug fix
If enough bug fixes have been done on the product /module,

the bug portion of the version number will be increased. The
number of user visible bug fixes will be also affect when the bug
fix number is increased .The more the visible bug fixes have
been made the closer the bug fix number will need to increase.
Minor Update
Other functionality added in the system/module like some

user friendliness performance function/interface, the version
number may be increased.
Major Update
The system will update functionality and user interface and

change the version number.

2.3.3 Work Products and Documentation
A document containing version revision bug reports, bug

fixe and enhancement request will be monitored and
documented.
2.4 Configuration Status Accounting (CSA)
We will be using two different ways to communicate with

other members or the people associated may concern.
2.4.1 Description
Two ways to communicate with other members or people

associated with the software development.
 Change request report

To change reports and request change will give to
SMC team to have documentation.
 Verbal communication
Verbal communication is better to have good
future plans to the project and also to tell bug and new
specification and function update needed by the system.
2.4.2 Work products and documentation
 Change request report

 Emails
 Verbal communication

3.0 Software Quality Assurance Overview
Software Quality Assurance consists of those procedures,
techniques and tools used to ensure that a product meets the
requirements specified in software requirements specification,
the scope of this document is to outline all procedures,
techniques and tools to be used for quality assurance of this
project.
Scope and intend of SQA Activities

The objectives of SQA are:
 A quality management approach

 Effective software engineering technology (methods and
tools)
 Formal technical reviews that are applied throughout the
software process
 A multi testing strategy
 Control of software documentation and change made to it
 A procedure to assure compliance with software
development standards when applicable
 Measurement and reporting mechanisms
Reviews and Audits

A formal technical review is a software quality assurance activity
that is performed by software engineers. The objectives of the
are
 To uncover errors in function , logic, or

implementation for any representation of the software

 To verify that the software under review meets it
requirements
 To ensure that the software has been represented
according to predefined standards
 To make projects more manageable
3.1 Generic Review Guidelines

ISO 9001 (International Organization for Standardization)
is the assurance standard that applies to software engineering.
The following are the 20 requirements delineated by them. And
we are tried to follow them as our quality assurance plan.
Management Responsibility
 Quality System
 Contract Review
 Design Control
 Document and Data Control
 Purchasing
 Control of Costumer Supplied Product
 Product Identification and Trace Ability
 Process Control
 Inspection and Testing
 Control of Inspection, Measuring , and Test Equipment
 Inspection and Test Status
 Control of Nonconforming Product
 Corrective and Preventive Action
 Handling Storage ,Packaging , Preservation, and delivery
 Control of Quality Audits
 Training
 Servicing

 Statistical Techniques
3.1.1 Conduction a Review

Conduct an interview for client and team mate about
the system to gather data usage of system and keep record
before implement another changes.
3.1.2 Roles and Responsibilities

 Conceptual and Advance Interface Development
 User Interface Design and Development
 Editor /Tester/ Maintenance
3.1.3 Review Work Product

Review work weekly to see errors and detect problems early
also a early solution will done.
3.2 Formal Technical Reviews

Formal Technical Reviews that will conduct during the software
process
 Walkthroughs
 Inspections
After each form (interface) we design, will do a test on the

interface using block box testing method. And for each week,
when the team set down come to meeting ,we will ask the team
mates to do inspection on the interface ,then hook up the others
work do a walkthroughs of all interface.

3.2.1 Description of Review Walkthroughs
The integration of all subsystem and the design will be
unified and the transferring and flow of data will secure.
3.2.2 Description of Review

This review focus on debugging of system or testing the
system to look for errors
3.2.3 System Specification Review

All of the system specification of the system will meet the
needs, set meeting to the clients to gathered more data to meet
the proper specification of the system.
3.2.4 Software Project Plan Review

Software project plan overview has a capacity to help
organize, and manage resource depending in the project plan of
the software it can include tools for estimation and planning,
scheduling, cost control and budget management, resource
allocation, and documentation.
3.2.5 RMMM Review

Risk mitigation, monitoring and management plan is to
identify as many potential risks as possible. To help determine

what the potential risks. The development team will consistently
be monitoring their progress and project status as to identify
present and future risks as quickly and accurately as possible.
With this said, the members who are involved with the
implementation of the product will also need to keep their eyes
open for any possible risks that the development team did not
spot.
3.2.6 Requirements Reviews (Models, Specification)

Requirement Reviews has a capacity to help organize, and
manage resource depending in the project plan of the software it
can include tools for estimation and planning, scheduling, cost
control and budget management, resource allocation, and
documentation.
3.2.7 Data Design Overview

Data design review involving several design of the database
schema, design of the programs that aces and update the data,
and design of a security scheme to control aces to data and
interface design process.
3.2.8 Architectural Design Review
The architectural design review when applied over the cycle
of a system, review and control of its performance, functional and
physical attributes verifies that a system performs as intended,
and is identified and documented in sufficient detail to support
the project.
3.2.9 Interface (GUI)

Interface and design of a system is up on client and add
other processes to improve the system.

3.2.10 Component Design Review
A design review is a milestone within a product development
process whereby a design is evaluated against its requirements
in order to verify the outcomes of previous activities and identify
issues before committing to - and if need to be re-priorities -
further work.
3.2.11 Code Review

A code use to create a system more often with mistakes but
some software developers often rely on manual or automated
testing to verify their code the ability to see and correct mistakes
ourselves.
3.2.12 Test Specification Review
3.2.13 Change Control Reviews and Audits
3.3 SQA Audits
 Team members will have weekly report on their individual

performance for the past week .Any problems, question
regardless on the performance of other team members will also
note.
 Any changes that will affect the project will consult with other
team members before doing any change. These are the change
that is minor or require a little code change, but still different from
the original architectural design.

3.4 Problem Reporting and Corrective Action/Follow-up
This section will describe problems reporting mechanisms

that occur as a consequence and conducted and the means for
corrective action and follow up.
3.4.1 Reporting mechanisms
The process and how the reporting a problem by the team

who developed the system and also the medium use to report a
problem
3.4.2 Responsibilities
Each of the team members have their own responsibilities

and duty to fulfill, the team leader is the responsible to separate
the gobs of each member all of the member will be update their
gob status.
3.4.3 Data Collection and Valuation
Software Quality Assurance
1.0 Introduction
It focus on the management issues and the process specific

activities that enable a software organization to ensure that it
does "The right things at the right time in the right way" this

section gives a general overview of the software quality
assurance plan.
1.1 Scope and Intent of SQA Activities
The objective of SQA are:
 High quality of software maintenance (tools and help)

 Multi testing process
 Process are assure that may comply when its exist
1.2 SQA Organizational Role
Item Management Structure
Editor/Tester/
Maintenance
Conceptual & Advanced (1)
Interface Development
(1)
User Interface design &

Development/Trainer
(1)
2.0 SQA Tasks
Here are the task we have for the SQA:
 Brainstorming
 Close contact on the supplier
 User friendly design
 Separate windows for Procurement and Warehousing

2.1 Task Overview
Task that written above cover minimize errors, control
process flow, and high quality of design
2.2 Standard Practices & Conventions
Brainstorming
We giving are suggestion when it comes software

development, Develop software is came from the idea of each
member of the group
Close contact on the supplier
In selecting of supplier it will undergo to an biding
User friendly design
Develop software have simple but unique interface to

became understandable for any user
Separate windows for Procurement and Warehousing
We decide to separate the window of Procurement

and Warehousing to avoid scramble of data and the user know
what is the process or window is being use
SQA Resources
No external SQA are redefined for this project.
3.0 Reviews and Audits
A formal technical review (FTR) is a software quality

assurance activity that is performed by software engineers. The
objectives of the FTR are:

 To make projects more manageable.
 To ensure that the software has been represented
according to predefined standards.
 To achieve software under review meets its
requirements.
3.1 Generic Review Guidelines
3.1.1 Conducting a Review
Reviewing of the system is one way of avoiding some

errors that may affect when it's working. After reviewing of the
software all the members may give suggestion to fix the error
3.1.2 Roles and Responsibilities
 Project Manager: John Roland B. Bentor

 Programmer: John Stephen Laurio
 Document Specialist: Mhark John Paul Dayag
 System Analyst: Jherick S. Survida
 Business Analyst: Kristian Ian T. Tamesis
3.1.3 Review Work Product
Product wok review are the reports given by weekly of

every administrator to know the error may be encounter during
the daily use of software, this report can help the developer if the
system have some achievements.

3.2 Formal Technical Reviews
Walkthroughs - describe and focus to the review
Inspections - We will ask the team members to a

inspections on the interface.
3.2.1 Descriptions Of Review Walkthroughs
It focuses on the subsystem integration flow.
3.2.2 Descriptions Of Review Inspection
The idea is try to allow other team members to bring

out the test case.
3.2.1 System Specification Review
All of the system specification of the system will meet

the needs, set meeting to the clients to gathered more data to
meet the proper specification of the system
3.2.2 Software Project Plan Review
Software project plan overview has a capacity to help

allocation, and documentation.
3.2.3 RMMM Review
Risk mitigation, monitoring and management plan is to

identify as many potential risks as possible. To help determine
what the potential risks. The development team will consistently

be monitoring their progress and project status as to identify
present and future risks as quickly and accurately as possible.
With this said, the members who are involved with the
implementation of the product will also need to keep their eyes
open for any possible risks that the development team did not
spot.
3.2.4 Requirements Reviews
Requirement Reviews has a capacity to help

allocation, and documentation
3.2.5 Data Review Design
It's focus on the data flow between each form to the

database.
3.2.6 Architectural Design Review
It's focus on the flow of the system and transition of its

window
3.2.7 Interface
The GUI of the system is depends on the suggestion

of each member
3.2.8 Component Design Review
A design review is a milestone within a product

development process whereby a design is evaluated against its
requirements in order to verify the outcomes of previous activities

and identify issues before committing to - and if need to be re-
priorities - further work.
3.2.9 Code Review
A code use to create a system more often with

mistakes but some software developers often rely on manual or
automated testing to verify their code the ability to see and
correct mistakes ourselves.
3.2.10 Test Specification Review
Base on our the Test Specification we do random

testing to ensure the system will function normaly
3.2.11 Change Control Reviews and Audits
3.3 SQA Audits
 Team members will have weekly report on their

individual performance for the past week .Any
problems, question regardless on the performance of
other team members will also note.
 Any changes that will affect the project will consult
with other team members before doing any change.
These are the change that is minor or require a little
code change, but still different from the original
architectural design.
4.0 Problem Reporting And Corrective

Action/Follow Up

This section will describe problems reporting mechanisms
that occur as a consequence and conducted and the means for
corrective action and follow up.
4.1 Reporting Mechanisms
The process and how the reporting a problem by the

team who developed the system and also the medium use to
report a problem.
4.2 Responsibilities
But since Project Manager has a lot of experience or

software development and has great knowledge on the project
so he's the leader of the team.
 Project Manager: Roland B. Bentor

 Programmer: John Stephen Laurio
 Document Specialist: Mhark John Paul Dayag
 System Analyst: Jerick S. Survida
 Business Analyst: Kristian Ian T. Tamesis
4.3 Data Collection And Valuation
It focus on the collected, evaluated data,

statistical SQA helps for improving quality of the project
4.4 Statistical SQA

5.0 Software Process Improvement Activities
Product
Supplier Business
Process
Development Environment
People Technology
Characteristic
Condition
5.1 Goals And Object of SPI
 To correct each errors and defect is

recorded.
 Number of errors and defects in each
 Error and defects are categorized by
the origin.

 Cost of overall errors and defects in
each category is computed.
 Analyzing the result of data to uncover
the categories that result in highest cost
to the organization.
 To modify the process of plans to be
developed.
5.2 Task And Responsibilities

The responsibly of each team member will
doing some activities.
6.0 Software Configuration Management And

Overview
Software configuration is developed so that we can identify
the changes control the changes making sure that the plan is
implemented correctly and to making sure that we report the
change to other members and the clients.
7.0 Tool, Techniques, Methods

Different tools had been use for this project. But the truth is
limited by the time and the size of the team.

System Specification
1.0 Introduction
System specification is to identify the use of application

and system we can do add or delete and the features can
make a update and hardware specification to run this
system.
1.1 Goals and objectives
Generally, the purchasing department’s goals are

similar to those of anyone who buys something: get the best
possible quality of all supplies, services and equipment at the
lowest cost. Most often, the purchasing department is that part of
the procurement section that handles the supply chain process.
To ensure quality and to prevent unethical practices, purchasing
is usually separate from receiving and accounts payable
Purchasing departments have changed over time.

Historically, they issued purchase orders for all supplies,
services, equipment and raw materials, but to save costs they
began to put in place "master" agreements for repetitive orders,
and they streamlined other routine tasks. This led to a larger role
for purchasing departments as strategic sourcing managers who
are concerned with purchasing large capital equipment, bidding
processes and negotiating with suppliers.
1.2 System Statement of Scope

This section of the Statement of Work should provide
a brief statement of what you expect to accomplish as a result of
this scope of work. While specific deliverables and tasks will be
presented in the Work Requirements section, this section should
highlight what is and is not included in the scope of the project in
broader terms.
1.2.1 General Requirements
The following general requirements were laid out for

our project name Procurement and Warehousing System.
 To provide manageable records.

 To lessen the paper works.
 To develop an effective document filing.
 To identify the usage and spoilage.
 To make the user comfortable of using the
system.
 To make the process faster and manageable.
 Interface Enhancement
We make the interface easier to understand
and manage by the user all the buttons and the functions are
place according to a normal interface of the system by its
purpose to understand.
 Database Administrative Interface

We will make all tables separate by
Procurement or Warehouse list all the attributes of every
tables.

 Training
The use or the member have also
requested throughout training for the entire user for the
functions and the use of the software.
1.3 System Context
User will be using our software for their own purpose, if the
software is compatible and likes by the user or the company.
This leads to issues about future support for a larger user base.
1.4 Major Constraints
Transparency – all phases in the procurement process are fair

and accurately documented;
Accountability – accountability to donors who may require

certain rules to be followed when using the money they have
provided;
Efficiency and cost effectiveness – meeting the six rights of

supply; price, right time, right quantity, quality services, delivery
to the required places and from the most cost effective source
Minimum Hassle – Since our goal was to create a system that

people would actually incorporate into their existing Net News
system, our software had to be designed for ease of integration.
This is difficult given the large number of platforms on which Net
News runs and the many configurations in which Net News
systems come.

Accessibility – Users must be able to control who has access to
their opinions on articles of information. Some users may only be
willing to contribute information anonymously, while others will
want to put their names on their opinions
2.0 Functional Data Description
This functional data description describes how the

process works or how running an information to the
database
2.1 System Architecture
2.2.1 Architecture Model
ADMIN
LOG
IN
PLATFORM
OPTION
End Exit DATABASE
PROCUREMENT WAREHOUSE GENERATE

REPORT
RELEASING STORING PRINT DATABSE

OF ITEM OF ITEM REPORT MANAGEMENT

DATA
STORE
IN DB
2.2.1 Subsystem Overview
Procurement is a key activity in the supply chain. It can

significantly influence the overall success of an emergency
response depending on how it is managed. In humanitarian
supply chains, procurement represents a very large proportion of
the total spend and should be managed effectively to achieve
optimum value. Procurement works like a pivot in the internal
supply chain process turning around requests into actual
products/commodities or services to fulfill the needs. It serves
three levels of users:
The internal customer
Programs in response to emergencies and ongoing programs
Prepositioning of stocks, for both internal customers and

program need
2.2 Data Description
2.2.1 Major Data Object
1. Supplier ID
2. Company Name
3. Contact Name
4. Contact Title

5. Address
6. City
7. Telephone Number
Categories
1. Category ID
2. Category Name
3. Description
4. Picture
Products
1. Product ID
2. Product Name
3. Supplier ID
4. Category ID
5. Quantity Per Unit
6. Unit Price
7.Unit In Stocks
Orders
1. Order ID
2. Product ID
3. Product Name
4. Costumer ID
5. Employee ID
6. Order Date
7. Required Date

Order Details
1. Order ID
2. Product ID
3. Unit Price
Items
1. Item ID
2. Item Name
3. Employee Name
4. Contact Titl
2.2.2 Relationships
Supplier Products
Supplier ID Product ID
Order Details
Company Name Product Name
Contact Name Supplier ID Order ID
Product ID
Contact Title Category ID
Unit Price
Address Quantity per Unit
City Unit Price
Region Unit in Stocks

Employee
Telephone Number Recorder Level
Employee ID
Last Name
First Name
Title
Orders
Order ID
Product ID
Product Name Item
Costumer ID Item ID
Employee ID Item Name
Order Date Employee Name
Required Date Employee Title
2.3 Human Interface Description

The proposal that we have of human interface description is
to show the record of system. If the user return from the facility to
insert a data from the database which uses java net beans as front
end the software uses ms SQL
The user logs into the database using his or her username
and password
The first screen that will be show up is PROCUREMENT &

WAREHOUSING MANAGEMENT and It contains five buttons with
several different option to choose from. the user will choose a
button to add a new facility into the database ,can find an existing
facility to print blank checklist for next inspection. User can also
choose button to print a blank

staff report. Or to go help menu. Or exit out the java net beans.
PROCUREMENT
Procurement History windows user will allow to generate

a new letter, checklist or report. It also allows users to view, or print
existing checklist. User can also edit historic data, update order
information or delete action using this window this window contains
help and return to main menu button
Order Information window allows user to fill in order

information to entries such as Supplier ID , Company Name ,
Contact Name ,Contact Title , Address, City , Region, Telephone
Number also about Supplier or mailing the Supplier. It also allows
users to fill in any comments regarding facility information
If the user searches for an existing order and order cannot be

found, the user will be shown order information such as no match
window that will have search again. Add new facility help or return
to main menu options.
If the user selects historic data option from the window

above he or she will be presented with historic data window which
will allow the user to fill in data such as inspection type. First
inspection date secondary inspection date, compliance action,
company response, inspectors information and completed
activities.
From select a checklist windows the user can select a

checklist to either fill out or print a blank one of from this screen you
can also access the file and return to the procurement history
screen

Search for an existing facility window enables user to
search for a facility that you believe has already been entered into
database. You can search by Company Name, Address, City,
Region, Supplier ID, or any combination of the five. If at least one of
your search criteria is Company Name or Company City and the
exact Company Name is not found, a list of close matches will be
displayed. If one of the close matches is the facility that you are
searching for, if none of the close matches are the facility that you
are looking for, you can either search again or add a new facility.
You will be taken to the procurement history screen and information
about that facility displayed.
Form the Report window the user can either generate a

commented report for the facility which you are currently working
on, print a blank report, access the help file, or return to the
procurement history screen
WAREHOUSING
Warehousing History windows user will allow to generate

a new letter, checklist or report. It also allows users to view, or print

information to entries such as Product ID ,Product Name , Supplier
ID , Category ID ,Telephone Number also about Supplier or mailing
the Supplier. It also allows users to fill in any comments regarding
facility information

If the user searches for an existing order and order cannot
be found, the user will be shown order information such as no
match window that will have search again. Add new facility help or
return to main menu options.

above he or she will be presented with historic data window
which will allow the user to fill in data such as inspection type. First
activities.

can also access the file and return to the warehousing history
screen

warehousing history screen
from the maintenance for item the contractor allow to check

or to fix all bugs or error in the database of warehousing screen you
screen
3.0 Subsystem Description
3.1 Subsystem Flow Diagrams
Procurement FAB/ POS

Contact
&
Supplier
Warehousing
Procurement Give Items Vendor
&
Warehousing
Procurement BILLING
Issue
&
Payments
Warehousing
Procurement Report General

& Ledger
Warehousing
Procurement Get Items Accounts

& Payable and
Warehousing Receivable
Procurement Reports Treasury

&
Warehousing
Procurement Get Items Reservation

&
Warehousing
Procurement Customer
Get Items
Procurement&and Warehousing System Page 70
Management
Warehousing
Procurement Get Items Human
& Resource
Warehousing
Procurement Get Items Payroll

&
Warehousing
3.1.1 Create Checklist
Requisition Requisition
Purchase
creation approval (initial
order creation
encumbrance)
NO
Requisition
processing Contractor
assignment
required
YES
Assign
Retrieve Returns Send supplier contractor
approved
Procurement and Warehousing
approveSystem notification Page 71
(adjust
suppliers from suppliers from encumbrance)
ASL ASL
NO OFFLINE
global Supplier Applicant

blanket response(offline) tracking(offline)
agreement
found
Retrieve rate
information from
YES agreement
3.1.2 Print Checklist
ACCOUNTING REQUESTOR MAINTAINANCE
BILL REQUEST ITEMS REPAIROF GOODS
PAYMENTS PROCUREMENT WAREHOUSE

REALEASE OF ITEM
STORING OF ITEMS
SELECTION FOR SUPPLIER

SUPPLIER
BIDING ITEMS/PORDUCT
SUPPLYING GOODS

3.1.3 Generate Letter
list of some letter types

appears letter types
from DB
required letter type letter types

letter types fro SCR
from DB
infringement code
procurement and description
information from DB
from DB
Information of all letters

checklist and appears on
information
from DB
date of letter
date of letter
Procurement and Warehousing System from SYSTEM Page 73
date response letter
Finalize letter
requested information
date response
updated on DB
requested
from SYSTEM
check letter to have

Letter information
change from SRC
form DB
4.0 Enhanced Interface Prototyping
4.1 Prototyping Requirements
We focus on an approach to simulation and

debugging of formal software specifications for control
systems called specification-based prototyping. Within the
context of specification execution and simulation,
specification-based prototyping combines the advantages of
traditional formal specifications precision and analysis with
the advantages of rapid prototyping risk management and
early user involvement. The approach lets us refine a formal
and executable model of the system requirements
specification to a detailed model of the software
requirements specification. Throughout this refinement
process, the specification is used as an early prototype of
the proposed software. By using the specification as the
prototype, most of the problems that plague traditional code-

based prototyping disappear. First, the formal specification
will always be consistent with the behavior of the prototype
excluding real-time response and the specification is, by
definition, updated as the prototype evolves. Second, the
common problems associated with evolving the prototype
into a production system are largely eliminated. Finally, the
dynamic evaluation of the prototype can be augmented with
formal analysis. To enable specification-based prototyping,
we have developed the NIMBUS requirements engineering
environment. NIMBUS, among other things, allows an
engineer to dynamically evaluate an RSML-e
Requirements State Machine Language without events
specification while interacting with user input or text file
input scripts, RSML-e models of the components in the
embedding environment, software simulations of the
components, or the physical components themselves
hardware-in-the-loop simulation.
Software Requirements Specification
1.1 Goals and Objectives
Generally, the purchasing department’s goals are similar to

those of anyone who buys something: get the best possible
quality of all supplies, services and equipment at the lowest cost.
Most often, the purchasing department is that part of the
procurement section that handles the supply chain process. To
ensure quality and to prevent unethical practices, purchasing is
usually separate from receiving and accounts payable
Purchasing departments have changed over time. Historically,

they issued purchase orders for all supplies, services, equipment

and raw materials, but to save costs they began to put in place
"master" agreements for repetitive orders, and they streamlined
other routine tasks. This led to a larger role for purchasing
departments as strategic sourcing managers who are concerned
with purchasing large capital equipment, bidding processes and
negotiating with suppliers.
1.1 System Statement of Scope

Below are the different kinds of tests that the team will
take to ensure the quality of the software.
 Unit testing
 Netbeans IDE 7.3.1
 Ms Sql
 Integration Testing
- null
 Validation Testing
- null
 High-order Testing
-null
1.2 General Requirements


system.

and manage by the user all the buttons and the
functions are place according to a normal interface of
the system by its purpose to understand.

Procurement or Warehouse list all the attributes of
every tables and
 Training
The use or the member have also requested
throughout training for the entire user for the functions
and the use of the software.
1.2.2 Extends Enhancements
1.3 System Context

User will be using our software for their own purpose,
if the software are compatible and likes by the user or the
company. This leads to issues about future support for a
larger user base.
Transparency – all phases in the procurement process are

fair and accurately documented;

provided;
Efficiency and cost effectiveness – meeting the six

rights of supply; price, right time, right quantity, quality
services, delivery to the required places and from the most
cost effective source.
Minimum Hassle – Since our goal was to create a system

that people would actually incorporate into their existing Net
News system, our software had to be designed for ease of
integration. This is difficult given the large number of
platforms on which Net News runs and the many
configurations in which Net News systems come.
Accessibility – Users must be able to control who has

access to their opinions on articles of information. Some
users may only be willing to contribute information
anonymously, while others will want to put their names on
their opinions.
2.0 Usage Scenario
2.1 User Profiles
 Full Control (Administrator)
2.2 Use-Cases
3.0 Data Description
3.1.1 Data Objects and Dictionary

1. Supplier ID
2. Company Name
3. Contact Name
4. Contact Title
5. Address
6. City
7. Telephone Number
Categories
1. Category ID
2. Category Name
3. Description
4. Picture
Products
1. Product ID
2. Product Name
3. Supplier ID
4. Category ID
5. Quantity Per Unit
6. Unit Price
7.Unit In Stocks
Orders
1. Order ID
2. Product ID
3. Product Name
4. Costumer ID
5. Employee ID
6. Order Date
7. Required Date

Order Details
1. Order ID
2. Product ID
3. Unit Price
Items
1. Item ID
2. Item Name
3. Employee Name
4. Contact Title
2.2.2 Relationship
Supplier Products
Supplier ID Product ID
Order Details
Company Name Product Name
Order ID
Contact Name Supplier ID
Product ID
Contact Title Category ID
Unit Price
Address Quantity per Unit
City Unit Price
Region Unit in Stocks
Telephone Number Recorder Level

Orders
Order ID
Categories
Product ID
Category ID Costumers
Product Name
Category Name Costumer ID
Costumer ID
Description Company Name
Employee System
Procurement and Warehousing ID Page 80
Picture Contact Name
Order Date
Contact Title
Required Date
Employees
Employee ID
Last Name
2.3 Human Interface First Name
The proposal that we have of human interface Title

description is to show the record of system. If the user return from
the facility to insert a data from the database which uses java net
beans as front end the software uses ms SQL
The user logs into the database using his or her

username and password
The first screen that will be show up is

PROCUREMENT & WAREHOUSING MANAGEMENT and It
contains five buttons with several different option to choose from.
the user will choose a button to add a new facility into the database
can find an existing facility to print blank checklist for next
inspection. User can also choose button to print a blank staff report
or to go help menu. Or exit out the java net beans.
PROCUREMENT
Procurement History windows user will allow to generate a

new letter, checklist or report. It also allows users to view, or print
help and return to main menu button order Information window
allows user to fill in order information to entries such as Supplier ID
, Company Name , Contact Name ,Contact Title , Address, City ,
Region, Telephone Number also about Supplier or mailing the

Supplier. It also allows users to fill in any comments regarding
facility information, If the user searches for an existing order and
order cannot be found, the user will be shown order information
such as no match window that will have search again. Add new
facility help or return to main menu options.

activities.

can also access the file and return to the procurement history
screen Search for an existing facility window enables user to
search for a facility that you believe has already been entered into
database. You can search by Company Name, Address, City,
Region, Supplier ID, or any combination of the five. If at least one of
your search criteria is Company Name or Company City and the
exact Company Name is not found, a list of close matches will be
displayed. If one of the close matches is the facility that you are
searching for, if none of the close matches are the facility that you
are looking for, you can either search again or add a new facility.
You will be taken to the procurement history screen and information
about that facility displayed.

procurement history screen

WAREHOUSING
Warehousing History windows user will allow to generate a

new letter, checklist or report. It also allows users to view, or print

information to entries such as Product ID ,Product Name , Supplier
ID , Category ID ,Telephone Number also about Supplier or mailing
the Supplier. It also allows users to fill in any comments regarding
facility information
If the user searches for an existing order and order cannot

be found, the user will be shown order information such as no
match window that will have search again. Add new facility help or
return to main menu options.

activities.

screen


warehousing history screen
From the maintenance for item the contractor allow to check

or to fix all bugs or error in the database of warehousing screen you
screen
6.0 Validation Criteria
1.2 Restrictions, Limitations and Constraints
 Time
Time is the most important thing to manage and priorities for
our project, because we only have 1 year to finish the entire
project. It is very useful to use watch for the time or calendar to
spend every phase of the software development project.
 User Skills
User skill may help us do our project easier and fast by their
knowledge
We will not spend more time by changing or adding their
demands for the interface and Designs.

Software Design Specification
1.0 Introduction

This system shall work properly, do the task properly
and fast. The system undergo testing process to be sure that
the system run properly and have a hardware compatibility ,
after the testing stage the developer shall review the system
to test the quality of the job works. First initiate all the data
in the system and test the limit and functions.
Developer test the system in different hardware to know if
the system run properly and easier to use. The testing
process may help the developers make and think a new
plan to compile with the error encounter to this existing
system
.
1.2 Statement of Scope
This document provides the Overview of the Material
Management Procurement and Warehousing. This manual
should be read first.
1.2.1 General Requirements


system.
and manage by the user all the buttons and the
functions are place according to a normal interface of
the system by its purpose to understand.
Procurement or Warehouse list all the attributes of
every tables and
 Training
The user or the member have also requested
throughout training for the entirefunctions of the
software.
1.3 System Context
User will be using our software for their own purpose, if the
software are compatible and likes by the user or the company.
This leads to issues about future support for a larger user base.
Transparency – all phases in the procurement process are fair

and accurately documented;

provided;
efficiency and cost effectiveness – meeting the six rights of

supply; price, right time, right quantity, quality services, delivery
to the required places and from the most cost effective source.
Minimum Hassle – Since our goal was to create a system that

people would actually incorporate into their existing Net News
system, our software had to be designed for ease of integration.
This is difficult given the large number of platforms on which Net
News runs and the many configurations in which Net News
systems come.
Accessibility – Users must be able to control who has access to

their opinions on articles of information. Some users may only be
willing to contribute information anonymously, while others will
want to put their names on their opinions.
Time
We only have one (1) semester to finish all the documentation for
the software and enhancements. We share different ideas and
strategies to the documentation, But we cannot reached the
exact time or date due to time constraints. One of the major
problems is resources and information about our project.

2.0 Data Design
2.1 Database Description
Procurement USER/
1 N 1 N Items &
ADMIN
& Warehousing Stocks
Facility N
Inspection
N N 1 1
1
Procure_ 1 N N
Items
Warehouse Inspection_
Inspection
Stocks detail
checklist
items
Entities Each record in the entity represents a (N)
Procurement & Warehousing User/Admin

User/Admin Staff/Manager
Items & Stocks User/Admin
Facility Inspection
Inspection Inspection
3.0 Architectural and Component-Level Design

3.1 Program Structure
3.1.1 Overall
Login
Main Screen
File Procurement Warehousing Maintenance Supplier Reports
Menu Items
The Following shows the architecture of the main menu

File
 Switch User
 Exit
Procurement
 Items
 Types of items
Warehousing
 Stocks
 Types of Items
Maintenance
 Add
 Edit
 Change
Supplier
 Name
 Types of Supplies
Reports
 Print Report
 Separate list of procure item and warehouse
stocks.
3.1.2 Create Inspection
Create -Procurement & Select Print Blank

Inspection Warehousing Checklists/ Checklists
-Schedule Inspection Procure
Procurement and Warehousing System Items/Stocks Page 90
3.1.3 During Inspection
D/L Check Lists Complete Checklists Print Check-lists

- Procure Items - Procure Items
- Stocks - Stocks
- -
3.1.4 Post-Inspection
Files Select Enter Preview Print

Results Checklists Data Letter
Revise
Letter
3.1.5 Approval
Approval View View Facility Approve

Letter Info Letter

Description for Components
3.2.1 Switch User
Major Forms(s) : from Login

Major Actions(s) :Login
The form frmLogin will appear. User enter their username in txtUserName and password
in txtPassword. Then click cmdOkay. User will be logged in if it is a valid username and
password pair. If user clicks cmdCancel on this form, application will end
confirmed they action.
3.2.2 Facility
Major Forms(s) : frmFacility, frmFacilityBrowse, and frmFaclitiy
Major Actions(s) : Browse, Add, Edit, Save
Browse
Object Name: cmdBrowse
To browse all Maintenance, user can click in the bomb button next to the
txtMaintenanceID field, frmMaintenanceBrowse will appear. User can highlight facility in
the grid, and then click cmdOkay. All the information on frmFacility will be filled in.
Add
Object Name: cmdAdd
To search for a facility, user can click on the multi-page document button next to the
txtFacilityID field. frmFacilitySearch will appear. User can highlight a facilty in the result
grid, the click memory cmdOkay. All the information on frmFacilty will be filled in.
Edit
Object Name: cmdEdit

The Edit button should be disabled unless no historical data have been found for the
facilty. The Delete and Save button should never be enabled at the same time.
Save
Object Name: cmdSave
The save button should be disabled unless the txtEdit field is filled in, and any there
have been changes made to any field on the frmMaintenance. When the save button is
click, new record will be generated if the Maintenance does not exist in the system,
otherwise, current record will be updated.
3.2.3 Create/Modify Inspection- Step 1
Major Forms(s) : frmInspection, frmInspectionBrowse, frmInspectionSearch
frmMaintenanceBrowse, nad frmMaintenanceSeacrh.
Major Actions : Create Inspection, Modify Inspection (Inspection Browse,

Inspection Search), Next Step and Add/Edit/Save
4.0 User Interface Design
5.0 Restriction, Limitations, and Constraints

 Time
Time is the most important thing to manage and priorities for
our project, because we only have 1 year to finish the entire
project. It is very useful to use watch for the time or calendar to
spend every phase of the software development project.
 User Skills

User skill may help us do our project easier and fast by their
knowledge. We will not spend more time by changing or adding
their demands for the interface and Designs.
6.0 Testing Issues
7.0 Appendices
Test Specification
1.0 Introduction
Test Specification discuss if the develop system is tested in
the in work place given by the user and to know the system
limits, and what is the problem may be occur when using it.
This system shall work properly, do the task properly
and past. The system under go to a testing to test the
system run proper and to trace if the system may occur
error, after the testing stage the developer shall review the
system to test the quality of the job works. First initiate all
the data in the system and test the limit of the flow.
Developer test the system in different hardware to know if
the system run proper and to know what error may
encounter if the hardware was change. The testing process
may help the developers may give a plan to compile with the
error encounter when the system existed.
1.2 Statement of Scope
Below are the different kinds of tests that the team will
take to ensure the quality of the software.

 Unit testing
 Netbeans IDE 7.3.1
 Ms Sql
 Integration Testing
- null
 Validation Testing
- null
 High-order Testing
-null
2.0 Testing Plan

We assure that the system that develops was error free and
to make sure that the system is working properly. We do different
process of testing in developing of system. Below are the testing
procedure and strategy and timing schedule of the test to be
carried out.
2.1 Software (SCIs) to be tested
2.1.1 Interfaces
The test carried on describe below.
Login Window
We use different names in log in system, so the log in
system will be test. We also test the entire button in the log
in process.

Design Window
We have different menus in this window. File,
Procurement, Warehousing, Maintenance, Supplier, and
Reports,and each menu have their different tpes of categories,
this are the button menus that the software have.
File
When file button is clicked by user the interface of the
system shows the button switch user and the exit button.
Reports
When Reports button is clicked by user it show the
reports like how many items used daily or weekly and if they
reach the critical level.
List of Item
When List of item is clicked by user ait show all the
stocked and items that we have.
Maintenance
When Maintenance button is clicked by user it shows
the comment how to fix the system in minor error and how to
use the system.
Help
When Help button is clicked by user it show contents
and about the system.
2.2 Testing Strategy

This describe the following strategic testing that we have been
do, each of us do different methods of test to our product.
2.2.1 Unit Testing

In unit test we test the separate way of software. We test the
component of the software individually. We test the passing of
data logically because of 10% done of our system. We test all
components can function properly without any error.
2.2.2 Integration Testing

In this methods we test run our system into their workplace so
that we know what problem may be occurred of our system into
their workplace. We make sure that there is no error in our
system to run it properly. We ensure that all of data save
correctly and there is no loss of data or data redundancy and the
entire button is functional
2.2.3 Validation Testing

In this method we test the interaction between the users. We
obligate the entire user to look for the software requirements if
they can't understand a simple process. We use trial and error to
if the system work properly and save data in the database to
know if it can handle large data safely.
2.2.4 High- order Testing

This method show different types of testing that make sure the
system is useable.
 Recovery Testing

The system we build is can retrieve small lost data, because
recovery of data is not included to our system but we can ensure
the storing of data.
 Security Testing
In this method we sure the security of system because of high
security code that are system have.
 Stress Testing
Its focus on the software ability in current transaction when it
comes on the system shutdown or failure, this testing is to avoid
it happen
 Performance Testing
In this method we test is system up to her limit to determine the
compliance in the given task in her higher performance.
2.3 Testing Resources and Staffing

It may use different resource to assure the software testing
2.4 Test Record Keeping

The data will be test if it can hold huge data
2.5 Testing Tolls and Environment
Developers may use available resources for the
development of the software.
2.6 Test Schedule

Below is the schedule of Test.
Project Test Plan
The project test plan is to show if the project was succeed
System Testing
Develop system was under go in many ways of test to
ensure the system working
Generate Testing Report
Develop system can generate report in daily weekly and
monthly
3.0 Test Procedure

In this we give the detail of our system procedure. First we
test all the system function and button to know the error may
encounter in using the system, and we test the hardware
specification if our system works in different hardware and how
large data can store in our database.
3.2.1 Unit Testing

Unit testing is to know if the software may run into different
operating system and hardware specification
3.2.2 Integration Testing

The develop system was test in integration to know if the
system can process with some other subsystem
3.2.3 Validation Testing

Validating the software is the process were the software is ready
to publish
3.2.4 High- order Testing

High order testing are the combination of some methods
 Recovery Testing
The system we build is can retrieve small lost data, because
recovery of data is not included to our system but we can ensure
the storing of data.
 Security Testing
In this method we sure the security of system because of high
security code that are system have.
 Stress Testing
Its focus on the software ability in current transaction when it
comes on the system shutdown or failure, this testing is to avoid
it happen
 Performance Testing
In this method we test is system up to her limit to determine the
compliance in the given task in her higher performance.
3.3 Testing Resources and Staffing
The first personnel who conduct the testing process is the

programmer and the nest is the System Analyst and the Project
Manager to check if the software is comply with the needs of the
users
3.4 Test Record Keeping and Log

Ps1finaldoocuments Final Na Po To2

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

Ps1finaldoocuments Final Na Po To2

Uploaded by

Copyright:

Available Formats

Project Charter

Project Name: Material Management (Procurement and Warehousing)

Bentor, John Roland H.

Tamesis, Kristian Ian T.

Laurio, John Stephen A.

Dayag, Mhark John Paul E.

Procurement and Warehousing System Page 1

 Accuracy - exact quantity of items

 The inventory process of other restaurant is just a manual

Procurement and Warehousing System Page 2

1.4 Stakeholders and Clients

MATERIAL MANAGEMENT (PROCUREMENT AND WAREHOUSING)

PROCUREMENT SUPPLIER WAREHOUSING

Procurement and Warehousing System Page 3

Project deliverables Work Products/Description

Project deliverables Work Products/Description

Procurement and Warehousing System Page 4

Project deliverables Work Products/Description

Project deliverables Work Products/Description

2.3 Out of Scope

 The storing of goods

Procurement and Warehousing System Page 5

3.2 Project Timeline

ID TASK NAME START FINISH DURATION

Procurement and Warehousing System Page 6

3.2 Success Criteria

3.3 Issues and Policy Implications

Procurement and Warehousing System Page 7

Compliance H H Make it before the

A. Corrupted files- unable to open the files

3.5 Options Analysis

3.6 Technical Features

Procurement and Warehousing System Page 8

ROLE NAMES & CONTACT RESPONSIBILITIES TIME

Procurement and Warehousing System Page 9

Advisors and  Participate in

Budget Item: Description: Budget Cost:

One-Time item 1: Description:

Total One-Time Costs

Ongoing item 1: Description:

Total Ongoing Costs

Procurement and Warehousing System Page 10

2.1 Foreign studies

Bob Evans Restaurant

Bob Evans Farms, Inc. is a food service, processing, and

Procurement and Warehousing System Page 11

Procurement and Warehousing System Page 12

Portillo's, which is the main entity within The Portillo

Procurement and Warehousing System Page 13

Spangles is a family-owned fast food chain based in Wichita,

Procurement and Warehousing System Page 14

Fatburger was founded by Lovie Yancey in Los Angeles,

Procurement and Warehousing System Page 15

Perkins Restaurant and Bakery

The Perkins chain was established in 1958, when Matt and

Procurement and Warehousing System Page 16

Procurement and Warehousing System Page 17

Procurement and Warehousing System Page 18

Congo Grille is a chain of family restaurants in the

Procurement and Warehousing System Page 19

Gerry’s Grill is a group of restaurants based in the

Procurement and Warehousing System Page 20