planning for effective testing case study - · pdf filethis case study provides the...

© Copyright 2004-2014, ASK Process, Inc.

Planning For Effective Testing

Case Study Version 5.1

November 2014

Case Study Introduction

© Copyright 2004-2014, ASK Process, Inc. Version 5.1 Page 1 of 1

1. Introduction This Case Study provides the information you will need to complete the exercises

for this course.

2. Contents This document is comprised of: • Case Study Introduction – This page. • Richman Country Club, Reservation Management System, Golf

Enhancement Requirements – These are the requirements for the system you are producing a plan for testing. It is an enhancement to the original reservation management system.

3. Background Richman Country Club has 275 member families. The clubhouse contains a

restaurant, banquet facilities, and the Pro Shop (which supports both Golf and Tennis). They have an 18-hole golf course with a full-time golf pro, as well as a dozen tennis courts and a full-time tennis pro.

RCC has computers and a local area network to support their existing applications (Membership, Accounting and Restaurant Reservations). But they have no in-house IT personnel. They have contracted with Geeks-R-Us to come to the club to do maintenance every Thursday afternoon. According to the contract, any IT support beyond the weekly maintenance call is provided on a time and materials basis.

Your company developed the original Reservation Management System for the restaurant at the Richman Country Club. They have been using it for two years, and are so satisfied with it that they want to extend its use to the Golf course.

Your company had originally lobbied to create a general-purpose reservation management system to support the golf course and tennis courts in addition to the restaurant, but the RCC board of directors insisted that you focus solely on the restaurant. Now, they are insisting that (despite recent history), they do not want the system to support tennis, and you are to focus only on adding support for golf. (Go figure!)

4. This Project The project is expected to take a total of 6 weeks to develop and test. Because

your development department uses an iterative development lifecycle, you will be able to begin testing as follows:

• Increment 1: Golf Reservation functionality (set up date, create, edit, cancel, honor, etc.) will be ready for testing at the end of week 2.

• Increment 2: Golf Closeout functionality (creating transactions, but not editing them) will be ready for testing at the end of week 3.

• Increment 3: Complete functionality will be ready for testing early in week 5.

Richman’s Country Club Reservations Management System Golf Enhancement Requirements


Table of Contents 1. Introduction ................................................................................1

1.1. Purpose ..............................................................................1 1.2. Scope .................................................................................1 1.3. Definitions.........................................................................1 1.4. References .........................................................................1 1.5. Overview ...........................................................................2

2. Overall Description ....................................................................3 2.1. Product Perspective ...........................................................3 2.2. Product Functions .............................................................3 2.3. End User Characteristics ...................................................3 2.4. Constraints ........................................................................4 2.5. Assumptions and Dependencies .......................................4

3. Specific Requirements ...............................................................5 3.1. External Interfaces ............................................................5 3.2. Functional Requirements ..................................................5

3.2.1. Main Golf Reservation Window ...........................6 3.2.2. Golf Reservation Pop-up .......................................9 3.2.3. Member Lookup Dialog ......................................11 3.2.4. Manager Sign-in Dialog ......................................12 3.2.5. Cancel Confirm Dialog .......................................13 3.2.6. Setup Date Dialog ...............................................14 3.2.7. Golf Closeout Window .......................................15 3.2.8. Golf Transaction Pop-up .....................................17

3.3. Performance Requirements .............................................18 3.4. Design Constraints ..........................................................18 3.5. Software System Attributes ............................................19 3.6. Other Requirements ........................................................19

3.6.1. Data Dictionary ...................................................19

Richman Country Club Golf Enhancements Reservation Management System Software Requirements Specification


1. Introduction

1.1. Purpose This document details the requirements for an enhancement to the software that

automates restaurant reservations at the Richman’s Country Club. This enhancement will add support for Golf Course reservations to this system.

1.2. Scope This document details the requirements for only the software changes that will be

required. Hardware, network, and other requirements are addressed in the Richman’s Country Club Reservations Management System Requirements Specification. The “Golf Course Reservations” functions that this software will address are enumerated in section 2.2, below. No other functions will be addressed.

