Visible Analyst 2008教程：Zachman框架版企业架构指南

需积分: 10 184 浏览量更新于2024-07-22 收藏 2.36MB PDF 举报

Visible Analyst 2008 Manual 是一本专门针对 Systems Corporation 开发的可视分析工具的用户指南，旨在帮助用户有效地理解和掌握这个企业架构规划、分析、设计与开发的强大工具。该手册涵盖了多个版本，包括： 1. **Visible Analyst – Zachman Framework Edition**: 这个版本是基于Zachman框架构建的，Zachman框架是一种广泛应用于企业架构领域的方法论，它将企业架构分解为不同的维度，如业务、数据、组织和技术等，以支持更全面的决策制定。 2. **Visible Analyst – Corporate Edition**: 专为企业级环境设计，提供高级功能和定制选项，满足大型组织复杂项目的需求。 3. **Visible Analyst – Standard Edition**: 适合一般商业场景，提供基础的功能，适用于日常企业架构管理任务。 4. **Visible Analyst – DB Engineer**: 针对数据库架构师，专注于数据库设计和管理的可视化工具。 5. **Visible Analyst – University Edition** 和 **Zachman University Edition**: 提供教育和研究用途的版本，旨在培养未来的架构专业人才。 6. **Visible Analyst – Student Edition**: 专为学生设计，可能包含简化版功能和学习资源，便于教学和入门学习。此手册强调了模型驱动的系统架构方法，即通过创建和维护可视化的模型来指导整个企业架构生命周期。它包含了创建模型、执行分析、设计和开发过程的详细步骤，并且强调了软件使用需遵循的许可协议，禁止未经授权的复制或传播。值得注意的是，手册中的信息可能会根据Visible Systems Corporation的政策而变动，不构成法律承诺，且软件只能按照许可证或保密协议的规定使用。在使用过程中，用户必须遵守相关规定，确保合法合规。 Visible Analyst 2008 Manual 是一个实用的资源，无论是对企业架构师、项目经理还是开发者来说，都是理解和优化企业架构流程的重要参考，有助于提升项目的有效管理和协作。

Getting to Know Visible Analyst

Entity Relationship Model (also known as a Data Model) - Shows the data entities of the

application and the relationships between the entities. The entities are things and the

relationships are actions. The data attributes can be defined for the entities via the repository

and then shown on the diagram. Entities and relationships can be selected in subsets to

produce views of the data model.

Object Model (also known as an Object Class Model) - Shows classes of objects, subclasses,

aggregations and inheritance. Defines structures and packaging of data for an application.

State Transition Model (also known as the Real Time Model) - Shows how objects

transition to and from various states or conditions and the events or triggers that cause them to

change between the different states.

Process Model (also known as the Data Flow Diagram) - Shows how things occur in the

organization via a sequence of processes, actions, stores, inputs and outputs. Processes are

decomposed into more detail, producing a layered hierarchical structure.

Product Model (also known as a Structure Chart) - Shows a hierarchical, top-down design

map of how the application will be programmed, built, integrated and tested.

Use Case Model – Shows the relationship between a user and a computer system.

Activity Model – Is a special form of state diagram where states represent the performance of

actions or sub-activities. Transitions are triggered by the completion of the actions or sub-

activities.

Sequence Model – Shows how objects collaborate in some behavior.

Collaboration Model – Shows an interaction organized around the objects in the interaction

and their links to each other.

Business Process Modeling Notation- Provides a modeling notation that can be

communicated to and understood by all business users, from the business analysts developing

the models, to the technical analysts implementing the model processes, to the business

people who manage and monitor the processes.

Repository or Library Model (also known as the Project Database) - Keeps the records of

all recorded objects and relationships from the diagrams and allows for the definition of

detailed specifics and extensions of the individual items. Used for evaluation, reporting and

generation of details about the project and its products.

Getting to Know Visible Analyst

Visible Analyst Choices

Today systems designers have multiple choices. They can follow the Structured Analysis and

Structured Design (SA/SD) approach and build on functions/processes, data models and

product concepts; or they can follow the object-oriented approach and build class hierarchies,

