Rational Tool Overview

1. Rational Tool Overview

2. Introduction • Requirements-Driven Software Development with Rational Analyst Studio. Tafadzwa Nzara Analysis & Design Consultant Eli Lilly & Company

3. Agenda • The Purpose of Requirements • Requirements-Driven Software Development • Company Information and Resources

4. The Benefits of a Requirements Driven Approach • Build better Software fulfill Customer and User Needs. • Understanding the business Context of your solutions. • Effectively gather users’ input. • Stay In touch with changing user needs. • Deliver Software on time and budget. • Protect requirements from unnecessary change • Effectively scope manage your project • Deliver quality products • Validate your software against requirements. • Implement what your customer expects

5. True Purpose of Requirements • The purpose of Requirements Management is to establish a common understanding between the customer and the software project team […] This agreement with the customer is the basis for planning and managing the project. (Capability Maturity Model) • Requirements Drive all software activities • Design • Requirements express the solution you will implement • Test • Requirements express the solution you will validate • User Documentation • User manual documents the solution expressed by the requirements. • Project Planning • Project schedule is linked to project scope (number of requirements) • What are the six best practices of software development?

7. Requirement-Driven Software Development Tools • A requirements management tool • A visual modeling tool • A change request management tool • A test management tool These tools together address the six best practices of software development.

8. Poll: Which of the following represents the biggest software challenge? • Understanding what the user wants? • Ensuring that developers know what they need to build? • Managing change? • Predicting when we will deliver?

9. Which of the following represents your biggest software challenge? Poll Results

10. Rational Solution 1 - RequisitePro • A requirements management tool • To capture and track requirements • To ensure requirement coverage • To measure impact of change • A visual modeling tool • A change request management tool • A test management tool

11. Rational RequisitePro A Team-based Requirements Management Tool • Track your requirements documents • Organize requirements • View requirements coverage • Visualize the impact of change • Web access to requirements (Requisite Web)

15. Rational Solution 2 – Rational Rose • A requirements management tool • A visual modeling tool • To increase software acceptance • To get agreement early on • To increase developers’ understanding of the requirements • A change request management tool • A test management tool

16. Rational Rose Leading Visual Modeling Tool • To increase software acceptance • Document business processes where software will be deployed • To get agreements early on • Express requirements visually – “The Big Picture” • Increase Developer understanding of requirements • Express requirements in use case design.

17. Increase Software Acceptance • Business modeling for software projects • To ensure your software fits upon deployment • Document your software business context • Business activities to be automated • Scope and Vision • Who will use your system • Actors • Set of services your software will need to provide to the user • Use Cases • Non-functional software requirements • Business Rules, performance requirements, etc

24. Rational Solution 3 – Rational ClearQuest • A requirements management tool • A visual modeling tool • A change request management tool • To minimize requirements change • To sort and prioritize requirements • To map user feedback to requirements • A test management tool

25. How Can you Manage Requirements Change Impact • Distinguish between change requests and requirements • Requirements are unambiguous, complete, non-conflicting, … • Change requests are free form requests, often incomplete, maybe conflicting and not agreed upon by the team • Establish a CCB* to formally accept/reject change • Triage change requests • Assess impact of change before accepting change. *CCB – Change Control Board

26. Rational ClearQuest Rational Change Request Management Tool • Formatted web form to collect all change requests • Simplifies the sorting and prioritization of change requests. • Links requirements to user feedback • Associate change requests to requirements • Same tool can be used for defect tracking

28. Rational Solution 4 – Rational TestManager • A requirements management tool • A visual modeling tool • A change request management tool • A test management tool • To build test cases from requirements • To ensure test coverage of requirements

29. Rational TestManager Comprehensive Test Management Tool • Test the right thing • Direct link to requirements, use cases and more • Ensure test coverage • Out-of-the-box test coverage reports

31. Requirements-Driven Software Development Tools • A requirements management tool – Requisite Pro • A visual modeling tool – Rational Rose • A change request management tool – ClearQuest • A test management tool – Test Manager

35. Rational Unified Process – The Six Best Practices • Develop iteratively • Manage requirements, • Model visually (UML), • Control changes, • Use Component architecture • Verify quality.

36. Where to Get More Information • www.rational.com