1.3. Definitions, Acronyms, Abbreviations RCC – Richman’s Country Club

RMS – Reservation Management System SRS – Software Requirements Specification (this document)

SyRS – System Requirements Specification

1.4. References Richman’s Country Club Reservation Management System Software Requirements

Specification, Version 1.0 – describes the requirements of the reservation system, as it exists (before this enhancement).

Richman’s Country Club Reservation Management System Statement of Work, Version 1.0 – defines cost and schedule constraints and general expectations for the project.

Richman’s Country Club Reservation Management System Concept of Operations, Version 1.0 – Describes the scope and requirements for this project from the business stakeholders’ perspectives.

Richman’s Country Club Reservation Management System Requirements Specification, Version 1.0 – Details the general requirements for this project, and allocates them to hardware, networks, and software. This SRS details the requirements that are allocated to software in the SyRS.

Richman’s Country Club Procedures Manual – The “Reservations” section of this manual contains the day-to-day operating procedures that are currently used in taking and honoring reservations at RCC.

Richman’s Country Club Members Handbook – The “Reservations” section of this handbook contains instructions to guide the members in making and keeping reservations.



1.5. Overview This document is comprised of three sections with subsections:

Section 1 – Introduction to the document: provides the document’s purpose, scope, definitions, references to other pertinent documents, and this overview.

Section 2 – Describes the context in which this software is being developed, and will be used, including how it fits into the entire system, the types of people who will be end-users of the software, the constraints on both the development project and the finished software, and all pertinent assumptions and dependencies.

Section 3 – Details the software requirements

Section 3.1 – Details the requirements for the software interfaces, including user interfaces as well as any interfaces to other systems.

Section 3.2 – Details the functional requirements for the features that the software will implement.

Section 3.3 – Details the requirements for software response times, throughout, and other performance issues.

Section 3.4 – Details all standards and other constraints on how the software is designed and implemented.

Section 3.5 – Details the quality attributes that the software must exhibit, including reliability, availability, security, maintainability and portability.

Section 3.6 – Details any other requirements for the software that do not fit in Sections 3.1-3.5. The Data Dictionary is in this section.



2. Overall Description

2.1. Product Perspective Extend the Richman’s Country Club (RCC) Reservation Management System

(RMS) to support the golf course. This includes: • A Golf Reservation Screen with the additional ability to reserve golf carts, golf

clubs and golf pro time. • A new daily Close Out for golf that submits financial transactions, for

appropriate charges. The existing restaurant reservation look, feel and functionality must remain

completely unchanged.

2.2. Product Functions The RCC RMS will automate the management of Golf Course reservations in the

same way as it already does for Restaurant reservations. These functions are detailed in Section 3 of this document:

• Limit reservations during each time period to avoid over-booking • Validate member status against the membership database (already exists) to

assure at least one currently-active member will be in each party • Capture necessary information, including number of people in the party,

request for lessons or other golf pro assistance, and any need for golf cart or club rental

• Record reservations honored • Record reservations not used by members • Interface with Accounting system (already exists) to make appropriate charges

to members’ accounts. (This item is new for Golf reservations; the Restaurant reservation system does not interface to the Accounting system.)

2.3. End-User Characteristics The following types of users will use the software as described.

2.3.1. Sales Associates This class of users includes sales associates in the pro shop and the golf pro. These

people will use the system to verify people’s membership status, take reservations, honor reservations, and record parties’ use of the facilities.

The people in this class of users have a variety of experience. Although the current employees know the manual procedures for making and honoring reservations, it is expected that all will need to be trained in new procedures to switch over to the new automated system. In addition, new employees are hired on a regular basis, and they must be trained as well.

The people in this class of users represent a wide range of comfort with the use of computers. It should be expected that some will have never used a computer for this



sort of work before, and may even be hesitant to do so, while others will find it natural and easy to learn.

2.3.2. Managers This class of users includes the golf course & pro shop managers, their assistants,

and other RCC managers who may stand in for them from time-to-time. These people will use the system for all of the same activities as the Sales Associates, plus overriding system controls (e.g. allowing non-members to use facilities), and performing the daily setup and close-out.

The people in this class of users are all very experienced. Although the current employees know the manual procedures for making and honoring reservations, it is expected that all will need to be trained in new procedures to switch over to the new automated system. Managers are almost always promoted from within, so training for new managers will usually consist of only those functions that are unique to the managers.

The people in this class of users will have a general level of comfort with the use of computers. (It is a prerequisite for the position.)

2.4. Constraints This enhancement is subject to these constraints: • Cost must remain within the not-to-exceed value stated in the signed and

approved Statement of Work (SOW). (The RCC Board of Directors must approve all changes to the SOW.)

• Schedule must remain within 10% of the signed and approved Statement of Work (SOW). All deviations from the SOW schedule (even those not exceeding the 10% threshold) must be reported to the Board of Directors as soon as they are known.

• Capital Investment is expected for new computer equipment, networking, and other technical infrastructure, but the Board of Directors must approve the costs of such investment before they are committed to.

2.5. Assumptions and Dependencies This project is predicated on these assumptions and dependencies: • The RCC General Manager and the affected department managers will be

available for interviews, reviews, and other meetings on a regular basis. • Other affected RCC staff will be available for interviews from time-to-time. • All affected staff and managers will be available for training shortly before the

system is deployed. • The RCC Restaurant Reservation user interface and functionality will not be

changed in any way by this project. • The RCC Membership Management System will not be affected by this

project. The functions of the RMS will make use of membership data that already exists.



• The RCC Accounting System will not be affected by this project. The functions of the RMS will submit financial transactions using the Accounting System’s existing interfaces.

3. Specific Requirements

3.1. External Interface Requirements

3.1.1. User Interfaces All screens/windows will conform to the corporate standards as documented in the

RCC System Standards document, Version 4.2. Layouts for all pertinent windows, pop-ups and dialogs will be as shown in the

figures in Section 3.2, Functional Requirements. All of the windows, pop-ups and dialogs in the existing Restaurant Reservation

system will remain unchanged.

3.1.2. Hardware Interfaces The software will be designed to run on the Personal Computers that have been

specified in the RCC RMS SyRS, on the network that already exists in RCC. No specialized hardware is required.

3.1.3. Software Interfaces The software must interface with the RCC Membership and Accounting Systems.

RCC Membership System: The membership data is stored in the Member table as specified in the Data Dictionary in Section 3.6.1 of this document. The system shall identify valid current members as those with a status of 1.

RCC Accounting System: The software will submit transactions that comply with the requirements of the Member Transaction table as specified in the Data Dictionary in Section 3.6.1 of this document.

3.1.4. Communications Interfaces RCC’s intranet will connect PC’s on which RMS will run with the back-office

servers on which the Accounting and Membership Management Systems run. This system will not require any external communication interfaces (e.g. internet).



3.2. Functional Requirements

3.2.1. Main Golf Reservation Window (Note: The look, feel and functionality of this window will be the same as the

Restaurant Reservation Main Window, with the exception that it says “Golf” at the top, and it will be used for managing Golf reservations.)

The main Golf Reservation window (Figure 1) will show the reservations and available slots for a particular day, and allow reservations to be made, changed, cancelled and honored. This window allows the user to page forward or backward through days, or to jump to a specific date.

Richman's Country Club -- Golf Reservations

Thursday, Dec 16, 2004

8:00 am

Miller -- Party of 4 Available

Available Available

8:30 am

Available Available

Available Available

9:00 am

Rosenblum -- Party of 2 Smythe -- Party of 5

Arnold -- Party of 4 Available

Figure 1: RCC RMS Main Window for Golf Reservations

Go To Date ⇐ Prior Date

Next Date ⇒ Today

On initial startup, this window displays the reservation information for the current date. For the date that is being displayed, the data in the database is selected and displayed.

