AllFusion ERwin Data Modeler Documentation Survey

The AllFusion ERwin Data Modeler Documentation Survey provides a valuable tool to help us create and improve our documentation to better satisfy your needs. The intent of the survey is to measure the effectiveness of the documentation by analyzing tasks, how and when documentation is used, whether it is written to the appropriate level of understanding, and any additional comments our customers wish to make. The results of this survey will be analyzed by our documentation team, and we will try to incorporate as many suggestions as possible in our future releases.

1) What is your Company Name?

2) Approximately how many employees do data modeling in your Company?

Under 10   10-25   26-75   more than 75

3) What is your role? Check all that apply.

Logical Modeler   Physical Modeler   Architect   DBA   Data Warehouse Designer   Integrator/Third Party Developer

Comments:

4) How many years experience do you have at data modeling?

Under 1 year   1 - 5 years   6 - 10 years   More than 10 years

5) Which CA modeling tools do you currently use? (Please specify the version number in the comments field.)
Check all that apply.

AllFusion ERwin Data Modeler   AllFusion Model Manager   AllFusion Process Modeler   AllFusion Model Navigator   AllFusion Data Model Validator

Comments:

6) How often do you use the following features or perform the following tasks?

	Never	Rarely	Sometimes	Often
Install and update the software	Install and update the software Never	Install and update the software Rarely	Install and update the software Sometimes	Install and update the software Often
Logical Modeling	Logical Modeling Never	Logical Modeling Rarely	Logical Modeling Sometimes	Logical Modeling Often
Physical Modeling	Physical Modeling Never	Physical Modeling Rarely	Physical Modeling Sometimes	Physical Modeling Often
Generate DDL from physical models	Generate DDL from physical models Never	Generate DDL from physical models Rarely	Generate DDL from physical models Sometimes	Generate DDL from physical models Often
Create and implement modeling standards	Create and implement modeling standards Never	Create and implement modeling standards Rarely	Create and implement modeling standards Sometimes	Create and implement modeling standards Often
Use macros (pre- and post-scripts, triggers and stored procedures)	Use macros (pre- and post-scripts, triggers and stored procedures) Never	Use macros (pre- and post-scripts, triggers and stored procedures) Rarely	Use macros (pre- and post-scripts, triggers and stored procedures) Sometimes	Use macros (pre- and post-scripts, triggers and stored procedures) Often
Forward Engineering	Forward Engineering Never	Forward Engineering Rarely	Forward Engineering Sometimes	Forward Engineering Often
Reverse Engineering	Reverse Engineering Never	Reverse Engineering Rarely	Reverse Engineering Sometimes	Reverse Engineering Often
Transforms	Transforms Never	Transforms Rarely	Transforms Sometimes	Transforms Often
Design Layers	Design Layers Never	Design Layers Rarely	Design Layers Sometimes	Design Layers Often
Derive a model	Derive a model Never	Derive a model Rarely	Derive a model Sometimes	Derive a model Often
Reporting	Reporting Never	Reporting Rarely	Reporting Sometimes	Reporting Often
Dimensional Modeling	Dimensional Modeling Never	Dimensional Modeling Rarely	Dimensional Modeling Sometimes	Dimensional Modeling Often
Data Warehousing	Data Warehousing Never	Data Warehousing Rarely	Data Warehousing Sometimes	Data Warehousing Often
Workgroup Modeling	Workgroup Modeling Never	Workgroup Modeling Rarely	Workgroup Modeling Sometimes	Workgroup Modeling Often
Change Management/Complete Compare	Change Management/Complete Compare Never	Change Management/Complete Compare Rarely	Change Management/Complete Compare Sometimes	Change Management/Complete Compare Often

Comments:

7) In general, how often do you refer to the following documentation?

	Never	Rarely	Sometimes	Often
API Reference guide	API Reference guide Never	API Reference guide Rarely	API Reference guide Sometimes	API Reference guide Often
Implementation guide	Implementation guide Never	Implementation guide Rarely	Implementation guide Sometimes	Implementation guide Often
Methods guide	Methods guide Never	Methods guide Rarely	Methods guide Sometimes	Methods guide Often
Online Help	Online Help Never	Online Help Rarely	Online Help Sometimes	Online Help Often
Readme	Readme Never	Readme Rarely	Readme Sometimes	Readme Often
Release Summary	Release Summary Never	Release Summary Rarely	Release Summary Sometimes	Release Summary Often

Comments:

8) Why do you consult the product documentation?
Check all that apply.

To find out information about new or existing features   To find out how to do something   To troubleshoot a problem   To train other users   I don't refer to the documentation at all   Other (please specify)

If you selected other, please specify:

9) Rank the method you generally use to search for information (#1 being the most frequent and #4 being the least frequent): 

• Table of Contents or PDF Bookmarks
• Index
• Keyword Search
• Browse document

1)	Table of Contents or PDF BookmarksIndexKeyword SearchBrowse document
2)	Table of Contents or PDF BookmarksIndexKeyword SearchBrowse document
3)	Table of Contents or PDF BookmarksIndexKeyword SearchBrowse document
4)	Table of Contents or PDF BookmarksIndexKeyword SearchBrowse document

10) What types of information are most important to you?

	Not Important	Somewhat Important	Important	Very Important
Concepts (theory)	Concepts (theory) Not Important	Concepts (theory) Somewhat Important	Concepts (theory) Important	Concepts (theory) Very Important
Procedures ("how-to" information)	Procedures ("how-to" information) Not Important	Procedures ("how-to" information) Somewhat Important	Procedures ("how-to" information) Important	Procedures ("how-to" information) Very Important
Screenshots/Graphics	Screenshots/Graphics Not Important	Screenshots/Graphics Somewhat Important	Screenshots/Graphics Important	Screenshots/Graphics Very Important
Architectural diagrams	Architectural diagrams Not Important	Architectural diagrams Somewhat Important	Architectural diagrams Important	Architectural diagrams Very Important
Command Line	Command Line Not Important	Command Line Somewhat Important	Command Line Important	Command Line Very Important
Task examples	Task examples Not Important	Task examples Somewhat Important	Task examples Important	Task examples Very Important
Installation/Configuration	Installation/Configuration Not Important	Installation/Configuration Somewhat Important	Installation/Configuration Important	Installation/Configuration Very Important
Troubleshooting/Problem Solving	Troubleshooting/Problem Solving Not Important	Troubleshooting/Problem Solving Somewhat Important	Troubleshooting/Problem Solving Important	Troubleshooting/Problem Solving Very Important
Best Practices	Best Practices Not Important	Best Practices Somewhat Important	Best Practices Important	Best Practices Very Important

11) Does the Modeling Suite documentation contain enough technical detail?

Adequate   Too technical   Not technical enough   Don't know

Comments:

12) Enter any additional comments or suggestions for improvement related to the Modeling Suite documentation: