Applying Use Cases (Chapters 25,26)

1
Applying Use Cases(Chapters 25,26)

• Sriram Mohan

2
Outline

• Use Cases in Design and Implementation
• From Use Cases to Test Cases

3
Tracing Requirements to Design

• Some Requirements can be easily traced to code
• Orthogonal Design Problem

4
Solving the Orthogonality Problem

• Object-oriented design
• Well written use cases
• Modeling Software Systems

5
Solving the Orthogonality Problem

• A potential solution comes from software
  architecture
• The software architecture helps us understand
• what the system does and how it works, how the
  elements interact, and what type of patterns and
  pieces or the system are involved

6
Solving the Orthogonality Problem (continued)

• Architectural views
• Logical (for users)
• Implementation (programmers)
• Process (integrators)
• Deployment (system engineers)
• Use-case view (designers/testers ties things
  together)

7
Extra Credit

• How are use cases realized in the design model?
  Read Chapter 25 and submit a report. Please
  submit it via (Angel Weekly Content Extra
  Credit Week 05 Use Case Realization)

8
Outline

• Use Cases in Design and Implementation
• From Use Cases to Test Cases

9
Questions before Testing

• What is this system supposed to do?
• What are the things that can go wrong?
• How does the system respond?
• How do I create and record testing scenarios?
• How do I know that the system has been tested
  completely?
• Is there anything else the system is supposed to
  do?

10
Testing Terms

• Test Plan
• Test Case
• Test Procedure
• Test Script

11
Test Plans

1. The use cases each become multiple test cases in
   the test plan.

12
How do we use the use case?

• Steps in creating a test case
• Identify use-case scenarios (basic and alternate
  flows)
• Identify the test cases
• Identify the test conditions
• Add data values to the test case

13
1. Identify the Scenarios

• Identify the various paths through the system

Scenario Number OriginatingFlow Alternate Flow Next Alternate Next Alternate..
14
2. Identify the Test cases

• More than one test case can occur from each
  scenario. For instance, based on the input the
  expected result could be different.

Test Case ID Scenario Description Expected Result Actual Result
15
¾.Identify Conditions and Populate table
Test Case Id Scenario Description Cond. 1 Cond. 2 Cond. 3 Expected Result Actual Result




Use as many conditions as necessary for a use
case,
16
Some final remarks

• How much do we test?
• Black box testing tests the functionality. What
  about the internal design decisions?