Business Driven Enterprise Engineering |
Visible's Enterprise Modeling & Code Generation Products |
Zachman Enterprise Workbench |
Zachman Edition |
Corporate Edition |
Standard Edition |
| |
| 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 |
|
|
|
|
| BUSINESS PROCESS MODELING (BPMN) SUPPORT |
|
|
|
|
| SYTEM/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 |
|
|
|
|
| Component Diagrams |
|
|
|
|
| Deployment 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 |
|
|
|
|
| VISIBLE UNIVERSAL DATA MODEL (Template)
|
| The Universal model is based on a data model that contains more than 50 business subject areas or primary object classes, encomapassing more than 600 entities with 1,000 attributes. The model is fully normalized with a high level of abstration making the model reusable. |
|
|
|
|
| ISO 9000 BUSINESS TEMPLATES
|
This comprehensive set of business templates enable you to automate your ISO 9000 documentation while integrating with your existing Manufacturing Resource Planning (MRP) and Enterprise Resource Planning (ERP) applications.
|
|
|
|
|
| LICENSING
|
| Floating point licenses |
|
|
|
|
| TRAINING & CONSULTING
|
| Available as needed |
|
|
|
|
| VISIBLE ENTERPRISE DEVELOPER
|
| Code Generation Engine |
|
|
|
|
| 3-tier Business Application Code Patterns
|
| VB6 |
|
|
|
|
| ASP |
|
|
|
|
| VB.NET |
|
|
|
|
| C# |
|
|
|
|
| ASP.NET |
|
|
|
|
| User-defined |
|
|
|
|
| SQL Server or Oracle Stored Procedures |
|
|
|
|
| LICENSING
|
| Floating point licenses |
|
|
|
|
| TRAINING
|
| Webinars, On-site, and Public Courses |
|
|
|
|
| CONSULTING
|
| Available as needed |
|
|
|
|
| |
|
| Enterprise APPLICATION BROWSER/COBOL CODE REENGINEERING AND MODERNIZATION - OPTIONAL |
COBOL Reengineering and Modernization
Application Browser is a unique COBOL reengineering product that produces produce reports and diagrams describing the legacy application, as well as extracting critical information regarding the data and process flows of COBOL legacy systems and then stores this information as a model in the repository of our modeling tools. This gives you the power and flexibility of a robust, multi-user repository when reverse engineering your legacy system. |
|
|
| The supported versions of COBOL include:
|
VAX / VMS
|
|
|
IBM VS COBOL and IBM VS COBOL II
|
|
SPERRY UNIVAC Series 1100
|
|
Ryan McFarland COBOL - 85
|
|
MBP COBOL
|
|
HP COBOL II/V (ANSI 74 and 85)
|
|
Honeywell HVS 6 Plus and GCOS MOD 400 DPS 6 & Level 6 GCOS 6
|
|
Data General COBOL (AOS/VS) (ANSI 74)
|
|
PDP10: TOPS-10 / TOPS-20 (74 and 8x ANSI)
|
|
| |
|
| Enterprise Polaris - OPTIONAL |
| Issue / Problem Tracking |
|
|
| Process and Workflow Management |
|
| Visual Studio.NET Addin |
|
| Links to Your Version Control Provider |
|
| Customizable |
|
| Manage Issue-Related Tasks |
|
| User-Defined Views |
|
| Concurrent Multi-user Access |
|
| Attach Files to Issue |
|
| HTML-based Reporting |
|
| Visual SourceSafe Addin |
|
| LICENSING
|
| Floating point licenses |
|
|
| TRAINING
|
| Webinars, On-site, and Public Courses |
|
|
| CONSULTING
|
| Available as needed |
|
|
| |
|
| Enterprise Lifecycle Support Information System (LCSIS) - OPTIONAL
|
| APPLICATION LIFECYCLE MANAGEMENT |
| Product Identification |
|
|
| Change Control |
|
| Status Accounting |
|
| Workflow |
|
| Electronic Document Management |
|
| Multiple Data Vaults |
|
| Field Modifications |
|
| APPLICATION IDENTIFICATION |
| Application Structure |
|
|
As-Planned
|
|
As-Built
|
|
| Baselines |
|
As-Planned
|
|
As-Built
|
|
As-Modified
|
|
| Application Component Structures |
|
Family Trees
|
|
Component Hierarchies
|
|
Where Used Data
|
|
| Application Catalog |
|
Comprehensive Tables
|
|
Customized Listings
|
|
| Configuration Item Data |
|
Standard Details
|
|
Customized Attributes
|
|
| Application/Component/Document Cross Reference |
|
Alternative Components
|
|
Reusable Components
|
|
Superseding/Superseded Components
|
|
| Component Serialization |
|
Application Level
|
|
Component Hierarchies
|
|
Component Level
|
|
| Vendor/Customer Information |
|
Status Accounting of All Applications by Components
|
|
Status Accounting of All Customer Requirements
|
|
| Data Vault Access |
|
Viewing
|
|
Redlining
|
|
Security Controls
|
|
| CHANGE CONTROL |
| Automated Processing |
|
|
Problem Reports
|
|
Change Requests/Proposals
|
|
Variences (Deviations and Waivers)
|
|
| Electronic Workpackage Folders |
|
Data Vault Access
|
|
Local/Network Access
|
|
| Change Impact Assessment |
|
Baseline Effectivity
|
|
Part/Documents Affected
|
|
Serial/Date Break-in Effectivity
|
|
| STATUS ACCOUNTING |
| On-Demand Reports |
|
|
Application Structure
|
|
Baselines
|
|
Component Structures
|
|
Change Status
|
|
Component Status
|
|
Where-Used
|
|
Document Location and Status
|
|
Serialized Component Tracking
|
|
Change Request History
|
|
Revision History
|
|
Customer Data
|
|
Metrics
|
|
| ELECTRONIC DOCUMENT MANAGEMEN
|
| Access-Controlled Electronic Data Vaults |
|
|
Application
|
|
General
|
|
User
|
|
Multi-Criteria Search Capability
|
|
Check-in/Check-out of Files
|
|
Version Control
|
|
Local Copy of Files
|
|
View and Redline
|
|
| Prelininary and Formal Document Processing |
|
Revision Histories
|
|
Current Status of Changes
|
|
Version Control
|
|
Automated Report Generation
|
|
| Query and Search Capabilities |
|
Application/Component Catalog
|
|
Data Vaults
|
|
Change Documentation
|
|
Serialization Location and Status
|
|
Workflow
|
|
| System Administration |
|
Group Management
|
|
Access Controls
|
|
User Profiles
|
|
Utilities
|
|
| WORKFLOW
|
| Electronic Workbasket Routing |
|
|
| Workflow Management |
|
Workflow Critical Path Creation
|
|
Task Definition and Modification
|
|
| Project Management |
|
Project Creation and Launch
|
|
Workflow Assignment and Tracking
|
|
Electronic Workpackage
|
|
Statusing and Metrics
|
|
| Implementation Planning and Direction |
|
| Work-in-Process Status Tracking and Metrics |
|
| LICENSING
|
| Floating point licenses |
|
|
| TRAINING
|
| Webinars, On-site, and Public Courses |
|
|
| CONSULTING
|
| Available as needed |
|
|
|
|
| Enterprise Configuration Management - Razor & IssueWeaver - OPTIONAL |
| PROBLEM TRACKING |
| Issues/IssueWeaver is the problem/error tracking tool within Razor. |
|
|
| Can Issues/IssueWeaver to be tailored to the individual customer? |
|
| Can you create user defined form fields? |
|
| Can you enable and disable user-defined fields at specific times? |
| Can you group people into established roles? |
|
| Can you control access to operations for individuals or roles? |
| Does Razor allows for customized scripts to be attached to specific actions such as sending email notifications, logging information, verifying output, etc? |
|
| Does Razor allow for attaching commands to client toolbars and buttons? |
|
| Does Razor allow for extended state control? |
|
| Can Issues be associated to files in Versions upon file introduction, check in, and check out? |
| Can the Issues form be defined and designed to include an unlimited number of custom fields? |
|
| Can the Issues Text Panes support an unlimited number of characters? |
|
| Can files be attached directly to individual Issues? |
|
| Can change requests be imported from other bug tracking software? |
| VERSION CONTROL |
| Versions is the file control/source code control tool within Razor. |
|
|
| Does Versions allow you to introduce and house any file type? |
|
| Does Versions provide you with the ability to establish a software change workflow and approval process based on your needs? |
|
| Does the Versions GUI provides identification of who currently has a file checked-out? |
|
| Can files can be diffed in Versions? |
|
| Can files can be promoted? |
| Can ASCII type files can be viewed directly in the Versions tool? |
| Can files can be reverted to a prior version? |
|
| Are there any limitations on the number of files that can be introduced and housed within Razor? As long as there are enough server resources available to handle the load? |
|
| Can Issues can be associated for example, when files are introduced, checked out, or checked in? |
|
| Does Razor provide remote access, file branching, file merging, and support for multiple baselines? |
|
| Does Razor use the ‘sandbox' approach to file control? *Razor uses the individual checkout/checkin method to do file control. The sandbox approach may be somewhat achieved by use of custom scripts. |
 * |
