Exercises


graphics/exercise.gif

4-1. Using the use cases of your project as a starting point, you add the Frequency and Criticality fields to them. Perform the risk analysis for the use cases and fill in that field for each use case. Develop an ordering of uses that reflects how intensely each should be tested. Write test cases for the use cases in the model. Write one test case for the least important use case. Write additional test cases for each of the use cases.

4-2. Conduct a guided inspection session for the initial analysis model for your project. Generate a report that lists the discrepancies between the models.

4-3. Develop three scenarios from the use cases given in this chapter. Then, using the models given in Chapter 2 and Chapter 4, identify examples of incompleteness, inconsistency, and incorrectness.

4-4. Select the phase in your software development process in which, in your estimation, more defects are created than any other. Design a guided inspection checklist that will lead developers to finding the types of defects created in that phase.



A Practical Guide to Testing Object-Oriented Software
A Practical Guide to Testing Object-Oriented Software
ISBN: 0201325640
EAN: 2147483647
Year: 2005
Pages: 126

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net