After you select your identity integration solution candidate, the next step toward integrating
your organization\u2019s identity data is creating a system dataflow design. During the development of
the solution proposal, you identified the real-world objects that need to be managed by the
metadirectory. The dataflow model identifies the data sources that store the data related to those
real-world objects. It also identifies the objects used by those data stores to maintain the object
data and describes how the data from those objects flows into and out of the metadirectory in
order to meet the needs of your business objectives.

The system dataflow designer uses the information contained in the solution proposal, which
records your system and data assessments and outlines your plans for deploying Microsoft\u00ae
Identity Integration Server (MIIS) 2003, to define your dataflow and produce a system dataflow
design document.

Overview of Designing Your Dataflow Model............................................3 Dataflow Design Concepts............................................. ..........................6 Process Steps for Designing the System Dataflow.................................17 Summary................................................................. ..............................31

Designing a System
Dataflow Model for
MIIS 2003

Overview of Designing Your Dataflow Model............................................3
Dataflow Design Concepts............................................. ..........................6
Filtering Metadirectory Dataflow.......................................................9
Design Constraints............................................................. .............11

Process Steps for Designing the System Dataflow.................................17
Step 1: Identify Real-World Identity Types.......................................18
Step 2: Identify Your Data Sources............................... ...................20
Step 3: Identify System Objects.................................. ....................22
Step 4: Identify System Attributes................................................... 24
Step 5: Diagram the Design.......................................... ..................27
Step 6: Establish Metaverse Object Types.......................................29
Step 7: Obtain Approval for Your Dataflow Model............................30

After the project team produces the solution proposal, the designer of the dataflow model
develops the logical dataflow model. This model is a complete design of all the object types and
attributes flowing in and out of MIIS 2003 that are required to meet your business objectives.
The dataflow model also includes a brief description of how the objects and attributes relate to
each other.

The goal of the dataflow model is to define the data that is imported into the metadirectory and
the data that is exported from the metadirectory for use by various connected data sources as
required by your business rules. The dataflow model identifies the following:

Various characteristics of the data flowing into and out of the metadirectory, characteristics that might influence your design decisions, such as which attributes are required for certain object types and whether a value stored by an attribute must be unique within its namespace.

Part of the design process is identifying these characteristics and recording them for later
use. You then use this recorded data when you create the integration policies and rules
during later steps in the planning and design process.

The dataflow model should describe the ideal design that meets the needs of the established
business rules. The dataflow designer need not consider the optimal design. The dataflow model
describes in general terms any changes that the metadirectory might be required to make to data
in order to make it useful for other data sources. Keep the following non-goals in mind while
creating your dataflow design:

During the creation of the solution proposal you identified the
real-world objects that you want to manage through the
metadirectory. The objects and attributes you identify in the
dataflow model are the actual objects that are used by the
various data sources to store the real-world objects.