CMIS 330 WEEK 6 STS

1. Buy here:
http://theperfecthomework.com/cmis-330-week-6-sts/
STS
Instructions
Scenario
You have been asked to lead a software development team to build a system fulfilling the
Statement of Need specified in project 1. Your team is employed by a small company. The
customer wants a project that balances reasonable development cost, timely delivery,
software quality, and functionality.
In this project, you will work as part of team to define, refine, and proof test case descriptions
for the B&B system. If you do not submit project 3 as part of a team you shall receive a zero
for this project. Assume that the code for your B&B system has been developed based on
the SDD whose requirements trace through the SRS to the SS. The next step is to develop a
software test specification (STS) that describes the test cases that you will perform to verify
correctness and validate compliance to customer requirements of your B&B system.
You will select components from the Architectural Context Diagram (ACD) for the B&B
system and using the derived use case and software requirements set for each software
component (as detailed in project 2) write the complete set of associated white and black
box test case definitions.
Completing this project will require that you produce a software test specification (STS)
document for the system. The objective is to produce a cookbook for testers. A tester really
only needs the STS, the test environment, the test tools, the test data, and of course, the
software.
STS Templates
Please develop your STS using the IEEE Standard for Software Test Documentation,
standard 829-1998, posted in the Reserved Readings section on the Class Menu. Section 6

2. in the IEEE Std 829-1998 is most relevant to this assignment, so focus on completing this
section as thoroughly as you can.
The assignment
Please provide test cases for the following:
● Test Case 2-Test the financial reports against the ledger (white box)
● Test Case 3- Test the credit card system with a bad credit card (white box)
Hints and suggestions
For the STS, we shall be using only a subset of the IEEE template; specifically section 6 of
the IEEE (Test Case Specification). Refer to Module 4 for information on software testing
and examples of black-box and white-box test case definitions. Remember: Each test case
is used to assess compliance to a SRS/SS requirement (i.e., Black Box) or to assess correct
computation, e.g., correct inventory level (i.e., White Box). Here are the details required for
each test case description:
Test objective
unique test case identifier
input specification
output specification
special environment conditions
special procedural requirements
execution procedure steps
dependencies
```````Test Case 1 has been completed```````````````````
Test Case 1

3. Test case specification identifier:
BBMTS-TS-01
Objective:
The main objective is to prepare a white box testing method for the calendar functions
section to ensure that various inputs/actions return expected results of the
Bed-and-Breakfast Tracking and Management System.
Test items
The test items used for this test case are the following:
● • Reservation[] verifyDates(date, date)
● • void reserveDates(date,date)
Input specification:
1. Click on a specific day in the calendar outlook located in the Calendar menu of the
BBTMS.
2. Press on the arrow button located on the upper left-side of the calendar outlook located in
the Calendar menu of the BBMTS.
3. Press on the arrow button located on the upper right-side of the calendar outlook located
in the Calendar menu of the BBMTS.
4. Insert “01/01/2016” into the text field on the upper right-side of the Calendar
menu.
5. Insert “07/01/2016” into the text field on the lower right-side of the Calendar
menu.
6. Press on the rectangular button located on the center right-side of the
Calendar menu.

4. 7. Inspect items located inside of a list view located in the center right-side of the
Calendar menu.
8. Press on the circular button located on the lower left-side of the Calendar
menu.
9. Press on the circular button located on the lower right-side of the Calendar
menu.
Output specifications
1. The specific day selected is highlighted in the calendar outlook.
2. Previous month is displayed in the calendar outlook.
3. Next month is displayed in the calendar outlook.
4. Reservation starting date is entered and displayed in the calendar menu.
5. Reservation ending date is entered and displayed in the calendar menu.
6. Check range date is selected for verify room availability.
7. Room items display vacancy status of the rooms based on the range date.
8. Help button is triggered by displaying useful content information to assist
user.
9. Exit Menu is triggered by closing calendar menu.
Environmental needs
The following needs are required for proper conduction of the test case; Acceptable amount
of hard drive space to store temporary data inputs, workstation equipment (desktop
configuration or laptop configuration) capable enough to perform multiple task

5. simultaneously, as well as an operating system with the BBMTS software installed.
Additionally, the following peripherals are used to perform the test case; monitor display
(CRT, LCD or LED), keyboard (QWERTY keyboard layout, AZERTY keyboard layout,
QWERTZ keyboard layout or HCESAR keyboard layout), and a computer mouse
(mechanical-type, opto-mechanical-type, laser-type or optical-type).
Special procedural requirements
User must initiate calendar services by selecting calendar menu in the BBMTS main menu.
Additionally, the user must insert start date and end date inputs into the BBMTS before
execute verification for an available room. Start date and End date must be entered using
Gregorian “DD/MM/YYYY” format (little-endian sequence). Room items only display the
vacancy status of the rooms on the range date after “Check” button is pressed. The calendar
outlook only highlights the current reserved dates for a particular month and not the vacancy
status of the rooms on a particular month.
Intercase dependencies
No intercase dependencies are applied for this test case
Intercase dependencies are not used in the test case.