Ps 2 Revise

Chapter 1
1.0 Project Background

Introduction
Nowadays there a lot of business using a highly technology as an
integrated software. But as a developer the proponents propose a
computerized system that can easily to use for those users and to ease their
works. Procurement its a bidding process such as market research, and
searching through internet that the merchants or observers will see our
advertisement through web-based system and they are competing their
products that has a good quality of the right cost and right price. The purpose
in procurement logistics might be contradictory for maximizing efficiency by
concentrating on core competences, outsourcing while maintaining the
autonomy of the company, or minimizing procurement costs while maximizing
security within the supply process. The proponents provide clients
comprehensive procurement solutions for their complex problems. As
proponents it will give them the advantage with proposal support, preparation
of request for proposal packages and negotiation. An advanced of
purchasing system and stock control program which brings into the
organization a professionally managed warehousing and purchasing system
among integrated defined warehouses and related departments through a
systematic process. Warehousing and Procurement integrates powerful
security features rendering your vital business information highly protected.
An advanced security simplifies processed for configuring and managing user
security, and maintaining high levels of protection for the company system. At
the core of the system is a series of fully integrated reports delivering Supply
its vital information which are successful pre-requisites to operating their
businesses and decision- making when it approaches the preparation of
tenders and requests. Thus, through its wide variety of its applications
varying from documentation, support, the system becomes a must for
businesses to grow.
Service Management System (MM Procurement and Warehousing)
Page1
1.1 Problem/Opportunity Description

In Procurement and Warehousing it shows here the strategic way on how to
prevent the failure in every transaction in the business matters. And here the
problems include:
Inaccurate information in the system

-This matters of problem in the business environment are usually seen
in the persons in charge to do his/her job well for the company, to give the
complete details of information into the system for the good feed in the
company.
Delays in delivery of supplies

-This is where the transaction delayed during dispatching of equipment.
In this transaction you are responsible to deliver on time to the clients so
that, this problem must be avoided in delivery of supply.
Orders for out-of-stock items are automatically back-ordered and filled

when equipment are re-supplied.
-This transaction the existing system must avoid on the critical level of
stock the process might be slow.
Difficulty locating items as they are moved within the warehouse

-this difficulty of locating items within the warehouse that usually are not
unorganized putting the materials into the file cabinet/computer and this
might be cause a problem in the company.
Equipment losses or damage

-losses or damages of equipment because they did not checked very
well before they deliver the materials through in different companies. To
Page2
prevent this matters should check it the quality of product and to carry
carefully to those heavy things that should be avoided.
1.2 Benefits
In this section this is where the proponents take an advantage to their clients
have a good benefits. The clients will be the first thing that can take this
advantage of the systematic and well-presented way in efficiency of process.
Has a good features of the system
It is user-friendly
To efficient the transaction of purchasing equipment
To ease in inventory control
it can notify the critical level of stock
Web-based tracking queries and status reports allow users to check the
current status of their warehouse order
Reduction of paperwork
Flexible and integrated Items and Purchases cost calculation using Average.
Immediately report on shortage, late delivery and defective parts
Manage supplier corrective actions
Collaborate with suppliers to solve problems faster.
Control cost and make better products the first time
1.3 Goals
The purpose of proponents a proposed system is to lessen the work load
such as writing the document, save it to the cabinet and find it manually. And it is
developing to ease staff and clients with facilities of computerized timely useful
information on how best to enhance performance and to ease the staff save time
and resource. Procurement aims for managing and standardizing the
procurement process within an accurate data and organizing the purchase
sources and procedure through clear presented standardized order forms within
concrete and measurable data. It meets the company unique and changing
Page3
business needs with rich reporting and analysis capabilities, customizable

transactions flow, and the flexibility, security features, and control needed to
maximize operational efficiency. And what makes this system efficient is its
capacity of holding inventory, its instant access to warehouse, and it integrates
all warehouses together. The system has a variety of functions by which items
are organized and classified in an accurate well-presented way. Warehousing
and Procurement will coordinates procedures of warehouse varying from
requesting to receiving items through standard purchase and request forms.
Designed for rapid time to benefit and low cost of ownership, Warehousing and
procurement it helps the company unify its business processes for increased
productivity and efficiency, gain better visibility and control over decision driving
information; and help insure your business is highly valued and well regarded.
The system also provides authorized users with concrete, measurable, and
reliable date to take actions about different transactions taking place.
1.4 Stakeholders and Clients

Proponents
It will have the opportunity to enhance the Material management
Procurement and Warehousing of the company by undertaking a project
study and produce an up-to-date information system that will surely help
the Procurement and Warehousing department and able to answers the
company problems.
Staff
It will surely gather information about the Material management
Procurement and Warehousing.
Company
Page4
The company who will benefits the most when the results of the project
study will be implemented. Proponent thanks for allowing to know the
process and details of the company and we are appreciate for giving the
opportunity to do our project.
2.0 Project Scope

In this section this is where the scope of project development system that
proponents document the boundaries of Materials Management Procurement
and Warehousing (MMPW).
Procurement
-Procurement is able to support the complete cycle of project progress, bid
invitation, purchase order, and acceptance of logistics services, as well as
the invoice verification process.
Bidding
Supplier
Estimation of cost and price of the equipment
Request purchase order
Warehousing
-Warehousing is a monitoring process of a level stock of the materials and
inventory control that can determine the materials has a damage or loss.
Inventory control
Checking the items if it has been losses or damage
Delivery equipment
Stock monitoring
Receiving equipment
Disposal equipment
Page5
2.1 Objectives
In this section this is where the proponent objectives as an integrated
software that can easily to use and the comprehensive system.
2.1.1 Service Management System-(MMPW Procurement and
Bidding)
Bidding
Bidder/Suppliers
Supplier info
company name
company address
contact number
Purchasing
quantity of product
price&cost
Page6
Warehouse
Inventory control
Receiving
invoice
checking the items
notification
monitoring
Figure 2.1.1 it shows here the procurement and warehousing

objectives.
Page7
2.1.2 Service Management System-(Materials Management Procurement and

Warehousing [MMPW])
Procurement and Warehousing
Bidding
supplier
purchasing order
approval
Warehouse
stock monitoring
inventory control
receiving
invoice
Web-based system
update info
notification
deactivate/ activate
help
mobile apps
Figure 2.1.2 it shows the procurement and warehousing objectives for the
development system
Page8
2.1.3 (WBS) concerned with defining and controlling not included in the project.
SERVICE MANAGEMENT SYSTEM
MM-Procurement&Warehousing
System
Planning
Develop the
project
System
Analysis
Gathered
Information about
the system
Project
Scope&Out of
Scope
Determine
the problem
Determine
the business
flow
Analyze the
business flow
Bidding
Warehouse
flow
Procurement
flow
Stock Monitoring
level
Review the
related
study&system
Research local
and foreign
studies
Construct
matrix of
related studies
System Design
Interface
Design
System
Implementation
System
Maintenance&Operation
Request
purchase
report
Technical
problem
User-friendly
Has a good
features of
the system
Graphical
User
Interface
Bidding
report
Inventory
control
Print
Debugging
Fixing
errors
Troubleshooting
Add Item
Update
Information
Notification
Draft of
Chapter 3
Figure 2.1.3 it show in the above of WBS Word Breakdown Structure the plan
for the project development system
Page9
2.2 Project Deliverables

Objectives 1- Procurement-Bidding
Project Deliverables
Work Products/Description
This is where the company finds bidders that

Bidding
will give the right price, the right cost and

good quality of products from suppliers. It will
have a negotiation between supplier and
company for the supply of materials.
This is where the supplier supply needs of
Suppliers
the company and it must have a good quality

of services during the delivery of
equipment/materials that should not delivery
delay.
In this transaction that will easily and efficient
Request Purchase Order
in purchase order of equipment from the

company through supplier.
This process where staffs add other

equipment/materials into the system that very
Add item
efficient and will generate during encoding

the equipment.
Page10
Objectives 2- Warehousing-Inventory Control
Project Deliverable
Project Deliverable
Inventory Control
In inventory
this section,
this this
is where
control
processthe
thatsuppliers
usually
Update supplier
updating
information
because of it the
is
encounter their
of losses
or damage
Ob
information
important
to the company
have theinventory
details
equipment/materials
and during
jec
information
frombe
the
supplier. It is part of your
control it should
correctly.
tiv
obligation as a part of the companys supplier.
es
3-
Stock Monitoring
In warehousing management, the
Inf
staff/employee should monitor the level of stock
or
of the equipment that will be avoided in critical
ma
level in storage like overstocking of equipment
tio
but this system it will have a notification in the
critical level of stock.
up
dat
e
Receiving and
The receiving and checking item, this is very
Checking Item
significant in a business environment especially

the equipment/materials that should be aware to
receive and check during delivery of materials
shall be correctly and strictly from the damage
materials.
Page11
In this section, this is where the company needs

to update their facilities and also the quantity of
Companys update
their products.
User is also need to update their information

Users update
because it is important mostly from the bachelor

to married. User give the details of his/her
information because it was a policy of the
company to give the information in the human
2.3
resource department.
Ou
t of
Sc
op
e
In this section this is where the out of scope that may not related to the project
development system.
Salary/ payroll of the employees
Contract management
3.0 Project Plan

3.1 Approach and Methodology
Strategy General Features of
the strategy are
described,
accompanied by Illustrative examples from existing operations. But

proponents also used a Software Development Life Cycle also known as
SDLC. In this procedure that will easily to discuss in each members of the
group to develop this project.
System Planning- this is where the proponents scheme for the
development system and using step this will be easily to identify the
Page12
problem and all the details need of the developer to determine the process
of the system develop especially in the business environment.
System Analysis-this where the proponents analyze of the problem
and they need to visualized all the details they have gathered through the
interviews and survey from the company. So that, proponents need a little
more to think or analyze on how to avoid failure during the procedure of
the developing project.
System Design- in designing process this is where you can design
in your own idea for the designing in the development system like the
interfaces of your system and the graphical user interface.
System Implementation- this is where you can implement a system

that was already navigating in the process and has an integrated software
to other department in the company. The system implement is a perfect
software that you already created and it was tested the flow of system and
sub-system.
System Maintenance and Operation- in this section, this is where
you can a system has implemented but you have to do this first a debug
and fix the errors from the defecting problems of your created system.
Page13
3.2 Project Timeline
Page14
Page15
Page16
Page17
3.3 Success Criteria
The system can save & store large number of files.
The systems process becomes fast because the GUI is easy to

understand.
The system can lessen the time needed to finish transaction.

Theres more time saved.
The system can view the files that you want to see. Its done to
prevent printing from time to time.
The system prevents errors and erasures.
The system easily to retrieve files
The system shall notify the overstocking of equipment
3.4 Issues and Policy Implications

In this section this is where the proponents discuss the issues and policy
of the company the will be prohibited to those developer and company violent the
rules and regulation in both parties under by government laws.
Recruitment and Deployment of the employee
Payroll of the employees
Property Monitoring.
3.5 Risk Management Plan
Risk Factor
Financial Risk
Probability
Impact
(H-M-L)
(H-M-L)
Risk Management Action
There is not enough money

to save it
Page18
Strategic Risk
No Cooperation of every
members
System failures and human
Operational
System Problem
error
Encountered errors/defect
during the process of
development
Implementation
Technical problem
Determine the scope
Risk
Compliance Risk
3.6 Service Transition
The system will give a good quality of service to the clients
It is easily to access to the staff of the company
The system shall ease the facilities work unlike before that it was a
manual process.
The system can determine the critical level of the stock of equipment
The system can easily identify during inventory of the equipment if it have
loss or damage.
The system shall notify on the storage of materials/equipment
Help button will give detail instruction to the users
Page19
In every transaction of purchasing order will efficient
3.7 Option Analysis

In this section this is where the proponents had another option used the other
language and database for the project development.
Java Netbeans IDE 7.3 and 8.0
Java Eclipse
MS SQL
1.0 Technical Features
Front End: Graphical User Interface
Java Netbeans IDE 8.0 used for the development of project and it is
very useful using this programming language.
Back End data
MySQLyog xammpp server is the back end of the system. All data
input on the GUI by the users of the java Netbeans IDE 8.0.
Internal users
Page20
5.0 Project Organization and Staffing

Role
Name & Contact Information
Project Manager
System Analyst
Business Analyst
Magtangob, Caroline F.
Tenorio, Mark Anthony T.
Lastimosa, Mark joel E.
responsibilities
time
Manages the team

Project Execution
Planning Strategy
Project Initiation
Project Control
Risk Management
Resolving the issues
Budget the project
Scheduling of tasks
Leader of the team
Handling of business
Rules
System Design
Technology Analysis
Document Framework
Business
Requirements
Analyze business
process
Business plans
Monitoring
Translate Business
process
Requirement
management
Requirement Analyst
Analyze Requirement
Communicate w/
clients
Analyze the audience

Page21
Documentation
Specialist
Lead Programmer
Cabug-os, Florita C.
Ceno, Elvin S.
Documenting the
process
Craft the right
message
Distil the message into
effective documents
Release the
documentation
Evaluate the results
System Coding
Handling System
Software
Program Development
Perform System
Analysis
Train subordinates in
programming
Develops
programming methods
Correct errors on the
system coding
Page22
6.0 Project Budget

Budget item
Description
Budget cost
The book that the proponents

Project Study Module
use as a guide in creating
P1,300.00
their documentation.
The proponents contributed

Transportation
P100.00
p20.00 each for searching

