A J A C Systems
description
Transcript of A J A C Systems
Hotel Reservation System
The Hotel
3 Story Hotel Floor Plan Currently using calendars and manual
filing system Room types Pricing
Proposed System
Access Database 2 Main Functions
Reserve Room○ Take guest information and input○ System will check for availability
Print Reports○ Room Availability○ Guest History○ Room History
Scenarios
TypicalEnter guest informationSelect date range of staySelect room typeIf room is available, schedule roomIf room is not available message will appearThe employee can then print out a functional
receipt.
Scenarios (cont.)
AtypicalEntering wrong date range backwards
○ Error messageLeaving a required field blank
○ Message stating required fieldsEntering guest information that exists
○ Will ask to verify current guest information
Optional Features
Must HavesStore Guest InformationStore Reservation InformationCheck against current reservationsHold guest informationChange pricing and room typesPrint functional recepit
Optional Features
Would like to haveOnline guest reservationMulti-employee loginCheck in / Check out guestTake payment and keep track of payments
Impacts Improvements
Increased efficiencyFaster customer service
DisadvantagesSystem failure / CorruptionRetraining of employees
LimitationsRestricted to development
RisksSystem FailureUser Error
Applicable Standards
Coding StandardGNU Standard
Document StandardOffice 2003No First Person10pt Font
Project Team Ogranization Christopher
WebsiteTechnical Director Database Management
AnqiTest PlanningQuality Assurance
JinlongRequirements SpecificationsUse Case Generation
AndonEditor and Technical Director
Software Life Cycle Process
Tools and Computing Environment Back – End
Microsoft SQL
Front – EndMicrosoft Access
Additional ComponentsC++PHPPayPal API
Quality Assurance
TestingTo be performed after development cycles
DocumentsForwarded to Andon for editingNew documents forwarded to team
Code ReviewsWhen time is available
Risk Management
Language Barrier Tasks are pooled together
Written WordAbstraction
Iterative Model
PERT Chart
Software Requirement Specs Assumptions
EnvironmentDatabaseProcessorMemory
StakeholdersCompanies that use search engines to
search for products on the web
Use Case
GuestsCall or Email reservations
EmployeesCheck rooms and print reportsReserve rooms
Specific Requirements
Functional RequirementsValidity checks on the inputsExact sequence of operationsResponses to abnormal situations
Specific Requirements
Interface RequirementsWhat data items are inputWhat data items are outputData type / FormatFrequency of data sent and received
Specific Requirements
Physical Environment RequirementsType of equipment to run softwareLocation of equipmentEnvironmental considerations
Specific Requirements
Users and Human Factors RequirementsDifferent types of usersSpecial accommodations for usersMisuse?
Specific Requirements
Documentation RequirementsCurrently printed documentationMedium understanding of XP and msSQL
Specific Requirements
Data RequirementsData calculationsRetained data requirements
Specific Requirements
Resource RequirementsPersonnel requiredPhysical spaceHardware / Software
Specific Requirements
Security RequirementsSystem controlIsolationData backup
Specific Requirements
Quality Assurance RequirementsQuality attributes
○ ReliablePrescribed time of availability
○ All times hotel is openMaximum allowed time for restart
○ No
Test Plan
Overall objective Test Environment Stopping Criteria Individual Test Cases
View reportsAdd GuestAdd ReservationAvailable rooms