Integrating : Focal Point and the Rational solution for Collaborative Lifecycle Management : Business case scenarios
  
Business case scenarios
This is a typical business case scenario in, where the capabilities of Focal Point is integrated with Rational Requirements Composer and Rational Team Concert so that process of decision making, planning, implementing, tracking, and delivering solutions work together.
Scenario workflow
Business case scenario workflow of using Rational Focal Point, Rational Requirement Composer and Rational Team Concert.
Focal Point and Rational Requirements Composer integration scenario
Focal Point and Rational Requirements Composer integration to elaborate requirements and track the progress: These are the high-level steps that can be performed in this scenario.
1 Prioritize the business needs : High-level business needs are proposed in Focal Point by the product manager.
2 Define the initial project scope: The prioritized business needs are then scoped into the project for elaboration.
3 Publish business needs as requirements to Rational Requirements Composer: To get a better idea of what it means to implement the business needs, the product manager or any project stakeholder publishes the prioritized business needs from Focal Point to Rational Requirements Composer for requirement elaboration.
4 Elaborate the requirements and align them to the business strategy: The business analyst or the product manager elaborates the next level of requirements in Rational Requirements Composer. During elaboration, the business analyst aligns the project requirements to the business strategy by regularly reviewing the Focal Point business needs priorities and progress change.
5 Fetch the status and view the progress of the requirements: To manage and track the requirement elaboration, the management checks the progress at regular intervals in Focal Point and finalizes the project scope.
6 Expand the project scope: New business needs might get added subsequently and scoped into the project in Focal Point. These business needs must be published to Rational Requirements Composer for elaboration. Similarly, new requirements might be defined Rational Requirements Composer that must be communicated with the management by publishing these new artifacts as business needs to the Focal Point project.
See also Elaborating requirements and tracking the status
Focal Point and Rational Team Concert integration scenario
Focal Point and Rational Team Concert integration to establish the project scope, implement the project and track the progress: These are the high-level steps that can be performed in this scenario.
1 Establish the project scope in Focal Point: A project is approved with planned business needs in Focal Point. The management communicates the scoped elements to the implementation team and ensures adequate understanding and traceability. This is done by publishing business needs to Rational Team Concert as work items.
2 Detailed planning and implementation in CLM: During implementation, more planning and elaboration is done in Rational Team Concert.
3 Update implementation status in Focal Point: The project implementation status is regularly fed into Focal Point for the stakeholders to see the current status and progress of the overall project and the individual business needs.
4 Expand the project scope: New business needs might get added subsequently and scoped into the project. These business needs must be published to Rational Team Concert for implementation. Similarly, new high-level work items might be defined in Rational Team Concert that must be communicated with the management and defined within the project scope as business needs.
Go up to
Focal Point and the Rational solution for Collaborative Lifecycle Management