available Service
Management / Agency that
can be asked for an interview.
Total One-Time Cost P1,400.00

On-Going Cost
The group contributes P10.00
each day individually that
Group Savings
serves as a group budget
P300.00 per week
where they can use it on

other expenses that the group
may pay encounter in future.
Each member of the
Printing
proponents contributes
P20.00
money.
Page23
Chapter 2 Review Related Literature
2.0 Introduction
The purpose of this research is to analyze materials management in
construction. One issue is Information Technology. An efficient IT systems
results in a competitive advantage, rapid communication and lower cost.
Managing the flow of materials, information and associated engineering and
financial resources between suppliers, service providers and construction job site
is the most effective way. To aim of the procurement is to carry out activities
related to procurement in such a way that the goods and services so procured
are of the right quality, from the right source, are at the right cost and can be
delivered in the right quantities, to the right place, at the right time.
Materials management is a core process of projects with multiple modules from
the beginning of project information through reporting. Implementing the system
covers lost time, minimizes lost materials and will provide the most efficient
operation. Although there is general agreement on the critical role of innovation
in the procurement process, the strategy for implementing and achieving
beneficial innovation by choosing the most appropriate procurement mode and
accompanying terms has been the subject of much discussion among
practitioners, policy makers, researchers, and other project stakeholders.
Page24
Chapter 2
2.1 Foreign Studies
2.1.1SAP Warehouse Management System
Warehouse system is critical to businesses producing perishable

materials. Items must get to the customers at their peak.
Seamless is a word that would best describe a good warehousing system. Since
there are costs associated with prolonged storage for example, spoilage or
diminished quality as well as delayed delivery, the objective is to receive the
goods, store them, and ship them off at the lowest cost possible. Aside from the
costs, customers will also be kept satisfied as they receive their orders at
precisely the date agreed upon, with the products in top condition as expected.
Only a good warehousing system will guarantee these results.
To do this, practically every batch of product that comes in has to be logged and
watched closely. And since such effort is not humanly possible, this is where the
benefits of a warehouse management system come into play. A warehouse
management system or WMS as it is also known, tracks and monitors the
progress of products through the warehouse, from the time they are received to
the time they are moved out for shipping. It involves the physical infrastructure
(the warehouse itself), the tracking systems, and the communication and data
sharing between product stations.
There are also multiple levels of warehouses. There may be a central
warehouse, a regional warehouse and retail warehouse. In each of these, a
warehouse inventory system has to be in place so that every single product, or
batch of products, arrives, stays and leaves for just the right amount of time.
Having established the advantages and the benefits of a warehouse
management system, we go now to the functionality of such systems.
First, there is a standard receiving process that handles a shipment when it
arrives. This can be individualized to each warehouse or product type.
Page25
Then, there is the receipt of stock and returns into a warehouse facility. There are
costs to storing unnecessary parts and products; hence, there is a optimum
amount of product that should be in storage at any given time.
The logical representation of the physical storage facility is also important. For
example, some products may be sold more often than other types. These can be
grouped together or moved near the entrance to speed up picking, packing, ad
shipping to customers.
There must be a link to order processing and logistics management.
Finally, there must be something which tracks where products are stocked, or
which suppliers they come from, or for how long they are stored.
Warehouse management alone cannot achieve automation. It must be used in
combination with business processes for best results.
Sometimes, a warehouse management system is a stand-alone system.
In other times, it is but a module in an enterprise resource planning system is a
supply chain execution suite.
The warehouse management system will really all depend on the size and
sophistication or complexity of the organization. In its most simple, it is like a
handwritten list that is updated periodically, or as soon as new products are
received or shipped out. Sometimes, simple spreadsheets using Microsoft Excel
or Access are enough; sometimes, purpose-built software programs are best.
Indeed, technology has done much to enable managers to more effectively track
the flow of goods in and out of the warehouse. A warehouse inventory system
has immediate and very visible results. Those warehouse managers and
business decision makers who were quick to decide on adopting a warehouse
inventory system observed improvements in their business than those who were
hesitant to modernize. Inventory is of just a bunch of your products sitting in one
corner of your warehouse. It is key to performance, efficiency and customer
satisfaction.
If on the other hand one is hesitant or if one outright refuses to adopt a
warehouse management system, be prepared to observe losses in revenue and
productivity as well as foregone income. This is because ultimately, too much or
too little is not good. What is good is just right, just in time.
Indeed it is not good for the business of all the goods are at the back of the store
and the shelves are empty. Nobody would know that the products are there.
Page26
Similarly, it is also not good if everything is on the shelves and nothing is stocked
anymore.
Another bad warehouse practice is having an inadequate amount of products
such that clients expectations are not met. On the other hand, having too much
stock also causes a problems as they take up space and the products may lose
their optimum quality.
Optimization is the operative word, be it in picking, packing, and shipping. A
warehouse system software also integrates information from front-of-house
inventory and sales (whats sitting on the shelves) to back-of-house inventory
and sales (warehouses, in stock that are shipped directly to customers). One will
tell the other when that it is time to replenish or not yet.
Finally, a good warehouse management system must be user friendly in that the
employees handling it would be able to be familiar with the system in no time.
Businesses have everything to gain from having in place a warehouse
management system, in a level of sophistication proportionate to the needs of the
company.
SAP Warehouse Management System
Computer support for the organization and management of warehouses has
become imperative for timely, effective processing of logistic requirements within
a company. The SAP Warehouse Management (WM) application provides
flexible, automated support to assist you in processing all goods movements and
in maintaining current stock inventories in your warehousing complex.
Benefits:
Reduce total cost of ownership & receive quick return on investment

Speed up supply chain & customer service
Increase overall transparency & user-friendliness
Optimization of warehouse activities
Functionalities:
Create purchase order

Create sales order
Create deliveries
Work load estimate
Plan picking wave
Create transfer order
Page27
Delivery monitor
Create task
Confirm task via radio frequency
TRM monitor
Carry out packing
Weigh parcel with scale
Provider tracking number
Labeling
Load goods
Issue goods
http://www.fasttrackph.com/warehouse-management-systemphilippines/?gclid=CIT7mv-T9MACFdcTvQodK1oAIg
2.1.2 Warehouse Management System

From inventory control, shipping and receiving, to order fulfillment,
a Warehouse Management System (WMS) is vital to improving the efficiency of
a company's warehouse operations. Barcoding, Inc., offers warehouse
management software packages that can be customized to fit the needs of
companies of any size. By combining a warehouse management system with a
wireless network, mobile computers, radio frequency identification (RFID)
technology, and voice picking applications, Barcoding can help fully extend your
enterprise to the mobile worker, while increasing operational efficiencies and
enhancing your customer service.
Benefits of a Warehouse Management System
A comprehensive warehouse management system helps streamline multiple functions of your

enterprise:
Page28
Receiving Gain insights into shipments that have been delivered, but that are not yet at
their final location. Make sure items at low stock levels are staged and put away first,
reducing the impact of out-of-stocks and inefficient fulfillment processes.
Put-Away Know the location of all inventory on your shelves. Route your workers to the
right location, set up their picks in the proper order to minimize travel time, and increase the
number of orders they can pick each day.
Picking Improve error-proofing and productivity in the picking process. Workers receive
their picks on a mobile device that routes them to the proper location. Scanning items when
you pick them verifies that the right item at the right quantity is picked.
Packing Ensure the accuracy of each order that is picked and reduce material costs by
determining the right sized shipping carton.
Shipping See that each order is properly packaged and shipped to the right destination
and delivered on the right date.
The ROI in a Warehouse Management System

Although installing a full-scale warehouse management system can be a costly investment, you
will quickly recognize its value. After a warehouse management system has been up and running
for only a few months, many of our customers say that they cannot envision their operations
without it. From achieving real-time visibility into inventory and orders, to decreasing the time it
takes to invoice and receive customer payments, a warehouse management system package
extends mobility to each worker in your warehouse and prepares you to scale your business.
Problems Solved with a Warehouse Management System
Relying on paper trails and manual data entry to manage your warehouse compromises worker
productivity and inventory accuracy. Once received via printer, orders are picked, packed and
shipped, with a paper trail tracking every step of the process. That information is then manually
entered it into the system and filed. Should a discrepancy appear in a customer's order or invoice,
pinpointing the problem requires cross referencing the data in both the system and file cabinets.
As a result, your organization can avoid experiencing:
Delayed access to information in the system if has been entered days, or weeks late.
Inaccurate information in the system
Mis-shipments
Late invoices
Difficulty locating items as they are moved within the warehouse
http://www.barcoding.com/trackingsoftware/barcode_warehouse_wms.shtml
Page29
2.1.3 Procurement and Warehouse Module

An advanced electronic purchasing system and stock control program
which brings into the organization a professionally managed warehousing
and purchasing system among integrated defined warehouses and related
departments
through
systematic
process.
Warehousing
and
Procurement Module integrates powerful security features rendering your

vital business information highly protected. Advanced security simplifies
processed for configuring and managing user security, and maintaining
high levels of protection for the healthcare center's system.
At the core of the system is a series of fully integrated reports
delivering both Medical Supply and Financial departments vital information
which are successful prerequisites to operating their businesses and
decision- making when it approaches the preparation of tenders and
requests, communicated with both Arabic and English Languages
available in specified fields. Thus, through its wide variety of its
applications varying from documentation, online forum and support, the
system becomes a must for businesses to grow.
Objectives:
What makes this system efficient is its capacity of holding
inventory, its instant access to warehouse, and it integrates all
warehouses together. The system has a variety of functions by which
items are organized and classified in an accurate well- presented way.
Page30
Warehousing and Procurement Module coordinates procedures of

warehouse varying from requesting to receiving items through standard
purchase and request forms. Designed for rapid time to benefit and low
cost of ownership, Warehousing and procurement Module helps the
healthcare center unify its business processes for increased productivity
and efficiency; gain better visibility and control over decision driving
information; and help insure your business is highly valued and well
regarded. The system also provides authorized users with concrete,
measurable, and reliable date to take actions about different transactions
taking place.
Functionalities:
A. Features
Multi-Warehouses
Multi-Currency
Dual Currency
Item Detail Categorizations by Brand, Types, Models and Families
Barcode Management with automatic generation and
Printing
Lots and Expiry date management
Serial numbers tracking and management
Size and Colors management
User defined unit of measurement tables
Various price definition scenarios
Flexible and integrated Items and Purchases cost calculation
using Average, FIFO or LIFO.
Several units of measurement for the same item code
User defined transaction workflow with extensive
Parameters
Data Collector integration for Inventory adjustment and easy
physical stock count
Automatic VAT definition by item, customer or
Page31
Supplier
Item substitution list while inputting transactions
Batch or online posting to the Accounting module
Ability to recalculate your inventory cost at any time
Automatic minimum quantity reminder list
Automatic landed cost calculation by importing direct expenses
from the accounting module
B. Reports
Detailed Purchase orders list by multiple selections of suppliers,

dates, group of items, locations ..
Purchase Orders status report
Inventory listing by criteria Warehouse, Date,

Supplier, Item group, Item, Etc.
Re-ordering suggestion list based on defined specification for

each item or group of items
Complete History of any item since creation date
Valorized inventory list
Inventory Evaluation list
Inventory Movement report
Stock aging report
Detailed listing of item transactions
Detailed combination and stock tracking from quotation, sales

orders, reservations, invoices, deliveries, consignments, goods
returns, transfers between warehouses or locations, inventory
adjustments or sampling, physical stock variances, assemblies
and productions
Multiple layouts of Sales Statistics by customer, supplier, items,

categories, locations and periods
Price list
Items profitability report
VAT Report
Page32
Monthly statistics
Price & cost comparisons
Warehousing Module Description:

With the Warehousing System, the healthcare center manages its
inventory in different locations, warehouses, transfer between
warehouses, point-of-sale and consignment becomes simple. The
healthcare center is addressed to online information about its inventory
with all its status and historical information.
Through this module, the existing stock is managed and organized
in the way the user receives, records, stores, arranges, and re-orders the
stock. The set up program operates in respect to the governmental
regulations of warehousing and purchasing procedures. At the same time
any reengineering or adjustment applications is flexible to insert by
authorized users. The warehouses of the healthcare center are
interrelated and share integrated services whereby users communicate
through the module with support to bilingually modes. The authorized user
can create and record what is taking place within and between the
healthcare center warehouses. It is time saving by which both medical
supply and financial department can access warehouse data instantly as
all items are recorded in an organized accurate cost accounting manner in
terms of maximum efficiency. Through this system the healthcare center
can detect whether it is confronting a shortage or surplus in its
warehouses as it functions as a cycle count and a monitoring tool to alert
storekeepers about any lack. The system also supports tracking the
healthcare center's assets and is available for all the healthcare center's
users to view the records. The system holds a large capacity of fitting and
defining unlimited numbers of warehouses. Warehousing Module defines
unlimited number of items which these last pour into several classifications
based on their types and nature. The item number is then submitted with a
code number. Items definition, having a specialized scale unit, involves
Page33
criteria on which the healthcare center and includes item location in

warehouse, quantity, stock unit and other related informationbased criteria.
Item quantities are transferable within and among warehouses

without altering the original data of the transferred items. Adding items is
also one aspect by which the system supports.
The system gives the authorized user feasibility in assigning a

