Research Of Transforming UML Collaboration Diagram To Finite Automata Observation Model

Component-Based Software Development Technology is a new and gradually mature software development technique. As a Large size of the reuse unit, the component makes software development to transform into Component Integration, so it reduces the cost greatly and improve the software quality. However, traditional software testing technology is no longer applicable to component system testing made by the new properties of component itself. So it has become a very important problem in studying a new testing method which is suitable for component system and guiding the component testing via component system modeling.The paper starts from the analysis of software system structure, neglects the internal implementation details of software system, and unities software system structure into event and state. With the foundation of that, this paper summarizes the running behaviors of the software system, and specifies the requirement of component software to finite automata observation model.As the available industrial standard, UML can use the graphical method for modeling software systems. But because lots of concept of UML is based on non-formal Semantics, UML could not describe the model accurately, as well as lacking of accurate semantic, which is easy to generate fuzzy and ambiguity.The Finite automata can just make up the deficiency of accurate semantic of UML, and lay the foundation for component testing through the language identification principle of the automata. On the other hand, UML can reduce the difficulty of the software system modeling directly through the Finite automata. Their combination has very important meaning to the development of the component software testing.On the base of the analysis on the characteristics of UML Model, this paper chooses the UML collaboration diagram to model for component interactive, and transforms it into finite automata observation model to guide the component integration testing. The transformation step is as follows: first, defining the UML collaboration diagram formally and classifying the type of messages; second, using the RoseREI to extract the related information of the messages of collaboration diagram, and save it into database file *. MDL; then, defining the mapping rules from database file*. MDL to observation model; and last, generating automata observation model according to the message type of the collaboration diagram and the mapping rules.Finally, an confirmed example of PIN is analyzed to explain the transformation from UML collaboration diagram into automata observation model. And analysis and verify it using JFLAP.