Hotel Reservation System A J A C SYSTEMS

Hotel Reservation System A J A C SYSTEMS

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 � Typical �Enter guest information �Select date range of stay �Select room type �If room is available, schedule room �If room is not available message will appear �The employee can then print out a functional receipt.

Scenarios (cont. ) � Atypical �Entering wrong date range backwards ○ Error message �Leaving a required field blank ○ Message stating required fields �Entering guest information that exists ○ Will ask to verify current guest information

Optional Features � Must Haves �Store Guest Information �Store Reservation Information �Check against current reservations �Hold guest information �Change pricing and room types �Print functional recepit

Optional Features � Would like to have �Online guest reservation �Multi-employee login �Check in / Check out guest �Take payment and keep track of payments

Impacts � Improvements �Increased efficiency �Faster customer service � Disadvantages �System failure / Corruption �Retraining of employees � Limitations �Restricted to development � Risks �System Failure �User Error

Applicable Standards � Coding Standard �GNU Standard � Document Standard �Office 2003 �No First Person � 10 pt Font

Project Team Ogranization � Christopher �Website �Technical Director Database Management � Anqi �Test Planning �Quality Assurance � Jinlong �Requirements Specifications �Use Case Generation � Andon �Editor and Technical Director

Software Life Cycle Process

Tools and Computing Environment � Back – End �Microsoft SQL � Front – End �Microsoft Access � Additional Components �C++ �PHP �Pay. Pal API

Quality Assurance � Testing �To be performed after development cycles � Documents �Forwarded to Andon for editing �New documents forwarded to team � Code Reviews �When time is available

Risk Management � Language Barrier � Tasks are pooled together �Written Word �Abstraction � Iterative Model

PERT Chart

Software Requirement Specs � Assumptions �Environment �Database �Processor �Memory � Stakeholders �Companies that use search engines to search for products on the web

Use Case � Guests �Call or Email reservations � Employees �Check rooms and print reports �Reserve rooms

Specific Requirements � Functional Requirements �Validity checks on the inputs �Exact sequence of operations �Responses to abnormal situations

Specific Requirements � Interface Requirements �What data items are input �What data items are output �Data type / Format �Frequency of data sent and received

Specific Requirements � Physical Environment Requirements �Type of equipment to run software �Location of equipment �Environmental considerations

Specific Requirements � Users and Human Factors Requirements �Different types of users �Special accommodations for users �Misuse?

Specific Requirements � Documentation Requirements �Currently printed documentation �Medium understanding of XP and ms. SQL

Specific Requirements � Data Requirements �Data calculations �Retained data requirements

Specific Requirements � Resource Requirements �Personnel required �Physical space �Hardware / Software

Specific Requirements � Security Requirements �System control �Isolation �Data backup

Specific Requirements � Quality Assurance Requirements �Quality attributes ○ Reliable �Prescribed time of availability ○ All times hotel is open �Maximum allowed time for restart ○ No

Test Plan � Overall objective � Test Environment � Stopping Criteria � Individual Test Cases �View reports �Add Guest �Add Reservation �Available rooms