Implementation Guide › Planning and Design › Requirement Gathering Session (All Roles)

Requirement Gathering Session (All Roles)

The requirement gathering session is the first critical step in the implementation of CA Business Service Insight, and should include all key personnel involved in the implementation.

The information required for this session must be provided by people who are very familiar with the selected SLAs, including the SLA business logic, how the SLAs are currently being managed, what reports are currently being generated for them, and what full reporting requirements are expected in the future.

The following personnel must participate:

• Service Catalog Manager(s)
• Contract Manager(s)
• Data Source Expert(s)
• Business Logic/Scripting Expert(s)
• Any other relevant staff members familiar with the selected SLAs
• Project manager (if appointed)

CA recommends the following:

• It is important to ensure there are personnel present who can make decisions regarding any unclear definitions that might arise while reviewing selected SLAs.
• It is advisable that the implementation team receive, prior to this meeting, a copy of the SLAs selected for this project. The attendees should be familiar with all relevant data sources that pertain to the selected SLAs, be able to provide data dumps of them, and explain their inner structures, where applicable.

The main goals of the planning session are to define and specify:

• Scope of planned work
• Success criteria
• Roles and responsibilities of all involved parties
• Implementation process and schedule
• Required hardware/software requirements

This is accomplished by:

• Reviewing SLAs to be used in implementation
• Reviewing "Business Logic" for each objective within selected SLAs
• Reviewing reports, alerts, and Dashboard requirements related to selected SLAs
• Reviewing relevant data sources to be used in implementation
• Reviewing relevant Infrastructure topology
• Collecting relevant data dumps from relevant data sources
• Identifying key people and their responsibilities
• Defining communication paths for duration of implementation, review meetings, Q&A process, and so on
• Reviewing implementation's process and schedule
• Reviewing current state of affairs, that is, how are these SLAs managed, and what is missing
• Defining implementation's success criteria
• Defining required hardware/software requirements
• Defining time line for implementation