Chapter 15. Domain Verification


The models we have built are the application, or some fragment of it. After we've done all this work to create these Executable UML models, complete with constraints and executable actions, it only makes sense that we actually execute these models to ensure they produce the desired behavior.

There are different kinds of verification that can be applied to the models. Static verification is the kind of checking a modeling tool does. A tool that understands the semantics of Executable UML can check to make sure that the models are constructed properly classes have attributes, attributes have types and constraints, states have procedures, procedure action language compiles correctly, and so forth.

This chapter focuses on dynamic verification the process of running actual test cases against the models, just as you would test a Java or C program. After all, the models are executable, so most of the techniques you already know about how to write and run software tests apply equally.

While this chapter appears near the end of the book, remember that domain verification is an ongoing process throughout the life of a project. Just as we recommended developing models incrementally, we recommend testing the models incrementally as well.

This chapter provides a starting point for understanding how to establish test vectors from use cases and from the models, how to execute them automatically, and how to link unit test cases together to make system tests. For a more complete treatise, see a book that focuses on testing.



Executable UML. A Foundation for Model-Driven Architecture
Executable UML: A Foundation for Model-Driven Architecture
ISBN: 0201748045
EAN: 2147483647
Year: 2001
Pages: 161

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