PROJECT MANAGEMENT PLAN

AmberGrey
Dress Shop
Inventory and Record System Project Proposal

ICT & CHEMISTRY PROJECT

Submitted by:
Esperanza R. Sabangan
Esperanza R. Sabangan
Esperanza R. Sabangan

Submitted to:
Rowena Andaya-Reyes
Esperanza R. Sabangan
DOCUMENT CONTROL

MAKATI SCIENCE HIGH SCOOL

Project AmberGrey Document
Trail
10/15/2016 Initial Draft Project Plan Engr. Jaime P. Licuanan
Revision history
10/29/2016
Final Draft Project Plan Engr. Jaime P. Licuanan

Project AmberGrey Document

Details
CLIENT NAME: AmberGrey Dress Shop

LOCATION: Taytay, Rizal

NATURE OF BUSINESS: Garments Retail

BUSINESS CATEGORY: Small (Less than 10 with Proprietor as the owner)

PROJECT LOCATION
The countrys project origin is Philippines and it will be entirely
situated in the City of Rizal for the project clientele, which is AMBERGREY
Dress Shop, is located at Taytay, Province of Rizal. All meet ups will be held
within the vicinity and stakeholders meetings at the AMBERGREYS office
conference room. The alpha and beta testing of web-based Inventory and
Record System will be conducted at the AMBERGREYS accounting office
in the presence of all office staffs and the proprietor, all of them will be
participants to do the evaluation for acceptability of the developed Inventory
and Record System on the level of functional suitability and usability based
on ISO 25010 software engineering standards.

2
INTRODUCTION
The Inventory and Record System (IRS) facilitates the operation of

MAKATI SCIENCE HIGH SCHOOL

AMBERGREY. The primary goal of the system is to facilitate lending by
tracking the status of AMBERGREY inventory and record system and
enables users to perform related business activities. The users of the
inventory and record system are AMBERGREYS employees. They use the
system to maintain an accurate inventory, document lending activities and
other business operations for AMBERGREY.

The AMBERGREYS IRS is a database-driven web site. The site is

organized into two sections. The inventory and record section provides the
user with all of the primary functionality for which the system exists. The
administration system exists to support the operation of the inventory and
record section. Users operate within the record section for all day-to-day
activities, and use the administration section for special-purpose and
occasional activities.

Operational Concepts

The Inventory and Record System is a real-time inventory database

capable of connecting multiple users. This can be used to track the
inventory of a single store, or to manage the distribution of stock between
several branches of AMBERGREY in the future if larger franchise. However,
the system merely records sales and restocking data and provides
notification of low stock at any location through email at a specified interval.
The goal is to reduce the strain of tracking rather than to handle all store
maintenance. Further features may include the ability to generate reports of
sales, but again the interpretation is left to the management. In addition,
since theft does occasionally occur, the system provides solutions for
confirming the store inventory and for correcting stock quantities.

OBJECTIVES

AMBERGREY needs a customized, flexible, scalable web-based

system to manage inventory assets, create and fulfill orders from an
inventory database. Upon completion of the development of the site,
AMBERGREY will assume responsibility for web site content maintenance
and administration. All content, coding and graphics will become the sole
property of AMBERGREY. Additional consulting for expanded services
and/or programming outside of the scope of this Request for Proposal will
be arranged under separate contracts. Any design, programming, or
services that fall under the purview of this proposal will be included in the
design and development costs quoted. Programming problems resulting in a
lack of comprehensive testing will be resolved without additional fees. Upon
successful completion of the project, additional hours for new features and
regular maintenance may be negotiated.

3
Specific Objectives

Our primary project objective is to provide an efficient asset-management

tool for employees to use in the following ways:

MAKATI SCIENCE HIGH SCHOOL

1. Track current inventory and location.
2. Track inventory usage.
3. Support for sub-letted and temporary items. (expiring items)
4. Streamline reservations of equipment for production events
5. Allow administrators to quickly see where needs are for equipment
purchases. This may be part of an overall reporting system.
6. Ability for administrators to run inventory and scheduling reports
7. The ability to add custom line items to any order may or may not be
related to inventory.

