IBM WIoT CP Summit Open Labs (NO COST - not a substitute for full training courses)

Transcription

1 IBM WIoT CP Summit Open Labs (NO COST - not a substitute for full training courses) November 14-16, :00 AM - 4:00 PM The Westin New Orleans Canal Place 100 Iberville Street, 12th floor Salon New Orleans, LA Registration 11/14: 11/15: 11/16: Labs are self-paced with workbooks SMEs will be present to answer questions

2 Choose from one or more of these Self-Paced, Hands-On Labs: Requirements Management IOT9661 DOORS Next Generation Rational Collaborative Requirements Definition with DOORS Introduction to Rational Publishing Engine for DOORS Next Generation (NEW) Publish Your Rational DOORS Requirements with RPE Design Management IOT Integrating Your System Design into the Development Lifecycle OMG SysML with IBM Rational Rhapsody and IBM Jazz Introduction to Rhapsody for Software Engineers (NEW) Introduction to Rhapsody for Systems Engineers (NEW) Introduction to Rational Publishing Engine for Rhapsody (NEW) Continuous Engineering IOT The IBM Continuous Engineering Solution v6.0.1

3 Choose from one or more of these Self-Paced, Hands-On Labs: Collaborative Lifecycle Management (CLM) DEV Quick Planner in IBM Collaborative Lifecycle Management v6.0 / RTC Getting Started with CLM (NEW) CLM for Agile Development (NEW) Scaled Agile Framework (SAFe) It s an Idea whose time has come! Let s adjust our plans the SAFe 4.5 way (NEW) Collaborative Lifecycle Management for Scaled Agile (SAFe 4.5) (NEW) Report Management Jazz Reporting Services for Continuous Engineering (NEW) Creating Reports using Jazz Reporting Service in IBM CLM (NEW) Impact Analysis using Rational Engineering Lifecycle Manager (NEW)

4 Requirements Management

5 IOT9661 DOORS Next Generation (Duration: 3 4 hours) This workshop demonstrates how the IBM Continuous Engineering solution can help companies reduce the time, cost, and risk of developing profitable products and systems. Participants of this Proof of Technology (PoT) will get hands on experience with the Requirements Management application of the IBM JazzTM platform. Over the course of the PoT, users will explore how integrated IBM tools support the product development lifecycle, decreasing cost and time to market by: Managing Requirements across the entire lifecycle and disciplines, from stakeholder requirements to system, software and hardware requirements, through to test. Enabling distributed teams to collaborate and communicate throughout the development lifecycle. Enabling projects to be managed effectively, by providing accurate visibility into project health status and team workloads. Automating traceability and auditability by managing artifacts and their inter-relationships across the lifecycle, empowering teams to deliver more value by removing manual tasks. ü Lab 1 RM Fundamentals with a Web Client ü Lab 2 Dealing with Changes to Requirements ü Lab 3 Importing ü Lab 4 Reporting and Dashboard Widgets ü Lab 5 Configuration Management of Requirements ü Lab 6 Extension Exercises üdoors Next Generation 6.0.1

6 Rational Collaborative Requirements Definition with DOORS (Duration: 3 4 hours) Rational DOORS is a leading requirements management tool that makes it easy to capture, trace, analyze, and manage changes to information. Control of requirements is key to reducing costs, increasing efficiency, and improving the quality of your products. Using the Rational DOORS family of products, you can optimize requirements communication, collaboration, and verification throughout your organization and across your supply chain. Rational DOORS makes it easy for everyone in your organization and beyond to participate in and contribute to the requirements management process. This workshop will provide attendees with the opportunity to learn from IBM professionals and use DOORS and DOORS Web Access (DWA) hands-on in a Systems Engineering based example scenario. ü Lab 1 Import User Requirements from existing documents ü Lab 2 Create System Requirements and Traceability ü Lab 3 Analyze Requirements ü Lab 4 Verification of Requirements ü Lab 5 Review Requirements, Baseline and Sign-off ü Lab 6 Manage Changing Requirements and Impact Analysis ürational DOORS Rational ürational DOORS Web Access

7 Introduction to Rational Publishing Engine for DOORS Next Generation (NEW) (Duration: 2 hours) IBM Rational Publishing Engine (RPE) automates document generation from IBM Rational solutions and select third party tools. You can use RPE to automate the generation of documents for ad hoc use, formal reviews, contractual obligations or regulatory compliance. In this Lab you will use Rational Reporting for Document Generation (RRDG) to generate a report from within DNG itself. You will then use RPE Document Builder to assemble a report from a set of predefined templates and generate documents in both Word and PDF formats. Rational ü Lab 1: Reporting on Modules in DNG Using Rational Publishing Engine (RPE) ü Lab 2: Creating Document Templates for DNG Using Rational Publishing Engine (RPE) ürational DOORS Next Generation ürational Publishing Engine 2.1.2