• A slot with reservation data displays the Member last name, and number in the party (as shown in Figure 1). If Arrived is TRUE for the slot, it is shaded.

• For slots with no information, the word, “Available” is displayed.



If the reservation slots for the date have not yet been set up, then the date displays empty, and no reservations can be made for that day. (Refer to section 3.2.6 of this specification for a description of the Setup Date Dialog.)

3.2.1.1. Usage: Main Golf Reservation Window The user can navigate to any date they wish by using the Prior Date, Today, Go To

Date, or Next Date buttons.

To enter a reservation, the user will double-click an “Available” slot. (Available slots only exist on days that the manager has set up but not yet closed out.) This will display the Golf Reservation pop-up (Section 3.2.2) where the user can enter the reservation information.

To change the date and/or time of a reservation, the user will right-click on the reservation in the main window, and select CHANGE TIME in the pop-up menu. (The reservation will remain in its old date and time until the change has been completed.) The user will then navigate to and right-click on the desired Available slot, and select NEW TIME from the pop-up menu. The reservation will be moved from the old slot to the new one. (The CHANGE TIME menu item will only be available on Reservations. The NEW TIME menu item will only be available on Available slots, and only immediately after CHANGE TIME have been selected on a reservation. Any actions other than navigating to a new date/time will cancel the Change Time operation so that the NEW TIME menu item will not be available.)

To change anything other than the date and/or time of a reservation, the user will double-click on the reservation in the main window to display the Golf Reservation pop-up (Section 3.2.2) and make the needed changes.

To honor a reservation, the user will right-click on the reservation in the main window and select ARRIVED from the pop-up menu. This will change the background color to indicate that the reservation had been honored. To reverse this action, the user can right-click on the reservation again, and select NOT ARRIVED (which will replace ARRIVED) in the pop-up menu.

To cancel a reservation, the user will right-click on the reservation in the main window and select CANCEL from the pop-up menu. The Cancel Confirm dialog (Section 3.2.5) is displayed before the reservation is cancelled.

At the end of each day, the department manager will right-click on the date and select CLOSEOUT from the pop-up menu. (This menu item is only available if the earliest date that has not yet been closed out is in the past, or if it is today and there are no reservations for later in the day that have not yet been honored.) The Manager Sign-In dialog (Section 3.2.4) is displayed, and if valid sign-in is performed, the Golf Closeout window (section 3.2.7) will be displayed, allowing the manager to close out the date.

To set up reservation slots for a new date, the manager navigates to that date in the Main Window (It will display blank, indicating that date has not been set up.) The manager will right-click on the date and select SETUP DATE from the pop-up menu. The Manager Sign-In dialog (Section 3.2.4) is displayed, and if valid sign-in is



performed, the Setup Date dialog (section 3.2.6) is displayed, allowing the manager to set up that date for reservations.

3.2.1.2. Controls: Main Golf Reservation Window On initial startup, this window executes the TODAY button click.

Buttons: • Prior Date: Reduce the date by one day and display the data for that date. • Today: Set the date to TODAY and display the data for that date. • Go To Date: Set the date to the content of the edit box and display the data for

that date. (If the edit box is empty or is not a valid date, then display an error dialog, and leave the window unchanged.)

• Next Date: Increase the date by one day and display the data for that date.

Pop-up menu on date: • Setup Date: Call Setup Date dialog (Section 3.2.6). When it returns, update

the window. • Closeout: Call the Golf Closeout Window (Section 3.2.7). When it returns,

update the window.

Pop-up menu on reservation slots: • Add Reservation (on Available slots) Edit Reservation (on reserved slots):

(This menu item is the double-click action when it is available. It is not available on slots where Arrived is TRUE or on any slots on a day that has been closed out.) Call the Golf Reservation pop-up (Section 3.2.2) with the data for the selected reservation. When the pop-up closes, update this window.

• Change Time: (This menu item is available only on slots that are Reserved, and Arrived is FALSE on days that have not yet been closed out.) Mark the selected reservation to be moved. (Refer to the NEW TIME menu item, next.)

