|
|
||
|
|
||
Visible Analyst
|
This table shows the capabilities for the various editions of Visible Analyst
|
Product
|
|||
| ZACHMAN ENTERPRISE ARCHITECTURE | |||
|
Zachman Archtectural Framework
|
|
|
|
|
Support for All 30 Zachman Cells
|
|
|
|
|
Zachman Implementation Technology
|
|
|
|
|
Zachman/Modeling Integration
|
|
|
|
| DFD BUSINESS PROCESS MODELING | |||
| Data Flow Diagrams |
|
|
|
| Parent Flow Auto-Add To Child |
|
|
|
| Model Balancing Check |
|
|
|
| Data Store = Entity Possible |
|
|
|
| Data Store = Entity Mandatory |
|
|
|
| Four rule sets: Yourdon/Demarco, Gane/Sarson, SSADM, Metrica |
|
|
|
| Ability to split data flows into component flows |
|
|
|
| Composite data stores/files |
|
|
|
| Process Decomposition diagram auto-generated |
|
|
|
| FUNCTIONAL DECOMPOSITION | |||
| Function To Decompose Into Processes |
|
|
|
| Derive Decomp From DFD Hierarchy |
|
|
|
| Off page connectors for complex models |
|
|
|
| Auto-connect diagram symbols |
|
|
|
| FDD / DFD balancing |
|
|
|
| SYSTEM/APP DESIGN MODELING | |||
| Structure Chart (SC) Modeling |
|
|
|
| 3GL Code Generation From SC |
|
|
|
| COBOL Reverse Engineering Into SC |
|
|
|
| Fan-in, Design Complexity, Completeness Analysis |
|
|
|
| PROCESS INTEGRATION WITH DATA | |||
|
ERD / DFD Balancing Rules
|
|
|
|
|
Process view of data model, auto-generated
|
|
|
|
| LOGICAL DATA MODELING | |||
|
Log/Phys Different Model Structure
|
|
|
|
|
Trace Log/Phys Difference
|
|
|
|
|
Supports Complex Key Identity
|
|
|
|
| VERY LARGE MODEL SUBSETTING |
|
|
|
| DRAG and DROP SYMBOLS FROM OBJECT BROWSER |
|
|
|
| CONTEXT SENSITIVE HELP |
|
|
|
| STRATEGIC PLANNING | |||
| Planning Statement hierarchy |
|
|
|
| Customizable statement types |
|
|
|
| Statement to object link validation |
|
|
|
| RELATIONAL EXTENSIBLE CENTRAL REPOSITORY | |||
| Relational database engine included with purchase |
|
|
|
| Any ODBC complaint database used as repository |
|
|
|
| Dynamic text or item search |
|
|
|
| Object reuse across models |
|
|
|
| Create new entries choosing items from pick list |
|
|
|
| XML SUPPORT |
|
|
|
| LOGICAL-PHYSICAL TRANSLATION | |||
| 1:1 Entity = Table |
|
|
|
| Rename Attribute/Field |
|
|
|
| Combine Subtypes to Sub. (automatic/dynamic) |
|
|
|
| Dup Supertype to Subtype (automatic/dynamic) |
|
|
|
| Database View Design |
|
|
|
| Intelliview Error Prevention |
|
|
|
| DBMS Independent View Spec |
|
|
|
| Compare model v schema or schema v model |
|
|
|
| CONCEPTUAL VIEW OF LOGICAL | |||
| Summarize Logical to Conceptual |
|
|
|
| PHYSICAL DATABASE DESIGN | |||
| Logical Data Type |
|
|
|
| Trigger Support |
|
|
|
| Trigger RI Generation |
|
|
|
| Stored Procedure Support |
|
|
|
| Tablespace Storage Support |
|
|
|
| Database View Support |
|
|
|
| Alter DB to Match Model (Comp & Alter) |
|
|
|
| Alter Model to Match Database |
|
|
|
| REVERSE ENGINEERING OF DB | |||
| SQL |
|
|
|
| Direct/ODBC |
|
|
|
| LEGACY DESIGN RECOVERY | |||
| SQL Script |
|
|
|
| Direct/ODBC Connection |
|
|
|
| COBOL Data Division Import |
|
|
|
| Import / Export ERwin .ER1 files |
|
|
|
| OBJECT MODELING | |||
| Classes |
|
|
|
| Methods/Operations |
|
|
|
| Association Aggregation ... |
|
|
|
| State Diagrams |
|
|
|
| Activity Diagrams |
|
|
|
| Collaboration Diagrams |
|
|
|
| Sequence Diagrams |
|
|
|
| Use Case Diagrams |
|
|
|
| Model linking for class, use case objects |
|
|
|
| MODEL MANAGEMENT | |||
| Real-time, concurrent Multi-user |
|
|
|
| Custom Field Extensibility |
|
|
|
| Custom Object Extensibility |
|
|
|
| ENTERPRISE COPY-Simple Versioning | |||
| Divisions Model Subsetting Capability |
|
|
|
| Check-out/in w/lock |
|
|
|
| Proposed Change Authority |
|
|
|
| Post Change Conflict Coordination |
|
|
|
| Object Change Auth Control |
|
|
|
| Object Ownership Controls |
|
|
|