8 Publish Your Rational DOORS Requirements with RPE (Duration: 2 3 hours) This is your opportunity to learn about Rational Publishing Engine (RPE) and take it for a hands-on test drive. The objective of this Workshop is to demonstrate how RPE helps your projects meet business goals, satisfy customer needs, and address applicable regulations and standards, to help customers achieve greater value and performance from their global investments in software. RPE can be used to generate documents with data from different sources (System Architect, DOORS, Focal Point, Rhapsody, and the Jazz family tools) and to different output formats like Word, PDF, HTML and XSL- FO. The lab exercises are designed to give the student an introduction to the RPE application using data from a Rational DOORS project. This Workshop consists of three lab exercises. The student is to follow the related lab workbook at your own pace. The work book instructs the student how to perform various tasks within RPE with the intention of the student becoming more familiar with RPE s functions and capabilities using Rational DOORS data. The student is encouraged to ask questions and get assistance whenever necessary. Rational ü Lab 1 - Document Generation from the DOORS Client ü Lab 2 Modify a Document Specification ü Lab 3 Add Traceability Matrix to Requirements Document Template ürational DOORS ürational Publishing Engine

9 Design Management

10 IOT9650 Integrating Your System Design into the Development Lifecycle (Duration: 2 hours) This lab will show some of the benefits of Integrating your System Design into the Development Lifecycle. Architectural analysis and design is an important part of a Systems Engineering process and whether using SysML, DoDAF or UML in Rational Rhapsody, or simulating using Simulink models, the use of traceability links to relate the models to the requirements being analyzed and to the design requirements which result ensures that work is justifiable and the design decisions explained. By working through this lab, you will experience how to: Work with a model using the actively managed mode of configuration management, and using the Rhapsody profile for Systems Engineering Create, navigate, and analyze traceability links between design and requirements artifacts Make comments and mark-ups as part of a Rhapsody model review. Systems engineers and software engineers typically use the Rhapsody desktop client to create and maintain models, while stakeholders and other product development roles use Rhapsody Design Manager to review models and create links between design artifacts and other artifacts. ü Exercise 1: Exploring the Automated Meter Reader Model ü Exploring the Model using the Rhapsody Desktop Client ü Exploring the Model using Rhapsody Design Manager ü Exercise 1 Review ü Exercise 2: Adding Links to the Rhapsody Model ü Add a Link using the Rhapsody Desktop Client ü Add a Link using Rhapsody Design Manager ü Exercise 2 Review ü Exercise 3: Model Reviewing ü Model Reviewing Using the Rhapsody Desktop Client ü Model Reviewing Using Rhapsody Design Manager ü Exercise 3 Review ürhapsody

11 OMG SysML with IBM Rational Rhapsody and IBM Jazz (Duration: 3 4 hours) The focus is model-based systems engineering (MBSE) using standards-based support for the OMG Systems Modeling Language (OMG SysML). The Architect for Systems Engineers Edition of IBM Rational Rhapsody is used. Optional labs show how Rhapsody works in combination with IBM Rational Design Manager 5.0. Later labs also show Open Services for Lifecycle Collaboration (OSLC) links can be made with Requirements Management (RM) tools. This approach is contrasted with the conventional approach of using the Rhapsody Gateway to synchronize requirements with a Rhapsody project. ü Lab 1 Explore the HSUV SysML Model ü Lab 2 Requirements, Tables, Matrices, and Metrics ü Lab 3 More on SysML Blocks, Ports and Parts (Optional) ü Lab 4 Create a Rhapsody DM Project Area ü Lab 5 Modifying a Project on the Design Manager Server ü Lab 6 Create a Lifecycle Project that Includes Jazz/RM ü Lab 7 Linking Modeling Elements to Jazz/RM ürhapsody Architect for Systems Engineers ürational Design Manager 5.0