storekeeper for each warehouse to operate the overall warehouse
responsibilities of managing warehousing operations and inserting
received items manually. Storekeeper receives items based on a
purchase order. The system also provides a standard purchase order by
which the storekeeper receives items through. When receiving items, the
system provides their quantity with a batch number and a calendar
covering their expiry date and alert reminder of quantity issue. Whether
items are depreciated or suspended, decreased in number or returned,
the system supports target actions. It provides functions of ceasing
transactions for suspended items, handles returned and defective stock
according to rules and regulations established.
The system provides order entry standard form that can be used by
authorized users. The data is directly forwarded to the Inventory Control
division to issue the request.
Page34
Procurement Module
Procurement Module is an electronic based system that deals with

all transactions of procurement process managed by the variety of the
system functions and tools to help healthcare centers make faster
decisions.
Objective
Procurement Module's tools aims for managing and standardizing
the procurement process within an accurate data and organizing the
purchase sources and procedure through clear presented standardized
order forms within concrete and measurable data. It meets the healthcare
center unique and changing business needs with rich reporting and
analysis capabilities, customizable transactions flow, and the flexibility,
security features, and control needed to maximize operational efficiency.
Procurement Module Description:
The system has a converter that converts types of numbers to

words up to hundreds of millions and two digits to the right of the decimal
point based on English and Arabic Language rules. The system handles
efficiently multinational transactions with comprehensive multicurrency
control. The local currency of the country and international currencies but
later to be switched when dealt with internally. The system operates upon
Page35
two purchase sources; one through public tender and the other is direct
purchase.
The system supports the types with concrete precise information
which includes unlimited number of defined suppliers, their contact and
business information based upon the 5 types of items classification or
individual by which the authorized user selects.
Once selected, the authorized user makes us of the standard

supplier email which undergoes criteria such as the name of the
tender/purchase order, or any additional information needed to convey the
purpose of the invitation.
http://www.ogersystems.com/pdf/Warehousing_Procurement_Document.pdf
2.1.4ACCPAC Warehouse Management System

ACCPAC Warehouse Management System (WMS) is a powerful,
feature-rich solution for automating the materials-handling processes of
retailers, manufacturers, distributed and third-party logistics providers. By
integrating advanced radio-frequency (RF) and bar-coding technologies
with
core
warehousing
functionality,
ACCPAC
WMS
provides
Comprehensive fulfillment center and warehouse management solutions

that include Order management, receiving, stocking, replenishment,
picking and other related Warehouse tasks. ACCPAC WMS is a complete
warehouse management solution specifically designed to Increase
Page36
inventory-handling accuracy, improve allocation of human resources

within the Warehouse and reduce carrying costs associated with obsolete
and slow-moving stock. With ACCPAC WMS, you can efficiently pick,
pack and ship orders putting nearly 100 Percent picking and shipping
accuracy within your reach. ACCPAC WMS scales to accommodate the
varied demands of small to highly complex, high-volume distribution
Centers and works in conjunction with ACCPAC Advantage Series and
ACCPAC Pro Series. Additionally, ACCPAC WMS is specifically designed
to interface with industry-Standard shipping systems that enable an
automated picking, packing and shipping Solution. This unique and
seamless integration capability allows ACCPAC WMS to effectively
orchestrate the movement of personnel and inventory. As a result, multiple
orders can be picked in a single wave by one or multiple warehouse
pickers, saving time and money.
OBJECTIVES:
COMPLETE CONTROL
ACCPAC WMS utilizes RF and bar-coding technologies, creating a

powerful picking, packing and shipping warehouse Management solution.
ACCPAC WMS makes order fulfillment easy by allowing warehouse
managers to view which orders can be filled immediately. Equipped with
RF-based terminals, Warehouse personnel are given explicit directions for
picking every order such as quantity, location and other carton-specific
Page37
requirements. With ACCPAC WMS, youre in control, guiding warehouse

personnel to the right location, automatically generating shipping labels on
demand and indicating the right size box for the order. Whichever picking
style works for your warehouse wave, batch, simultaneous or sequential
zone ACCPAC WMS manages the process efficiently and cost
effectively. Picking inventory in a warehouse that is managed by ACCPAC
WMS means never having to look for missing stock or walking aimlessly
around the warehouse to fulfill customer orders. With ACCPAC WMS all
your warehouse activities operate at peak performance, enabling your
enterprise to:
Increase order accuracy
Eliminate paper error
Pick and pack concurrently
Fill multiple orders simultaneously
Track inventory in real time
Print packaging slips on demand
Increase customer satisfaction
FULL PRODUCTIVITY
ACCPAC WMS offers you the ability to maximize the productivity of your
warehouse personnel. By maintaining detailed information on the flow of
inventory from both pick and overstock locations, your staff is directed
to a specific bin knowing the item will be there every time. Furthermore,
requests to replenish pick bins can be managed during off-peak hours or
Page38
coordinated to
run simultaneously with
picking activities
without
interruption.
Functionalities:
A.
features
REAL-TIME VISIBILITY AND DATA
ON-TIME DELIVERY
REDUCED LABOR COSTS
Boost productivity
Reduce cost
Increase accuracy
http://www.pcginc.com/docs/WarehouseManagementSystem.pdf
2.1.5 WMS Software (Warehouse Management System)
Egemins Warehouse Management System (Ewms) is our
advanced WMS software application to manage inventory, orders, and
locations
and
transport
flows
in
warehouses
and
distribution
environments. It constitutes the perfect link between your logistics

environment
and
the
equipment
available.
Ewms is a mature and flexible WMS solution for increasing productivity

and inventory accuracy in your warehouse or distribution center.
Page39
OBJECTIVE:
We develop and integrate intralogistics automation solutions for
companies that are looking for a more efficient organization of their
distribution, intralogistics and material handling. Our solutions are based
on intralogistics systems for internal transport, storage an order picking
which we control and manage fully automatically with own controls and
software. Our core solutions include:
automated warehouse systems and distribution solutions
automated guided vehicle systems (AGV systems) in-floor chain

conveyor systems retrofit solutions, modernization of material
handling systems
FUNCTIONALITY:
Ewms is available as an integrated WMS application suite, but can
also be configured providing only the required layers and features. It is
suitable for stand-alone operations or for a seamless integration within
your existing administrative systems. Ewmsconsists of two main
functionality
layers:
The Ewms (warehouse management system) WMS layer containing the

administrative modules:
inventory management module
order management module
Page40
The Ewcs (warehouse control system) WCS layer covering all features
related to the material flow control:
location management module
transport management module
visualization
Core features of Ewms from reception to delivery:
Receiving & inventory management: inbound flow of products in

warehouse
Replenishment of (dynamic) picking zones
Inventory allocation: assign stock to orders
Order assignment: assign orders to resources or work stations
Load balancing and control of picking stations and/or order picking

resources
Consolidation and dispatch labeling
EWCS - WAREHOUSE CONTROL SOFTWARE

Egemins warehouse control system (Ewcs) is a control system that
integrates all automated warehouse equipment in your warehouse into an
efficient transport system. It ensures an optimal usage of the transport
means and storage methods and avoids overload problems as much as
possible.
Ewcs
consists
of
two
main
modules
The Location management module manages the current locations of

your carriers (pallets, totes, bins, trays, boxes). The products are assigned
Page41
to a storage location in the warehouse based on a unique five dimensional

coordinate system allowing for different types of storage in the warehouse:
single
deep,
double
deep,
multi
deep.
The Transport management module defines how goods are moved

between the various zone in your warehouse, e.g. from storage to working
zone or vice- verse. Individual movements of carriers are realized through
transport orders which consists of a number of sub transports, each
executed
by
an
individual
transport
means.
Core features of Ewcs:
Flow control of individual carriers and management of open
transport orders.
Management of warehouse locations
Equal supply of carriers to working stations to avoid saturation and
to provide a balanced workload

http://www.egemin-automation.com/en/automation/material-handlingautomation_ha-solutions_automated-warehouse-systems_wdssystems/warehouse-management-system
Page42
2.2 Local Studies

2.2.1 CERQUIT Warehouse
The Cerquit Warehouse Management System is a web-based
application that allows users to manage the company's supply chain and
enhance customer satisfaction by providing reliable information about
inbound / outbound delivery as well as current inventory levels.
Tracking of items - inventory, quantity at each warehouse, movement
history, stocking status are all made easier using the system it can
manage various types of Bill of Materials (BOM) necessary for every item
processing of a certain project? It allows effective item planning for every
project/branch involved and maintain an optimum level of inventory
monitoring.
It performs instant availability of checks and track item stock levels
with real-time visibility of the inventory on hand. The software provides
quantity details that are adjusted by what is already committed to other
customers, incoming purchases, and project orders.
The system can generate reports to meet any of the warehouses
and inventory reporting needs. Detailed reports on the different features
like purchase ordering, stock receiving, item transfer, job issuance, and
material billing requirements provide the information necessary to make
quick and effective management decision.
Cerquit Warehouse Management System can be integrated to
Cerquit Financial Suite to streamline your business process and improve
efficiency of your employees.
System Components
Page43
Multiple Site and Warehouse Inventory. System is capable of

supporting unlimited number of warehouses and sites, and allows
tracking of all stock movements from one site to another in full
detail from requisition, purchasing, to delivery and receiving in
sites.
Machinery and Equipment Management. The system has a

facility to monitor history of repairs of machineries and equipment,
their rental statuses and revenues.
Project Management. The BOM (Bill of Materials) is the heart of

the Cerquit Warehouse which allows company to have a total
control of items/materials, project budget and schedule.
Reports. Cerquit Warehouse is capable of delivering intelligent

reports based on real time transactions, helping company in
creating wise business decisions in no time.
Reports
Suppliers Performance Report
Delivery Schedule
Stock Ledger
Purchasing History
Bill of Materials
Inventory Stock
Materials Utilization Report
Equipment/Machineries rental and usage report
Application Features
Supports BOM (Bill of Material) - which is the project

management blue print that covers essential project
information - from project staffing, to budget, to detailed
materials listing, with their corresponding costs, delivery
Page44
schedule, stocks ledger and complete inventory levels

information.
Project Budget facility the system automatically

calculates project budget for easy yet effective cost
management.
Purchasing History tool allows you to keep accurate

records of Stock Transactions. Supports dynamic growth of
warehouses; system can store unlimited number of
sites/warehouses to be monitored.
Delivery Scheduling - a facility that allows scheduling of

items dispatch schedule from warehouse to different
destinations. Or shipment schedule of item from warehouse
to project site.
Stock Ledger and stocks monitoring the system can

supply information for every requisition/purchasing activity
for each warehouse.
Item Adjustments - transaction that allows authorized

personnel to change the current system stock level so that it
matches the amount of stock that are physically available.
Dashboard - automatic notifications of urgent transactions

needed to be done and closely monitored information.
Requisition, purchasing, receiving and delivery forms

for processing items/materials; covering all inventory levels
for efficiency and productivity and reduced paperwork.
Canvassing allows purchaser to keep canvassing records

from different suppliers for each items/materials on record.
User Defined Roles allows administrator to assign roles to

each user in the system defining access permissions.
Item coding for uniquely identifying each

items/materials/products.
Page45
System Key Benefits
Real time visibility and control of all the stocks in the

warehouse.
Company management has high control with warehouse

processes.
Easy project monitoring.
Reduce inventory levels and increase inventory turns across

the whole warehouse operation.
Reduction of paperwork.
Improve instances of location spot checking to ensure that

the system balances and actual location quantities match.
Improved customer service efficiency.
Improved productivity through manpower efficiency.
http://www.cerquit.com/Products/Warehouse-InventorySystem
Page46
2.2.2Strategic Approaches to Materials Management for Industrial Projects

Abstractthe purpose of this research is to analyze materials
management in construction. One issue is Information Technology. An efficient
IT systems results in a competitive advantage, rapid communication and lower
cost. Managing the flow of materials, information and associated engineering and
financial resources between suppliers, service providers and construction job site
is the most effective way.
MMS (Materials Management System) is a core process of EPC (Engineering,
Procurement and Construction) projects with multiple modules from the
beginning of project information through reporting. Implementing the system
covers lost time, minimizes lost materials and will provide the most efficient
operation.
In the world, many contractors in this loop have achieved long-term success and
gained high-level profit.
I. INTRODUCTION
Materials Management is an organizational theory-philosophy process that
involves multi-systems approaches for all management functions. The system
brings necessary approaches to plan, acquire, select, purchase, deliver, store
and move with sub function modules.
Materials represent a major expense in construction, so minimizing procurement
costs improves opportunities for reducing overall project costs. Delays and extra
expenses may be incurred if materials required for particular activities are
unavailable. Planning at the strategic, tactical, and operational levels is never
separated. The most value is realized by integrating the strategic vision, based
Page47
on demand patterns, into tactical plans that are actualized via operational
scheduling in the Materials Management System.
A systemic approach provides an ability to examine, model, and optimize our
supply chain, across different levels, strategic, tactical, and operational. This is
facilitated by an integrated reflect up of Materials Requirements Planning (MRP)
and Scheduling.
II. THE MASTER KEYS

Lead Plan. A core step of a Materials Management System is to issue a stronger
framework. There are four key performance value criteria:
Benchmarking. Comparing performance and standards, which

approaches to bring about improvements, set goals, establish priorities for
change and resource allocation. Benchmarking allows for identifying
and monitoring standards and performance in order to improve suppliers,
processes and practices, discover new ideas for achieving suppliers core
objectives', inform planning and goal setting.
Operate. Operate is to start an evaluation of review of bidders according

to their proposals. This is the core step before the last core. The ability to
create a preparation condition to go finalize scheduling.
Competitive bidding is effective when: Volume is high enough to justify

