IBM Innovate 2013 Define and Manage Requirements with IBM Rational Requirements Composer Peter Luckey North America Requirements Management & Quality Management Segment Technical Lead Workshop 2266 © 2013 IBM Corporation

2 Please note the following IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

Good requirements are key to project success 3

IBM Rational Requirements Composer – Complete Picture 4

Understanding the Context 5 The Money that Matters life cycle scenario 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 sprint by the team responsible for delivering capabilities in support of a business initiative called "Business Recovery Matters". All of 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 Requirements Composer, manage design information with IBM Rational Software Architect Design Management, and plan, construct and record execution of tests with IBM Rational Quality Manager. The scenario is a companion to the JKE Banking sample project shipped with the Rational CLM solution and focuses on the practices, activities, and collaboration that occur as shown below.

6 Labs Tour of RRC & JKE Banking sample Leverage the Requirements Across the Lifecycle Conduct a Review Respond to Change Request Update the Business Process Refine the Use Case Diagram & Specification Change the User Interface Project Status

Tour of RRC & JKE Banking sample Leverage the Requirements Across the Lifecycle Conduct a Review Respond to Change Request Update the Business Process Refine the Use Case Diagram & Specification Change the User Interface Obtain awareness through dashboards & viewlets Examine quick access to artifacts - hover Discover the benefit of collections & reviews Explore traceability relationships in a trace tree Inspect artifact change history & recent changes viewlet Project Status Lab 1

8

Tour of RRC & JKE Banking sample Leverage the Requirements Across the Lifecycle Conduct a Review Respond to Change Request Update the Business Process Refine the Use Case Diagram & Specification Change the User Interface Expedite creation of requirements with one-click create Edit attributes simultaneously with multi-select Expedite creation of new requirements with CSV import Re-use external Word documents & import to create new requirements Group artifacts with Web 2.0 tags to aid filtering Project Status Lab 2

Tour of RRC & JKE Banking sample Leverage the Requirements Across the Lifecycle Conduct a Review Respond to Change Request Update the Business Process Refine the Use Case Diagram & Specification Change the User Interface Examine RRC capabilities for business process diagrams Evaluate what changes are required to refine diagram Modify business process diagram to incorporate new functionality Group artifacts with Web 2.0 tags to aid filtering Collaborate with team to inform them of refinements Project Status Lab 3

Tour of RRC & JKE Banking sample Leverage the Requirements Across the Lifecycle Conduct a Review Respond to Change Request Update the Business Process Refine the Use Case Diagram & Specification Change the User Interface Explore the components in a use case diagram Use hover to examine linked resources Learn how templates drive consistency for specifications Create a module documenting a use case specification Browse a Module used to document a use case specification Collaborate with team about changes and apply tag for filtering Embed a sketch to provide context regarding the user interface Project Status Lab 4

Tour of RRC & JKE Banking sample Leverage the Requirements Across the Lifecycle Conduct a Review Respond to Change Request Update the Business Process Refine the Use Case Diagram & Specification Change the User Interface Examine storyboards, sketches and parts Edit a storyboard and user interface part Illustrate requirement workflow in the storyboard Collaborate with team about changes and apply tag filtering Learn about inheritance and apply concepts to quickly refine UI Project Status Lab 5

13

Tour of RRC & JKE Banking sample Leverage the Requirements Across the Lifecycle Conduct a Review Respond to Change Request Update the Business Process Refine the Use Case Diagram & Specification Change the User Interface Create a review and learn about the types of reviews Learn the various roles in the review and assign roles to participants Participate in a review and learn phases in review Optional: Finalize the review Provide feedback in review Project Status Lab 6

Tour of RRC & JKE Banking sample Leverage the Requirements Across the Lifecycle Conduct a Review Respond to Change Request Update the Business Process Refine the Use Case Diagram & Specification Change the User Interface Filter requirements using Web 2.0 tag Change status in- line using multi- select “set attribute” Refine release collection to add new requirements Execute lifecycle traceability filter to view links to development & test Create new lifecycle links Project Status Lab 7

Tour of RRC & JKE Banking sample Leverage the Requirements Across the Lifecycle Conduct a Review Respond to Change Request Update the Business Process Refine the Use Case Diagram & Specification Change the User Interface Examine the contents of the user dashboard & how to customize it Tips for creating & executing filters Execution of filters to verify project status Report generation from view Execution of filters to verify coverage & gaps Project Status Lab 8

17

18 Acknowledgements and disclaimers The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM, Cube Views, Informix, Rational System z, AIX, CICS, DB2, developerWorks, Lotus, Lotus Workflow, Redbooks, Red Brick, Tivoli, WebSphere, ClearCase, DRDA, MQSeries, RequisitePro, Workplace, ClearQuest, Cloudscape, IMS, IMS/ESA, OmniFind, System I, System p Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. See Java Guidelines Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. Other company, product and service names may be trademarks or service marks of others.

19 © Copyright IBM Corporation All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.