Testing Object-Oriented Software - Homework #10 | ECEN 5543, Assignments of Electrical and Electronics Engineering

Material Type: Assignment; Class: Software Engineering of Standalone Programs; Subject: Electrical & Computer Engineering; University: University of Colorado - Boulder; Term: Spring 2004;

Typology: Assignments

2019/2020

Uploaded on 11/25/2020

koofers-user-an6-1
koofers-user-an6-1 🇺🇸

5

(1)

9 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
ECEN5543 University of Colorado Spring, 2004
Testing OO Software
Homework #10, due April 15, 2004
Consider this Guided Inspection Process Checklist from A Practical Guide to Testing
Object-Oriented Software by McGregor and Sykes:
1. Decide how completeness, consistency and correctness will be judged for the
particular use in the model under test (MUT).
2. Determine which scenarios to sample from the use case model to use as test
cases.
3. Create test cases by supplementing the scenarios with specific data.
4. Select the model/notation that will record the results of each execution.
5. Conduct tests.
6. Evaluate the results of the test executions to determine which tests the model
passed and which it failed.
7. Record the results for use in guiding the repair and testing processes in the
next iteration.
Your Homework Assignment:
a. Apply step 1 to
Domain Model Inspections (An example of a domain model is on page 176.)
Collaboration Diagram Inspections (An example of a Collaboration Diagram is on
page 199; another example is attached.)
Do steps b through f in the context of the Collaboration Diagram Guided Inspection, using
the attached diagram as the MUT.
b. Apply step 3 using the Fully Dressed Example in Applying UML and Patterns, page 50,
for the Success Scenario and Alternative Flows 3a through 3-6c. That is, create test cases
with actual values for these (about 10).
c. Decide whether you will use Collaboration Diagrams or Sequence Diagrams as the
model/notation to record the executions. (Do not invent a new model/notation; you will
need to annotate an existing model/notation with your specific data or computed return
values.)
d. Conduct (execute) tests using three of the test cases you created above.
e. Evaluate the results of the test executions.
f. Record the results.
Turn in your work products for steps a. through f.
Note: This collaboration diagram has some mistakes with respect to OO guidelines and
UML rules for capitalization. For example, the message initiateSale() is capitalized.
However, this is a “picture” that I included into this document. I do not have the ability to
edit it.
pf2

Partial preview of the text

Download Testing Object-Oriented Software - Homework #10 | ECEN 5543 and more Assignments Electrical and Electronics Engineering in PDF only on Docsity!

ECEN5543 University of Colorado Spring, 2004 Testing OO Software Homework #10, due April 15, 2004 Consider this Guided Inspection Process Checklist from A Practical Guide to Testing Object-Oriented Software by McGregor and Sykes:

  1. Decide how completeness, consistency and correctness will be judged for the particular use in the model under test (MUT).
  2. Determine which scenarios to sample from the use case model to use as test cases.
  3. Create test cases by supplementing the scenarios with specific data.
  4. Select the model/notation that will record the results of each execution.
  5. Conduct tests.
  6. Evaluate the results of the test executions to determine which tests the model passed and which it failed.
  7. Record the results for use in guiding the repair and testing processes in the next iteration. Your Homework Assignment: a. Apply step 1 to  Domain Model Inspections (An example of a domain model is on page 176.)  Collaboration Diagram Inspections (An example of a Collaboration Diagram is on page 199; another example is attached.) Do steps b through f in the context of the Collaboration Diagram Guided Inspection, using the attached diagram as the MUT. b. Apply step 3 using the Fully Dressed Example in Applying UML and Patterns, page 50, for the Success Scenario and Alternative Flows 3a through 3-6c. That is, create test cases with actual values for these (about 10). c. Decide whether you will use Collaboration Diagrams or Sequence Diagrams as the model/notation to record the executions. (Do not invent a new model/notation; you will need to annotate an existing model/notation with your specific data or computed return values.) d. Conduct (execute) tests using three of the test cases you created above. e. Evaluate the results of the test executions. f. Record the results. Turn in your work products for steps a. through f. Note: This collaboration diagram has some mistakes with respect to OO guidelines and UML rules for capitalization. For example, the message initiateSale() is capitalized. However, this is a “picture” that I included into this document. I do not have the ability to edit it.

: Customer : Cashier : Payment : ProductCatalog : ProductSpecification : Register : SaleLineItem : Sale

  1. (^) Checkout[array of Items]
    1. InitiateSale()
    2. [1...N]addItem(ID,Qty)
    3. makePayment(cashTendered)
  2. [1...N]lookupInfo(ID) 8.1 [1...N] setInfo(price,description)
  3. CreateSale()
  4. [1...N]addItem(ID,Qty)
  5. makePayment[cashTendered()
  6. [1...N]CreateSaleItem(ID,Qty)
  7. createPayment(cashTendered)
  8. GetSpec(ID) 7.1 [1...N]SetInfo(price,description) Collaboration Diagram for the UseCase UC1: Process Sale analysis.