USC IITV Presentation Template

CS 577b Spring 2009 – Test Cases from UML Model

CS 577a Fall 2009

Test Cases from UML & UC Desc.
EC32a…V8
Nov 16, 2009

A. Winsor Brown

Goals of Presentation

Reference Material from RUP

Pre-Requisites for Acceptance Tests from Use Cases

· Business Activity Model from OCD

· Use Cases covering Business Activities

· Use Case Descriptions (from SSAD=document+models)

Reference Material from RUP

Version 2002.05.01.305.000 [UML 1.8?] (available on old documentation CD) also ”GuidelinesAndArtifacts--TestCaseDevelopment.zip”[See HTML files in un-zipped "ec33b-Guidelines...zip"]

· Artifact--UseCase

· Guidelines Test Case

· Guidelines--ActivityDiagramInTheBusinessObjectModel

· Guidelines--ActivityDiagramInTheBusinessUse-CaseModel

· GuidelinesTestData

Artifact--UseCase

Guidelines Test Case

Guidelines--ActivityDiagramInTheBusinessObjectModel

Guidelines--ActivityDiagramInTheBusinessUse-CaseModel

GuidelinesTestData

Reference Material from ebase

Fulltext Title Database – Team #08 Spring 2001
Iteration 3 http://ebase.usc.edu:8080/usercontrol/csci577/cs577b_2001/team08b/default.aspx
[NOTE: Exact reference being checked; to be added to EP page.]

· As-built OCD

· As-built SSRD

· As-built SSAD

· As-built Rose Models (MDL)

Fulltext Title Database – Use-case Descriptions(generated after the fact); See Guidelines page (on Course website), Rose and UML section.

The Business Activity Diagram

Also known as a business workflow

Should be first diagram(s) in MBASE OCD section “4.5.3 Processes”

· Ooops: 4.5.3 says

- “Describe how the new system will change the organization’s processes….

- “Representation: As in section OCD 3.3.3 (current organization processes), create either:

a. A list of process names & a “story” to describe each one.

b. A Business Use–Case Model"

· Ooops: 3.3.3 says

- “b. A Business Use–Case Model is a kind of Use–Case Model that describes the organization’s processes, …. Create one or more Use–Case Diagrams that show the processes, the actors, and the relation among them. For each process, create a Business Use–Case Description, and an Activity Diagram. "

LeanMBASE moved these to SSAD

Workflow Diagram 1

Workflow Diagram 2

Correct Business Process (use-case) Diagrams

Same level of detail as use-cases for each activity (workflow) diagram.

To be supplied: would have just Sys Admin Process and User Process use-case!

To be supplied.

More Detailed Business Use-case Diagram

What’s a “Scenario”

From Work Flow diagram: a thread from start state to an end state. The diagram below has three?

Acceptance Test Case

For every action/activity in a thread, use the Use-case description to guide in the development of the Test Case Data and response. Screen shots can help web based systems.

Admin Login Use-case Description

Acceptance Test Case from Use-Cases

Pick a scenario from the Business Activity (Workflow) diagram (in OCD). Identify the steps.

For each step, using the SSAD if necessary, go to a use-case description that fulfills the “action” step.

Use the Use-case Description and your imagination to create the test data. From the test data and the prototype (in the beginning) or the running system, re-use screen shots (WITH annotations) added to show expected results.

Does anyone see a problem??

· For instance, step Alternate course of action, step "4" of Admin Login)?[How many repetitions? Implications for password busters? Caught when? Caught how? Reported when?]

· Others?

EP-? alludes to detecting these types of problems.

Test Case(s) from Use-case(s)

Acceptance Test Characteristics

· Functional or Performance (at least some)

· Black Box

· Use Activity diagram’s scenario(s) traced to Use-case Descritions

Integration Test

· Interface tests

· White Box

· Sequence Diagram or Collaboration Diagram

What about “tests” for non-functional non-performance requirements

AKA IICM-Sw’a Project Requirements; generally called “constraints”

Examples

· Programming Languages X & Y

· Particular COTS package Z

“Test” (identify compliance with requirements) after software is built

· Active execution of test cases

· “Inspection”

Very Lst Line- format is Tiny