In the past decade, the use of Unified Modeling Language (UML) modeling for software applications has become increasingly clear advantage. At the same time, RUP is already a proven software development process, Zachman framework is a framework of proven organizational and communication framework for the workpiece.
UML, RUP and Zachman framework functions overlap
Among the many overlapping methods, UML, RUP and Zachman are a modern information system architecture of the three important pillars. By examining the characteristics of their element and some combination of their methods and organization to consider the combination of these methods.
By definition, UML is a modeling language. It attempts to model software-intensive systems standardized graphical language elements. It's the latest version of UML2.0 by the use of structural modeling, behavioral modeling and interaction modeling of the 13 chart type composition. Meaningless, although mainly for object-oriented (OO) analysis and design, but the UML can be used in many other conditions. For example, UML use case method itself is not an OO process, but it is already confirmed to be a general functional requirements of the best technology. Other UML diagram, such as interaction, status and activities of the diagram is also described in the real world we often users the status of projects available tools.
Origin of Zachman
Framework is a framework used to develop and maintain a wide range of tools for architecture. When it comes to support enterprises in custom enterprise architecture (EA) function, Zachman framework can provide a lot of help. It grades into a corporate theme 6x6 matrix of cells, each cell representing each organization a unique view.
Zachman in the columns represent the most important aspects of business (data, function, network, people, time, motivation), but be different according to different perspectives (size, business, systems, technology, details of assets) and associated with one aspect of the stakeholders (planners, business owners, designers, implementers, who carry children) to divide. In addition, the Bank also for details of the level is different, because they are an abstract expression of enterprises (in the environment, conceptual, logical, physical, detailed and practical), which in turn may be connected to stakeholders and the angle to form the business model and the responsibilities of the cell. Example is: "A system model (angle) is a designer (group) as part of terms of reference of the logical (abstract) entity."
36 framework of the cell can select the element characterization based business models and artifacts to divide, for example, the details of the level or type of interest. Framework does not provide for filling the cells of the symbol or sequence, as this knowledge is beyond the point of reference to structural target range. (Assumed to be created behind the use of UML and RUP framework to support the case.)
Process can be defined as "a series of actions to produce results, changes or functions." RUP is a process framework that allows project work processes and tasks are organized as the ultimate goal of delivering software products and solutions to a series of moves. RUP should be cut to create a specific organization or project to meet the needs of the process instances and methods.
RUP thinking from the realization of a unified system, the system through the use of UML notation to describe the delivery of the workpiece. Important that the new iterative process has to architecture-centric and demand-driven features, and these features are not available in existing systems.
Since there has been, RUP has been derived from Objectory methods from software engineering process based on UML2.0 by the development of a Rational Method Composer (RMC) to support the process for cutting a flexible, fully customizable platform. 7 For example, the use of RMC, a skilled process engineers can create an instance of a systems engineering process, customize the structure, from other industry standard methods and best practices need to add the hyperlink text content and to create an alternate form, organization or project to adapt the process instance.
Integrated drive
According to the discussion earlier, in each of these three systems have been created to serve a specific needs, while they also have Quefa on them outside of a broader focus Ling Yu adaptive disadvantage. In many organizations, the Zachman framework on which I noticed is that the surface it is a great good that everyone said the posters, but no one use it. I attribute this to this little fact: As with any other static framework, Zachman did not specify how to handle the introduction of the workpiece. Another practical weaknesses, is generally considered the advantages of a framework for the lack of standard symbols.
UML dependency relations in the role of the problem a little less, because RUP different, it does not make the role, so there is no way mapping needs. Nevertheless, the process and framework also limits the independence of the effectiveness of UML. Fortunately on the UML, although many organizations use other like entity-relationship diagram (ERD) and business process modeling notation (BPMN) method and the structure of such symbols, but the UML is still met with general approval.
In the attempt to express these limitations as well as three methods to find the common application process, once again noted that they were created to represent different areas of the same issues (information system architecture), and the goal set before them virtually no functional overlap. Enterprise and project architect for this is good news because it means that UML, Zachman and RUP can be used together to produce a more comprehensive business value.
UML and the RUP to integrate Zachman
In most organizations, when the system may in some form very long time, such as UML has been around at least ten years of time, lack of standards for the symbol is understandable. Even in relatively modern system environment, UML design documents also may be due to time constraints and lack the necessary skills set and other reasons, have not been used.
RUP-driven system through the delivery of the project will be applied to UML organization, its use can be extended to companies based on Zachman framework, there is no need to reduce its risk.
As I stated above, Zachman, and RUP are dependent on UML. RUP UML-driven exclusively by, and unknown symbol symbol Zachman dependent on its implementation. UML can be proved to be the best use of symbols Zachman, because it does not rely on other methods, it can be used as the starting point of RUP and Zachman. Moreover, even if later you decide not to use RUP or Zachman, UML is still a very useful and easy-to-understand visual language can be used for comprehensive analysis of the solution analysis and design and to improve team communication.
RUP and Zachman learning together
In the RUP can be practiced in many Zachman could parallel to, and indeed such a method to help increase the value Zachman. For example, the use of RUP business process modeling, use case and sequence diagrams to represent the Zachman "function" Similarly, the use of use cases and UI design to deal with "human-computer interaction", using class and object diagram to deal with "data." Zachman structure of some of the lines and RUP's demand-driven, incremental, and to the principles of the framework is connected to the center, while the column is equivalent to a number of UML models and best practices of goal setting. For example, the "how" of this column with emphasis on process, and can be compared with the UML activity diagram.
Can be shown to understand the Zachman RUP and UML more than about simply because Zachman dealing with a static view of enterprise system architecture, rather than dynamic models and processes. Nevertheless, the study Zachman approach may benefit from some of the main principles of RUP key - for example, "demand driven", "architecture-centric," "model-driven" and "iteration" - the application. My view is that when these principles to the learning process and its practical application, Zachman framework easier to master.
There is a business and project architect must collaborate limitations, Zachman here to play a role - the work of the project framework specific framework. While each organization will connect to corporate and project-level jobs to develop its own unique way, but a common goal is to Zachman cells and RUP workflows and activities connected. Unfortunately, these examples represent only a part of description, because they only describe the parts to the form of static maps, often do not provide a dynamic phase / iteration / activity events guidance.
Of course, some architects who, according to the method described by the author using the Zachman may sound too confusing, and experienced professionals may feel that their own intellectual framework for it that is superfluous. I still believe that most practitioners will find Zachman in their work is to facilitate the analysis of reference resources. When the build environment for the project, planning is an important task of its own, it is usually not difficult, but very worthwhile projects and organizations that.
As a leader in their respective fields, UML, RUP and Zachman Framework can be shared in any organization to produce a more comprehensive framework for value. RUP and Zachman are model-driven and need to achieve some kind of symbolic function. Since UML RUP provides its symbol, then the framework for business is to make UML as standardized symbols may be more meaningful, because usually, it has no weaknesses.
Although the RUP and Zachman are model dependent, but in fact they are not functional overlap. This is mainly because RUP is a process, a framework for Zachman, but also reflects the RUP framework for the goals of project, and Zachman's focus is on business organization.
Since RUP and Zachman can rely on UML, which is the first introduction of the three methods the preferred method. Zachman or RUP applied to the contrary, contribute to a more comprehensive learning experience.
Project results also benefited from the application of the Zachman, because it can quickly make you get the requirements gathering or analysis / design artifacts can be used. Even when not connected to the workpiece Zachman, Zachman structure itself is still very helpful, and because the project reflects the operational issues on which provides a variety of Guandian helpful.
An organization will almost certainly support the enterprise architecture and artifacts between their projects to benefit traceability, traceability can be established that a piece from the creation to the end of the life cycle to gain control. In this way, RUP and Zachman management can be applied to the workpiece.
When you want to create flexible and maintainable solution when the project and business teams should collaborate. Project members should understand the broader business environment, and their corresponding companies must constantly monitor the project to keep knowledge up to date. RUP and Zachman in the integration of application use cases can help narrow the gap between the enterprise and its projects, thus making organizations more effective. Finally, it is everything.
UML RUP and Zachman Framework link
Recommended links:
How to find the owner of a phone numberExpert Q & A: formation of six key issues WLANClear links in the production of hidden "oil tiger"brief BROWSERSSpecialist Pager ToolsMP4 To WMPESSO Card From The City To Look Into The Need For IntegrationZack Rusin interviewed the beauty and magic of KDEQingdao Shengli Oilfield Nursing Home Use MaximaDVR-MS to MPGMake a IPhunter3G2 To MOVFounder joint hits: not only GANQINGZUOYONG