this method of business.
Implement. Setting expectations for implementing and maintaining

supplier performance measures ensures the measures are fully
understood by all parties and are good indicators of the health of the
relationship to all parties involved. Ensuring all business requirements are
fully understood and met. Ensuring collaborative work practices are
Page48
implemented to ensure a joint approach to problem solving and the

identification of improvement opportunities.
PROCUREMENT PROCESS
A. Procurement Cycle
It is able to support the complete cycle of project progress, bid invitation,
award/order placement phase, and acceptance of logistics services, as well as
the invoice verification process.
Understanding goal setting
Its really important to gain the lowest price, but this needs to be engaged with
budget, what is the optimum term, your risk appetite, and other user-specific
criteria that can be determined by understanding your objectives and
understanding what works and what doesnt work.
Supplier Identification and Short-listing
In this stage, organizations shortlist vendors who deal in the products which a
company wants to buy. Once vendors are shortlisted, the company will
communicate with the vendors sharing an RFP (Request for Proposal) with them.
Negotiations with Bidders
Page49
After the commercial and technical evaluations have been completed, the project
team shall meet to select the bidders to be short-listed to plan their negotiation
strategy. All issues, such as exceptions and clarifications must be resolved
during the negotiation meetings with the bidders. A record of negotiations with all
bidders will be prepared that contains all items discussed.
Benefits:
Track supplier metrics.
Immediately report on shortages, late shipments and defective

parts.
Track in-line and receiving issues.
Manage supplier corrective actions.
Rate and rank suppliers with scorecards.
Collaborate with suppliers to solve problems faster.
Control costs and make better products the first time.
http://www.mypurchasingcenter.com/purchasing/industryarticles/strategic-approaches-materials-management-industrial-projects/
Page50
2.3 Synthesis and Relevance to the Study (Matrix-Comparative Analysis)

Foreign and Local Studies
Foreign Related Studies
Local Related Studies
FEATURES
R1
Delivery
Monitor
Purchase
Order
Create Sales
Order
Work Load
Estimate
Shipping
R2
R3
R4 R5 R6
R7 R8 R9 R10
Service
Management
System
Materials
Management
Procurement
&Warehousing
Multi
Warehousing
Price and Cost

Comparison
Reduce Cost
Page51
On Time
Delivery
Reduced Labor
Costs
Real time
Visibility and
Data
Boost
Productivity
Management of
Warehousing
Location
Stock Ledger
Bill of Materials
Inventory Stock
Item
Adjustment
Canvasing
Item Coding
EquipmentRental and
usage report
Page52
Chapter 3
Risk Mitigation, Monitoring and Management Plan
1.0 Introduction
The proponents propose a system that the risk management seeks to
mitigate the impact of the risk reducing and avoidable consequences through
planning, monitoring and other appropriate actions. Whether in general or in the
specific case, As a proponents/clients should identify and analyze all risk factors
that are likely to occur on a project, and then decide on the most appropriate
management response for each risk/combination of risks. In these scenarios, risk
analysis and management are intended to help a software proponent to
understand and manage uncertainty during the development process. The
important thing is to remember that things can go wrong and to make plans to
minimize their impact when they do.
1.1 Scope Intent of RMMM Activities
The purpose of the proponents is to mitigate the problem for developing
software that clients and the developer must work together that intent to avoid
error/defects for the process. If when all the risks have been identified, that will
be evaluated to determine their probability of occurrence, and how the company
Page53
will be affected if they do occur. The plans will be made to avoid each risk, to
track each risk to determine if it is more or less likely to occur, and to plan for
those risks should be occur. It is responsibility to perform risk mitigation,
monitoring, and management in order to produce a quality product. The quicker
the risks can be identified and avoided, the smaller the chances of having to face
that particular risks consequence. The fewer consequences suffered as a result
of good RMMM plan, the better product and the smoother development process.
1.2 Risk Management Organization Role

The customers can avoid risk by double-checking the possible defects/errors
of the existing system preventing the problem. The proponent will consistently be
monitoring their progress and project status as to identify present and future risks
as quickly and accurately as possible. But also, staff and clients must know on
how to manage the risk in that will occur the problem.
2.0 Functional Data Description

2.1 Risk Table
Category
Employee risk
Risk
Probability
Impact
Inability to manage and lack of
30%
Slow process
55%
In estimated the proper size of the
35%
25%
experience
Process risk
Product size
product and Constraints of project

Inaccurate
and
Inconsistent
the
Page54
Development
process of delivery
risk
Failure to communicate
15%
50%
40%
Customer risk
Technology
will
not
Meet
Technology risk Expectations and Computer Crash

Business
Late delivery
impact
2.1.1 Description of Risk
Business Impact Risks:

This is the risk where concern is that of the not being able to come
up or produce the product that has impact on the clients business. If the
software produced does not achieve its goals or if it fails to help the
business of clients improve in special ways, the software development
basically fails.
Customer Risks:
The proponents that consumer risk is a potential risk found in all
consumer-oriented products, which a product not meeting quality

standards will pass undetected though the manufacturer's quality control
system and enter the consumer.
Development Risks:
In developing the software/system the team must take a request to
the clients for all the equipment/materials and it must have to provide the
necessary needs for the development software. As a team there must
have a resource/strategic ways during the development of the system that
Page55
it cant cause a failure. As clients it is an obligation to provide the

equipment/materials for a developing system.
Employee Risks:
As part of the team it must have to cooperate or to make an effort
avoiding failure for the development system.
In a procurement
management the employee must be aware the process especially on how

handle the work in management process of the equipment/materials and
must have an ability and experience. It is important to the proponents to
have cooperation in every member of the team that will not be fail for the
developing of a system.
Process Risks:
Operational risk, is the risk of a change in value caused by the fact that actual
losses, incurred for inadequate or failed internal processes, people and systems,
or from external events (including legal risk), differ from the expected losses".
Operational risk is, nonetheless, manageable as to keep losses within some level
of risk tolerance determined by balancing the costs of improvement against the
expected benefits. It should be noted that the structured method has been
adopted for the development project. At the completion of the project, it will be
determined if the software method is acceptable as a standard process, or if
changes need to be implemented
Product Size:
As a proponent should estimate the proper size of the product that may not fail
the project. And also the numbers of staff that will be fairly low. There will be one
user per instance of the software running, as the software is not client/server or
intended for multi-user use. Number of projected changes to the requirements.
The proponents estimate the possible changes to the requirements these will be
as a result of our realization of what is required and not required as team get
Page56
further into implementation, as well as a result of interaction with the customer

and verification of the customers requirements.
Technology Risks:
Information technology risk, or IT risk, IT-related risk, is any risk related to
information technology. This relatively new term due to an increasing awareness
that information security is simply one facet of a multitude of risks that are
relevant to IT and the real-world processes it supports. Generally speaking, risk
is the product of the likelihood of an event occurring and the impact that event
would have on an information technology asset.
2.1.2 Probability and Impact for Risk m

Category
Risk
Probability Impact
Inability to manage and lack of 30%

Employee risk
experience
Slow process
55%
In estimated the proper size of the 35%
Process risk
Product size
product and Constraints of project

Inaccurate
Development
and
Inconsistent
the 25%
15%
process of delivery
risk
Failure to communicate
Customer risk
Page57
Technology
Technology risk
will
not
Meet 50%
Expectations and Computer Crash

Late delivery
40%
Business
impact
Table- Risk table (sorted)

Impact Values
Description
H-high
Catastrophic
M-medium
Critical
L-low
negligible
3.0 Risk Mitigation, Monitoring, and Management

This section in detail describes Risk Mitigation, Monitoring, and Management for
each of the possible risks. It will talk about ways to avoid, monitor and to have
ways to manage the risks.
3.1 Risk Mitigation for Risk m

The proponents must have to plan or create a planning step and procedure
for the development software that will not be fail. Proponent aim to avoid and
mitigate the problem from encountering errors/defect. It is important to have a
mitigation plan that will easily to identify the defects/error from the existence of
the development software/system. The risk mitigation step involves development
of mitigation plans designed to manage, eliminate, or reduce risk to an
acceptable level. Once a plan is implemented, it is continually monitored to
assess its efficacy with the intent of revising the course-of-action if needed.
Page58
3.1.1 Product size

Proponents should have to correct all overestimation in order to
prevent this happen, meetings (formal and informal) will be held with the
customer on a routine business.
This insures that the product we are
producing and the requirements of the customer are equivalent. In

overestimation it may cause a trouble in producing the product because it is
important to have and correctly product size.
3.1.2 Business Impact
As a proponent, the cost associated with a late delivery is critical. A
late delivery will result in a late delivery of a letter of acceptance from the
customer. Without the letter of acceptance, the group will receive a failing
grade for the course. Steps have been taken to ensure a timely delivery by
gauging the scope of project based on the delivery deadline. But as a
mitigation plan on how to prevent this matters it should be aware in every
delivery of the products. The proponents must be avoid this problem using
mitigation plan that it will not cause a failure in development of system.
3.1.3 Customer (User) Risks

In dealing to the development the participation of the customers it is
very important to develop a software or system that has the ability to plan
and coordinate your materials, production and people assets effectively to
meet customer demand. To mitigate this problem it should take a ways
avoiding defects by communicating to each other. The obvious strategy to
reduce customer concentration risk is to diversify and increase your
customer base.
3.1.4 Process Risks
Page59
In proponents managing risk is a process that assesses a

participants that can give more clients in the future because of the quality of
the equipment/ materials. An assessment of risk is generally conducted as
part of the needs assessment and service planning process it should utilize a
person-centered approach. In developing specific program policies and
procedures that clearly outline roles and responsibilities of all involved
parties, to develop a process it is easily to identify situations giving the right
price and cost, discussing to mitigate the problem in development software
shall ensure the process is in place to protect participants right to assume
risk while honoring their decisions, and monitoring the plan to ensure the
goodness of the development software. Having a right quality and standard
in delivery of the product that will assure the increase of the customer.
3.1.5 Technology Risks

Proponents defined the technology risk that cost is associated with
a computer crash resulting in a loss of data is crucial. A computer crash itself
is not crucial, but rather the loss of data. A loss of data will result in not
being able to deliver the product to the customer, to mitigate this problem the
group will not receive a failing grade for the course. As a result the
organization is taking steps to make multiple backup copies of the software
in development and all documentation associated with it, in multiple
locations. In order to prevent this from happening, the proponents will be
required to learn the languages and techniques necessary to develop this
software.
The member of the team that is the most experienced in a
particular facet of the development tools will need to instruct those who are
not as well versed.
3.1.6 Development Risks
Page60
The proponents developing an effective Risk Management Plan

can help keep small issues from developing into emergencies. There is
the different types of Risk Management Plans can deal with calculating the
probability of an event, and how that event might impact you, what the
risks are with certain ventures and how to mitigate the problems
associated with those risks.
3.1.7 Employee Risks (Team Members)
The team required to learn the languages and techniques
necessary to develop this software. The member of the team that is the
most experienced in a particular facet of the development tools will need
to instruct those who are not as well versed
3.2 Risk Monitoring for Risk

In this section we will identify the conditions to monitor to determine
whether risk m is becoming more or less likely.
3.2.1 Product size:

To monitor the risk here, that we will keep track of the amount of
functions necessary for the program throughout the entire development
cycle. This will tell us if the project may come across risk in future.
Proponents will keep track of the Java code produced during the coding.
3.2.2 Business Impact:

As monitoring step in this risk that proponents will setup user
meetings to show them the work that has been completed and to get user
input on the work. We will have meetings every other week to present the
Page61
work that has been done from the time of the last meeting. This will help
the proponents in staying in touch with the customers and will also be very
efficient way to derive customers input on the progress made.
3.2.3 Customer (User) Risks:

To monitor this risk proponents will monitor the successes of the
meeting by keeping track of people that have attended the meeting. If the
outcome of the meeting is low we can contact responsible person to help
us overcome this problem. And will also have the login charts to show the
customer who is attending the meetings and who needs to be reminded to
start attending meetings.
3.2.4 Process Risks:

To monitor the risk here we will review each others work to find the
problems and to help each other in achieving better product quality. The
proponents will also have the general guidelines set for all of the work to
be carried on for the software development. Software development will
constantly check each others work and will compare it with the set
guidelines, and will inform a proponent member who is failing to
participate in following the guidelines.
3.2.5 Technology Risks:
For monitoring phase during the development of the software
proponent will keep eye on new technology. This will help us to keep up
with new technology. For example plan will be drawn to use multiple set of
Page62
the Palm-size PC so that proponent can see if the different brand PC with
same operation system is capable of carrying the task needed to perform
checklist operations.
3.2.6 Development Risks:
For monitoring phase during the development of the software we
will keep eye on tools being used and their effectiveness. This will help us
to keep up with new technology. Proponents will keep track of the new
equipment being brought into use at DEQ. And will also look for the
availability of the inexpensive equipment that may provide help in
completion of this project.
3.2.7 Employee Risks (Teammates):
Monitoring and managing of this risk will include looking out for
each other, that if some of the proponent-member is having difficulties in
performing some tasks or using particular tool or technique other
members of that proponents will help him out.
3.3 Risk Management for Risk m
In this section we will identify several different software development risks and
will try to create a plan to manage these risks if they do occur.
3.3.1 Product size:

After careful monitoring of the process, if we still end up with
underestimation of the FP, we will put more man-hours into the project.
This is the only way that we think we can manage the risk.
3.3.2 Business Impact:
Page63
If a mistake has been made, user input on the completed work will
provide us with information to fix or improve the software. We have done
very many meeting with the clients and plan to do meeting every two
weeks; this should clear any misunderstandings between the software
development of proponent and customers. This is the best way to go at
since the work that is done on the project is revealed during the meetings
and customer gets chance to make adjustments necessary.
3.3.3 Customer (User) Risks:
If the turn out in the meetings is not encouraging we will pass out
questionnaire to easily gather customers' view. We will ask them question
rather than waiting for them to ask us questions. We will also talk to the
manager at the DEQ to help us come up with plan that will increase the
attendance during the meeting. If the outcomes of the meetings is
satisfactory there should not be any major difficulties regarding customer
risks.
3.3.4 Process Risks:

If the problem exists with the quality of the work, the quality
assurance plan will be revised in the risk management phase. Other team
member will attempt to take over or swap the work of the member whose
work does not meet the quality standards.
3.3.5 Technology Risks:
For monitoring phase during the development of the software that
proponent will keep eye on new technology. If we spot new techniques
that can be implementing without major changes in our project we will
Page64
include such techniques in the development of the project. And will also
keep a look out for major shifts in the technology and how it affects the
software that we are working on. If there is a need change in the
technology will be discussed among team members and will be presented
to the client. If client agrees necessary changes will be made with the
existing technology.
3.3.6 Development Risks:
In the management phase if the funding for the technology and
tools are not enough we will have to reschedule the phases of software
development cycle to allow more time to coding phase. As part of this
development will provide information on the several different Palm-size
PCs and will let the customer to choose the one that is most appropriate
for the customer to buy. And will also make sure that the equipment is
allowed to be purchased under government controls and contracts.
3.3.7 Employee Risks:

Monitoring and managing of this risk will include looking out for each
other, that is if some team-member is having difficulties in performing some tasks
or using particular tool or technique other members of that team will help him out.
This is where team members may have to spend little time with each learning or
teaching what others know. If team member lacks ability to use certain
programming language or application, other team members will take some time
off to teach the team member basics related to that application.
Page65
Software Configuration Management Plan
1.0 Introduction
This Software Configuration Management (SCM) Plan specifically
addresses configuration management for software. Configuration management
for hardware, telecom, operating systems, and other components managed by
Procurement and Warehousing Services are addressed by the Service
Management System Process and Procedures.
1.1 Scope and Intent of SCM Activities
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
Page66
without significant backtracking, lessening development time and

resulting in a higher-quality product.
The Proponents will oversee these activities, and any changes to
existing code or architectural design must pass their inspection before
they are carried out.
SCM Activities are developed to:
Identify the changes
Ensure that change is being properly implemented
Also have a way to document the change.
1.2 SCM Organizational Role

The SCM team will work closely with the SQA (Software Quality
Assurance) proponents, cross-examining many of the submitted documents and
software change requests. Software Engineers will submit change requests
directly to the SCM for their inspection and approval.
Adviser
Manages appropriate schedule
Oversees overall project reviews
Provides leadership and program support for a wide range of analytical,

management, and coordination duties
Guiding in every procedure of this project
Client
Page67
Coordinates and sets up meetings, change request analysis, and

configuration audits.
Supports coordination/communication efforts with other activities
Identifies opportunities for improvement and develops strategies for

improving processes
Developer
Develops IT system, build codes and fix bugs
Responsible for system integration
Translates design elements into traceable source code elements
2.0 SCM Task

Changes are inevitable when software is built. A primary goal of software
engineering is to improve the ease with which changes can be made to software.
Configuration management is all about change control. Every software engineer
has to be concerned with how changes made to work products are tracked and
propagated throughout a project. To ensure that quality is maintained the change
process must be audited. A Software Configuration Management (SCM) Plan
defines the strategy to be used for change management.
2.1 Identification
In this section the proponents will describe the way software configuration
items will be identified for the software configuration management plan. As a
developer they need to determine in every details of what system they developed
to, because of this project it will take a lot of time for changing the process came
from the original plan they to visualize the necessary needs of the company.
2.1.1 Description
Identify Changes
Development Methodology and Documentation
System Decomposition
Page68
Unique Identifier
Version/Revision Identifier
Interface Control
Change control
Involves controlling and managing the changes to the network. The goal
of change control is to establish mechanisms that will help ensure the
integrity of the network.
Maintain Network Configuration Baselines

A configuration baseline is the foundation of configuration management.
Each baseline captures an approved snapshot of the SN and its components at a
given point in time. The conventional configuration management model
constructs a system baseline from the top-down. In this single-tiered model, a
baseline is comprised of a specific release of each component and any change
to any component must be considered and approved by the CCB.
2.1.2Work products and documentation
Configuration Control
Description
The term Configuration Control is defined in Section 1.1 of this document.

Software Configuration Control includes the following objectives:
Procedures for changing baselines
Change requests approvals
Responsibilities for change control
Change control process
Request for Change process
Page69
Level of control
Management of release documentation
Configuration control tools and techniques
System Change Requests (SCRs)
Complete a System Change Request if the change has been initially
approved.
Enter the SCR on to the SCR Log.
Forward the SCR to the Project Manager.
2.2 Configuration Control
2.2.1 Description
The proponents will change and controlled the human procedures
and that will be automated processing of the procurement and
warehousing.
2.3 Version Control

Document dates
The author of the document will ensure the date the document is created
or revised is identified on the first page and, when possible, is incorporated into
the header or footer of the document and appears on every succeeding page.
Page70
Version numbers
The author of the document will ensure the current version number is
identified on the first page and, when possible, is incorporated into the header or
footer of the document and appears on every succeeding page.
2.4 Configuration Status Accounting (CSA)

We will be using one way to communicate with the team members and to inform
others that changes may concern.
2.4.1Description
Verbal communication: since our software development team is

small and all the team members are in constant touch with each
other it would be better to communicate verbally.
Software Quality Assurance Plan
1.0 Introduction
The proponents will give an overview about this Software Quality
Assurance plan for the development of the system.
1.1 Scope and Intent of SQA Activities
Fixing error
Documentation
Editing
1.2 SQA Organizational Role

Ego-Less Structure
Page71
Manage the
team
Handling
the
business
rules
Handling
the system
software
Analyze the
business
Documentin
g the
process
Figure 1.2 it shows here at the above of roles every members of the proponent
development system.
Project Manager
Manage the team
System Analyst
Handling of business Rules
Business Analyst
Analyze business process
Documentary Specialist
Documenting the process
Lead Programmer
Handling System Software
2.0 SQA Task
Gathering (brainstorming/meeting)
Detailing the design
Count the product
Number of item
Page72
2.1 Task Overview

Gathering (brainstorming/meeting)
On every gathering the decision making was decided by hearing
every ones opinion on a certain changes and topic. So that every ones
idea was acknowledge and summaries to make a conclusion.
3.0 Problem Reporting and corrective Action/Follow up

3.1 Reporting Mechanism
All defects or enhancements are referred to the SQA leader. Most often,
this will be completed in every SQA review held. If a defect occurs between SQA
meetings, the defect will be reported to the SQA promptly, so that the SQA
leader can analyze the defect and assign a priority level to it. This can occur
either by word of mouth (as long as the SQA leader is taking note), email, or a
hand written report.
3.2 Responsibilities
The SQA leader is in charge of all SQA activities. Any defect or

enhancement reported is analyzed and given a priority ranking. The SQA leader
then assigns a particular software engineer to correct the problem or add the
enhancement. After the correction or addition has taken place, it is the SQA
leaders responsibility to review it and ensure that the appropriate action was
taken. If the solution or enhancement does not meet the standards of quality set,
the SQA leader will redistribute the task to the software engineers until the task is
complete.
Page73
3.3 Data Collection and Valuation
The SQA leader is responsible for all data collection and evaluation. Any
product defect or enhancement will be reported to the SQA leader so that he can
record the problem and evaluate its priority level. The data is collected by
keeping a record of each SQA meeting and keeping track of all problem
submissions outside of the SQA meetings.
System Specification
1.0 Introduction
The system specification is also written during the design stage. This
document contains the technical details such as the software and hardware that
will be used to develop and run the system. It will also contain details of any
additional systems/ database which will be needed to create the system.
1.1 Goals and Objectives

Purpose of the proponents is what makes system
efficient that has a capacity, in instant access to warehouse,
and it integrates all warehouses together. The system has a
variety of functions by which items are organized and classified
in an accurate well-presented way. In warehousing and
Page74
procurement coordinates procedures of warehouse varying

from requesting to receiving items through standard purchase
and request forms. Designed for rapid time to benefit and low
cost of ownership. It helps the consumer unify its business
processes for increased productivity and efficiency to gain
better visibility and control over decision driving information and
help insure your business is highly valued and well regarded.
The system also provides authorized users with concrete,
measurable, and reliable date to take actions about different
transaction taking place. In procurement to aim for managing
and standardizing the procurement process within an accurate
data and organized the purchase sources and procedure
through clear presented standardized order forms within
concrete and measurable data.
The goals are:

Functions:
Automatic VAT definition by item, customer or supplier
Automatic landed cost calculation
by importing direct
expenses from the accounting module

Report:
Price list report
Page75
1.2 System Statement of Scope
The proponents must be aware the system implemented because

sometimes there is the circumstances system does not function. Proponents give
details what the system implemented and make sure that has a functionality in
every module execute of what data or information produced their system.
1.2.1 General Requirements

The following general requirements were identified and specified for the
Materials management procurement & Warehousing.
A way in which the company could purchase an item/product.

A way in which the company to request the item/product of each
employee or client.
A way in which in the item/product they needed to every day.
1.3 System Context

The main objective of this thesis is to implement a server platform. The
platform has an interface that connects to municipalities enabling them to upload
polls, and another interface that connects to Android client devices for tracking
them and delivering polls based on their location (as defined by the municipality).
Clients fill polls and are then delivered back to municipalities via the server
platform. Privacy measures should be accounted for by adopting an opt-in
functionality.
1.4 Major Constraints
Time
The proponents only have an approximately five months to finish all
documentation, software and interface enhancements. This is a disadvantage
Page76
for the proponents knowing that the system development and documentation
has to finish within five months at the same time the proponents are still
studying on their classes and still searching on how the software development
will takes place.
Workforce
The proponents only have a maximum of five members. That is why
the number of people who work for the development of the software comes
up in a disadvantage in terms of the numbers. The proponents have to double
time regarding of the execution of the project documentation and
requirements specification regardless of the shortage of the manpower of the
project team.
Funding
Funding is the worst possible constraints for the proponents, the funds
that the proponents are only limited considering they are currently dependent
as a students who lacks on personal fund to support the expenses for
developing the HRMS. However, this constraint will not be an issue for not
pursuing the objectives for the development of the HRMS.
Resources
The software and hardware that the proponents used to develop the
HRMS are also limited. The proponents only have one laptop and one
desktop to be able to use in developing and documenting the software. It is
more efficient for having at least one laptop / desktop per member of the
project team to be able to execute the software development on time.
2.0 Functional Data Description
This section describes overall system function and the information domain
in which it operates.
2.1 System Architecture

Page77
2.1.1 Architectural Model
Figure 2.1.1 it shows the process of the procurement and warehousing
Page78
2.1.2 Subsystem Overview

The summary of system elements provides a brief survey of the system
element to be realized. It describes tasks and objectives of the system element
and its role within the system.
2.2 Data Description

2.2.1 Major Data Objects
User Administrator Information
1.)
Log Form
1.
Admin name
Admin name for the administrator
2.
Username
Username of the administrator is one of the important information
needed to access the system.
3.
Password
Password for the user administrator this code are needed to access
the system.
Page79
2.2.2 Relationships
Procurement
Page80
Figure 1.1 shows the Relationship Diagram of Procurement
Warehousing
Page81
Figure 1.2 shows the Relationship Diagram of Warehousing
3.0 Subsystem Description
3.1 Subsystem Flow Diagrams
Figure 3.1 shows the sub-system data flow diagram of procurement and
warehousing
Page82
3.1.1 Create Checklist
Figure 3.1.1 shows the create checklist of procurement and warehousing
3.1.2 Print Checklist
Page83
Figure 3.1.2 shows the print checklist of procurement and warehousing
3.1.3 Generate letter
Figure 3.1.3 shows the generate letter of procurement and warehousing
Page84
Software Requirements Specification
1.1
Goals and Objectives
The purpose of the proponents is what makes system efficient that

has a capacity, in instant access to warehouse, and it integrates all
warehouses together. The system has a variety of functions by which
items are organized and classified in an accurate well-presented way.
In
warehousing
and
procurement
coordinates
procedures
of
warehouse varying from requesting to receiving items through

standard purchase and request forms. Designed for rapid time to
benefit and low cost of ownership. It helps the consumer unify its
business processes for increased productivity and efficiency to gain
better visibility and control over decision driving information and help
insure your business is highly valued and well regarded. The system
also provides authorized users with concrete, measurable, and
reliable date to take actions about different transaction taking place. In
procurement to aim for managing and standardizing the procurement
process within an accurate data and organized the purchase sources
and procedure through clear presented standardized order forms
within concrete and measurable data.
Page85
The goals are:

Functions:
Automatic VAT definition by item, customer or supplier
Automatic landed cost calculation by importing direct expenses from

the accounting module

Report:
Price list report
1.2 System Statement of Scope

The proponents must be aware the system implemented because sometimes
there is the circumstances system does not function. Proponents give details
what the system implemented and make sure that has a functionality in every
module execute of what data or information produced their system.