| Does Razor rely upon exclusive file locking, merging, and branching techniques. |
|
| BASELINE MANAGEMENT |
| Threads is the baseline management tool within Razor. |
|
|
| Can Threads be given user defined titles? |
|
| Can Threads can be built based upon associated Issues? |
|
| Are individual versions of each Thread maintained? |
|
| Is there a capability to identify all baseline (thread) entities? |
|
| Can Projects (a collection of threads or a thread of threads) easily be created? |
|
| Can Threads can be extracted to an external directory? |
|
| Can Projects (a collection of threads or a thread of threads) be extracted to an external directory? |
|
| Can Threads can be reverted to a previous version at any time? |
|
| Can prior versions of Threads be extracted? |
|
| GENERAL RAZOR INFORMATION |
| Data entry screens are customizable. |
|
|
| Help functions are customizable. |
|
| Unlimited number of databases running on multiple platforms. |
|
| Razor contains an integrated Report Generator. |
|
| Supports user groups and roles. |
|
| Razor is a multi-platform tool. |
|
| Supports heterogeneous environments. |
|
| Does not require the purchase of additional software. |
|
| Can be used out of the box, immediately following installation. |
|
| Razor is easy to administer. |
|
| Razor supports the Microsoft Source Code Control API. |
|
| GUI's are very intuitive, user friendly and easy to use. |
|
| Ability to tailor view and filter upon specific criteria. |
|
| Web access to problem tracking tool via IssueWeaver. |
|
| Ability to limit tool access based upon user, group or role. |
|
| Users can be notified of changes via e-mail. |
|
| Support for expansion of RCS and SCCS keywords. |
|
| History/audit trail for all items in database maintained. |
|
| Public training is available. |
|
| On-site, custom training is available. |
|
| Custom consulting and support is available. |
|
| Tool provides all necessary database architecture. |
|
| Ability to support all CM theories/process/life cycles. |
|
| LICENSING |
| Floating point licenses |
|
|
| TRAINING |
| Webinars, On-site, and Public Courses |
|
|
| CONSULTING |
| Available as needed |
|
|
|
|
|
|
|
|