Project Vision

1. View in house inventory

2. Improve order process efficiency
3. Provide focused web-based solutions that work on both desktop and
mobile devices.
4. Reduce possibility of human error.
5. Increase productivity, reduce time to build orders and check availability.
6. Error checking before order creation.

Primary Goals of the Project

1. Engage a web development/design consultant to assist in

analyzing the current state of AMBERGREYs web presence, identify
and implement critical improvements, and develop a modern,
compelling interface design (look and feel) and a set of design
templates for AMBERGREYS Inventory and Record System.

2. Create a complementary set of designs for AMBERGREYS

Inventory and Record System making the web site accessible to any
type of mobile devices, ensure that AMBERGREYS Inventory and
Record System is mobile friendly and develop a strategy for the
AMBERGREYS online presence on mobile devices

3. Create a fluid and rewarding web portal information architecture

that reflects the needs of AMBERGREY stakeholders and
encourages positive user interactions

4. Establish a strategy that articulates how the web will be used as a

communications and teaching and learning tool aligned with the
AMBERGREY goals and objectives

5. Establish policy and standards for web-based inventory and record

system management, design, content, presentation and development
for creating consistent and professional web content.

4
Specific Objectives and Success Criteria

Objective Description Success Criteria

1. IRS design must be compliant The banner of IRS meets the

MAKATI SCIENCE HIGH SCHOOL

with AMBERGREYS identity specifications documented at
standards http://ambergreydressshop.we
ebly.com/
2. IRS design must be AMBERGREY approval
aesthetically pleasing and
convey an impression of
modernity, scientific
excitement, and educational
excellence
3. Users must be able to IRS must follow User Interface 1. fewer phone contacts from
navigate and orient easily standards, render properly on all people seeking information that is
major browsers and operating available on IRS
systems 2. positive reactions from people
using IRS
3. AMBERGRES employee and
clients are able to find information
easily
4. IRS must be easy to maintain IRS structure will allow non- After training, AMBERGREYS
technical staff to update content; office staff will be able to enter
dynamic elements will be and modify content without
managed through user-friendly difficulty. New content managers
forms will be able to come up to speed
with only one or two hours
investment in learning the
system.
Documentation and training will be
provided for content managers
and authors
5. IRS must be robust and Site uptime >99%
perform well Average page load time < 5
seconds average (except on
dialup connection)
Site renders correctly on all major
browsers and in print
6. IRS content must be Content will be entered and All issues identified in QA are
comprehensive and accurate proofed for every page specified in corrected and verified; Client
the site map (by client) approval or any other
independent QA at clients option

Project IRS Continuity

The Project Manager will work with WEBEXPERT which is

AMBERGREYS previous website developer and WEBMASTER the present
about AMBERGREYS web-based Inventory and Record System developer.
The project manager will be responsible to talk to the owners to arrange for
taking the sites live, using the standard transition checklist for web site. The
newly developed web-based IRS will be linked to the old or existing site.

A redirect utility will be built into the new web-based IRS to capture
attempts to access present AMBERGREYS website urls (as from existing
bookmarks) and redirect them within the new AMBERGREYS IRS. Unless
all such accesses are directed to the new home page, the clients will fill in a
Legacy Links Redirection List, identifying where each old-site link is to be
directed.

5
Description

Create a flexible, scalable web site that is easy to maintain. We must

develop a user-friendly site driven by data stored within a relational database. In

MAKATI SCIENCE HIGH SCHOOL

addition to designing a user-friendly site with an intuitive interface, we must also
develop a web-based, database-driven administration tool that allows key
management personnel to easily update content without directly accessing
source code. The site needs to be viewable by authorized employees, and it
needs to have an administrative backend for authorized users to control
inventory assets and scheduled usage of these assets. The order creation
process should have a shopping cart feel. Quotes will need to be turned into
orders; every quote/order will also have a job number associated with it.

