Analyze Of UML Model Inconsistency

It is very difficult and fussy to model a complex system. In order to control and decrease the complexity of system model, multi-views are used to simplify the expression of models. A software system model is described by many different views, but each view only show certain content from some aspects, as a result, complexity of a model is separated into many different views. In common case, many sub-views are necessary to express the view clearly, thus, software system is separated to many different views and views are separated to many different sub-views. There are complex collaboration and restrict relationship among those views and sub-views, and because our limited ability to deal with that relationship, inconsistency is hard to avoided.The inconsistency in UML modeling process is mainly discussed in this paper. It is the collision phenomena of describing the same thing by different views and sub-views, caused by the complexity of system and different development criterion or thinking style among development groups. In the beginning stage, we should develop under certain tool with correct lead and atomic maintenance ability, and should abide some modeling rules to avoid inconsistency as soon as possible. We can make use of real time examination, dynamic examination , static examination and assistant technique to detect diagrams, also can we use a method named view-Integra approach, this method separate the inconsistency comparison from inconsistency diversion, and comparison occurred after switching those into the same diagram style, by this way, we decrease complexity from 0(n~2) to 0(n). With this idea, all diagrams are divided into three categories and transforming between those categories often involves similar...