1.  Week03 Jerry Kotuba SYST30009-Engineering Quality Software 1

2.  Quiz No 1 (week04)  Schedule o Assignment Details  Recap last class o Use Cases Scenarios “Includes” & “Extends” relationships  Software Testing o Black Box Techniques Generating Test Cases o White Box Techniques Jerry Kotuba SYST30009-Engineering Quality Software 2

3.  Includes o Case In Point – “Stop Payment”  Extends o Case In Point – “Register Student” Jerry Kotuba SYST30009 - Engineering Quality Software 3

4.  Tend to see more includes.  Extends are fewer. Jerry Kotuba SYST30009 - Engineering Quality Software 4

5. Jerry Kotuba SYST30009 - Engineering Quality Software 5

7.  Coupling o Each use case should be as independent as possible should stand alone (i.e., have little or no coupling)  Cohesion o Each use case should have a single responsibility/goal Each use case should specify a significant chunk of functionality and show how the system provides value to an actor. All the functionality in one use case should be about accomplishing one goal of an actor (i.e., have high cohesion). In a system for a typical automated teller machine (ATM), one use case would be "Withdraw Cash" and another "Transfer Funds." Each use case concentrates on a single goal. Jerry Kotuba SYST30009-Engineering Quality Software 7

8.  A test case is… o A set of test inputs o Execution conditions o Expected results …developed for a particular objective: to exercise a particular program path or verify compliance with a specific requirement. Jerry Kotuba SYST30009-Engineering Quality Software 8

9.  Test cases are necessary to verify successful and acceptable implementation of the product requirements Jerry Kotuba SYST30009-Engineering Quality Software 9

10.  Three step process o For each use case, generate a full set of use-case scenarios o For each scenario, identify at least one test case and the conditions that will make it “execute”. o For each test case, identify the data values with which to test. Jerry Kotuba SYST30009-Engineering Quality Software 10

11.  Activity Diagrams can be particularly helpful here Jerry Kotuba SYST30009-Engineering Quality Software 11

12.  Course Registration System Jerry Kotuba SYST30009-Engineering Quality Software 12

13. Jerry Kotuba SYST30009-Engineering Quality Software 13  Register For Course  1. Logon  This use case starts when a Student accesses the Sheridan Web site.  The system asks for, and the Student enters, the student ID  and password.  2. Select 'Create a Schedule'  The system displays the functions available to the student. The  student selects “Register for Course.“  3. Obtain Course Information  The system retrieves a list of available course offerings from the  Course Catalog System and displays the list to the Student.  4. Select Courses  The Student selects a course offering from the list of available course  offerings.  5. Submit Schedule  The system verifies that the Student has the necessary prerequisites.  6. Display Completed Schedule  The system displays the schedule containing the selected course  for the Student. Basic Flow

14. Jerry Kotuba SYST30009-Engineering Quality Software 14  Register For Course  1. Unidentified Student  In Step 1 of the Basic Flow, Logon, if the system determines  that the student ID and/or password is not valid, an error  message is displayed.  2. Unfulfilled Prerequisites, Course Full, or Schedule  Conflicts  In Step 5 of the Basic Flow, Submit Schedule, if the system  determines that prerequisites for a selected course are not  satisfied, the system will not enroll the student in the course. A  message is displayed that the student can select a different  course. The use case continues at Step 4, Select Courses, in the  basic flow.  3. Course Catalog System Unavailable  In Step 3 of the Basic Flow, Obtain Course Information, if the  system is down, a message is displayed and the use case ends.  4. Course Registration Closed  If, when the use case starts, it is determined that registration  has been closed, a message is displayed, and the use case  ends. Alternate Flows

15.  Illustration – System Architect Jerry Kotuba SYST30009-Engineering Quality Software 15

16.  There is one more thing to describe before we concentrate on how use cases can be used to generate test cases: a use-case scenario.  A use-case scenario is an instance of a use case, or a complete "path" through the use case.  End users of the completed system can go down many paths as they execute the functionality specified in the use case.  Following the basic flow would be one scenario.  Following the basic flow plus alternate flow A1 would be another. The basic flow plus alternate flow A2 would be a third, and so on. Jerry Kotuba SYST30009-Engineering Quality Software 16

17. Jerry Kotuba SYST30009-Engineering Quality Software 17 Use Case Scenario Table

18. Jerry Kotuba SYST30009-Engineering Quality Software 18

19. Jerry Kotuba SYST30009-Engineering Quality Software 19

20. Jerry Kotuba SYST30009-Engineering Quality Software 20

21.  ICE-02 is in week 03 of the course materials on SLATE Jerry Kotuba SYST30009-Engineering Quality Software 21

22.  Investigate Other Black Box Testing Techniques Jerry Kotuba SYST30009-Engineering Quality Software 22