AMBERGREY will maintain ultimate editorial control of content.

AMBERGREY employees will efficiently manage web-publishing processes - Ipsum by
using a system with a browser-based user interface. Administration of web
content will be based on roles to control access and work flow (e.g. super-user,
administrators, editors and read-only authorized users).

The site/database would require the following:

Design components:
1. Works on mobile devices (iOS)
2. Easy and intuitive
3. CSS colors optimized for easy viewing.
4. Quick to load and use
5. Branded with provided AMBERGREY graphics/style guide.
6. Visually appealing
7. Works the same way on cross-platform systems via multiple current browser
interfaces (IE, Firefox, Chrome, Safari, Opera).
8. End users can print quote order and inventory results to a PDF page branded
with AMBERGREY branding. (Sample Attached)

Technical components:
1. Written in PHP
2. Resulting pages rendered in HTML5
3. Styled using CSS
4. Database-driven (MySQL preferred)
5. Strict enforcement of data relationships (either DB level or programmatic
level)
6. Calendaring system that checks for time conflicts of equipment reservations
including publishing of calendar data to CALDAV server.
7. Built in system to enforce time constraints and notification of staff.
8. Safe and secure from web exploits, cross scripting, and MySQL injections
9. Error checking for duplicate inventory items
10. Grouping of items for consolidated items (cube, etc)
11. Error checking for overlapping inventory checkout events
12. Javascript code is allowable if security is not compromised, and only if it
enhances usability.
13. Record and list views. Minimal drill down, interface should be easy to read
on smaller screens and not require complicated navigation.
14. Notification system via e-mail.

6
 PLANNING

PROJECT SCOPE MANAGEMENT PLAN

MAKATI SCIENCE HIGH SCHOOL

Scope management for the AMBERGREYS Inventory and Record
System will be the sole responsibility of the Project Manager. The Scope
Statement, Work Breakdown Structure (WBS) and WBS Dictionary define
the scope for this project. The Project Manager, Sponsor, and Stakeholders
will establish and approve documentation for measuring project scope which
includes deliverable quality checklists and work performance
measurements.

The Project Manager, Stakeholders or any member of the project

team may initiate proposed scope changes. All change requests - Ipsum
will be
submitted to the Project Manager who will then evaluate the requested
scope change. Upon acceptance of the scope change request the Project
Manager will submit the scope change request to the Change Control Board
and Project Sponsor for acceptance. Upon approval of scope changes by
the Change Control Board and Project Sponsor the Project Manager will
update all project documents and communicate the scope change to all
stakeholders. Based on feedback and input from the Project Manager and
Stakeholders, the Project Sponsor is responsible for the acceptance of the
final project deliverables and project scope.

1. Scope of Work:

1.1. Methods and Activities

The proponent of AMBERGREYS Inventory and Record System

will be using the agile software development based on Agile Software
Development Quality Assurance, which refers to a group of software
development methodologies based on iterative development, where
requirements and solutions evolve through collaboration between self-
organizing cross-functional teams. Agile methods or Agile processes
generally promote a disciplined project management process that
encourages frequent inspection and adaptation, a leadership philosophy that
encourages teamwork, self-organization and accountability, a set of
engineering best practices intended to allow for rapid delivery of high-quality
software, and a business approach that aligns development with customer
needs and company goals. Below are the processes that the proponent will
undertake upon the fulfillment of AMBERGREYS Inventory and Record
System.

7
PLANNING

MAKATI SCIENCE HIGH SCHOOL

- Ipsum

Figure 1: AGILE System Development Life Cycle

Requirements

The proponents would like to build AMBERGREYS Inventory and

Record System to respond to the needs of the client. The diagram below
represents the processes that the proponents will use in the study.

Plan

Once these proposals have been approved, the proponents are

