1. Stratford University Restaurant Reservations System
Initial Analysis
Rachel Amato
Andrew Davis
Mike Valore

3. Initial Definitions
Project: A temporary endeavor undertaken to create a unique product or service
Operations: An ongoing and repetitive set of processes. It involves work that is continuous without an ending date, and is often repeated to produce the same results.
Difference:
The purpose of a project is to meet its goals and to conclude
The purpose of operations is to keep the organization functioning

4. Higher Echelon / Overall Mission and Intent
Who: Culinary Dept (more specific?)
What: Online Restaurant Reservations System
Why: More effectively manage Restaurant Reservations
Where: Stratford University Culinary Center and Dining Room
When: ASAP / Upon initial release of developed project

5. Task Analysis (Determine Own Specified, Implied, and Essential Tasks)
Guests Create / Manage Reservations
Restaurant personnel adjust dining events to reservations list
Guests and Restaurant personnel execute reservations list plan
Implied
Setup of Web Site
Development of Application
Customer access to Web Site
Maintenance of Web Site

6. Current Status (Determine Known Facts, Assumptions, or Conditions)
This is REAL-Time project for continuous use – not an occasional, educational effort
No development team in Va Beach (where are they?)
No budget to develop Web Site
All tools and processes used for project and operation are candidates for class case studies
Assumptions
Requirements Complexity & Volume are relatively easy and low
Request for augmentation into Stratford Portal will take a LONG time (NPV?)
After initial development (“project”), web application will require on-going maintenance (“operations”)
Development can also be used as class projects
Development velocity will be low
Stratford portal is available … ???
Stratford URL moniker will be required (i.e.,
Infrastructure can be made available
Will not use a budget
Conditions
Near-Term development doable,
long-term sustainability a question
Will not be a budget
Staff & Key Faculty personnel turnover may require a reset/revisit

7. Operational Limitations (Identify Constraints & Restraints)
No Budget
IT Response Staff one-deep (Andrew Davis)
Limited to existing infrastructure
No dedicated development staff
Restraints
Will develop without a budget
Will operate and maintain without a budget
Importance of Web Site = (on scale of 1 to 10)
Guests limited to students and invited public

8. Determine End State (List Objectives and Initial Effects)
Operational Web site that’s …
Available 24/7 ???
Used by Culinary Dept to manage restaurant operations
Maintained by IT Dept (Infrastructure Team)
Patches & Upgrades
Damage Control (failures, etc)
Enhanced by IT Dept (Development Team)
Corrective (bug fixes)
Adaptive (HW, SW, & OS platform changes)
Perfective (requirement spec changes)

9. Initial Asset Structure Analysis
List personnel requirements
List equipment requirements
List infrastructure requirements

10. Initial Asset Structure Analysis (Personnel requirements for Project)
Culinary
Director (act as Project Sponsor)
User Rep(s)
IT (Development)
Director (act as Project Manager)
Dev Team
IT (Infrastructure)
IT Rep

11. Initial Asset Structure Analysis (Equipment requirements for Project)
Hardware
At least one Server (can handle both Web and DB servers)
Development Server can be handled by Dev Team Lead
Backup media to store developed code and database backups
Backups should be handled by both Dev Team Lead and IT Infrastructure Lead
Software
Tools that are used by students toward education
Java (code), MySQL, (database), Tomcat (web server)
OS: Windows x64 architecture

12. Initial Asset Structure Analysis (Infrastructure Requirements for Project)
Internet access
Stratford University’s locality?
What about remote housing through ISP?

13. Conduct Initial Risk Assessments (Assess & Identify the associated risks)
For each Risk; analyze
Assess Hazards
Develop Control Measures
Supervise Measures
Evaluate Measures
See Spreadsheet
Assessment provides:
Centers of Gravity (Factors that cause the project or operation to fold)
Critical Information Requirements (factors that require a decision point)

14. Determine Center(s) of Gravity (Factors that cause the project or operation to fold)
Critical Factors and Decisive Points
Critical Capabilities (CC)
Critical Requirements (CR)
Critical Vulnerabilities (CV)
List:
Near-Term development possibly NOT doable
Long-term sustainability may be untenable
Staff & Key Faculty personnel turnover may require a reset/revisit
Dev Team availability may erode

15. Center(s) of Gravity (List from Risk Assessment)
CG #1: Near-Term development possibly NOT doable
(CC) Dev Team Lead experience, and availability of students
(CR) Dedicated Dev Team for project to handle complexity and volume
(CV) Volume & complexity too much for capacity and velocity
CG #2: Long-term sustainability may be untenable
(CC) Key Personnel to continue Project and Operations
(CR) Key Personnel to continue Project and Operations
(CV) Key Personnel leave or no longer associated with project
CG #3: Staff & Key Faculty personnel turnover
CG #4: Dev Team availability may erode
(CR) Dev Team Lead as part of Project and Operations
(CV) Dev Team Lead leaves or no longer associated with project

16. Determine Critical Information Requirements (Key information that causes changes to project or operation)
List:
Guests cannot Create or Manage Reservations (long term)
Cannot perform Web Site Maintenance (Recovery)
Dedicated development staff no longer available
Volume & complexity too much for capacity and velocity
Importance or priority of Web Site declines
DB Backups or Legacy Source Code lost, not available, or no longer works

17. Develop (updated) Mission Statement
Who: Culinary Dept (more specific?)
What: Online Restaurant Reservations System
Why: More effectively manage Restaurant Reservations
Where: Stratford University Culinary Center and Dining Room
When: ASAP / Upon initial release of developed project

18. Next Steps Create Project Charter Gather Project Requirements
Identify & Inform Key Personnel
Gather Signatures to ensure project and operational continuity
Gather Project Requirements
Web Site specs
Design Infrastructure
Identify Hardware
Create Work Breakdown Structure
From Project Requirements
Create Informal Project Plan