12 Introduction to Rhapsody for Software Engineers (NEW) (Duration: 3 hours) IBM Rhapsody for Software Engineers is an integrated software engineering environment for designing, generating and testing embedded applications. It uses the OMG Unified Modeling Language (UML) to enable rapid requirements analysis and visual, model-based design and code generation. You will start by creating (in time-honored fashion) a Hello World project. You will see how Rhapsody generates code from models and how the code or model may be modified. You will then create a simple application, first importing requirements from a spreadsheet (note that in the Systems Engineering Lightning Lab Requirements are imported from a real requirements tool through OSLC) and continuing to add architecture and behavior. You will see how requirements may be generated into code for compliance purposes. You will see how such applications may be debugged graphically using Rhapsody, and how code may be generated for embedded targets as well as the host machine allowing early testing of the code before hardware is available. Finally, you will see how to graphically debug an executing application using the model. ü Lab 1: Creating a Hello World Project ü Lab 2: Importing Requirements ü Lab 3: Creating a Software Model ü Lab 4: Design Level Debugging ürhapsody Developer for Software Engineer

13 Introduction to Rhapsody for Systems Engineers (NEW) (Duration: 3 hours) IBM Rhapsody for Systems Engineers is an integrated, systems engineering environment for analyzing project requirements. It uses the OMG Systems Modeling Language (OMG SysML) to enable rapid requirements analysis and visual, model-based design. Models may be verified and validated through execution and simulation. Rhapsody for Systems Engineers helps systems engineering teams design complex functionality in less time. You will create a very simple model, first importing requirements from an OSLC source (in this case DOORS Next Generation) and connecting them to Use Cases. You will model system behavior using Sequence Diagrams and Activities and prove the model by simulating the design. Lightning Labs are designed to take less than two hours to complete as such this is a highlysimplified example and you will barely scratch the surface of the power that Rhapsody offers. Further labs and training are available that cover both Rhapsody and more formal workflows such as Harmony for Agile Model Based Systems Engineering. ü Lab 1: Creating a Project ü Lab 2: Importing Requirements ü Lab 3: Requirements Traceability ü Lab 4: Creating an Executable Model ü Lab 5: Creating Interfaces ürhapsody Designer for Systems Engineer

14 Continuous Engineering

15 IOT The IBM Continuous Engineering Solution v (Duration: 3 to 4 hours) This workshop demonstrates how the IBM Rational Continuous Engineering solution can help companies reduce the time, cost, and risk of developing profitable products and systems. Participants of this lab will get hands on experience with Rational Team Concert, DOORS Next Generation, and Rational Quality Manager to explore the linkage of artifacts across the development lifecycle. Participants will take on several development team roles, to navigate the relationships among requirements, change requests, development tasks, design artifacts, test cases, and test execution results. All of these capabilities are greatly automated when using the IBM Rational Continuous Engineering solution. Users will explore how integrated Rational tools support the product development lifecycle, decreasing cost and time to market by: Managing Requirements across the entire lifecycle and disciplines, from stakeholder requirements to system, software, and hardware requirements, through to test Incorporating Systems Engineering practice guidance and process enactment Enabling distributed teams to collaborate and communicate throughout the development lifecycle Enabling projects to be managed effectively, by providing accurate visibility into project health status and team workloads Automating traceability and auditability by managing artifacts and their inter-relationships across the lifecycle, empowering teams to deliver more value Using Configuration Management to work on a variant and to create a baseline across requirements and tests. ü Lab 1 Introduction to Continuous Engineering Project Planning and Management ü Lab 2 Overview of Global Configurations and Configuration Management ü Lab 3 RM Fundamentals with a Web Client ü Lab 4 Lifecycle Traceability Across the V Cycle ü Lab 5 Creating a New Baseline Across Requirements and Tests ürational Team Concert üdoors Next Generation ürational Quality Manager 6.0.1

16 Collaborative Lifecycle Management

17 DEV Quick Planner in IBM Collaborative Lifecycle Management v6.0 / RTC (Duration: 2 hours) In this lab, you are a member of a development team that is working for a bank called JKE Banking. The bank already has a web presence, but it has been decided that this presence needs to be expanded to the mobile market. The solution is required rapidly, and so the developers who are working on this application must have some way to track their progress. They must know what deadlines are in place and who is responsible for developing the different parts of the application. Three developers are tasked to work on the application. It is also decided that development will follow the agile process, with a subset of complete work provided to the stakeholders on a cyclic basis (called releases). There is also a daily meeting of the team members to track progress (this meeting is called a scrum). Apart from developers, the team includes an administrative leader (called a scrum master), a product owner with the vision of what must go into the product, and a stakeholder, someone who requires the final application. ü Add new item to Product Backlog ü Provide details and estimates for stories ü Rank high priority stories ü Add estimates for other high priority stories ü Reorder stories in the Product Backlog ü Select stories for the release ü Create a baseline for the release plan ü Refine Release Backlog ü Planning the sprint ü Decompose stories into tasks ü Review team workload for the Sprint ürational Team Concert 6.0.1