The following general requirements were laid out for our project named
SMS-Service
Management
System
with
the
sub-system
MM-Materials
Management Procurement and Warehousing.
1.2.2 Extended Enhancements
1.3 System Context
Eventually multiple users will be using the product simultaneously. Therefore,

concurrent connection will be an issue for implementation. In addition, this is a
Page86
pilot product that hopefully if the successful can be used in other location as well.
This leads to issues about future for a larger user base.

Time
We only have about two months to finish all documentation, software creation
and enhancements. We have a lot of ideas but cannot implement them due to
time constraint. One of the major ones is to move the application to be
completely browser-based.
Funding
To develop and implement the palm pilot integration, we will need funding to buy
at least one palm pilot. We will request the funding from University of Michigan
Dearborn should we decided to pursue this function.
2.0 Usage Scenario

This section will define the user level of the Materials Management
Warehousing & Procurement (MMWP).This will define the user type and the
accessibility level upon logging in into the system.
2.1 User Profiles
The Materials Management Warehousing & Procurement (MMWP) will have

the following levels of users:
Read / View (User)
Full Control (Admin)
Read/ Write/ Modify All (Materials Manager)
Read/ Write/ Modify own (Encoder)
2.1 Use-Cases
Page87
The following use cases are typically interaction between external environment
and the internal system
1. Log in
2. Adding user
3. Adding item
4. Viewing user
5. Viewing user Information
Add supplier/bidder
Update supplier/bidder
Create bidder
3.0 Data Model and Description

Data object
User account data objects
Item data objects
Supplier data objects
3.1 Data Description

3.1.1 Data Objects and Dictionary
Administrative Information (Linked with Form)
1. F-ID
The number is given to each facility that is inspected or is to be inspected.
2. EPA ID
3. F-Name
Name of the facility that is inspected or is to be inspected.
4. F-Address
Page88
This field contains facility address.

5. F-City
This field contains the name of the city facility is located in.
Actions Completed on a Facility
1. Company ID
This field contains number given to each facility.
2. ID
This field contains number given to the specific inspection (Inspection
Number).
3. Letter/Checklist Date
This field contains number given to the specific inspection (Inspection
Number).
4. Letter/Checklist Location
This field contains information on where the generated checklist letter is
stored.
5. Inspector Initials
Initials of the inspector that did the inspection.
Inspection Form
1. ID Number
Page89
This field contains inspection ID number

2. Checklist Number
This field contains number given to the checklist generated after all the
inspection.
3. Description
This field contains description of the inspection done at all facilities
4. ID
This field contains compliance status of the facility during inspection
5. EPA ID
This field contains acronym given to inspection process.
6. Abbreviated Flag
Yes or No status for the inspection.
7. Checklist ID
Description of the inspection.
Inspection Results
1. Actions ID
This field contains inspection ID Number given to each inspection.
2. ID Number
This field contains inspection ID Number
Page90
3. Item Results
This field contains results of the inspection done.
4. Comments
This field contains comments regarding inspections.
5. Add in comments too
Contains information to specify comments for someone particular.
Inspector Details
1. Inspector Initials
Initials of the inspector that did the inspection.\
2. Inspector Name
This field contains name of the inspector.
3. Title
This field contains title given to inspector from DEQ.
4. Salutation
Expressions given to the name to automatically generate letter.
5. Phone Number
This field contains phone number of the inspector.
Compliance Options
1. ID
Page91
This field contains compliance option ID Number.

2. Compliance Description
This field contains description of the compliance option.
EPA CODE
1. EPA ID
Internal EPA ID.
2. EPA Code
Actual EPA code.
Letter Template and Checklist
1. ID
Field contains letter/checklist ID Number.
2. Name
Name or a description of the letter.
3. Location
Location information of the letter/checklist.
Page92
4. Is a Letter
Checklist to know if the letter is generated or not.
Inspection Details (Linked with Form)
1. F-ID
ID Number given to each facility.
2. I Type
Inspection type 1.
3. I Type 2
Inspection type 2.
4. Staff
This field contains staffs initials.
5. I Date 1
This field contains the date on which inspection was done.
6. Priority
This field contains the priority information of the inspection.
7. C Action
This field contains description of the compliance action.
8. C Date
This field contains compliance date.
Page93
9. Co Resp1
Inspection flag.
10. Inter LOW1
Inspection flag.
11. Co RespI3
Inspection flag.
12. Inter LOW2
Inspection flag.
13. Co RespI3
Inspection flag.
14. 10-day
Inspection flag.
15. Co Resp10
Inspection flag.
16. LOW2
Inspection flag.
17. Co Resp2
Inspection flag.
Page94
18. C Due
Compliance due date.
19. RTC Date
Inspection flag.
20. CA
Inspection flag.
21. Ref Date
Reference date
22. Comment
Unmatched Records
1. FACILITY NAME
Name of the facility with unmatched records.
2. FACILITY NUMBER
Facility number of the facility with unmatched records.
3. FACILITY TYPE
Facility type of the unmatched record facility.
4. ADDRESS
Address of the specific facility.
5. CITY
Name of the city where the facility is located.
6. ZIP CODE
Page95
Zip code of the city where the facility is located.

7. THIS FILES DATES
Date of day the file was created.
8. COMMENTS
Comments on the reports.
9. F-ID
Numeric number that is given to each facility.
3.1.2 Relationships
Procurement
Page96
Figure 3.1.2 shows the Relationship Diagram of Procurement
Page97
Warehousing
Figure 3.1.2 shows the Relationship Diagram of Warehousing

Page98
4.0 Functional Model and Description

4.1 Subsystem Flow Diagram
Figure 4.1 shows the sub-system data flow diagram of procurement and
warehousing
Page99
4.1.1 Create Checklist
Figure 4.1.1 shows the create checklist of procurement and warehousing
4.1.2 Print Checklist
Figure 3.1.2 shows the print checklist of procurement and warehousing
Page100
4.1.3 Generate Letter
Figure 3.1.3 shows the generate letter of procurement and warehousing
Page101
4.2 Human Interface

In the proposed environment without use of hand help inspectors from the DEQ
goes out to facilities with checklist in the paper format and records the violation in
a checklist. When inspector returns form the facility he or she has to insert the
data in to the database which uses visual basis as front end. The software uses
access as the back end system.
Inspector logs into the database using his or her id. The first screen that the
inspector will come across is labeled Desktop Project Organizer. It contains
seven buttons with several different options to choose from. User can choose a
button to add a new facility into the database, can find an existing facility, print
blank checklist for the next inspection. User can also choose button to print a
blank staff report, or to go to help menu, or to go to options page or exit out
Visual Basic environment.
Depending on the selection made from the selection described in the paragraph
above user will get several different windows.
Facility History window allows user to generate a new letter, checklist or staff
report. It also allows users to view, modify or print existing checklist. User can
also edit historic data, update family information or delete action using this
window. The window also contains help and return to main menu buttons.
Facility information window allows user to fill in facility information with entries
such as EPA ID, facility type, name, address, city, country, and zip code, also
information about owner or mailing address of the facility. It also allows users to
fill in any comments regarding facility information.
If user searched for existing facility and facility cannot be found user will be
shown facility information no match window that will have search again, add new
facility help or return to main menu options.
If users selects historic data option form the window above he or she will be
presented with the historic data window which will allow user to fill in data such
Page102
as inspection type, first inspection date, secondary inspection date, compliance

action, company response, inspectors information and completed activities etc.
In options window user will be allowed to change location of the database,
letters, help file location and location to saved generated letters. This window will
also contain cancel, save changes, help buttons.
From select a checklist window user can select a checklist to either fill out or print
a blank one of. From this screen you can also access the help file and return to
the Facility History screen.
From select a letter window user can choose the letter that you would like to
generate a letter for the facility that you are currently working on. You can also
access the help file and return to the Facility History screen.
Search for an existing facility window enables user to search for a facility that you
believe has already been entered into the database. You can search by name,
city, address, EPA ID, or any combination of the four. If one of your search
criteria is facility address that will be all that is searched on regardless of the
other search criteria you have entered. If at least one of your search criteria is
facility name or facility city and the exact facility 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, you can simply double click on that close match and you will be
taken to the Facility History screen where information about that facility will be
displayed. If none of the close matches are the facility that you are looking for,
you can either search again or add a new facility. if your facility is found through
the search, you will be taken to the Facility History screen and information about
that facility will be displayed.
From the Staff Report window user can either generate a commented staff report
for the facility which you are currently working on, print a blank staff report,
access the help file, or return to the Facility History screen.
Page103
5.0 Restrictions, Limitations and Constraints

Time
We only have about two months to finish all documentation, bug fixing and
enhancements. We have a lot of idea but cannot implement them due to time
constraint. One of the major ones is to move the application to be completely
browser-based.
Funding
To develop and implement the Palm Pilot integration, we will need funding to buy
at least one Palm Pilot. We will request the funding from University MichiganDearborn should we decided to pursue this function.
6.0 Validation Criteria
The proponent evaluation of tenders to suppliers is an important phase of the
procurement process. It is this process that determines the actual quality,
reliability, delivery, etc. of the goods and services.
analyzing and evaluating the bids against set criteria, specification requirements
and presenting the analysis to an appointed committee; this process is applicable
for both quotations
verification of supplier capability and quality control/assurance processes;
reviewing product inspection results where necessary;
verification of technical evaluation reports where applicable;
Negotiates with vendors where it is recommended by the committee; and places
orders and expedites the delivery.
Page104
Software Design Specification
1.0 Introduction
This section describes the design for the Waste Management Inspection
Tracking System (WMITS).
1.1
Goals and Objectives

The main purpose of WMITS is to help automate the entire process that
the Department of Environmental Quality (DEQ) Waste Management Division

(WMD) staff members perform throughout an inspection.
The goals of WMITS are:
To minimize the time span of any inspection
To minimize the amount of paper work required
To provide a searchable database of all past inspections
To provide an automated channel for the public to request information
(under Freedom of Information Act)
1.2
System Statement of Scope
The proponents must be aware the system implemented because sometimes

there is the circumstances system does not function. Proponents give details
what the system implemented and make sure that has a functionality in every
module execute of what data or information produced their system.
Page105

The following general requirements were identified and specified for the
Materials management procurement & Warehousing.
A way in which the company could purchase an item/product.

A way in which the company to request the item/product of each
employee or client.
A way in which in the item/product they needed to every day.
A way in which could add new facilities in the database.
Interface Enhancement
A staff members of procurement and warehouse have
requested a lot of interface enhancements that will increase the
usability of the product for the staff.
Database Administrative Interface

There is current no documented interface for procurement
and warehouse staff members to maintain the checklist and
letter templates. Should no such interface existed, and it will
have to implement one from scratch.
Web-based System
To develop an extensive help menu for the users and also to
setup the web-based system help for the need of company
bidding and help in the future.
Training
The staff of the procurement and warehousing have also
requested throughout training for the entire staff for use with the
software.
Page106
1.3
System Context
Eventually multiple users will be using the product simultaneously. Therefore,

concurrent connection will be an issue for implementation. In addition, this is a
pilot product that hopefully if the successful can be used in other location as well.
This leads to issues about future for a larger user base.

Time
We only have about two months to finish all documentation, software creation
and enhancements. We have a lot of ideas but cannot implement them due to
time constraint. One of the major ones is to move the application to be
completely browser-based.
Funding
To develop and implement the palm pilot integration, we will need funding to buy
at least one palm pilot. We will request the funding from University of Michigan
Dearborn should we decided to pursue this function.
2.0 Data Design
2.1 Database Description
3.0 Architectural and Component-Level Design
3.1 Program Structure
3.1.1 Overall
Page107
3.1.2 Create Inspection

3.2 Description for Components
3.2.1 Switch User
3.2.2 Facility
3.2.3 Create/Modify Inspection Step 1
3.2.4 Create/Modify Inspection Step 2
3.2.5 File Results Step 1
3.2.6 File Results Step 2
3.2.7 Approval
3.2.8 Checklist Maintenance
3.2.9 Letter Maintenance
4.0 User Interface Design
4.1 Description of the User Interface
Page108
4.1.1 Screen Images

Log-in Form
Log-in form-this is where the user type their username and password that can
log-in into the computer they will have, in this matters it is easy to them used this
log form because just type the username and password.
Page109
Mai
n
Me
nu
Main Form- this is where you can see the main form of Materials Management
Procurement and Warehousing (MMPW).
Warehouse Menu
Page110
Warehouse Menu- this is where you can explore the warehouse menu as you
can see there are three button add item, item list and report.
Add Item
Add Item- this is where you can and add item through encoding the code of item
number, item name, quantity, price, category and description of the product and
where you can save the information that you have just encoded and also you can
Page111
update the data in the computer and it is easily to find the product through
searching the code of the product.
Warehouse Reports
Warehouse report- this is where you can view from the warehouse report
of all the data of the product has already exported from purchasing
equipment through the supplier then after you can print it right away.
Pro
cur
em
ent
me
nu
Page112
Procurement menu- this is where you can search all the information of the
supplier/bidders and then after the bidding you can request the materials
need of the company.
Bidding Item
Requ
est
List
Procu
reme
Page113
nts report
Procurement report- this is where you can view from the procurement
report of all the data of the product has already exported from purchasing
equipment through the supplier then after you can print it right away.
4.1.2 Objects and Actions