dynamic states and functional/process models. Both approaches can build better information

systems and both cover similar aspects of information systems definition. However, both use

different sequences of effort and focus on different aspects of the project. Visible Analyst

allows you to choose either approach or to combine the approaches to develop a

comprehensive product definition, design and development mechanism.

There are five keys to using Visible Analyst, or any MDA tool. The first key is to develop the

discipline to apply and follow the steps and procedures of the technique. The second key is to

develop skills in conceptualizing the MDA models to represent the real world requirements.

The third key is to be consistent in how you define and describe the real world. The fourth key

is to strive to be complete in the definition of all of the major parts of a real world application.

The fifth key is to progress from the conceptual to the operational specifications and

construction of a working information systems process.

VISIBLE ANALYST OVERVIEW

Visible Analyst is a Microsoft Windows application. Versions 7.1 and higher of Visible

Analyst work with Windows NT, 2000, 2003 Server and XP while VA2008 is also VISTA

compatible. This section defines the overall structure of Visible Analyst and identifies some

of its key operational characteristics.

Visible Analyst Architecture

The basic components of Visible Analyst are: a set of diagramming tools, a rules module, and

a repository module. Diagramming tools are used to construct the ―blueprints‖ of your target

system. These lessons guide you in the creation of diagrams and provide you with basic

information on the uses of the diagrams.

A system is designed and constructed according to rules, and the rules module manages the

methodologies of Visible Analyst tools for you. Visible Analyst allows you to choose the rule

set you prefer to use as a guideline for the development of your system. These rules are

important in determining the appearance of your diagrams, as well as the entire structure of

your system. For the purposes of the tutorial, you are introduced to the supported techniques

and learn how to designate the rule set to use and the different symbol types used for each

rules methodology.

Getting to Know Visible Analyst

Note

 Users not familiar with MDI Windows programs should take note: there is a

difference between the diagram Control menu button and the Visible Analyst

Control menu button. The former is in the top left corner of the diagram

window, or to the left of the File menu if the diagram is maximized. This

Control menu contains functions that affect the diagram only, such Maximize,

Close, etc. The latter is in the top left corner of the Visible Analyst window. The

Visible Analyst Control menu affects the whole Visible Analyst window and

program.

Selecting a Diagram Object

A diagram object is anything that appears on a diagram: symbol, line, text, or block. When

you click on an object with a mouse button, it becomes the current or selected object and you

can perform various operations on it. There are five different ways to select an object. The

following paragraphs describe the effect of selecting an object with the left mouse button, the

right mouse button, a double-click with the left mouse button, the TAB key and selecting a

Block.

Left Mouse Button

Clicking on an object with the left mouse button selects it. The object changes color to show

that it has been selected allowing you to make changes to the object or to move the object.

When a symbol or line is selected, text labels for that object are automatically highlighted.

Right Mouse Button

Clicking on an object with the right mouse button also selects it. In addition, the Object menu

appears containing all of the functions that can be performed on that object.

Notes

 Unless stated to the contrary, instructions to click a mouse button refer to the left

button. Instructions for the right button are explicitly mentioned.

 Left-handed mouse users: if you use a mouse with the buttons reversed, you should

reverse references to left and right mouse buttons in this text.

Double-Click

If you double-click on an object with the left mouse button, the repository entry for that object

appears. If the object is unlabeled, a dialog box for labeling the object is displayed. Double-

clicking is also used to indicate the end of a line.

TAB Key

剩余273页未读，继续阅读

sharonma1117

粉丝: 0
资源: 2

Visible Analyst 2008教程：Zachman框架版企业架构指南

Visible Analyst 中文操作手册

visible analyst 教学版

visable analyst

qml visible

cuda visible

bootstrap visible

vue visible

form2 的 Visible 属性可以设置为：varForm2Visible（当 varForm2Visible 为 true 时，form2 可见）怎么设 为什么我visible =fx varForm2Visible,它不能识别varForm2Visible

最新资源

form2 的 Visible 属性可以设置为：varForm2Visible（当 varForm2Visible 为 true 时，form2 可见）怎么设为什么我visible =fx varForm2Visible,它不能识别varForm2Visible