18 Getting Started with CLM (Duration: 1 to 2 hours) The IBM Rational Collaborative Lifecycle Management (CLM) solution is a set of seamlessly integrated application lifecycle management (ALM) tools that work together as one. IBM Rational Collaborative Lifecycle Management combines IBM Rational Team Concert, IBM Rational DOORS Next Generation and IBM Rational Quality Manager. It delivers requirements management, quality management, change and configuration management and project planning and tracking. These integrated capabilities foster greater communication, collaboration and visibility to accelerate delivery, improve quality and support better development decisions. This lab introduces a new user to the basic navigation of the applications (Requirements Management, Change and Configuration Management and Quality Management) of IBM Collaborative Lifecycle Management(CLM) solution. The Lab also covers basic concepts and terminologies that a CLM user should be familiar with. ü Lab 1 Getting Started with CLM applications ü Lab 2 Working with Dashboards ü Lab 3 Getting started with the Requirements Management application ü Lab 4 Explore the Change and Configuration Management application ü Lab 5 Explore the Quality Management application ürational Team Concert ürational DOORS Next Generation ürational Quality Manager 6.0.4

19 CLM for Agile Development (NEW) (Duration: 4 to 6 hours) This workshop is based on the Money that Matters lifecycle scenario which uses a fictitious banking company called JKE and a realistic software development project whose goal is to deliver Release 1 of the JKE Banking application. The scenario centers on a single iteration (sprint) by the team responsible for delivering an initiative called "Business Recovery Matters". All the activities within the scenario occur in the scope of a single sprint for one team. The team is using IBM Rational Team Concert to plan, track, collaborate, and deliver the release. Collaborative work is performed to capture requirements with IBM Rational DOORS Next Generation and plan, construct and record execution of tests with IBM Rational Quality Manager. This scenario can be applied to larger enterprise projects such as the one imagined for JKE Banking. To do so requires a hybrid agile approach, which is scaled to fit into an enterprise environment. The term "hybrid" is being used in the agile community to refer to combination of ideas from various methods, sometimes all agile methods but also sometimes from "traditional" sources, lean sources, and so on. ü Lab 1 Respond to a New Business Requirement ü Lab 2 Adjust Team Plans ü Lab 3 Implement a Story ü Lab 4 Plan the Test ü Lab 5 Test a Story ü Lab 6 Steer the Sprint ürational Team Concert ürational DOORS Next Generation ürational Quality Manager 6.0.4

20 Scaled Agile Framework (SAFe)

21 It s an Idea whose time has come! Let s adjust our plans the SAFe 4.5 way (NEW) (Duration: 2 to 3 hours) Enterprise scaled agile methodologies describe an approach for orchestrating the planning and execution of software or product delivery across an organization. While teams are happily executing, ideas are constantly coming into the portfolio. Some of these ideas require immediate attention while others can sit until the next planning cycle. In this workbook, you will explore how the Portfolio, Program and its teams process these ideas quickly using IBM Collaborative Lifecycle Management to know which is which so that important stuff doesn't fall through the cracks. You will see how an idea comes into the JK Enterprises line of business and then is triaged to drive change in the next delivery of an application. You will further witness how one such idea, deemed critical in nature by the Portfolio, is attended to by the Program Management Team. The Program analyzes the epic to determine the work, its dependencies and how to make room for this new work. We are using SAFe 4.5 for Lean Enterprises as a methodology for Enterprise Scale. ü Lab 1 Respond to urgent Business Requirement ü Lab 1.1 Submit a New Request ü Lab 1.2 Monitor and Assess New Request ü Lab 1.3 Adjust Plans to accommodate New Request ü Lab 1.4 Communicate Change to Impacted Programs ü Lab 2 Orchestrate Program Delivery ü Lab 2.1 Assess and Respond to Incoming Work ü Lab 2.2 Adjust the Program Plans ü Lab 2.3 Adjust Team-level Plans ü Lab 2.4 Synchronize Delivery at all levels ürational Team Concert ürational Quality Manager 6.0.4

