Business Requirements#
- Current State: Business Process flows
- Future State Business Process flows
- Use Cases
Determine the Existing IdM Infrastructure#
- Identify, validate the client’s current infrastructure in detail
- What the "standard" operating system and version is implemented
- Identify the client’s current business process flows
- Understand how both the current infrastructure and business process will change with an IDM solution
- Identify and understand any policies currently in place that would need to be reflected in the future state (i.e.: user object naming policy, password creation policy)
- Identify and validate the current tree structure, number of user objects, etc.
- Attributes needed, at a minimum, to create and maintain user objects, as well as new attributes that would be required for downstream applications or new attributes that are being requested
Determine Data Sources and Applications#
- Identify the application type(s) and their infrastructure in detail
- Identify the current business process flows
- How are new User's added
- How are users removed from Systems.
- When are they removed from Systems.
- Understand how both the current infrastructure and business process will change with an IdM solution
- Identify and understand any policies currently in place that would need to be reflected in the future state (i.e.: user object naming policy, password creation policy)
- Identify number and types of employees, non-employees, etc.
- Attributes available for consumption
- Attributes needed for consumption
High Availability and Disaster Recovery Requirements#
- What is the expected Availability of the IdM Architecture?
- What is the expected Disaster Recovery Requirements of the IdM Architecture?
Security Requirements#
Usually there are often pre-existing security requirements that the IdM Architecture will is expected to be compliant. Some often identified requirements are:
Auditing#
Often there are auditing requirements within an organization that are required due to policy or compliance organizations.
System Reporting or Monitoring Systems#
Organizations may have centralized Reporting or Monitoring Systems implementations that the IdM Architecture may need to integrate.
- Identity Any Reporting or Monitoring Systems
Hardware Requirements#
As the project moves forward and hardware requirements are determined the hardware procurement time should be considered and evaluated against the projected time-line for the project.
Software Requirements#
As the project moves forward and hardware requirements are determined the software procurement time should be considered and evaluated against the projected time-line for the project.
There might be more information for this subject on one of the following:
