Contents Module overview B-2 Introduction to CLMB-3 Collaboration across the lifecycleB-11 Common planningB-21 Lifecycle traceabilityB-28 Rational reportingB-35 Explore the Money that Matters lifecycle scenarioB-41 Additional CLM learning resourcesB-44
Notes: Instructor notes: Purpose — List the unit objectives Details — Timing: 60 minutes This module is targeted at practitioners using, or preparing to use, a CLM application within the larger CLM context. The goal of this module is to provide students with a high level overview of the Rational® solution for Collaborative Lifecycle Management, and, to familiarize them with the cross-application functionality within the CLM solution. This module can support any course in the CLM2013 curriculum. You can teach this module after you have delivered the main body of course content. Or, you can intersperse and reference topics presented in this module during the delivery of the course. Some content in this module may be repetitive if the same content was covered n the main body of the course. For example, in-context commenting on requirements and requirements reviewed are taught in the Essentials of Rational Requirements Composer course. If the content is repetitive, quickly review the concepts and move forward. Additional information — Transition statement —
The Rational solution for Collaborative Lifecycle Management seamlessly combines aplication lifecycle tools to support software delivery teams. The solution is based on Jazz technology, whih provides an open platform for collaborative software delivery. Built on web technology and Open Services for Lifecycle Collaboration (OSLC) standards, the Jazz platform provides an extensible architecture that is designed to make project delivery more collaborative, productive, and transparent. Instructor notes: You do not have to go into great detail about the architecture of CLM. Be sure that students understand the components of CLM and that they are seamlessly integrated. Explain that Jazz technology provides a open collaborative platform for CLM.
The Rational solution for CLM uses Open Services for Lifecycle Collaboration (OSLC) standards. OSLC is an open community of vendors, integrators, and users that creates freely available, scenario-driven specifications for integrating software applications. All of the specifications are based on the standard and proven architecture of the web. HTTP, REST, and linked integrations do not have to copy and synchronize data, but can link to data where it is. Wherever the data is, you can work with data from your current context because of OSLC-based integrations. Instructor notes: You do not need to have a lengthy discussion about OSLC. Be sure that students understand that the Rational solution for CLM is founded on OSLC standards. Point out the advantages of OSLC as they are outlined on the slide.
IBM® Rational® Requirements Composer, IBM® Rational Team Concert™, and IBM® Rational® Quality Manager are delivered as a set of applications together with Jazz Team Server. The CLM applications generally correspond to the products. Each CLM application consists of one or more capabilities. The distinction between applications and capabilities is related to role-based licensing. An application is the basic unit of installation, deployment, and update. A capability is the smallest unit of function that can be enabled through licensing. Instructor notes: This slide clarifies some of the terminology that is used in the product and the help topics. In the Rational solution for CLM, an application is the basic unit of installation, deployment, and update. Each application can contain several capabilities. Capabilities are the smallest unit of function that can be enabled through licensing.
For full details about client access licensing, see the help topic, “Client access license management overview.” Instructor notes: This slide shows how capabilities are enabled through role-based client licensing. For example, someone with a Quality Professional client access license has read/write permissions in the change management, report customization, planning, test management, and requirements management capabilities. Those capabilities span applications.
In each of the Collaborative Lifecycle Management (CLM) applications, teams perform their work within the context of a project area. A project area defines the project deliverables, team structure, process, and schedule. You access all project artifacts, such as iteration plans, work items, requirements, test cases, and files under source control within the context of a project area. You can associate project areas in different applications. Use lifecycle projects to: Create project areas Establish associations between project areas Centrally manage project areas Project templates can define which project areas to create and which associations to establish between those project areas. Instructor notes: Be sure that students understand the concept of a project area, and that they understand the notion that you can create associations between project areas in different applications. A lifecycle project enables you to create and centrally manage team areas across applications. Point out that lifecycle project templates can be used to automate the creation of associated project areas.
When you work within a lifecycle project, you have visibility into the work in associated project areas. You can perform work in those associated project areas, if your role permissions allow it. Instructor notes: Explain that when you use associated project areas within a lifecycle project, you have visibility into the resources in other project areas. Students have not necessarily been introduced to dashboards or work items yet. But, they should understand that OSLC enables data sharing and establishing links between resources in different project areas. Therefore, the dashboard example with “Implemented by” and “Validated by” trace relationships should make sense. Focus on these ideas of transparency and working within different project areas rather than the details of the information in the screen captures.
Instructor notes: The Home menu provides an easy way to navigate from one project area to another.
In-Context Collaboration is the ability to collaborate, in real time, on projects in the context of work being done. Information within the Rational solution for CLM is always the latest, and it is always easily accessible. Instructor notes: This section discusses features that enable in-context collaboration within CLM. It focuses on work items, dashboards, rich hover information, and commenting on and reviewing requirements.
Use work items to track and manage tasks and issues during a project. The project template defines the work item types for the project. For example, the Scrum process template defines the following work item types: Defect Story Task Epic Impediment Retrospective Track build item Adoption item Each work item type has a state transition model so that you can track its progress. Instructor notes: Work items are a key way that CLM teams plan, organize, and track their work. Be sure students understand what work items are and what value they provide.
In the work item Discussion section, teams can communicate about the work. You can create links between work items and other project resources to track dependencies or to create traceability relationships. Instructor notes: Point out the elements of a work item. Point out the attributes, state, and links. Point out that teams can use the Discussion section to communicate.
From dashboards, you can get current information about project resources. Project administrators can customize project dashboards. Team members can create and customize personal dashboards.
You can customize dashboards by adding widgets that display the results of queries.
Hover your cursor over a project resource in any CLM application or in a dashboard to see detailed information about the resource without clicking it.
Team members can comment on requirements in-context as the requirements are being developed, or as change requests are introduced. Instructor notes: Team members with the appropriate client access licenses can comment on requirements in-context.
Formal reviews ensure that artifacts are reviewed and approved by key team members. The reviewed artifacts can be compiled in requirements collections that are then linked to execution and validation plans.
Instructor notes: Ask the students this question: What are the benefits of common, aligned, real-time planning? The next slide provides a few answers.
Real-time planning is linked to project execution. Without this link, plans inevitably become stale and inaccurate. For example, if you maintain your project plan in a word-processing document that is outside of your ALM environment, your plan can easily become outdated. The Rational solution for CLM integrates planning with execution so that organizations can manage project resources, acclimate new team members, and react nimbly to changes that customers or market conditions introduce.
The release plan defines the high-level requirements and describes how the team will develop and test the release. The release plan provides a common way to view and manage all work associated with the release: Associate an approved requirements collection with the release plan Create work items to implement the requirements Create test plans and test cases to validate the requirements; link them to the requirements
The release plan has several views. The Traceability view provides information about requirements and test cases that are linked to plan items.
Lifecycle traceability is the ability to provide both forward and backward visibility across a project lifecycle. With the Rational solution for CLM, you can confirm that the software that you are delivering to a customer includes a specific requirement that was developed by using a specified process, associated with a specific software build, and validated by a specific set of test cases and test case results. Traceability helps to verify that you are complying with quality and regulatory requirements.
Instructor notes: This graphic on this slide is an example of the links that can establish traceability relationships in a CLM project.
Each team member can view links to and from project artifacts. Each application has a different interface for viewing links. Team members can navigate links to access linked resources. With the correct permissions, you can create and delete links.
The Requirements management and Quality management applications provide document-style reports in CLM. The Change and configuration management application does not provide document-style reports, but you can import them into the application on the Report Resources page. To customize Rational Reporting for Document Generation reports, you must have a licensed version of Rational Publishing Engine. Rational Reporting for Development Intelligence must be installed and configured separately by an administrator. The Requirements management, Quality management, and Change and configuration management applications all provide Development Intelligence reports in CLM. The report author can customize Rational Reporting for Development Intelligence report templates by using IBM® Cognos® Report Studio or IBM® Cognos® Query Studio. For more information about how to customize Rational Reporting for Development Intelligence reports, see these resources: Reporting tutorials in the information center at http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?nav=%2F2_5 Demonstration videos on YouTube at http://www.youtube.com/playlist?list=PL41F90AA10F4744B8
Reports are displayed in IBM® Cognos® Viewer. Requests, such as development items, must be linked to most requirements to ensure that requirements can be traced to development artifacts. To verify that requests are linked to requirements, you can view the pie chart to see the percentage of requirements that are covered by links to development items and the percentage of requirements that are not covered, or have no associated requests. If requirements are not linked to requests, investigate to find out why, and create links if necessary.
Notes: Instructor notes: Purpose — Summarize the unit Details — Additional information — Transition statement —
Appendix A: Introduction to Collaborative Lifecycle Management