1. Login Screen
User Name
User name can be ranged from 6 to 20 letters (numbers), as the industry
standard. No special characters, space. And mostly likely the users will use their
DEQ user name for this system as well.
There are 10 people using this project in DEQ, as current status. Eight of them
are inspector, one manager, and one network administrator. Even with a small
group like that, we are not going to use the drop down menu for the login name.
Page114
Logically speaking, drop down menu do save time, and more convenience. But
we change our mind after one of the inspector we correspond with make an
interesting comments, if someone cant even remember their login name, they
would find a new job. Furthermore, with a blind login name system, it will provide
extra level of security. Because its harder to get a users user name and
password compare to just get their password.
Password
Password can be ranged from 6 to 20 letters (numbers), as the industry
standard. No special characters, space.
Ok
If the users enter the right user name with the matching password, it will
immediately take them to the main interface.
Cancel
If the user wishes to exit the program, hit the Cancel button.
2. Main Interface
Menu Items
The following show the architecture of the main menu:
File
Switch User
Exit
Reports
Print Staff Report
Print Blank Checklists
Efficiency Report
(more TBD)
Facility
Inspection
Page115
Create/Modify
File Results
Get Approval
Print Letters
View Schedule
Maintenance
Checklists
Letters
Users
Options
Approval
Help
Contents
About
Switch User
Major Forms (s): frmLogin
Major Actions (s): Login
The form frmlogin will appear. User enters their username in txtUserNameand
password in txtPassword. Then click cmdOkay. User will be logged in if is a valid
username and password pair. If user clicks cmdCancel on this form, application
will end if they confirmed their action.
Facility
Major Form (s): frmFacility,frmFacility Browse, and frmFacility Search
Major Action (s): Browse, Search, Save, Delete and View
Browse
Object Name: cmdBrowse
To browse all facilities, user can click on the bomb button next to the
txtFacilityIDfield. frmFacilitySearch will appear. User can highlight a facility in the
grid, then click cmdOkay. All the information on frmFacility will be filled in.
Search
Page116
Object Name: cmdSearch

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 facility in
the result grid, the click cmdOkay. All the information on fromFacilitywill be filled
in.
Save
Object Name: cmdSave
To save button should be disabled unless the txtFacilityID field is filled in, and
any there have been changes made to any field on the frmFacility. When the
save button is clicked, new record will be generated if the facility ID does not
exist in the system, otherwise, current record will be updated.
Delete
Object Name: cmdDelete
The delete button should be disabled unless no historical data have been found
for the facility. The Delete and View button should never be enabled at the same
time.
View
Object Name: cmdView
The View button should be disabled unless no historical data have been found
for the facility. The Delete and View button should never be enabled at the same
time.
Create/Modify Inspection Step 1
Major Form (s): frmInspection, frmInspectionBrowse, frmInspectionSearch,
frmFacilityBrowse,andfrmFacilitySearch
Major Action (s): Create Inspection, Modify Inspection (Inspection Browse,
Inspection Search), Next Step and Add/Edit/Delete Date
Create Inspection
To create an inspection, user needs to enter a new Inspection ID in the
txtInspectionID field. To use an automatic number, click on the blank paper
button,
an
automatic
number
will
be
generated
and
filled
in
the
txtInspectionIDfield.
Page117
User also needs to enter the Facility ID. The browse and search functions are
identical to the ones in the Facility module.
Modify Inspection
To modify an inspection to enter an existing Inspection ID in the txtInspectionID
field. To browse all open inspections, user can click on the bomb button next to
the txtInspectionIDfield. frmInspectionBrowsewill appear. User can highlight an
inspection in the grid, then click cmdOkay. All the information on frmInspection
will be filled in.
Add Onsite Visit Date
User needs to click on the calendar icon, pick a date. txtTime can be left blank.
User can then click cmdDateAddto add the date to the grid.
Edit/Delete Onsite Visit Date
If a user highlights a row in the date grid, he or she can edit the contents in the
txtDate(using the calendar control) and txtTimefield. Then he or she can click on
cmdDateEdit to update the record. The user can also click cmdDateDeleteto
remove the highlighted row.
Next Step
frmPickChecklistwill appear. See Create/Modify Inspection Step 2 for more
info.
Create/Modify Inspection Step 2
Major Form (s): frmPickChecklist
Major Action (s): Print Checklist (s), Finish
For the second step user needs to pick the checklist (s) that they will be using for
the inspection using the initiative cmdAddand cmdRemovebuttons. Once they
have clicked cmdFinish, the inspection will be created/modified in the database.
File Results Step 1
Major Form (s): frmFileResult1, frmInspectionBrowse, and frmInspectionSearch
Major Action (s): Browse/Search Inspections, Next Step
Page118
To file inspection results, user needs to first select a previously created

inspection. He or she can use the standard browse and search function to locate
the inspection. After an inspection has been chosen, user needs to choose the
checklist (s) that they want to file the results. Click cmdNext to proceed to Step 2.
File Results Step 2
Major Form (s): frmFileResults2
Major Action (s): Add/Edit/Remove comments and status for each inspection
time.
Preview Letter, Spell Check (2)
Add Comments
To add comments for an inspection item in the checklist, user needs to highlight
an item in IstRegulations, enter comments in the txtComments and select status
in cboStatus. Then he or she needs to click cmdAdd. The item will be added to
IstInspected.
Inspected Comments
To remove comments for an added inspection item. User needs to highlight an
item in IstInspectedthen click cmdRemove.
Edit Comments
To edit comments for an added inspection item. User needs to highlight an item
in IstInspected. The comments for that item will be shown to the right. The user
can then update the comments and click cmdEdit to apply the changes.
Spell Check
User can check on cmdSpellCheck1 (for Add) and cmdSpellCheck2 (for Edit) to
check the spellings in the respective comments box.
Preview Letter
When cmdPreviewis clicked, the application will generate a letter in the right
portion of the screen. Which letter to use will depend on the letter in cboLetters.
Approval
Major Form(s): frmApproval,frmLetterDisplay
Major Action(s): View, Approved, and Deny
Page119
frmApprovalwill include a data grid that shows the approval request submitted by
the inspectors. The user has the option to view open or closed request on the
data grid. One a row has been highlighted, the user can click cmdViewto view the
letter. frmLetterDisplaywill appear. He or she then has the option to either
approve (frmLetterDisplay.cmdApprove) or deny (frmLetterDisplay.cmdDeny) it.
The
user
can
also
click
on
the
frmApproval.cmdApprove
and
frmApproval.cmdDenyto perform those
View
View details of the report
Redo
Send back to the inspector, either ask the inspector redo it, or take it over on
some details
Approval
Approval the report, and computer will generate a message, tells that the report
has been approval. Once the inspector sees the message, he/she will print out
the report, and send it to the facility.
4.2 Interface Design Rules

4.3 Components Available
4.3.1 Intrinsic Controls
4.3.2 ActiveX Controls
5.0 Restriction, Limitations, and Constraints
Time
Page120
Time is so far the biggest restriction or constraints for our project as we only have
around three months to finish entire project. It is very important for us to watch
the time we spend over every phase of the software development project. We
could have included many more components to the software like online help
menu but time restricts us from doing so.
Employee Skills
Employees programming and design skills is also one of the restriction. It does
not have a big of an impact on the project as time but it sure does limit us from
doing more addition to the projects.
Insufficient Resources
Not having all the necessary instruments also is a problem for our software. We
planned to use latest equipment for the project like Hand Held PC with keyboard
etc. but the employers cannot afford to provide such tools to all theirs employees
so we had to abandon the plans.
6.0 Testing Issues
6.1 Classes of Test
6.2 Performance Bounds

In a system development the proponents have a certain bounds of the
system implementing that will be able to maintain the quality of the system and it
is a user-friendly. In a search the function or process of the system will response
immediately in a 3 second of time and then, the browse function it will be next
then to the list of record in one second. From the log in user should be able to log
in within 0.1 second.
6.3 Identification or Critical Components
Page121
Test Specification
1.0 Introduction
This section provides an overview of the entire test document. This document
describes both the test plan and the test procedure.
1.1 Goals and Objectives

Overall goals and objectives of the test process are described.
1.2 Statement of Scope

A
description
of
the
scope
Functionality/features/behavior
to
of
be
software
tested
is
testing
noted.
is
In
developed.
addition
any
functionality/features/behavior that is not to be tested is also noted.

Any business, product line or technical constraints that will impact the mannerin
which the software is to be tested are noted here.
2.0 Testing Plan
Page122
We want the product to be bug free. We also want to make sure that there are no
defects in the product. So we will be spending large amount of the total software
development time on the testing. Below is the description of the testing
procedure and strategy. We will also be presenting the timing and scheduled of
the tests to be carried out.
2.1 Software (SCIs) to be test
2.1.1 Interfaces
Interface Components to be tested
Level editor
New World Wizard
New Sprite Wizard
Database Read/Write
File exporter
Engine Components to be tested
Object Handler / Engine Core
Data Loaders
Draw Handler
Sound Handler
Input Handler
Text Handler
Logic Handler
Help Components to be Tested
Help Files Search
Tutorials
Installation Components to be Tested
Software Install Process

Page123
Software Uninstall Process
2.2 Testing Strategy

In the following section we will describe the testing strategy. We will user four
different methods to test our product.
2.2.1 Unit Testing
In the unit test case we will be testing the separate modules of the software. We
will carry out white box testing where each module or component of the software
is tested individually. We will test the components by passing data through it and
we will be monitoring data to find the errors.
We will be looking for entry and exit conditions of the data. We will make sure
that all the components work without any troubles.
The test primarily be carried out by the programmer who designed and
implemented the module. Lead tester will carry out test on the modules to finalize
the testing.
2.2.2 Integration Testing
In this method of testing we will implement the software at the clients location
and will run it. So we will be testing the product on clients network. As art of
testing, will be looking for any signs of the collision between our software
components and those of the clients. We want to make sure there is no
confusion among the application on the network when they are running
simultaneously.
Page124
We will install the software at the clients site and will run it. We will have several
different other applications open as well. This applications will be the once that
have to interact with our software on normal bases. We will make sure that all the
data is saved correctly and there is no loss of data or database anomalies in the
product.
We will start from the login window and will go through all the software functions
and will test. We will be carefully looking for any sort of collision between several
different applications.
2.2.3 Validation Testing
In this method of test we will be working with the customer to find out if the
software developed in valid for the clients. We want to make sure that the client
is getting what he asked for. We will look at the software requirement document
in the case of conflict or misunderstanding with client regarding software
components.
We will perform the black box testing where the software is completed and we
test all the software components together. We will have several input data or test
data that we will derive results for. We will insert this data in the software and will
get results from the software. We will compare the results from the software with
the results that we derived. This way will check for the validation of the software.
In case there are problems with the software we will create a deficiency list and
will records all the problems in there. We will test all the components and
subcomponents of the software to perform the validation test.
We have and will try our best so that we dont have to create a deficiency list.
This is necessary because if the errors are found at this stage of the software
development we cannot fix them by the time we reach the software deliverance
date. In this case we have to negotiate with the customer to give us extension on
the project.
2.2.4 High-Order Testing
Page125
Recovery Testing
No Recovery testing will occur. While system failures are undesirable,
termination of the program in the event of a crash is acceptable.
Security Testing
No Security testing will occur. There are no security issues.
Stress Testing
The world builder and the engine will be loaded with abnormally high sprite
counts (with attributes and sounds) to determine how much Game Forge can
handle.
Performance Testing
The engine will be loaded with an increasing number of sprites while the frame
rate is monitored using the Frame Rate Counter.
2.3 Testing Resources and Staffing
Resources
No special resources are required beyond those already needed for
development.
Staffing
Test Team Leader Caroline Magtangob
Unit Testing Coordinator Florita Cabugos
Integration Testing Coordinator Elvin Ceno
System Testing Coordinator Mark Anthony Tenorio
Beta Testing Coordinator Mark Joel Lastimosa
Page126
2.4 Test Record Keeping

Test record keeping and Test work Products are described in section 3.4 of Test
Specification Document. For Information these topics, please refer to section 3.4
of the Test Specification Document.
2.5 Testing Tools and Environment

The proponents are used as testing tools as well as the testing environment. Test
data files will be constructed for unit and integration testing. A Frame Rate
Counter is also used in determining program performance. There are no other
special tools or hardware.
2.6 Test Schedule (WBS)
Page127
MM-Procurement&Warehousing
System
Analysis
System Planning
Develop the
project
Gathered
Information about
the system
Project
Scope&Out
of Scope
Determine the
business flow
Bidding
Warehouse
flow
Procurement
flow
System Design
System
Implementation
Interface
Design
Request
purchase
report
Determine the
problem
Userfriendly
Bidding
report
Analyze the
business flow
Has a good
features of the
system
warehouse
report
Review the
related
study&system
Graphical User
Interface
inventory
control
Research local and

foreign studies
Add Item
System
Maintenance&
Operation
Technical
problem
Debugging
Fixing
errors
Troublesho
oting
print
Update
Stock Monitoring
level
Construct matrix of
related studies
Notification
Draft of Chapter 3
Figure 2.6 it shows the WBS-word breakdown structure of the planning step for
the project development
3.0 Test Procedure

In this section we will describe the test procedures in detail.
3.1 Software (SCIs) to be tested
Page128
For detailed list of the software components items please refer to section 2.1
from the Test Specification document.
3.2 Testing Procedures
In this section we will try to describe over all software specification. We will
describe the methods for all the different tests to perform and will also declare
the expected outputs.
3.2.1 Unit Testing