• New Time: (This menu item is available only on slots that are Available, and if nothing other than date navigation has been done since CHANGE TIME was selected.) Copy the reservation information from its original slot to the selected slot, and delete it from its original slot. Update the window.

• Arrived (if Arrived is FALSE) Not Arrived (if Arrived is TRUE): (This menu item is available only on Reserved slots on days that have not yet been closed out.) If Arrived is FALSE, then set it to TRUE, otherwise, set it to FALSE, then update the window.

• Cancel Reservation: (This menu item is available only on slots that are reserved, and Arrived is FALSE, on days that have not yet been closed out.) Display the Cancel Confirm dialog (Section 3.2.5). If it returns TRUE, then update the window.



3.2.2. Golf Reservation Pop-up (Note: The look, feel and functionality of this pop-up will be the same as the

Restaurant Reservation Pop-up, with the exception that it says “Golf” at the top, and it will be used for managing Golf reservations, so it will have the extra fields relevant to golf.)

When users make or edit Golf reservations, the system will display the Golf Reservation pop-up as shown in Figure 2, below. (For AVAILABLE slots, it comes up blank.) The user can enter or change the reservation information in this pop-up.

Golf Reservation Reservation for Thursday, Dec 16, 2004 @ 10:30 am

123456

Smythe, Dr. Andrew R.

4

1

0

No

Figure 2: RCC RMS Golf Reservation Pop-up

Member #

Member Name

# in Party

# of carts

# of club sets

Need Pro?

Notes

Reserve Cancel

3.2.2.1. Usage: Golf Reservation Pop-up In the Reservation pop-up, the user can enter the member’s number, their name, or

any part of their name. If number or name as it is entered is not found or is not unique, the Member Lookup dialog (Section 3.2.3) is displayed. A Manager may enter Member #000000, and, after signing in, make a reservation for a non-member.

The user can enter or change information in the five data fields, then click the Reserve button to save the information. The Cancel button will close the pop-up without saving the changes.



3.2.2.2. Controls: Golf Reservation Pop-up On field exit:

• Member #: o If value is blank, then do nothing. o If value is “000000”, then call the Manager Sign-In dialog (Section

3.2.4); if it returns FALSE, clear Member # and remain in this field. o On any other value:

§ Select the Member.Last_Name, Member.First_Name, Member.Middle_Initial.

§ If Member # is not found, then call the Member Lookup dialog (Section 3.2.3) passing nothing.

§ Place the returned Member # and Member Name (if any) in the appropriate fields in the pop-up.

• Member Name: o If value is blank or Member # is not blank, then do nothing. o On any entered value:

§ Select the Member.Number, Member.Last_Name, Member.First_Name, Member.Middle_Initial.

§ If Member Name is not found or if more than one member matches the entered name, then call the Member Lookup dialog (Section 3.2.3) passing the entered name.


Buttons: • Reserve: If Member # is blank or # in Party is blank or zero, then display an

error dialog, otherwise update the database with the entered data and return TRUE.

• Cancel: Update nothing and return FALSE.



3.2.3. Member Lookup Dialog (Note: This dialog will be identical to the Member Lookup dialog in the Restaurant

Reservation system.) This dialog (Figure 3) displays all of the data from the Member table in

alphabetical order by Last_Name, First_Name, Middle_Initial. If a name was passed, it scrolls to the closest match to that name. Member Lookup

Figure3: RCC RMS Member Lookup Dialog

Member # Name Address

Use Cancel

123456 Smith, John A. 1245 Crown Ave.

247891 Smith, John C. 26 Worthington Ct.

756823 Smith, John R. 4721 Highland Ave., Suite 900

096432 Smith, Walter D. 1 Smith Way

827354 Smythe, Dr. Andrew R. 423 Forrest Rd.

698721 Snaite, Barbara, W. 56452 State Rte 437

3.2.3.1. Usage: Member Lookup Dialog The user may scroll through the membership list, select any name by clicking on it,