planning to start building AMBERGREYS Inventory and Record
System to meet the requirements of a web-based inventory and record
system for AMBERGREY. An initial and a final testing will be conducted
to validate its acceptability.

Build

Creation of web-based Inventory and Record System will roughly

take a month to finish. A simple design with friendly user functionality is
the priority in building.

Launch

Once AMBERGREYS Inventory and Record System is ready for

use, it will undergo initial testing to check for errors and things to improve
and revise. In the final testing, the questionnaire tool developed will be
given to the respondents to validate its acceptability in terms of functional
suitability and usability.

8
 PLANNING

MAKATI SCIENCE HIGH SCHOOL

Feedback

Part of the questionnaire tool enables the respondents to provide

relevant feedbacks that will be collected and analyzed to improve the total
functionality of AMBERGREYS Inventory and Record System.

1.2. Expected Outcome/Output

The proponent of this project is expecting the following outcomes:

(1.) All work shall be completed in time for a demonstration at the

Anniversary Celebration of AMBERGREY this coming December 16,
2016 in the new office building located at Taytay, Rizal.
(2.) The developed Inventory and Record System will have passed the
acceptability evaluation based on ISO 25010 parameters functional
suitability and usability.

1.3. Evaluation Plan

Functional Suitability and Usability Evaluation

This project involves functional suitability and usability tests and

users acceptance test of AMBERGREYS Inventory and Record System.
During the functional suitability and usability testing phase, the proponents
of this project will brief the participants for the tasks involved using
AMBERGREYS Inventory and Record System using the demo system in
real time. Upon completion of the set of IRSs required functions and tasks,
participants at AMBERGREY will be requested to give comments in the
online survey forms made available through google forms and link will
posted on the developed AMBERGREYS site for the user acceptance
results. The final result from this real-time test can be used to show the
functional suitability and usability of users acceptance of the developed IRS.
The diagrams below show the procedures and evaluation processes in this
study.

9
PLANNING

The Project Sponsor is responsible for formally accepting the

MAKATI SCIENCE HIGH SCHOOL

projects final deliverable. This acceptance will be based on a review of all
project documentation, testing results, beta trial results, and completion of
all tasks/work packages and product functionality.

SCHEDULE MANAGEMENT PLAN

Time is of the essence relative to finalization of this web portal for

demonstration at the foundation day celebration.

Working Days : Monday to Friday

Work Hours : 8am to 5pm PHT - Ipsum
Project Time Frame : July 31 December 15

AMBERGREYS INVENTORY AND RECORD SYSTEM SCHEDULE PLAN

Stage 1 Concept Development

Step Dates Description
Request for September AMBERGREYS description of project; begins to formalize
Proposal 9 the web-based concept and design. Define the scope.
(RFP)
Proposal September WEBMASTERs written estimate of the schedule and cost
16 of project.
Contract/Budg September AMBERGREY, WEBMASTER agree in writing to proceed
et Approval 22 with the project.

Stage 2 Planning
Step Dates Description

Product Septemb Submit written plan to AMBERGREY. Includes general

Requirement er 23 project overview and goals, resource/staffing plan, testing
(Project Plan) start plan, milestones, and other tactical details. Forms basis for
Project Definition Meeting.
Project Definition Septemb Meeting between key players from AMBERGREY,
Meeting er 26- WEBMASTER. Group agrees on exactly what will be
October 1 included in the web portal and how it is presented, on a
detailed section-by-section basis. Implementation begins
after this meeting. Note: After the client has signed off on
the creative and structural definitions, any changes may
affect the timeline and/or the budget of the project.
Project October WEBMASTER completes specific written description of
Specification 10-12 project as defined in Project Definition Meeting.
AMBERGREY approves Product Specification. Changes
after this date require Change Order Form and may incur
additional charges.

10
PLANNING
Stage 3 Implementation

MAKATI SCIENCE HIGH SCHOOL

