• Save
Appendix A: Introduction to Collaborative Lifecycle Management
Upcoming SlideShare
Loading in...5
×
 

Appendix A: Introduction to Collaborative Lifecycle Management

on

  • 322 views

Examine the overall landscape of software development and delivery processes and tools, and understand where Rational Team Concert fits in.

Examine the overall landscape of software development and delivery processes and tools, and understand where Rational Team Concert fits in.

Statistics

Views

Total Views
322
Views on SlideShare
322
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Contents <br /> Module overview B-2 <br /> Introduction to CLMB-3 <br /> Collaboration across the lifecycleB-11 <br /> Common planningB-21 <br /> Lifecycle traceabilityB-28 <br /> Rational reportingB-35 <br /> Explore the Money that Matters lifecycle scenarioB-41 <br /> Additional CLM learning resourcesB-44 <br />
  • Notes: <br /> Instructor notes: <br /> Purpose — List the unit objectives <br /> Details — Timing: 60 minutes <br /> This module is targeted at practitioners using, or preparing to use, a CLM application within the larger CLM context. <br /> 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. <br /> This module can support any course in the CLM2013 curriculum. <br /> 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. <br /> 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. <br /> Additional information — <br /> Transition statement — <br />
  • The Rational solution for Collaborative Lifecycle Management seamlessly combines aplication lifecycle tools to support software delivery teams. <br /> 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. <br /> Instructor notes: <br /> You do not have to go into great detail about the architecture of CLM. <br /> Be sure that students understand the components of CLM and that they are seamlessly integrated. <br /> Explain that Jazz technology provides a open collaborative platform for CLM. <br />
  • The Rational solution for CLM uses Open Services for Lifecycle Collaboration (OSLC) standards. <br /> OSLC is an open community of vendors, integrators, and users that creates freely available, scenario-driven specifications for integrating software applications. <br /> 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. <br /> Wherever the data is, you can work with data from your current context because of OSLC-based integrations. <br /> Instructor notes: <br /> You do not need to have a lengthy discussion about OSLC. <br /> Be sure that students understand that the Rational solution for CLM is founded on OSLC standards. <br /> Point out the advantages of OSLC as they are outlined on the slide. <br />
  • 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. <br /> The CLM applications generally correspond to the products. <br /> 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. <br /> Instructor notes: <br /> This slide clarifies some of the terminology that is used in the product and the help topics. <br /> In the Rational solution for CLM, an application is the basic unit of installation, deployment, and update. <br /> Each application can contain several capabilities. Capabilities are the smallest unit of function that can be enabled through licensing. <br />
  • For full details about client access licensing, see the help topic, “Client access license management overview.” <br /> Instructor notes: <br /> This slide shows how capabilities are enabled through role-based client licensing. <br /> 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. <br />
  • 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. <br /> You can associate project areas in different applications. <br /> Use lifecycle projects to: <br /> Create project areas <br /> Establish associations between project areas <br /> Centrally manage project areas <br /> Project templates can define which project areas to create and which associations to establish between those project areas. <br /> Instructor notes: <br /> 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. <br /> A lifecycle project enables you to create and centrally manage team areas across applications. <br /> Point out that lifecycle project templates can be used to automate the creation of associated project areas. <br />
  • 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. <br /> Instructor notes: <br /> Explain that when you use associated project areas within a lifecycle project, you have visibility into the resources in other project areas. <br /> 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. <br /> Focus on these ideas of transparency and working within different project areas rather than the details of the information in the screen captures. <br />
  • Instructor notes: <br /> The Home menu provides an easy way to navigate from one project area to another. <br />
  • 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. <br /> Instructor notes: <br /> This section discusses features that enable in-context collaboration within CLM. <br /> It focuses on work items, dashboards, rich hover information, and commenting on and reviewing requirements. <br />
  • Use work items to track and manage tasks and issues during a project. <br /> The project template defines the work item types for the project. For example, the Scrum process template defines the following work item types: <br /> Defect <br /> Story <br /> Task <br /> Epic <br /> Impediment <br /> Retrospective <br /> Track build item <br /> Adoption item <br /> Each work item type has a state transition model so that you can track its progress. <br /> Instructor notes: <br /> 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. <br />
  • In the work item Discussion section, teams can communicate about the work. <br /> You can create links between work items and other project resources to track dependencies or to create traceability relationships. <br /> Instructor notes: <br /> Point out the elements of a work item. <br /> Point out the attributes, state, and links. <br /> Point out that teams can use the Discussion section to communicate. <br />
  • From dashboards, you can get current information about project resources. Project administrators can customize project dashboards. Team members can create and customize personal dashboards. <br />
  • You can customize dashboards by adding widgets that display the results of queries. <br />
  • 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. <br />
  • Team members can comment on requirements in-context as the requirements are being developed, or as change requests are introduced. <br /> Instructor notes: <br /> Team members with the appropriate client access licenses can comment on requirements in-context. <br />
  • Formal reviews ensure that artifacts are reviewed and approved by key team members. <br /> The reviewed artifacts can be compiled in requirements collections that are then linked to execution and validation plans. <br />
  • Instructor notes: <br /> Ask the students this question: What are the benefits of common, aligned, real-time planning? <br /> The next slide provides a few answers. <br />
  • 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. <br />
  • The release plan defines the high-level requirements and describes how the team will develop and test the release. <br /> The release plan provides a common way to view and manage all work associated with the release: <br /> Associate an approved requirements collection with the release plan <br /> Create work items to implement the requirements <br /> Create test plans and test cases to validate the requirements; link them to the requirements <br />
  • The release plan has several views. The Traceability view provides information about requirements and test cases that are linked to plan items. <br />
  • 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. <br />
  • Instructor notes: <br /> This graphic on this slide is an example of the links that can establish traceability relationships in a CLM project. <br />
  • 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. <br />
  • 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. <br /> To customize Rational Reporting for Document Generation reports, you must have a licensed version of Rational Publishing Engine. <br /> Rational Reporting for Development Intelligence must be installed and configured separately by an administrator. <br /> The Requirements management, Quality management, and Change and configuration management applications all provide Development Intelligence reports in CLM. <br /> The report author can customize Rational Reporting for Development Intelligence report templates by using IBM® Cognos® Report Studio or IBM® Cognos® Query Studio. <br /> For more information about how to customize Rational Reporting for Development Intelligence reports, see these resources: <br /> Reporting tutorials in the information center at http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?nav=%2F2_5 <br /> Demonstration videos on YouTube at http://www.youtube.com/playlist?list=PL41F90AA10F4744B8 <br />
  • Reports are displayed in IBM® Cognos® Viewer. <br /> 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. <br />
  • Notes: <br /> Instructor notes: <br /> Purpose — Summarize the unit <br /> Details — <br /> Additional information — <br /> Transition statement — <br />