and click the Use button to return that member’s number and name, or the Cancel button to close the dialog without returning anything.

3.2.3.2. Controls: Member Lookup Dialog Buttons:

• Use: If no row has been selected in the list, then display an error dialog, otherwise return TRUE along with Member.Number, Member.Last_Name, Member.First_Name, Member.Middle_Initial.

• Cancel: Return FALSE and no data.



3.2.4. Manager Sign-In Dialog (Note: This dialog will be identical to the Manager Sign-in dialog in the Restaurant

Reservation system.) This dialog (Figure 4) allows managers to sign in for special functions that only

managers can perform.

Manager Sign-In

Figure 4: RCC Manager Sign-In

User ID

Password

Sign In Cancel

3.2.4.1. Usage: Manager Sign-In Dialog The manager must enter a valid User ID and Password. If a valid manager Userid

and Password are entered, the entry is accepted.

3.2.4.2. Controls: Manager Sign-In Dialog Buttons:

• Sign In: Validate the User ID and Password against the Manager Sign-In table. o If User id or Password is blank, display an error message and do not

return. o If the User id and Password match, then return TRUE, otherwise

display an error message and do not return. • Cancel: Return FALSE.



3.2.5. Cancel Confirm Dialog (Note: This dialog will be identical to the Cancel Confirm dialog in the Restaurant

Reservation system.) The Cancel Confirm dialog (Figure 5) will be displayed before a reservation is

cancelled to confirm this non-reversible action.

Cancel Reservation

Reservation for Thursday, Dec 16, 2004 @ 10:30 am

Smythe -- Party of 4

Figure 5: RCC RMS Cancel Reservation Pop-up

Remove Keep

3.2.5.1. Usage: Cancel Confirm Dialog The user must click the Remove button to confirm that the reservation should be

cancelled, or the Keep button to not cancel the reservation.

3.2.5.2. Controls: Cancel Confirm Dialog Buttons:

• Remove: Delete the reservation from the database, and return TRUE. • Keep: Leave the database unchanged, and return FALSE.



3.2.6. Setup Date Dialog (Note: This dialog will be identical to the Setup Date dialog in the Restaurant

Reservation system.) The manager uses this dialog (Figure 6) to set up the reservation slots for each day

that reservations will be taken.

Figure 6: RCC RMS Setup Date Window

Minutes/Period

Slots/Period

Set Up Cancel

Thursday, Dec 16, 2004

First Time

Last Time

Setup Date

3.2.6.1. Usage: Setup Date Dialog After signing in, the manager will enter the times when the first and last

reservation slots for that day will be available, the number of minutes in each period, and the number of slots for reservations in each period.

Clicking the Set Up button will add those Available slots to the database for that day. Clicking the Cancel button will leave the database unchanged.

3.2.6.2. Controls: Setup Date Dialog When this dialog opens, call Manager Sign-in dialog (Section 3.2.4). If it returns

FALSE, then return FALSE.

Buttons: • Save: Perform these validations (if any fails, display the error dialog and stop):

§ First_Time & Last_Time are valid times between 00:00 & 23:59 § First_Time < Last_Time § Minutes per period is an integer, > zero and a multiple of the

number of minutes between First_Time and Last_Time § Slots per period is an integer, and between zero and 25

o If all validations pass, then write an Available row in the database for each slot in each time period, and return TRUE.

• Cancel: Write nothing and return FALSE.



3.2.7. Golf Closeout Window (Note: This window is completely different from the Closeout Day dialog in the

Restaurant Reservation system.) The manager uses this window (Figure 7) to review the charges for the day and

make adjustments to them before submitting them to the Accounting System.

Richman's Country Club -- Golf Course Closeout Thursday, Dec 16, 2004

123456 -- Arnold, Richard A.

$20.00 -- 9 Holes for a 4-some

Figure 7: RCC RMS Golf Course Closeout Window

$25.00 -- Cart Rental

387512 -- Miller, Anita R.

$10.00 -- Golf reservation no-show fee