Step Dates Description
Content October 12-20 AMBERGREY supplies digital data and other content
Acquisition sources. WEBMASTER converts content into
application formats.
Data Integration October 12-25 Developer imports and integrates data content into
website.
Customization October 12-30 Developer creates unique graphics and screens
(pages) for the web-based inventory and record
system. Custom programming begins.
Server Set-Up October 23- Developer assists set up of Web Server, domain, and
November 1 options. - Ipsum

Stage 4 Testing
Step Dates Description
Alpha Testing November 1- WEBMASTER begins internal testing of application
(Staging) 10 functionality. Bugs are systematically reported and
fixed.
Beta Testing November 11- WEBMASTER validates the content and finalize live
(Staging) 16 project with review by AMBERGREY. AMBERGREY
reports any bugs, signs off fixes, and approves site for
launch.

Stage 5 Launch and Phase Out

Step Dates Description
Activation November 16- AMBERGREYS Website goes live.
30
Project Review December After WEBMASTER internal project review (non-billable
Launch time). Feedback requested from AMBERGREY.
Admin/Support ? Maintenance work by WEBMASTER begins.

11
ANALYSIS
System Overview

MAKATI SCIENCE HIGH SCHOOL

The AMBERGREYS Inventory and Record System consists of
three main software components: the database, the user interface(s) and
the bridge software between the user interface(s) and the database. The
bridge software is required because current web servers and browsers do
not have the ability to communicate directly with a database.

- Ipsum

Figure 1 System block diagram for an inventory management system. The

data flow shown represents a user searching for parts.

Relational Database

The relational database contains all of the information needed to

track the equipment room inventory. The database can be searched or
changed. Searching the database (called a query) causes it to return a
subset of the data (called a recordset) that matches the search criteria.
Changing the database by inserting, updating or deleting information causes
the database to return status information regarding the success or failure of
the change. Any operation on a database is called a transaction.

12
ANALYSIS

Database Driver

MAKATI SCIENCE HIGH SCHOOL

The relational database is usually stored in a proprietary format and
cannot be interpreted by the user or other software without the assistance of
a database driver. The driver takes incoming SQL or XML transactions and
converts them to a form understood by the database. The driver also passes
recordsets and the status of attempted database changes back to the
requesting application. Two of the most prevalent drivers are ODBC (Open
DataBase Connectivity) and JDBC (Java DataBase Connectivity). Our
prototype server will use the Microsoft SQL Servers built-in ODBC driver.
Our production server will use MyODBC.
- Ipsum
Application Server and Web Server

When a web server receives a request for a web page, it normally

retrieves the page and passes it back to the browser. Web pages that
retrieve or manipulate data from a database, however, contain sections of
non-HTML code (such as JavaScript or PHP) that browsers cannot interpret
on their own. Therefore, web servers pass such pages to application
servers, which interpret the non-HTML code, retrieve the data and return the
results in HTML for display in the browser. In general, application servers
may be implemented as actual server software, such as Macromedia
ColdFusion MX Server, or they may be as simple as small Java applets. Our
prototype server will use Macromedia ColdFusion MX Server Developer
Edition as its application server and web server. Our production server will
use PHP as its application server and Apache as its web server.

User Interface

Each class of user will have a separate user interface appropriate for
the functions that user class requires. This separation helps enforce security
and data integrity. All I/O shown in the block diagrams below is between the
users browser and the web server, conducted over HTTP (Hypertext
Transfer Protocol), as illustrated in Figure 1, unless otherwise noted. In
addition, all user interface blocks assume the presence of basic human
interface devices (keyboard, mouse and display).

Administrator Interface

The administrator is in complete control of the system and can

perform any and all functions associated with the system. The administrator
is the only user capable of adding, editing and deleting other users from the
system.

13
DESIGN

System Requirements

MAKATI SCIENCE HIGH SCHOOL

