- Please give a big thumbs up to whomever had the idea to throw in Cameo Requirements Management into MagicDraw 18. I'm using the plugin a ton now.
- No Magic's team were exceptional at delivering software that was on time and within specification.
- I'm working with MagicDraw for 3 years now and I'm still impressed by the tons of functionalities it has and by the great support team!
- I just wanted to thank you for your great customer service. I have enjoyed working with you (and MagicDraw) so far, and look forward to doing so increasingly in the future.
The Zachman Framework is a formal and highly structured way of viewing and defining an enterprise from different perspectives. It is represented as a classification schema for artifacts that is used for enterprise architecture modeling.
In order to meet this vision, No Magic has developed and introduces for MagicDraw users a new free Zachman Framework plugin which provides:
- Zachman Framework schema with a clickable interface
- Zachman Framework project template
- Zachman Framework perspective
- Sample project
The Zachman Framework represents the interaction between aspects and perspectives. Six rows represent six perspectives and six columns represent six different aspects. In the following figure, you can see the Zachman Framework two-dimensional schema as it is represented in the Zachman Framework plugin for MagicDraw.
Executive Perspective (Business Context Planners)
This perspective is a planning level. Business context planners describes what, how, where, who, when, and how should be done. During this phase, six scope identification lists should be prepared, each for the six different aspects.
Scope contexts describe a scope of models, architectures, and descriptions for the organization. This perspective also describes what planners should consider when thinking about the organization and how it interacts with the world.
Business Management Perspective (Business Context Owners)
In this perspective, the business concept model should be created. Business concepts describe models, architectures, and descriptions that are used by owners of the business process. A focus of this perspective is on the usage of products.
Business Management Perspective (Business Logic Developers)
In this perspective, the system logic model should be created. System logic describes models, architectures, and descriptions that are used by designers, engineers, and architects who are searching for a compromise
between what is desirable and what is technically possible.
Engineer Perspective (Business Phisics Builders)
In this perspective, the technology physics model should be created. Technology physics describes models, architectures, and descriptions that are used to design and create an actual project. The main focus here is on constraints and what will actually be constructed.
Technician Perspective (Business Component Implementators)
In this perspective, the tool concept model should be created. Tool components describe particular elements or element parts that are included in the final product (for example, software components, documentation, and so on).
Enterprise Perspective (Business Component Implementors)
The perspective of the Operations instances have no detailed description as it is the physical representation of the model defined in the previous perspectives. This perspective shows the goal of the model. You do not have to define any model in this perspective. Every step of this perspective represents a particular resource (real person, building, program, and so on).