Professional Documents
Culture Documents
Page1
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
Service Management System (MM Procurement and Warehousing)
Page3
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.
Bidding
Supplier
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
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
notification
monitoring
Page7
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
Project Deliverables
Work Products/Description
Suppliers
Page10
Project Deliverable
Project Deliverable
Work Products/Description
Work Products/Description
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
es
3-
Stock Monitoring
Inf
or
ma
tio
up
dat
e
Receiving and
Checking Item
Page11
their products.
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.
Contract management
described,
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.
Page13
Page14
Page15
Page16
Page17
The system can view the files that you want to see. Its done to
prevent printing from time to time.
Property Monitoring.
Risk Factor
Financial Risk
Probability
Impact
(H-M-L)
(H-M-L)
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
Risk
Compliance Risk
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.
Page19
Java Eclipse
MS SQL
Java Netbeans IDE 8.0 used for the development of project and it is
very useful using this programming language.
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
Project Manager
System Analyst
Business Analyst
Magtangob, Caroline F.
responsibilities
time
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
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
Description
Budget cost
P1,300.00
their documentation.
P100.00
proponents contributes
P20.00
money.
Page23
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
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.
Service Management System (MM Procurement and Warehousing)
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:
Functionalities:
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
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.
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
Service Management System (MM Procurement and Warehousing)
Page29
through
systematic
process.
Warehousing
and
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.
Service Management System (MM Procurement and Warehousing)
Page30
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
Price list
Items profitability report
VAT Report
Page32
Monthly statistics
Price & cost comparisons
Page33
Page34
Procurement Module
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.
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.
http://www.ogersystems.com/pdf/Warehousing_Procurement_Document.pdf
core
warehousing
functionality,
ACCPAC
WMS
provides
Page36
COMPLETE CONTROL
Page37
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
Service Management System (MM Procurement and Warehousing)
Page38
coordinated to
picking activities
without
interruption.
Functionalities:
A.
features
ON-TIME DELIVERY
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
and
the
equipment
available.
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:
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:
Page40
The Ewcs (warehouse control system) WCS layer covering all features
related to the material flow control:
visualization
Ewcs
consists
of
two
main
modules
Page41
deep,
double
deep,
multi
deep.
by
an
individual
transport
means.
transport orders.
Page42
Page43
Reports
Delivery Schedule
Stock Ledger
Purchasing History
Bill of Materials
Inventory Stock
Application Features
Page44
Page45
Reduction of paperwork.
http://www.cerquit.com/Products/Warehouse-InventorySystem
Page46
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.
Page48
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:
http://www.mypurchasingcenter.com/purchasing/industryarticles/strategic-approaches-materials-management-industrial-projects/
Page50
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
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
Service Management System (MM Procurement and Warehousing)
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.
Category
Employee risk
Risk
Probability
Impact
30%
Slow process
55%
35%
25%
experience
Process risk
Product size
and
Inconsistent
the
Page54
Development
process of delivery
risk
Failure to communicate
15%
50%
40%
Customer risk
Technology
will
not
Meet
Late delivery
impact
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
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
Employee Risks:
As part of the team it must have to cooperate or to make an effort
In a procurement
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
Service Management System (MM Procurement and Warehousing)
Page56
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.
Risk
Probability Impact
experience
Slow process
55%
Process risk
Product size
Development
and
Inconsistent
the 25%
15%
process of delivery
risk
Failure to communicate
Customer risk
Service Management System (MM Procurement and Warehousing)
Page57
Technology
Technology risk
will
not
Meet 50%
40%
Business
impact
Description
H-high
Catastrophic
M-medium
Critical
L-low
negligible
Page58
Page59
particular facet of the development tools will need to instruct those who are
not as well versed.
3.1.6 Development Risks
Service Management System (MM Procurement and Warehousing)
Page60
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.
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.
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.
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.
Page65
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
Service Management System (MM Procurement and Warehousing)
Page66
Adviser
Client
Service Management System (MM Procurement and Warehousing)
Page67
Developer
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
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.
Configuration Control
Description
Page69
Level of control
approved.
2.2.1 Description
The proponents will change and controlled the human procedures
and that will be automated processing of the procurement and
warehousing.
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.1Description
1.0 Introduction
The proponents will give an overview about this Software Quality
Assurance plan for the development of the system.
Fixing error
Documentation
Editing
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
System Analyst
Business Analyst
Documentary Specialist
Lead Programmer
Gathering (brainstorming/meeting)
Number of item
Page72
3.2 Responsibilities
Page73
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.
Page74
by importing direct
Report:
Purchase Orders status report
Detailed listing of item transactions
Price list report
Page75
Time
The proponents only have an approximately five months to finish all
documentation, software and interface enhancements. This is a disadvantage
Service Management System (MM Procurement and Warehousing)
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.
This section describes overall system function and the information domain
in which it operates.
Page77
Page78
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
Warehousing
Page81
Figure 3.1 shows the sub-system data flow diagram of procurement and
warehousing
Page82
Page83
Page84
1.1
warehousing
and
procurement
coordinates
procedures
of
Page85
Management
System
with
the
sub-system
MM-Materials
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.
2.1 Use-Cases
Service Management System (MM Procurement and Warehousing)
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
Page88
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
Service Management System (MM Procurement and Warehousing)
Page89
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
Service Management System (MM Procurement and Warehousing)
Page91
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.
Service Management System (MM Procurement and Warehousing)
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.
Service Management System (MM Procurement and Warehousing)
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.
Service Management System (MM Procurement and Warehousing)
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
Service Management System (MM Procurement and Warehousing)
Page95
9. F-ID
Numeric number that is given to each facility.
3.1.2 Relationships
Procurement
Page96
Page97
Warehousing
Page98
Figure 4.1 shows the sub-system data flow diagram of procurement and
warehousing
Page99
Page100
Page101
Page102
Page103
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
1.0 Introduction
This section describes the design for the Waste Management Inspection
Tracking System (WMITS).
1.1
1.2
Page105
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.
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
3.1.1 Overall
Page107
Page108
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
Service Management System (MM Procurement and Warehousing)
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
Service Management System (MM Procurement and Warehousing)
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.
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
Efficiency Report
(more TBD)
Facility
Inspection
Service Management System (MM Procurement and Warehousing)
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
Service Management System (MM Procurement and Warehousing)
Page116
an
automatic
number
will
be
generated
and
filled
in
the
txtInspectionIDfield.
Service Management System (MM Procurement and Warehousing)
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
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
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.
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
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.
description
of
the
scope
Functionality/features/behavior
to
of
be
software
tested
is
testing
noted.
is
In
developed.
addition
any
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
Database Read/Write
File exporter
Engine Components to be tested
Data Loaders
Draw Handler
Sound Handler
Input Handler
Text Handler
Logic Handler
Help Components to be Tested
Tutorials
Installation Components to be Tested
Page123
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
Service Management System (MM Procurement and Warehousing)
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
Service Management System (MM Procurement and Warehousing)
Page126
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
Add Item
System
Maintenance&
Operation
Technical
problem
Debugging
Fixing
errors
Troublesho
oting
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
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.
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
Service Management System (MM Procurement and Warehousing)
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
Help
Service Management System (MM Procurement and Warehousing)
Page131
Content
When the proponents select this choice that will be presented with
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
When the proponents select this choice that will be presented with
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
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 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
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 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.
Page134
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
Service Management System (MM Procurement and Warehousing)
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
Service Management System (MM Procurement and Warehousing)
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
popup without any problems when help button is selected.
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.
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.
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.
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