The AMBERGREYS Inventory and Record System uses a web-
based interface to display inventory data to the stock manager client. The
product will use of open-source software primarily due to cost of
implementation. A JSP (JavaServer Pages) servlet will be hosted by an
Apache Tomcat web server (on top of any choice of operating system,
although a flavor of Unix is recommend). The first feature of the Stock
Manager Client web interface component allows the Stock Manager Client
to view the current stock of products, along with the capabilities of searching
and sorting the products. The second feature of the Stock Manager Client
web interface will allow the user to modify application settings, such as the
threshold for email notifications, frequency of inventory scans (daily at a
particular hour, weekly, monthly, etc.), and security settings. The third
feature of the Stock Manager Client web interface will allow the user to
update the inventory during the restocking process. See Figure 1. Since a
web interface will be used, a network that supports the HTTP/HTTPS
protocol must exist, whether it is a private network for an isolated customer
deployment or an Internet connection for a multi-site customer deployment.
The bandwidth of the network depends on the frequency of transactions. A
bandwidth of at least 10 Mbps is recommended (small commercial
deployment). The database to store the inventory data will use a MySQL
database.

Since the software and hardware resources of cash registers are not
available due to the variation in software and cost, we will be developing an
emulated Cash Register client to interface with actual cash registers. The
Cash Register client will emulate purchases by having a simple graphical
interface with fields for a barcode number and quantity and a button to make
a purchase. See Figure 2. As these resources become available, the actual
implementation for specific cash register models will be considered for future
releases of the AMBERGREYS Inventory and Record System. JavaPOS
will be used as a reference for emulating cash registers, and could
potentially be used to create the actual implementation of the future release.

Alternatively, commercially licensed products are available. In

particular, the Microsoft ASP.NET (Active Server Pages) framework can be
used. This requires a Microsoft ASP.NET web server and a Microsoft SQL
Server database, which also requires a Microsoft operating system.
However, these alternative system requirements will increase the overall
costs for both implementation and deployment.

14
System and Software Architecture
Schedules
The programming language for the AMBERGREYS
Stock Manager Inventory andStock
Client: Current
Record System application willThe betime
in estimated
Java since the JSP/Tomcat
to complete the AMBERGREYS Inventory and

MAKATI

RIZAL TECHNOLOGICAL UNIVERSITY

architecture will be used. Both types of clients will is
communicate
fairly short. withSortthe

MAKATISCIENCE
Record System project There Bywill be three major Win-Win
server using Java Remote Spiral
Method Invocation
Model cycles (RMI)
throughwith our Secure Socket
prototyping stage, beta release, and final
Layer (SSL). Thus, security will be upheld by
release. We will Product HTTPS in both a
need two weeks of designing private Stock the architecture and
network and a network connected to the Internet.
implementing The application
core features and fivewill use aof adding functionality and
weeks
client-server model. See Figure 3. The project can be completed by 6-8 people in at most 7 weeks.
testing.

SCIENCEHIGH
Furthermore, the Java DatabaseRationale
Feasibility Connectivity (JDBC) will use the
MySQL Connector/J driver for the server to communicate to the inventory
database. Upon receiving Assumptions
requests from the clients, the server will issue
transactions to the MySQL database with ACID properties. The Cash
Register clients will maintain localThe log above
files inStock
the event
design Manager of communication
should Client:
work Settings
for the AMBERGREYS Inventory
downtime between Cash and Register
Record clients and the
System server. However,
application. Upon re- we are emulating a cash
establishing communication,registers
the Cash Register
interface clients
Security
to work willourre-synchronize
with software by simulating barcode inputs. A
with the server by issuing themore
requests that design
realistic occurredofduring HIGHSCHOOL
cash downtime.
register interface can be done to suit the
integration, as the interface does not interfere with the data collected. We
Alternatively, if the Microsoft
expect thatASP.NET
the cash Email
framework Address
registers isclients
used, are
thenable
the to update their data to the
programming language for current the application
point of salewill be Microsoft
in case C# ofwith
of loss a
connection to the server. The
SCHOOL

Microsoft SQL Server database. The Microsoft .NET

particular restocking procedure framework
Frequency adopted by includes
each store does interfere with
Threshold
built-ins for easy databasetheinterfacing and accuracy
feasibility and .NET Framework Remoting
of the application as it does not remind the stock
(analogous to skeleton and stub),
managerwhich to has the the
update ability to also
data eachuse HTTPS.
time they had done any restocking. We
also trust that that the Secure Socket Layer (SSL) is reliable in creating a
secure connection between a client and a server.
Stock Manager Client: Update
Risks

One of the major risks covered by this application is theft breaks

synchronization between Restock Synchronize
the inventory and the database. The information
could be generated by the data stored in this application. The confidence
level of trusting data generated depends on the accuracy of the restocking
procedure. Therefore, we are facing a risk of reckless stock manager who
could detriment the accuracy of the data. As of the reliability of the SSL
encryption, a resolution for this could be by developing SSL and digital
certificate policy and configuration guidelines. In addition, giving a choice to
the user to set the minimum level of SSL used by not violating the policy
Figure
should 1. The three
convince themfeatures of the StockofManager
the trustworthiness Client web interface.
the application.
Figure 3. Client-server architecture model of the Inventory Management System application.

Another riskCash Register

is the Client from other Point of Service software.
competition
Life Cycle Plan There are several large competitors in this field including a solution from
Microsoft; however, all of these tend to be expensive. AMBERGREYS
Objectives Inventory and Record UPC Quantity
System will be a low-cost solution mainly targeted
The main goal of AMBERGREYS Inventory and Record System is
at smaller businesses while including the possibility of later expansion.
to ensure consistent availability of supplies for consumers. Thus,
AMBERGREYS Inventory and Record System is directed toward owners
of small to large stores and stock managers who are responsible of
maintaining sufficient goods on hand in a retail or manufacturing business.
Purchase
It can scale from a single computer running both client and server software
up to multiple stores and warehouses.
Figure 2. The emulated Cash Register Client interface.
15
IMPLEMENTATION
Development Guidelines

MAKATI SCIENCE HIGH SCHOOL

The web site designed of AMBERGREYS Inventory and Record System
by the successful candidate must meet the following criteria:

Create a content management system that will permit non-technical staff to

instantly update web site content on specific pages.
Once completed and accepted, the site's database inventory content can
be managed through a combination of the site's backend web interface
AND/OR a MySQL stand-alone tool (such as phpMyAdmin or Navicat).
Once completed and accepted, the site's source code and template pages
can be edited via code editors.
Inventory data can be imported into the database via common spreadsheet
formats, such as CSV files.
Inventory data can be exported and saved as CSV.
Reports and quotes. Confirmations can be exported into printable PDF
formatted files for delivery to clients. Styling will be provided by
AMBERGREYS
The web interface should be accessible and usable on common mobile
devices and standard desktop browsers.
Adobe Flash should not be used in any programming of the site.
Consistent Design As stated above, each section of the site should have
a common look and feel. The use of photographs, fonts and layouts should
be consistent throughout the site.
Easy to Navigate The site should be easy to navigate. Information should
be grouped and presented in a logical manner and require no more than 2
levels of drill down for the user to find the desired information.
Development of navigation to accommodate the necessary proposed web
pages. Navigation should be logical.
Provide necessary software and licenses to maintain site internally or
externally, as decided by AMBERGREYS
Email notifications sent to users to alert of upcoming return deadlines,
overdue notices, and equipment problem notices.
Web site must not require plug-ins as a default.
Site must be built in accordance to the Web Content Accessibility
Guidelines 1.0, provided by the W3C
and should also be easily accessible to the novice as well as the
experienced internet user.
Fast Loading Pages The web site must be designed with a balance of
text and graphics such that each page loads fast, 2 seconds or less on the
average computer (using a T1 circuit).
Notification of expiring items, such as client insurance certificates.
Dashboard to provide important information and status at login.

16
IMPLEMENTATION
User Features

