Designer 2.1: The Magic of Information Flow
(co-authored by Peter Koletzke)

Paper
Presentation

Abstract

The way that information flows from one area to another in Designer/2000 is a key factor to successful use of the product. If you understand information flow, you can decide which properties are most important and how complete you need to be when filling out repository definitions. You are also better able to prevent errors due to missing information. Such errors can be costly when they appear later in the life cycle.

Therefore, there is nothing more important when working with Designer/2000 than knowing what will happen to the information in object definitions that you create in the repository. The problem is that this information is less well documented than other aspects of the product and the main way to master it is to use Designer/2000 for a couple of years. Whether you take time up front to learn the flow, or pick it up as you go, there is an inherent learning process that can be costly and, if not done completely, can actually slow down your work on a project. The result is a perception that Designer/2000 cannot easily handle many types of system development environments and methodologies. The reality is that Designer/2000 can do it, but you have to be in tune with the way it handles information.

This paper discusses this all-important topic and shows how particular properties in the Analysis, Design, and Generation areas affect work done via forward or reverse engineering both within and outside of the repository. It also presents our techniques for discovering this information so you can pick up where this paper leaves off to learn more about the way the repository data flows.

Search for on this site