Professional Documents
Culture Documents
AmberGrey
Dress Shop
Inventory and Record System Project Proposal
Submitted to:
Rowena Andaya-Reyes
Esperanza R. Sabangan
DOCUMENT CONTROL
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
Operational Concepts
OBJECTIVES
3
Specific Objectives
Project Vision
4
Specific Objectives and Success Criteria
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
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
1. Scope of Work:
7
PLANNING
Requirements
Plan
Build
Launch
8
PLANNING
9
PLANNING
Stage 2 Planning
Step Dates Description
10
PLANNING
Stage 3 Implementation
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.
11
ANALYSIS
System Overview
- Ipsum
Relational Database
12
ANALYSIS
Database Driver
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
13
DESIGN
System Requirements
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.
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
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
16
IMPLEMENTATION
User Features
17
IMPLEMENTATION
-lname (foreign key)
-uname (user name) foreign key)
18
IMPLEMENTATION
AMBERGREYS will provide documents for additional design and relational
Testing
Delivery
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
19