MAKATI SCIENCE HIGH SCHOOL

1) Basic user management tool for admins, basic but built into web interface.
2) User profile interface. Users, be able to update personal information and
track order history.
3) There should be multiple roles, with admins defining whom users get the
different roles
4) Roles
a) Super User
-can create, modify, and delete users/profiles.
-can create, modify, delete inventory assets.
-can create, modify, delete job reservations and corresponding asset lists
-can create, modify, delete asset types
-can create, modify, delete access types
-can run reports and generate pdfs
b) Inventory Admins
-can create, modify, delete inventory assets
-can create, modify, delete job reservations and corresponding asset lists
-can create, modify, delete asset types
-can run reports and generate pdfs
c) Job Admins
-can create, modify, delete job
-can create, modify, delete job reservations(quotes) and corresponding
asset lists
-can run reports and generate pdfs
d) Users
-can view inventory asset data, project schedules, list of available equipment
-can run reports and generate pdfs
e) Everyone
-no outside access
Possible DB tables
Users
-fname
-lname
-uname (user name)
-client number(PRIMARY KEY)
-email
-office phone
-mobile phone
-title
-notes
-fname (foreign key)

17
IMPLEMENTATION
-lname (foreign key)
-uname (user name) foreign key)

MAKATI SCIENCE HIGH SCHOOL

-client number(foreign key)
-PO
-invoice
Assets
-asset_ID/barcode# (primary key)
-item name
-item type (asset_type.type_ID") (foreign key)
-S/N
-model
-in/out status (rental status)
-future availability status (rental reserve?)
-manufacture date
-warranty status (date expires, notification for expired status)
-parts included (text field)
-description
-image (jpg, png, gif url reference to image in file system)??
-purchase date
-purchase locations
-purchase receipt
-item value
-vendor order number
-notes
Asset Type
-type_ID (primary key)
-type
Access
-access_ID (primary key)
-type
Job
-job_ID (primary key)
-job_title
-job_lead
-location (OR separate fields for address1, address2, city, state, zip)
Job-Based Inventory
-ID (primary key)
-job (foreign key to "job.job_ID")
-item (foreign key to "assets.asset_ID")
-date_start
-date_end
Rentals
-jobid
-symptoms
-diagnosis
-project_start (date out for rental)
-project_est_date (estimated date of return)
-project_end (date returned)

18
IMPLEMENTATION
AMBERGREYS will provide documents for additional design and relational

MAKATI SCIENCE HIGH SCHOOL

data references upon candidate selection.

Testing

Testing of the site will be performed during development on all

applicable platforms to ensure web site works as promised. Explain testing
plan through development process (i.e. focus groups, etc.). Specifically, Unit
Testing, Integration Testing, White Box testing, and Black Box Testing should
be applied during the production of the site.

Delivery

Delivery and uploading of site from client to our servers hosted by

MediaTemple. White box and black box testing should be done on
AMBERGREYS hosted MediaTemple servers. Sample Branding and PDF
reference material: Will be provided to selected candidate after the RFP
process at start of project.

1. Technology Resources and Integration Concerns

AMBERGREY will be importing existing records into this new database. An

import tool for CSV records should built into the tool.
This system will not be required to connect to any other management
systems.
The site should be developed in a modular and scalable way so that it can
be easily expanded upon later.

2. Staff Resources

The following AMBERGREY staff members will be involved with this project
in the following capacities:
EPS SABANGAN - Project Management
David Vottero - Brand and Copy
Brian Carr - Brand and Copy

3. Qualifications

1. Please provide examples of other web and database programming

projects to which you have significantly contributed. A portfolio is acceptable
as well.
2. Provide references upon request.
3. Please discuss your testing and support plan.
4. Time frame for completion. The time frame for completion of the project
will be evaluated. In addition, time frames will be part of the contractual
agreement; therefore, a realistic time frame for completion is requested.
5. Please discuss your terms and conditions.

19