In this method of testing we will test the smallest unit of software called modules.
We will be testing all the important paths to find any errors within the boundary of
module. So here we will apply sort of white box search. We will be testing parts
of the software rather than the entire software. The modules are as follows.
Login Window
The proponents make use several different names to log in to the system.
It will use to correct and incorrect usernames and password to access the
software and thus access database. And will not be allowed to log in using
incorrect password and error message will be shown. When correct password is
presented we will be able to log in be able to next window (Database language).
It will also test Ok and Cancel buttons on this window by performing test.
File:
When the file button is clicked user will be shown two choices.
Switch User
Proponents will test if the switch user button works. We
needs to make sure that the log in screen is presented when this
Page129
choice is selected. It will test this by choosing the switch user and
then by logging in as another user log in window.
Exit
Proponents want to make sure that user is logged out or is
able to exit button is selected. It will testing it by first logging in as a
user then by utilizing exit button to exit out.
Facility:
When the facility button is clicked proponents will be presented with facility
screen. It can add and edit facility using the screen. The test to make sure that
the facility screen is presented when the button is clicked. It will do this by
clicking on the button and making sure that the facility screen is presented
Inspection:
When inspection button is clicked user will be shown five choices.
Create/Modify
When click on this choice will be presented with inspection step 1
screen used to create or modify inspection. Just to make sure that this
screen is presented when selection is made. It will test it by making the
selection in drop down menu and by making sure that the correct window
is presented.
File Results
When proponents select this choice it will be presented with file
result window. The test of button by clicking on it to go to file result
window.
Approval:
Page130
This option is presented and works only for manager. As a proponents

need to make sure that when someone other than inspector loges in the button is
disabled. Proponents will do this by logging in as both as inspector and as
manager. It will make sure that manager is able to use button while inspectors
will not be able to use it. And also we need to make sure that when selected by
manager software will bring up window containing queued list of letters waiting to
be approved.
Reports:
Print Staff Reports
When the proponents select this choice that will be presented with
report window. In the test of button by clicking on it to go to report window.
We want to make sure that the proper window is presented.
Maintenance:
Users
users window. In the test of button by clicking on it to go to users window.
We want to make sure that the proper window is presented.
Options
option window. In the test of button by clicking on it to go to option
window. We want to make sure that the proper window is presented.
Help
Page131
Content
content window (help contents). In the test of button by clicking on it to go
to content window. We want to make sure that the proper window is
presented.
About
about window (window with software info). In the test of button by clicking
on it to go to about window. We want to make sure that the proper window
is presented.
Inspection Generator Window
This window is to allow inspector to generate the inspection id before
actually going out for inspection. This will have several windows to select options
form and also button test from.
Next Button
The proponent want to make sure that when we click next after
filing out all information in this window. They are presented with the print
checklist window from this window we will be able to select blank checklist
and print it out.
Cancel
The test of cancel button to make sure that when clicked it will
cancel all the work done or will delete all the options selected and will take
us to main window.
Help
Page132
Proponents will check the help button to see if the help menu is
made available to the user when help button is selected. The menu should
popup without any problems when help button is selected.
Print Inspection Form Window
This window will allow inspector to select and print blank print list.
Proponents want to make sure that all the available print lists are made available
and that inspector is able to select them.
Print Button
To use print button and to make sure that this will bring up print
menu to send print job to desired printer. This should work without any
problem.
Cancel
us main window.
Choosing Inspection Window
Adding Removing Inspection
Proponents want to test the box that allows us to select and
add/remove inspection checklist from the selected checklist box. They will
do this by selecting checklist from given list and then by adding it to
selected checklist box.
Cancel
us main window.
Page133
Next
The test of next button to see if it takes us to main checklist
window. And will do this by filing in all information and then clicking to next
button
Main Checklist Window
Adding item from item box to regulation box
The proponents has also test if it can add more than one item in to
the inspected item boxes from the regulation box. If the software is written
correctly that should be able to do this without any troubles.
Selected Checklist Items

Remove Item
If the test are able to remove an item from inspected item box by
using remove highlighted item button that will make sure if only selected
item is removed in case the box contains more than one item in it. If the
program is written correctly this should work.
Preview Button
If the test preview button to see if the letter is generated in the
window to the right of the generate checklist window. This window will
contain the letter with listing of all the regulations selected. The letter
should generate without any troubles.
Update Button
Page134
Proponents will use update button to see if the changes made to

the checklist are updated so that things to be removed are removes and
things to be added are added.
Help
Proponents will check the help button to see if the help menu is
made available to the user when help button is selected. The menu should
Save Button
At the end will test the save button to see if all the data is correctly
recorded and the generated letter is saved. This should work without any
troubles.
Inspection ID Explode Window
This window will come up when explode button is selected form choosing
inspection window. It is created to allow user to find the inspection id.
Ok Button
The test of Ok button that should take us back to choosing
inspection window with the inspection id number in the box and that will do
this by selecting the id and then clicking on the Ok button.
Cancel
us main window.
View Button
The test of view button which will able us to view the inspection id
record. The test of this button by selecting id and then clicking the view
Page135
button that will present us with data. And will also test it the button by not
selecting any inspection id and clicking view button. This will not bring us
to any other window since no selection is made.
Creating Facility
This window is utilized to create a facility entry in the database if facility
does not exist. User will have to simply complete from with text boxes and few
drop down menus.
The proponent make sure it will have the function that will check if the
boxes are filled when we hit the save button after the completion of the form. This
will not apply to the boxes that are in mailing information section or owner
information section. If any other box from remaining section other than fax
number is left blank error message will be shown and user will be told to fill the
box to proceed ahead. In test this by leaving some of the boxes empty that needs
to be filled. This will leave fax number boxes empty and this should not give us
any error messages.
Facility ID Box
Facility id box will contain the id assigned to new facility. It will
make sure that the box accepts all the characters and number in id. The
test make sure that the record is updated or added in database. Also we
will test to make sure that this box is not allowed to leave blank.
Search Button
This will also test search button (button with bomb), this should
bring up the window that will allow us to search for the facility id.
Facility Type Box
Facility type box will contain facility type. It will make sure that user
is able to put in data in the box and that the data is correctly inserted in the
database. The test by filing in box with some numbers and clicking save
Page136
after all the data is filled. This will also leave the box empty and we click
save, it will display error message saying the box is empty.
Name Box
Name box will contain the name of facility. It will allow name as long
as it want to be. We will test several names to test this box and will make
sure that data is updates in the database. And also want to make sure that
this box is not allowed to be left blank. This can be done by leaving the
box blank while clicking the save button which will give us error message.
Address Box
Address box will contain the address of the facility. It will allow
address to be as long as it want to be. We will use several different
addresses to test this box and will make sure that data is updates in the
database. It also want to make sure that the box is not allowed to be left
blank. Test can be done by leaving the box blank while clicking the save
button which will give us error message.
Contact Box
Contact box will contain the name of contact person at the facility. It
will allow name to be as long as it want to be. We will use several different
names to test this box and will make sure that data is updates in the
database. And also want to make sure that the box is not allowed to be left
blank. Test can be done by leaving the box blank while clicking the save
button which will give us error message.
City Box
City box will contain the name of the city that facility is at. It will
allow city name to be as long as it want to be. We will use several different
addresses to test this box and will make sure that data is updates in the
Page137
database. And also proponent want to make sure that the box is not
allowed to be left blank. Test can be done by leaving the box blank while
clicking the save button which will give us error message.
Zip Code Box
Zip code box will allow only five letter and no characters. If letters
typed are less than five letters error will be shown. Error will also be
shown if the character is typed in. In this test also insert incorrect data that
contains characters and less than five letters. This will give us an error
message.
Fax Number Box
Fax number box will only contain numbers and no characters. If the
character is typed in it will show error message. It will test the box by
typing in correct and incorrect data. Incorrect data will give us error.
Correct data should be stored in database.
Phone Number Box
Phone number box will contain the phone number of the facility. It
will allow the number to be 7 or 10 digits long. It is use several different
numbers to test this box and will make sure that data is updates in the
database. And also want to make sure that the box is not allowed to be left
blank. The test can be done by leaving the box blank while clicking the
save button which will give us error message. It is use numbers that are
more or less than seven digits but not more than or equal to 10 this will
show us error message and will not allow us to proceed forward.
Comments Box
In comments box user can insert unlimited lines of comments. It will
test to see if comment is correctly inserted into the form and also in
Page138
database. Test by filing it with data and those by clicking save. This should
work without any problem.
Save button will save the data in database. The test of the button to
see if the data is actually saved and that database is updated
Help Button
It will check the help button to see if the help menu is made
available to the user when help button is selected. The menu should
Save
At the end will test the save button to see if all the data is correctly
recorded and the generated letter is saved. This should work without any
troubles.
3.2.2 Integration Testing

In this method of testing proponent implement the software at the clients
location and will run it. So that it will be testing the product on client network. It
will start the test with login window and then main Java language window. After
the java language we will be testing each and every sub component or functions
of the software. Using stubs to perform test. Stubs are dummy functions that we
will use to test the separate modules. Each of the module to be tested will have
its own distinct stub, the stub will be created depending on the function of each
software component. Stub will help us to test the product without actually having
all the functions of the software.
As part of testing, will be looking for any signs of the collision between our
software components and those of the clients. We want to make sure there is no
Page139
confusion among the application on the network when they are running
simultaneously. Each of the software items will be test case for the integration
testing. So each form as whole will be a test case. It will be testing each and
every form for all the errors that logically can occur in it.
It will install the software at the clients site and will run it. We will have
several different other applications open as well. This application will be the one
that have to interact with our software on normal bases. It make sure that all the
data is saved correctly and there is no loss of data or data base anomalies in the
product. At the end of the test all the results should be positive. All of the
software components should work properly. In case we come across the errors
will record them in the error document and these errors will be fixed at the latter
time.
3.2.3 Validation Testing
Testing Procedure for Validation
The feature and functionality in the final system will be cross-referenced with the
Software Requirements Specification document to verify that the software
demonstrates conformity with the requirements.
Test Cases and their Purpose
Features corresponding to the design requirements will be evaluated.
Expected Results
The software will perform within the specification of the software requirements
document.
3.2.4 High-Order Testing

High-order test are combination of several different test methods. It will be
performing four different tests on our software. These test will be performed at
Page140
software developer facilities and at the client site using the hardware that are
available to clients.
Recovery Testing
No Recovery testing will occur. While system failures are undesirable,
termination of the program in the event of a crash is acceptable.
Security Testing
No Security testing will occur. There are no security issues.
Stress Testing
The world builder and the engine will be loaded with abnormally high sprite
counts (with attributes and sounds) to determine how much can handle.
Performance Testing
The engine will be loaded with an increasing number of sprites while the frame
rate is monitored using the Frame Rate Counter.
3.3 Testing Resources and Staffing
Testing Resources
No special resources are required for testing beyond those already needed for
development.
3.4 Test Record Keeping and Log
Page141
Microsoft Excel will be used to evaluate immediate test results. After the results
have been evaluated, they will be submitted to a Mysql express database for
storage.
A test log is kept to monitor the tests that have been applied. An error, or buglog
is kept to monitor any problems that have arisen during testing. Also, a betatester
report form exists to aid beta testers in organizing their communication with PA
Software.
Page142

Ps 2 Revise

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Ps 2 Revise

Încărcat de

Drepturi de autor:

Formate disponibile

Chapter 1

1.0 Project Background

1.1 Problem/Opportunity Description

Inaccurate information in the system

Delays in delivery of supplies

Orders for out-of-stock items are automatically back-ordered and filled

Difficulty locating items as they are moved within the warehouse

Equipment losses or damage

Service Management System (MM Procurement and Warehousing)

business needs with rich reporting and analysis capabilities, customizable

1.4 Stakeholders and Clients

Service Management System (MM Procurement and Warehousing)

2.0 Project Scope

Estimation of cost and price of the equipment

Request purchase order

Checking the items if it has been losses or damage

Service Management System (MM Procurement and Warehousing)

Service Management System (MM Procurement and Warehousing)

checking the items

Figure 2.1.1 it shows here the procurement and warehousing

Service Management System (MM Procurement and Warehousing)

2.1.2 Service Management System-(Materials Management Procurement and

Procurement and Warehousing

Service Management System (MM Procurement and Warehousing)

Service Management System (MM Procurement and Warehousing)

2.2 Project Deliverables

This is where the company finds bidders that

will give the right price, the right cost and

the company and it must have a good quality

Request Purchase Order

in purchase order of equipment from the

This process where staffs add other

efficient and will generate during encoding

Service Management System (MM Procurement and Warehousing)

Objectives 2- Warehousing-Inventory Control

obligation as a part of the companys supplier.

In warehousing management, the

staff/employee should monitor the level of stock

of the equipment that will be avoided in critical

level in storage like overstocking of equipment

but this system it will have a notification in the

critical level of stock.

The receiving and checking item, this is very

significant in a business environment especially

Service Management System (MM Procurement and Warehousing)

In this section, this is where the company needs

User is also need to update their information

because it is important mostly from the bachelor

Salary/ payroll of the employees

3.0 Project Plan

the strategy are

accompanied by Illustrative examples from existing operations. But

System Implementation- this is where you can implement a system

Service Management System (MM Procurement and Warehousing)

3.2 Project Timeline

Service Management System (MM Procurement and Warehousing)

Service Management System (MM Procurement and Warehousing)

Service Management System (MM Procurement and Warehousing)

Service Management System (MM Procurement and Warehousing)

3.3 Success Criteria

The system can save & store large number of files.

The systems process becomes fast because the GUI is easy to

The system can lessen the time needed to finish transaction.