Thoroughly transform UML 2.0
During the four years of the UML 2.0 specification development process was finally drawing to a close. June 12, OMG (Object Management Group, the international Object Management Group) proposed adoption of the U2 Partners submitted the UML 2.0 superstructure specification. Through April 15 with the infrastructure specification, object constraint language, and map the exchange agreement, the mainstream UML software modeling specification once the most important upgrade revision process was finally completed successfully.
Broad look at the UML, it has not just a modeling language, but a family can be used to define the language Yuan Yuan Yuan core and a common modeling language combination; as narrow UML, UML 2.0 compared to previous the version in component-based software engineering, real-time and Embedded systems, business process descriptions and other capabilities greatly enhanced.
OMG's UML Amendment Task Force and co-chair of the design team, said Cris Kobryn, UML 2.0 has become a more solid basis of norms for the future of software engineering, testing and modeling of business rules to provide more powerful support.
UML is the OMG in 1997 and software systems for visualization, detail, structure and documentation of the Unified Modeling Language, object-oriented modeling of various natural product of an integrated unity. Originated in the Booch, OMT and OOSE three kinds of object-oriented UML modeling method can attempt to extend the application of any type of modeling, its applications are from the extended object-oriented system modeling to structural design systems, business processes, things the system, real-time and embedded systems Web applications, even non-software systems in the field of modeling.
UML 1.X series of the amendment makes the UML is widely accepted. With a greater awareness of the expectations placed UML, OMG 1999, proposed amendments to the information needs of UML 2.0 has been more response, the majority of respondents have suggested that UML should be a major amendment.
Needs and proposals submitted proposals
OMG demand the release of 2.0, after the revised information, listen to the modeling tools from providers, users, academic institutions, advisory bodies and other standardization organizations, the recommendations of the 26 respondents, and in early 2000 released UML 2.0 4 the demand component of the proposal (RFP), are: infrastructure (Infrastructure), superstructure (Superstructure), Object Constraint Language (OCL) and Figure exchange (Diagram Interchange) demand. Infrastructure and superstructure in which the UML 2.0 proposal constitutes the main part of the demand.
Demand in the proposal after the release of three years, a number of proposals for organization analysis and design of the OMG Task Force (the Analysis and Design Task Force, referred to as AD) submitted their proposal document. AD members of Task Force meetings held from time to time to study the various proposals, the final adoption of the proposal or vote by the membership. The more important proposal organization: U2P (UML2 Partners Consortium), 2U (Unambiguous UML Consortium), 3C (Clear, Clean, Concise UML), DSTC (Distributed Systems Technology Centre), Fujitsu, OCL 2.0 consortium so.
Ultimately, U2P infrastructure and superstructure proposals and the OCL OCL 2.0 Consortium proposed to adopt the proposal by AD, which means OMG UML 2.0 was officially accepted. U2P the foundation and superstructure reason why the proposal can be adopted, and U2P proposal as the largest team of UML 2.0 is inseparable from the organization includes 19 sponsors and 33 supporters.
In the UML 2.0 specification document before release from the OMG, but also through a release process, this decision will be referred to as Task Force (Finalization Task Force, referred to as FTF) of the OMG agency after six months to a year to complete. There is still some debate, including whether the four should be completed specification into a FTF, and how the infrastructure MOF (Meta Object Facility, meta object facility) coherence and other issues.
Infrastructure: the focus of business
UML 2.0 Infrastructure design goal is to define a meta-language of the core InfrastructureLibrary, through the reuse of this core, in addition to the definition of a self-development of UML metamodel, you can define other element model, including the MOF, and CWM (Common Warehouse Model Public warehouse model), shown in Figure 1. As the common core library, the UML and MOF, CWM in more consistent architecture. Meanwhile, InfrastructureLibrary also provides custom UML stronger mechanism that allows user-defined for different platforms (such as. NET, J2EE, etc.) and areas (such as telecommunications, finance, engineering) dialect.
Figure 2 shows the internal structure of InfrastructureLibrary package. InfrastructureLibrary package from the containing element model highly complex structures with the Core package and for the definition of UML Profiles dialects in different areas formed package, Profiles package depends on the Core package. For the purpose of reuse, Core package further divided into several sub-package: atom type (PrimitiveTypes) sub-package contains some element modeling will be used in the predefined type; abstract elements (Abstractions) sub-package mainly consists of can be further specialization, or reuse by many abstract element model element class; structures (Constructs) sub-package mainly includes object-oriented modeling for specific element type; basic (Basic) sub-package contains a number of XML as the basis for creating structures.
In fact, on the basis of structure, standards makers and providers interested in modeling tools is much larger than ordinary modeler.
Superstructure: the user's interest
UML superstructure is the part of ordinary users really need, is UML the most interesting part of the natural users.
UML 2.0 superstructure design goals are: strict reuse infrastructure InfrastructureLibrary package structures; enhance component-based development and the MDA (Model Driven Architecture, Model Driven Architecture) support; optimization framework for the capacity of the Statute; enhancing behaviors Figure scalability, accuracy, integration and so on.
Figure (Diagrams)
UML 2.0 supports 13 types of diagrams (Figure 3), which can be divided into two categories: structure diagrams and behavior diagrams. Chart include: class diagrams, composite structure diagram, component diagram, deployment diagram, object diagram and package diagram; behavior chart include: activity diagram, interaction diagram, use case diagrams and state machine diagram, which is a sequence diagram interactive map, communications plan , interaction overview diagrams and timing chart referred to.
Compared with the UML 1.X, composite structure diagram, package diagram, interaction overview diagram and timing diagram are the new map. The original collaboration diagram renamed communication diagram, state diagram renamed the state machine diagram. Set of vocabulary to achieve the original plan (Implementation Diagram) was canceled.
Components (Components)
UML 2.0 is one of the most important amendments to enhance component-based software development support. Components can be combined to describe the internal structures chart, such as parts / implementation categories, connectors, and port structures and relationships. As part of a modular system, the internal components through the interface encapsulates the elements contained in the behavior and state of the external interfaces defined by its behavior, and can be replaced in their environment.
Components can be assembled and the collaboration between the interface components together to provide system functionality. In the UML 1.X, the concept of the main components used in the design phase of system implementation, while the 2.0 component model for the entire life cycle, the final deployment and runtime (Run-time) to optimize the environment.
Interactive (Interactions)
According to different purposes using the interactive, UML 2.0 can be expressed in several interactive map: sequence diagram, communication diagram, interaction overview diagram and timing diagram. Each plan provides the ability to adapt to different situations, but the interaction sequence diagram is the most abundant semantic graph, the strongest performance in a map.
In order to describe the complex interactions, UML 2.0 sequence diagram of the expansion in capacity has been significantly improved. The new core structures include: interaction occurred (Interaction occurrence), allows interaction from a reference to another, thus avoiding replication, are structurally more optimized; new combination of clips, interactive operator, the result in the sequence diagram can be expressed, such as selection, loop, parallel, orderly, and reference and other complex control structure; added to the Lifeline (Lifeline) decomposition ability, can be an example to refine the internal structure of interaction.
Interaction overview diagram is one of the new interactive map that describes the interaction (especially concerned about the control flow), but abstract away the message and the lifeline. It uses the activity diagram notation. Pure interactive overview map of all the activities are interactive place, so the chart will not have any information on and lifeline of the.
Another new, particularly suitable for modeling real-time and embedded systems is called the interaction diagram timing diagram. Concerned about the timeline along the linear sequence diagram, lifeline and the lifeline of the internal changes between conditions. It describes the object state changes over time, the situation, much like oscilloscope for analysis of periodic and aperiodic tasks.
Activities and actions (Activities / Actions)
UML 2.0 activity diagram enhanced the ability to model complex process, both support the control flow model, also support the object flow model. Which activities and actions to achieve the integration of activities defined flow diagram (process), action defines the implementation of the behavior of nodes, making a more direct and effective behavioral modeling.
The new core structures include: used bolt action input and output (Pins); structured node (Structured Nodes), can interrupt the regional (Interruptible Regions) and so on. Its original semantics of UML 1.X to enrich the core structures include: an increase in the edge of the flag, flow, abnormal parameters; enhanced activity graph on the multi-dimensional, layered and extended partition method; control node support bifurcation, convergence, decision-making, merged.
State Machine (StateMachines)
UML 2.0 major improvements for state machine are: the border through the state machine exit / entry points, for sub-state machine (state machine fragment) of the complete package, enabling pluggable replacement capacity; state machine can be specialized. A specialized state machine is a generalization of the extended state machine; protocol state machine can be an effective component of the port in the statute or operation sequence of the binding interfaces.
* Little information
The various comments for UML 2.0
Cris Kobryn (OMG's UML 2.0 Amendment Task Force and analysis of the design team's co-chairman): This is a more balanced language, which will map all of the acts better integrated. Popular component technology makes a better UML semantic elements. Enhance their language, in large part to help the embedded and real-time system developers and tool providers. In fact, UML has become the common language of MDA.
Grady Booch (UML one of the earliest advocates, Rational's chief scientist): UML 2.0 for system implementation in a lot of improvement to do, but also a lot of improvements for the MDA users.
Martin Fowler (OO methodologists): From UML 1.X to UML 2.0 has undergone a drastic change, which is the largest since UML accepted a check and revision.
Fred Waskiewicz (standard setter): UML to improve the usability. With the growth of UML, it is increasingly applied to new applications beyond the field of modeling.
Stan Hendryx (OMG's “Business Rules Special Interest” group chairman): UML 2.0 for most business users still too technical, difficult to use.
Sridhar Iyengar (MOF 2.0 specification one of the leaders from the IBM Corporation): UML and MOF are now integrated into a total core, and its internal integration more closely.
Jan Popkin (Popkin Software, Chairman): UML is growing, it is evolved into a multi-dimensional modeling. This is a good trend, because there is no one model can do everything, especially dealing with business process modeling notation.
Cameron Skinner (Embarcadero's chief architect): UML The main objective of many One of them is more easily understood and realized that it is to create a more clear and unambiguous language of ambiguity.
Stephen Mellor (Project Vice President, xtUML methodologists) and Bruce Powell Douglas (I-Logix's chief educator): UML 2.0 to consider a lot of real-time system design and code generation problem, the application of UML in the field will be more extensive.
Picked Inventory And Barcoding
vista missing dll errors fix now