Appendix A: Introduction to Collaborative Lifecycle Management Appendix A: Introduction to Collaborative Lifecycle Management Presentation Transcript

  • Accelerating Product and Service Innovation Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 9.0 The Rational solution for Collaborative Lifecycle Management (CLM) Appendix B: The Rational solution for Collaborative Lifecycle Management (CLM) © Copyright IBM Corporation 2008, 2014
  • Unit objectives After completing this unit, you should be able to: • Describe the Rational® solution for Collaborative Lifecycle Management (CLM). • Explain how the Rational solution for CLM enables these activities:  In-context collaboration across the lifecycle  Common, real-time planning  Lifecycle traceability  Rational reporting © Copyright IBM Corporation 2008, 2013
  • Introduction to CLM > = Current topic >Introduction to CLM  Collaboration across the lifecycle  Common planning  Lifecycle traceability  Rational reporting © Copyright IBM Corporation 2008, 2013
  • The Rational solution for Collaborative Lifecycle Management BM Rational solution for Collaborative Lifecycle Management Design (Beta) QualityRequirements Software Change and Configuration Open Lifecycle Integration Platform ArchitectEngineerAnalystDeveloperQuality ProfessionalDeployment Engineer Seamless integration of application lifecycle tools Transparency and open collaboration among teams across the lifecycle Powered by the Jazz technology platform © Copyright IBM Corporation 2008, 2013
  • Open Services for Lifecycle Collaboration (OSLC) Standardizes the way that software lifecycle tools share data  Link-based model  Data is where it should be  Standards-based model  Tool-, solution-, and technology-agnostic © Copyright IBM Corporation 2008, 2013
  • CLM products, applications, and capabilities Jazz Team Server Change and Configuration Management Quality Management Requirements Management Automation Change managementPlanning SCM Test management Requirements management Reporting (BIRT) Reporting (RRDG, RRDI) Distributed SCM Host system development Products Applications Capabilities: The smallest unit of functioning that can be enabled through licensing Report customization Design Management (BETA) Rational Team Concert Rational Quality Manager Rational Requirements Composer Rational Software Architect Design management © Copyright IBM Corporation 2008, 2013
  • Role-based client access licensing Access to capabilities is controlled by role-based licenses Roles Change management Report customization Planning SCM Automation Test Management Requirements Management CLM Professional RW RW RW RW RW RW RW Developer RW RW RW RW RW R R Quality Professional RW RW RW R R RW RW Analyst RW RW RW R R R RW Contributor RW RW RW R R R R Stakeholder RW R R Developer (Enterprise) RW RW RW RW RW R R R=read RW=read/write © Copyright IBM Corporation 2008, 2013
  • Project areas and lifecycle projects Change management project area Requirements management project area Design management project area Quality management project area Q uality m anagem ent (quality m anagem ent artifacts) Requirements (requirements) Change m anagem ent (requirem ents change requests) Change m anagem ent (im plem entation requests) Requirem ents (requirem ents) Change management (change requests) Q uality m anagem ent (quality m anagem ent tasks) C hange m anagem ent (defects)© Copyright IBM Corporation 2008, 2013
  • Working in a lifecycle project When you work in a lifecycle project, you have visibility into work in associated project areas. You can work in associated project areas, depending on role permissions. © Copyright IBM Corporation 2008, 2013
  • Navigating a lifecycle project Use the Home menu to navigate to project areas. © Copyright IBM Corporation 2008, 2013
  • Collaboration across the lifecycle > = Current topic  Introduction to CLM > Collaboration across the lifecycle  Common planning  Lifecycle traceability  Rational reporting © Copyright IBM Corporation 2008, 2013
  • In-context collaboration The Jazz technology platform facilitates real-time, in-context collaboration across the software lifecycle Work items Rich hover information Dashboards In-context comments and requirements reviews © Copyright IBM Corporation 2008, 2013
  • Use work items to manage project work Use work items to track and manage tasks and issues during a project  Record defects  Describe feature improvements  Identify tasks to be performed Project templates in CCM define work item types Each work item type has attributes and a state transition model • © Copyright IBM Corporation 2008, 2013
  • Work item example: Scrum process story item Unique identifier. The current state, which you can change. Attributes, which provide information to manage, track, and report on the project. The Discussion section, in which team members record notes or exchange information. Links to other CLM resources. Links are created on the Links tab. © Copyright IBM Corporation 2008, 2013
  • View project information in dashboards Customizable project and personal dashboards provide real-time views into project information across project areas. Have any change requests arrived since the last milestone? Which requirements are linked to stories for implementation? © Copyright IBM Corporation 2008, 2013
  • Query results in dashboard widgets Create queries and then view results in dashboard widgets. © Copyright IBM Corporation 2008, 2013
  • View information about project resources in rich hovers In-context rich hovers provide visibility into information about project resources. The information is always the latest. © Copyright IBM Corporation 2008, 2013
  • Comment in-context on requirements Comments display in dashboard widgets. You can comment in-context on requirements. © Copyright IBM Corporation 2008, 2013
  • Comment in-context on designs © Copyright IBM Corporation 2008, 2013
  • Participate in requirement reviews Participate in formal or informal requirement reviews as an approver, reviewer, or optional reviewer. © Copyright IBM Corporation 2008, 2013
  • Common planning > = Current topic  Introduction to CLM  Collaboration across the lifecycle > Common planning  Lifecycle traceability  Rational reporting © Copyright IBM Corporation 2008, 2013
  • Common, real-time planning What are the benefits of common, aligned, real-time planning? © Copyright IBM Corporation 2008, 2013
  • Common, real-time planning Everyone knows what tasks are in progress or in queue. Everyone understands the overall status. Teams can assess impact and respond to change. All team members are aligned. Teams can answer the question: “Are we done?” All team members are aligned with business priorities. © Copyright IBM Corporation 2008, 2013
  • Requirements collections define the goals for a release Teams collaborate to define the approve requirements. The requirements define the goals for the release and are input for common release planning. © Copyright IBM Corporation 2008, 2013
  • Common release planning The release plan provides a way to view and manage all work associated with the release. All team members have access to the plan, and help to keep it current and accurate. © Copyright IBM Corporation 2008, 2013
  • Plan an iteration You can organize the work of the release into iterations. Assign and track work within each iteration. © Copyright IBM Corporation 2008, 2013
  • Lifecycle view of plan items The Traceability view provides insight into coverage and status across the lifecycle. © Copyright IBM Corporation 2008, 2013
  • Lifecycle traceability > = Current topic  Introduction to CLM  Lifecycle planning  Collaboration across the lifecycle > Lifecycle traceability  Rational reporting © Copyright IBM Corporation 2008, 2013
  • Lifecycle traceability Linking in and across project areas enables real-time lifecycle traceability. Traceability helps teams answer difficult questions… Are we ready to release? Are we aligned with the business? Can we pass an audit? What defects were resolved in this release? Which requirements are addressed in this iteration? Are all of the requirements tested? What defects are affecting which requirements? Project ManagerAnalyst Quality ProfessionalRelease EngineerDeveloper What is the quality of the build? What is ready for me to test? What defects have been addressed since the last build? How can I standardize when teams use different tools? Where are the bottlenecks in our processes? How can I speed up my builds? Are build times getting longer or shorter? What requirements am I implementing? What test uncovered this defect, on which environment and what build? What changes occurred overnight? Are there reusable components we can leverage? Can we implement in a way that supports maintainability? Which requirements impact the design? Architect © Copyright IBM Corporation 2008, 2013
  • Traceability relationships across project areas: Example CCM RM DM QM Test plan Test case Plan Change request Work item Requirement Collection Tracks Validated by Implemented by Validated by Model Derives from Design resource Validated by Elaborates Test script © Copyright IBM Corporation 2008, 2013
  • Lifecycle queries Provide cross-discipline visibility into issues that affect the project. © Copyright IBM Corporation 2008, 2013
  • Identify gaps in coverage and assess completeness The Traceability view of the release plan Gaps in coverage No gap in coverage © Copyright IBM Corporation 2008, 2013
  • Assess the impact of change Graphical traceability explorer in the Requirements Management application enables you to visualize changes across links and assess the impact of a change. © Copyright IBM Corporation 2008, 2013
  • Rational reporting > = Current topic  Introduction to CLM  Lifecycle planning  Collaboration across the lifecycle  Lifecycle traceability > Rational reporting © Copyright IBM Corporation 2008, 2013
  • Rational reporting Rational Reporting for Document Generation uses a runtime version of IBM® Rational® Publishing Engine to produce document-style reports. Rational Reporting for Development Intelligence uses business- intelligence technology to produce reports that pull data from a data warehouse. © Copyright IBM Corporation 2008, 2013
  • Flow of information for data warehouse reporting You can use the data in the data warehouse to report on themes, trends, aggregations, and other relationships among data. Data is collected from the CLM applications and is then stored in the data warehouse, where data can be transformed to represent various relationships. © Copyright IBM Corporation 2008, 2013
  • Predefined Development Intelligence reports RM application CCM application QM application © Copyright IBM Corporation 2008, 2013
  • Report results You select parameters for the report. Click the “Not covered” section of the graphic to see a detailed list of uncovered requirements. © Copyright IBM Corporation 2008, 2013
  • Customize dashboards to display reports © Copyright IBM Corporation 2008, 2013
  • Explore the Money that Matters lifecycle scenario The Money that Matters scenario illustrates how a team uses the Rational solution for CLM in their software delivery project.  Understanding the Money that Matters lifecycle scenario: https://jazz.net/rm/resources/_wHF7wGveEeGkm4Q2RtIWRg  The Money that Matters scenario: https://jazz.net/rm/resources/_-QrUATKjEeGFPKPBgbKpsA  Tutorial based on the Money that Matters lifecycle scenario: https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.rational.clm.tutor © Copyright IBM Corporation 2008, 2013
  • Review Why might you use a lifecycle project? List a few ways that teams can collaborate within the Rational solution for CLM. What are the advantages of establishing traceability across the lifecycle? What is different about planning in the Rational solution for CLM? What are the advantages of using Rational Reporting for Development Intelligence warehouse reporting? © Copyright IBM Corporation 2008, 2013
  • Unit summary Having completed this unit, you should be able to: • Describe the Rational® solution for Collaborative Lifecycle Management (CLM). • Explain how the Rational solution for CLM enables these activities:  In-context collaboration across the lifecycle  Common, real-time planning  Lifecycle traceability  Rational reporting © Copyright IBM Corporation 2008, 2013
  • Additional CLM learning resources • CLM training paths:  http://www-304.ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=page • CLM resources in the Jazz.net library:  https://jazz.net/library/#project=clm • Rational software on DeveloperWorks (Jazz Resources tab)  https://www.ibm.com/developerworks/rational/ • The CLM 2012 playlist on the Rational Education YouTube channel:  http://www.youtube.com/playlist?list=PL3D4EC6A5D5ECC989&feature=plcp • IBM Rational Reporting for Development Intelligence playlist on the Rational Education YouTube channel:  http://www.youtube.com/playlist?list=PL41F90AA10F4744B8 • Additional learning resources topic in the CLM Information Center  http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?topic=%2Fcom.ibm.help.co © Copyright IBM Corporation 2008, 2013