Australian Journal of Basic and Applied Sciences, 5(6): 1594-1598, 2011 ISSN 1991-8178 Corresponding Author: Arifa Bhutto, Department of Energy and Technology, Esbjerg Niels Bohrsvej 8 6700 Esbjerg, Dk E-mail: Abh@et.aau.dk, Akh@et.aau.dk 1594 Formal Verification of UML Profile Arifa Bhutto, D.M. Akbar Hussain Department of Energy and Technology, Esbjerg Niels Bohrsvej 8 6700 Esbjerg, Dk Abstract: The Unified Modeling Language (UML) is based on the Model Driven Development (MDD) approach which capturing the system functionality using the platform-independent model (PMI) and appropriate domain-specific languages. In UML base system notations, structural view is model by the class, components and object diagrams and behavioral view model by the activity, use case, state, and sequence diagram. However, UML does not provide the formal syntax, therefore its semantics is not formally definable, so for assure of correctness, we need to incorporate semantic reasoning through verification, specification, refinement, and incorporate into the development process. Our motivation of research is to make an easy structural view and suggest formal technique/method which can be best applied or used for the UML based development system. We investigate the tools and methods, which broadly used for the formal verification of UML based systems. Key words: Formal Methods, Components, Formal syntax, Domain specific, Semantic. INTRODUCTION The increasing complexity of software systems makes essential that performance aspects can be analyzed from the early phases along the entire software lifecycle. Traditionally the system development is divided into analysis, design and implementation. If faults are discovered lately in the system development process, which lead you to either abandon the system entirely or go through redesign or re-develop the system, this process goes on until the system becomes acceptable, therefore, to avoid such faults, implementation phase is followed by the test phase and similarly analysis and design phase followed by the design verification phase. As we know commercially development of the software design is based on the UML diagrams (Tsiolakis, 2001). However UML does not provide the assurance of correctness and verify the design models according to the corresponding system desired properties. Therefore, verification of design should be done by the formal methods which provide the suitable verification and validate the system according to the desired properties of the systems (Bondavalli, 2005). The research focuses on to explore how formal techniques can be or should be used to verify the systems at different level of abstraction. We also investigate the various formal methods which is commonly used for the specification, verification and testing of the UML based design diagrams at different level of system development. UML Overview: In the last few years the Unified Modeling Language (UML) diagrams (W. Ahrendt, 2000) has been adopted as a standard design diagrams for software development, and it is positively helpful and successfully used from requirement specification to the implementation process. UML design diagrams are successful due to the following reasons: C UML modeling is favorably applicable for the different types of domain or subject area. C UML design diagram captures the structural, operational and behavioral aspect of the system. C The same notations can be used for specification to the implementation of the system. C UML is widely open language and most popular due to extensibility mechanisms. C In UML we can developed or design the different systems domain, methods and process easily and more comfortably. C UML can be extended or constructs in particular context like (e.g., performance requirement validation, refinements). C UML has to support for the various tools developed by the different vendors. C In UML diagram we can capture the static structure, behavioral structure and interaction of the systems components easily through available notations.