827354 -- Smythe, Andrew R.

$30.00 -- 18 Holes for a 4-some

$25.00 -- Cart Rental

$25.00 -- Clubs Rental

Submit Cancel

3.2.7.1. Usage: Golf Closeout Window After the manager signs in, this window compiles the proposed transactions for the

date from the Golf reservation data in the reservation database and the Reservation_Charge table, sorts them by Member.Last_Name, Member.First_Name, Member.Middle_Initial, and holds those transactions in a temporary table. It then displays those transactions, allowing the manager to review and make changes before submitting them to the Accounting system for processing.

To change a transaction, the manager right-clicks on any transaction and selects Edit Transaction from the pop-up menu. The Golf Transaction pop-up (Section 3.2.8) is displayed with the information from the transaction that was right-clicked, then the manager can change any information before updating it to the temporary table. The window is then re-displayed.



To delete a transaction, the manager right-clicks on the transaction and selects Delete Transaction from the pop-up menu. After confirmation, the transaction is removed from the temporary table, and the window is re-displayed.

To add a transaction, the manager right-clicks on any transaction and selects Add Transaction from the pop-up menu. The Golf Transaction pop-up (Section 3.2.8) is displayed with the information from the transaction that was right-clicked, then the manager can change any information before adding it to the temporary table. The window is then re-displayed.

When the manager is satisfied with all charges for the day, he clicks the Submit button to submit them to accounting, and the date is closed. If he clicks the Cancel button, after confirming, the temporary table is discarded and the date is not closed.

Closing a date consists of removing all unused (Available) reservation slots for that date and marking it as “Closed” in the database.

3.2.7.2. Controls: Golf Closeout Window When this window opens, call Manager Sign-in dialog (Section 3.2.4). If it returns

FALSE, then return FALSE.

Populate the temporary Golf transaction table with all of the charges for the selected date, based on the data in the Golf_Reservation and Reservation_Charge tables. Sort the temporary table by member number, then display the data in the Golf Closeout window.

Each time the Golf Closeout window is displayed or re-displayed, for each member who has any transactions in the temporary table, display the member number and name once, followed by all of the transactions for that member. On re-displays, scroll the list to the member whose data was changed. (If the last transaction for a member is deleted, then that member will not be listed in the re-displayed window, so scroll to the next member in the list.)

Pop-up menu on transaction: • Edit Transaction: Call the Golf Transaction pop-up (Section 3.2.8) passing

the transaction data and State = “Edit”. If the pop-up returns TRUE, then re-display the window.

• Add Transaction: Call the Golf Transaction pop-up (Section 3.2.8) passing the transaction data and State = “Add”. If the pop-up returns TRUE, then re-display the window.

• Delete Transaction: Display a confirm dialog. If the user confirms, then delete that transaction from the temporary table and re-display the window, otherwise do nothing.

Buttons: • Submit: Display a confirm dialog. If the user confirms, then copy all of the

transactions from the temporary table into the Member_Transaction table and return TRUE.



• Cancel: Display a confirm dialog. If the user confirms, then discard the temporary table and return FALSE.

3.2.8. Golf Transaction Pop-up (Note: This pop-up is completely new. None like it exists in the Restaurant

Reservation system.)

When a transaction is edited or added in the Gold Closeout Window (Section 3.2.7), the transaction is displayed in this pop-up (Figure 8). If the transaction is being added, the Save button will be hidden. Otherwise, the Add button will be hidden.

Golf Course Transaction Thursday, Dec 16, 2004

123456

Smythe, Dr. Andrew R.

$30.00

18 Holes for a 4-some

Figure 8: RCC RMS Golf Course Transaction Pop-Up

Member #

Member Name

Amount

Description

Save Cancel Add

The manager can change any information for the transaction and save those

changes in the temporary transaction table.

3.2.8.1. Usage: Golf Transaction Pop-up This pop-up window displays the data for the selected transaction in the Closeout

Window. The manager can change any information (including member number and name).

