Novell IDENTITY MANAGER 3.6.1, Installation Manual

Page: 21 / 104

Creating a Project Plan 21
no
vd
ocx
(e
n)
17
Sep
te
m
be
r 20
09
It might be advantageous to divide the deployment into phases that enable implementation of a
portion of the deployment earlier and other portions of the deployment later. You can do a
phased deployment approach as well. It should be based on groups of people within the
organization.
Š
Define the prerequisites.
The prerequisites required for implementing a particular phase of the deployment should be
documented. This includes access to the connected systems that you are wanting to interface
with Identity Manager.
Š Identify authoritative data sources.
Learning early on which items of information system administrators and managers feel belong
to them can help in obtaining and keeping buy-in from all parties.
For example, the account administrator might want ownership over granting rights to specific
files and directories for an employee. This can be accommodated by implementing local trustee
assignments in the account system.
After you have defined your business requirements, proceed to Section 2.2.2, “Analyze Your
Business Processes,” on page 21 .
2.2.2 Analyze Your Business Processes
After completing the analysis of your business requirements, there is more information you need to
gather to help focus the Identity Manager solution. You need to interview essential individuals such
as managers, administrators, and employees who actually use the application or system. Issues to be
addressed include:
Š
Where does the data originate?
Š
Where does the data go?
Š
Who is responsible for the data?
Š
Who has ownership for the business function to which the data belongs?
Š
Who needs to be contacted to change the data?
Š
What are all the implications of the data being changed?
Š
What work practices exist for data handling (gathering and/or editing)?
Š
What types of operations take place?
Š
What methods are used to ensure data quality and integrity?
Š
Where do the systems reside (on what servers, in which departments)?
Š
What processes are not suitable for automated handling?
For example, questions that might be posed to an administrator for a PeopleSoft system in Human
Resources could include:
Š What data are stored in the PeopleSoft database?
Š
What appears in the various panels for an employee account?
Š What actions are required to be reflected across the provisioning system (such as add, modify,
or delete)?
Š
Which of these are required? Which are optional?
Š
What actions need to be triggered based on actions taken in PeopleSoft?