OOPSLA '04

Program
Technical Program
  Invited Speakers
  Technical Papers
  Onward!
  Panels
  Practitioner Reports
  Tutorials
Workshops
DesignFest
Educators' Symposium
Demonstrations
Posters
Doctoral Symposium
Exhibits
Student Research Comp.
FlashBoF
 
Turing Lecture
 
Social Events
 
Week at a Glance
 
Final Program (1.5M .pdf)

Find in Program
 

Page
Printer-friendly

Basket
view, help

"Guided Inspection of UML Models"
Object-Oriented Programming, Systems, Languages and Applications
Home    Program    Housing & Transportation    Registration    Submissions    Wiki    Maps
 
  > Technical Program > Tutorials > All Tutorials

 : Sunday Morning Tutorials (8:30 - 12:00) : Sunday : Methodologies

Guided Inspection of UML Models

Meeting Room 16
Sunday, 8:30, half day
 


 
7·8·9·10·11·12·13·14·15·16·17·18·19·20·21

John McGregor, Clemson University:  Dr. John D. McGregor is an associate professor of computer science at Clemson University, a Visiting Scientist in the Product Line Systems program at the SEI, and a partner in Luminary Software, a software development consulting firm. Dr. McGregor has conducted research for organizations such as the National Science Foundation, DARPA, IBM and AT&T and consulted for many corporations. Dr. McGregor is co-author of "A Practical Guide to Testing Object-Oriented Software" published by Addison-Wesley. He has published numerous articles on software product lines, software design and quality issues. Dr. McGregor is a regular contributor to the Journal of Object Technology.

Tutorial number: 6

There is widespread agreement that finding defects as early in the development life cycle as possible is cost-effective; however, there are few systematic techniques for accomplishing this goal. Guided inspection is an inspection technique that is "guided" by test cases. By using test cases, each guided inspection is tailored to the semantics expected for that particular model.

By constructing a "complete" set of test cases, the guided inspection technique identifies elements missing from the model as well as evaluating the quality of those that are present. This tutorial will give attendees the tools they need to systematically inspect UML2.0 models and will help those using other design notations to create a process for their projects.

Guided Inspection has several benefits:

  • Objectivity—By systematically selecting test cases, all portions of the model can be given equal coverage.
  • Traceability—Test cases link the faults detected back to the requirements making them easier to correct.
  • Testability—By creating test cases early in the process, problems with the statement of the requirements or the design are identified while changes are less costly.

Beginner: Attendees should have a background in design and modeling using UML.