22 Collaborative Lifecycle Management for Scaled Agile (SAFe 4.5) (NEW) (Duration: 4 to 6 hours) This workshop is based on the Money that Matters (JKE Banking) with the SAFe Portfolio and Program to demonstrate Enterprise Scaled Agile. It helps understand how CLM works from top to bottom (Portfolio -> Program - > Team). The scenario centers on a single iteration (sprint) by the team responsible for delivering an initiative called "Business Recovery Matters". All the activities within the scenario occur in the scope of a single sprint for one team. The team is using IBM Rational Team Concert to plan, track, collaborate, and deliver the release. Collaborative work is performed to capture requirements with IBM Rational DOORS Next Generation and plan, construct and record execution of tests with IBM Rational Quality Manager. ü Lab 1 Respond to an Urgent Business Requirement ü Lab 2 Orchestrate Program Delivery ü Lab 3 Elaborate a Story ü Lab 4 Adjust Team Plans ü Lab 5 Implement a Story ü Lab 6 Plan the Test ü Lab 7 Test a Story ü Lab 8 Steer the Sprint ürational Team Concert ürational DOORS Next Generation ürational Quality Manager 6.0.4

23 Report Management

24 Jazz Reporting Services for Continuous Engineering (NEW) (Duration: 3 hours) This lab focuses on Jazz Reporting Services Report Builder (JRS) which allows self-serve reports to be dynamically created and executed. Reports may be in tabulated or chart form. Reports may be exported to physical documents such as Word and PDF or may appear on Dashboards across the Jazz Platform. Reports may also be exported to Rational Publishing Engine (RPE) for further enhancement such as adding company standard stylesheets, cover pages and so on. It should also be noted that JRS Report Builder can report on both live, configuration managed data in LQE but also on historical data stored in the Data Warehouse. This lab focuses on the former. ü Lab 1. Creating Reports Using Jazz Reporting Services Report Builder ü Lab 2. Exporting Reports to Rational Publishing Engine üjazz Reporting Services Report Builder 6.0.4

25 Creating Reports using Jazz Reporting Service in IBM CLM (NEW) (Duration: 2 to 3 hours) The Jazz TM Reporting Service is the default reporting solution for Rational solution for Collaborative Lifecycle Management (CLM). Jazz Reporting Service (JRS) provides practitioners with the ability to easily create their own reports in a powerful and easy to use interface. The JRS interface is designed to be intuitive without any technical knowledge of the underlying data warehousing technology. JRS contains the following components: Report Builder which a key component of the Jazz TM Reporting Service, Data Collection runs data collection jobs from Rational solution for CLM applications and loads data into the data warehouse, and Lifecycle Query Engine (LQE) provides index to data across lifecycle tools that support the tracked resource set (TRS) specification. In this Lab, Marco, the Scrum Master creates various kinds of reports that are table-based and graphical reports for single and multiple artifact types using the Jazz Reporting Service in CLM He works on various aspects of the report to specify the set of characteristics and filter on the artifact type that determines which data will be displayed. ü Lab 1 Explore the Report Builder interface ü Lab 2 Create a Summary Report ü Lab 3 Create a Cross-Project Traceability Report ü Lab 4 Create an Aging Report ü Lab 5 Create a Historical Trend Report ü Lab 6 Add a report as a widget on a CLM Dashboard üjazz Reporting Services Report Builder 6.0.4

26 Impact Analysis Using Rational Engineering Lifecycle Manager (NEW) (Duration: 3 hours) This lab focuses on Rational Engineering Lifecycle Manager (RELM) a powerful tool that allows dynamic analysis and visualization of the linked lifecycle data allowing impact analysis to be performed in a matter of minutes. Although RELM ships with a collection of sample views, it is very easy to build your own. In this Lightning Lab, you will build a simple Impact Analysis view starting with a work item in Rational Team Concert (RTC) and exploring the requirements and tests linked to that work item. Note that in this lab you will be using the sample data that ships with the product from Jazz.net, that is the JKE Banking sample. Whilst this is more of an IT project than an engineering one it still contains the same kinds of artifacts (requirements and tests for example). However, it does not contain any models and so Rhapsody/Design Manager data is not included in this lab. Further training is available that focuses on use of RELM to analyze model data. ü Exercise 1 Create RELM analysis view ü Exercise 2 Add Artifact to view ü Exercise 3 Explore linked data ü Exercise 4 Modify the analysis view ü Exercise 5 Save view and use it ü Exercise 6 Create a dynamic view ü Exercise 7 Explore Dependency analysis ü Exercise 8 Explore nodes ü Exercise 9 Exploring conditional properties ürational Engineering Lifecycle Manager 6.0.4