The Save button (Editing a transaction) updates the transaction in the temporary table. The Add button (Adding a transaction) adds a new row to the temporary table.



3.2.8.2. Controls: Golf Transaction Pop-up When this pop-up opens, if State = “Add”, then hide the Save button, otherwise

hide the Add button.

On field exit: • Member #:

o If value is blank, then do nothing. o If value is “000000”, then call the Manager Sign-In dialog (Section

3.2.4); if it returns FALSE, clear Member # and remain in this field. o On any other value:

§ Select the Member.Last_Name, Member.First_Name, Member.Middle_Initial.

§ If Member # is not found, then call the Member Lookup dialog (Section 3.2.3) passing nothing.


• Member Name: o If value is blank or Member # is not blank, then do nothing. o On any entered value:

§ Select the Member.Number, Member.Last_Name, Member.First_Name, Member.Middle_Initial.

§ If Member Name is not found or if more than one member matches the entered name, then call the Member Lookup dialog (Section 3.2.3) passing the entered name.


Buttons: • Save: If Member # is blank, then display an error dialog, otherwise update the

transaction in the temporary table, and return TRUE. • Add: If Member # is blank, then display an error dialog, otherwise add the

transaction as a new row in the temporary table, and return TRUE. • Cancel: Return FALSE.

3.3. Performance Requirements All transactions in this system must take less than 2 seconds to complete.

3.4. Design Constraints All screens/windows will conform to the corporate standards as documented in the

RCC System Standards document, Version 4.2.



3.5. Software System Attributes

3.5.1. Reliability This system must not fail more often than once per year. Any failure must result in

the loss of less than one day’s data.

3.5.2. Availability The system must be available during all business hours of the RCC (7:00am to

2:00am, 7 days per week). The system must recover from any failure in less than 10 minutes.

3.5.3. Security Most functions are available to anyone with access to the terminals located

throughout RCC. Manager functions are available only to managers who are authenticated by User ID and Password. The system will not be available remotely via the internet or by any other means.

3.6. Other Requirements

3.6.1. Data Dictionary

3.6.1.1. Database – Existing Tables The relevant attributes of the existing database tables that will be used by the

software are shown here.

Member • Number – 6 digits • Last_Name – Up to 20 characters & special characters • First_Name – Up to 20 characters & special characters • Middle_Initial – Up to 2 characters (a letter and a period) • Honorific – Up to 5 characters (Letters and period) • Street_Address – Up to 20 characters & special characters • City – Up to 20 characters & special characters • State – 2 Letters • Zip – 5 digits • Status – 1 digit (1 = Active member)

Manager_Passwords • User_ID – 3-12 characters (must be unique) • Password – 6-12 characters



Member_Transaction • Member_Number – 6 digits must be a valid Member.Number • Trans_Type – 3 digits (329 = Golf Course, 429 = Tennis Court,

779 = Restaurant reservation charge) • Trans_Date – Valid date (MM/DD/YYYY) • Description – Up to 50 characters & special characters • Dollar_Amount – Dollars and cents up to $9,999.99

3.6.1.2. Database Requirements New database tables that will be required by the software are shown here.

Golf_Reservation • Member_Number – 6 digits must be a valid Member.Number • Date – Valid date (MM/DD/YYYY) • Time – Valid time (HH/MM, HH=00-23, MM=00-59) • Party_Size – number from 1 to 99 • Carts – number from 0 to 9 • Clubs – number from 0 to 99 • Pro – Boolean (True or False) • Notes – Up to 250 characters & special characters • Arrived – Boolean (True or False)

Reservation_Charge • Type – 3 digits • Dollar_Amount – Dollars and cents up to $9,999.99 • Description – Up to 50 characters & special characters This table will be populated as follows: Type Dollar_Amount Description 100 $10.00 Golf Tee Time No-Show Fee 101 $20.00 18 Holes of Golf 110 $25.00 Golf Cart Rental 115 $25.00 Golf Clubs Rental 120 $50.00 Golf Pro Fee

planning for effective testing case study - · pdf filethis case study provides the...

Documents