Installation guide

Creating a Project Plan 17
 Create an agreed execution path for the Identity Manager solution.
 Define additional education for stakeholders.
Discovery provides a common understanding of the issues and solutions for all stakeholders. It
provides an excellent primer for the analysis phase, which is a phase that requires stakeholders to
have a basic knowledge of directories, Novell eDirectory, Novell Identity Manager, and XML
integration in general.
After you have completed the discovery phase, proceed to Section 2.2, “Requirements and Design
Analysis Phase,” on page 17.
2.2 Requirements and Design Analysis Phase
Take the high-level road map that was created in the discovery phase as a starting point for this
analysis phase. The document and the Designer project both need technical and business details
added. This produces the data model and high-level Identity Manager architecture design used to
implement the Identity Manager solution.
The focus of the design should be specifically on identity management; however, many of the
elements traditionally associated with a resource management directory, such as file and print, can
also be addressed. Identity Manager synchronizes user accounts to directories that do not have direct
access to the operating system’s file system. For example, you can have a user account in Active
Directory, but that does not grant you access to the file system on the Active Directory server.
Using the information gathered in the discovery phase, answer the following sample questions to see
what other information needs to be gathered. This might require additional interviews with
stakeholders.
 What versions of system software are being used?
 Is the eDirectory design appropriate? For example, does the Identity Manager server contain a
Master or Read/Write replica of the user objects that are synchronizing? If it does not, the
eDirectory design is not appropriate.
 Is the quality of the data in all systems appropriate? (If the data is not of usable quality, the
business policy might not be implemented as desired.) For example, there might be duplicate
accounts for the users in the systems that are synchronizing, or the format of the data might not
be consistent throughout each system. Each system’s data must be evaluated before information
is synchronized.
 Is data manipulation required for your environment? For example, a user’s hire date format in
the human resource system can only be 2008/02/23 and the hire date in the Identity Vault is 02-
23-2008. This requires that the date be manipulated for synchronization to occur.
Identity Manager contains a tool to help you simplify the process of analyzing and cleaning your
data. For more information, see Analyzer 4.0.1 for Identity Manager Administration Guide.
Review the information in Chapter 3, “Technical Guidelines,” on page 23 to help make the correct
decisions for your environment.
After the requirements analysis, you can establish the scope and project plan for the implementation,
and determine if any prerequisite activities need to occur. To avoid costly mistakes, be as complete as
possible in gathering information and documenting requirements. Here is a list of possible
requirements:
 Data model showing all systems, authoritative data sources, events, information flow, data
format standards, and mapping relationships between connected systems and attributes within
Identity Manager.