Software Testing and UML

These previous approaches ignore much of the complexity of software testing sure world systems, such as the fault models that apply to the system as it moves through the test phases. In the section below, I outline an agenda for applying the UML to the software testing process. Many of the steps require research and effort to show their feasibility, but I believe that the effort is sorely needed.

Model Based Software Testing

The need for specialized features for testing, the important research task at hand is to determine the course of action for using the UML for testing. The conservative approach would be to define modeling libraries to standardize components for reuse in developing test models. This is a preferred solution when it provides enough expressive power for building models. If more power is needed, extending the4-layered Meta model would need to be investigated.

Conclusion

I presented an overview of the UML and use of artifacts in OO software testing. The OO model current practices based tests fail to cover the entire cycle of software testing, and I presented a framework for using various UML diagrams in the testing process. Finally, I discussed the need for foresters to create their own models, or to change development models extensively to provide the required characteristics. These features require special support, such as the development of libraries to test models, or modification of the UML meta model to support test activities.