Rational Suite Tutorial

Transcription

1 Ratioal Suite Tutorial Product Versio Ratioal Suite Release Date April 2000 Part Number

2 IMPORTANT NOTICE Copyright Notice Copyright 1998, 1999, 2000 Ratioal Software Corporatio. All rights reserved. Trademarks Ratioal, the Ratioal logo, ClearCase, PureCoverage, PerformaceStudio, Purify, Quatify, Ratioal Rose, ad SoDA are trademarks or registered trademarks of Ratioal Software Corporatio i the Uited States ad i other coutries. All other ames are used for idetificatio purposes oly ad are trademarks or registered trademarks of their respective compaies. FLEXlm ad GLOBEtrotter are trademarks or registered trademarks of GLOBEtrotter Software, Ic. Licesee shall ot icorporate ay Globetrotter software (FLEXlm libraries ad utilities) ito ay product or applicatio the primary purpose of which is software licese maagemet. Microsoft, MS, ActiveX, BackOffice, Developer Studio, Visual Basic, Visual C++, Visual IterDev, Visual J++, Visual Studio, Wi32, Widows, ad Widows NT are trademarks or registered trademarks of Microsoft Corporatio. Ratioal Purify is licesed uder Su Microsystem s U.S. Pat. No 5,404,499. Oracle, Oracle7, ad Oracle 8 are trademarks or registered trademarks of Oracle Corporatio. Sybase ad SQL Aywhere are trademarks or registered trademarks of Sybase Corporatio. U.S. Govermet Rights Use, duplicatio, or disclosure by the U.S. Govermet is subject to restrictios set forth i the applicable Ratioal Licese Agreemet ad i DFARS (a) ad (a) (1995), DFARS (c)(1)(ii) (Oct 1988), FAR (a) 1995, FAR , or FAR , as applicable. Patet U.S. Patet Nos. 5,193,180 ad 5,335,344 ad 5,535,329 ad 5,835,701. Additioal patets pedig. Warraty Disclaimer This documet ad its associated software may be used as stated i the uderlyig licese agreemet, ad, except as explicitly stated otherwise i such licese agreemet, Ratioal Software Corporatio expressly disclaims all other warraties, express or implied, with respect to the media ad software product ad its documetatio, icludig without limitatio, the warraties of merchatability or fitess for a particular purpose or arisig from a course of dealig, usage or trade practice.

3 RATIONAL SUITE TUTORIAL Cotets Preface 1 Welcome to Ratioal Suite Priciples of Software Developmet Ratioal Suite Ca Help What s i Ratioal Suite? Tools that Uify Your Team Tools for Aalysts Tools for Developers Tools for Test Egieers Ratioal Suite Eterprise For More Iformatio About this Tutorial Prerequisites Determiig Which Ratioal Suite Tools Are Istalled Istallig the Tutorial Sample Applicatio ad Related Files Tip: Resettig the Tutorial Registerig the Repository Attachig the ClearQuest Database to the Repository About the Work You Will Do Tutorial Backgroud A Note about the Applicatio Orderig CDs Fiishig the Purchase Discoverig What to Build iii

4 How to Use this Tutorial What s Next Learig About the Ratioal Uified Process Audiece Gettig Your Bearigs What Is the Ratioal Uified Process? The Uified Process ad Ratioal Suite Learig the Mechaics The Process at a Glace Key Cocepts Explorig the Workflow Startig with Actors ad Use Cases Tool Metors: Implemetig the Process Usig Ratioal Tools Learig about Developig for the Web Summary For More Iformatio Cleaig Up What You Leared i this Uit What s Next Creatig Requiremets Audiece Gettig Your Bearigs Opeig the ClassicsCD Web Shop Project Why Worry About Requiremets? Where Do Requiremets Come From? Maagig Requiremets RequisitePro Startig with a Use Case Why Work with Use Cases? How Does it Work? How Does RequisitePro Hadle Requiremets? iv Ratioal Suite Tutorial

5 Cotiuig Use Case Work: Usig Rose Startig Rose Creatig a Use Case i Rose Associatig the Rose Model with the RequisitePro Project Creatig a New Requiremet Lookig at Requiremets i the Database Likig to Aother Requiremet Traceability Liks ad Suspect Liks Other Requiremet Types Whe Have You Fiished Gatherig Requiremets? Exteded Help Summary For More Iformatio Cleaig Up What You Leared i this Uit What s Next Test Plaig Audiece Gettig Your Bearigs Opeig the ClassicsCD Web Shop Project What Is Test Plaig? Risk Maagemet Test Plaig ad the Tutorial Workig with Test Requiremets Explorig Test Requiremets Desigig Tests Startig with the Use Case Creatig Test Cases Cotiuig with Test Plaig Risks ad Resources Types of Tests Schedulig Cotets v

6 Summary For More Iformatio Cleaig Up What You Leared i this Uit What s Next Modelig the Ehacemet Audiece Gettig Your Bearigs What Is Visual Modelig? Visual Modelig ad the Tutorial Workig with a Sequece Diagram Opeig a Sequece Diagram Addig Messages for the Ehacemet Publishig Part of the Model to the Web After Completig the Sequece Diagram Refiig the Objects Implemetig the Code Modelig Data Summary For More Iformatio Cleaig Up What You Leared i this Uit What s Next Creatig a Use Case Report Audiece Gettig Your Bearigs What Is SoDA? Why Create a Use Case Report? Creatig the Use Case Report Workig with SoDA Templates vi Ratioal Suite Tutorial

7 Summary For More Iformatio Cleaig Up What You Leared i this Uit What s Next Reliability Testig Audiece Reliability Testig Tools What Is TestFactory? Overview of Process Istrumetig the Applicatio Mappig the Applicatio Ruig a Pilot Test Suites: Puttig It All Together Usig TestFactory with Ratioal Robot Additioal Testig Tools Ratioal Purify Ratioal PureCoverage Ratioal Quatify Summary For More Iformatio What You Leared i this Uit What s Next Fuctioal Testig Audiece Gettig Your Bearigs What Is Fuctioal Testig? Start with Requiremets Creatig a Script Determiig Which Script to Work O Plaig the Script Cotets vii

8 Recordig the Script Scripts ad Modularity Startig ad Preparig Robot Is Iteret Explorer Istalled? Gettig to a Startig Poit Startig to Record the Show Ship Date Script Creatig a Verificatio Poit Fiishig the Recordig Sessio Addig the Show Ship Date Script to a Shell Script Playig Back the Script O a New Build Aalyzig the Results Hadlig a Itetioal Chage Hadlig a Real Error Reportig the Error Summary For More Iformatio Cleaig Up What You Leared i this Uit What s Next Plaig the Next Iteratio Audiece Gettig Your Bearigs Assessig the State of your Project Showig the Workload Assigig a Ehacemet Request Other Plaig Activities What Will Happe i the Next Iteratio? Cofiguratio Maagemet viii Ratioal Suite Tutorial

9 Summary For More Iformatio Cleaig Up What You Leared i this Uit What You Leared i this Tutorial What s Next Glossary Idex Cotets ix

10 x Ratioal Suite Tutorial

11 RATIONAL SUITE TUTORIAL Preface This tutorial teaches you the basics of usig Ratioal Suite to pla, desig, implemet, ad test applicatios. It also poits you to additioal iformatio so that you ca lear more o your ow. Ratioal Suite delivers a comprehesive set of itegrated tools that embody software egieerig best practices ad spa the etire software developmet life cycle. Ratioal Suite s uparalleled level of itegratio improves commuicatio both withi teams ad across team boudaries, reducig developmet time ad improvig software quality. Audiece Read this tutorial if you: Are a member of a developmet team a aalyst, developer, test egieer, or maager Have experiece with some aspect of Widows applicatio developmet You do ot eed prior experiece with ay Ratioal tools to use this tutorial. Other Resources Olie Help is available for Ratioal Suite. From a Suite tool, select a optio from the Help meu. All mauals are available olie, either i HTML or PDF format. The olie mauals are o the Ratioal Solutios for Widows Olie Documetatio CD. If you istall Ratioal Suite DevelopmetStudio RealTime Editio, PDF versios of the mauals for Rose RealTime are istalled i %ROSERT_HOME%\help. For more iformatio o traiig opportuities, see the Ratioal Uiversity Web site: 11

12 Ratioal Suite Documetatio Roadmap 12 Ratioal Suite Tutorial

13 Cotactig Ratioal Techical Publicatios To sed feedback about documetatio for Ratioal products, please sed to our techical publicatios departmet at Cotactig Ratioal Techical Support If you have questios about istallig, usig, or maitaiig this product, cotact Ratioal Techical Support as follows: Ratioal Techical Support Iformatio Locatio Cotact Iformatio Notes U.S. ad Caada Europe +31 (0) Whe sedig Specify the product ame i the subject lie, for example, Ratioal Suite. For existig issues, iclude your case ID i the subject lie. Asia Pacific [email protected] World Wide Web Click the Techical Support lik. Preface 13

14 14 Ratioal Suite Tutorial

15 RATIONAL SUITE TUTORIAL Welcome to Ratioal Suite Does your orgaizatio focus o developig ad deliverig software? If so, thik about your last project. Was it o time? Withi its budget? Was commuicatio amog team members clear ad timely? Did your team maitai cosistecy throughout the project as it defied requiremets, developed desigs, ad wrote code? Was your build process repeatable? Did your software meet requiremets, satisfy users, ad perform reliably? May project teams experiece problems i these areas. I fact, may software projects fiish late (or ot at all), ad the result ofte does t match the requiremets. May projects ucover serious desig flaws late i the process. Defects are ofte foud after the software ships, istead of durig developmet. How ca you make your ext project more successful? Priciples of Software Developmet Ratioal Software Corporatio, the e-developmet compay, helps orgaizatios develop ad deploy software for e-busiess, e-ifrastructure, ad e-devices through a combiatio of tools, services ad software egieerig best practices. Ratioal's e-developmet solutio helps orgaizatios overcome the e-software paradox by acceleratig time to market while improvig quality. Ratioal helps you icrease your productivity ad effectiveess by focusig o these software developmet priciples: 15

16 Develop software iteratively. Iterative developmet meas aalyzig, desigig, ad implemetig icremetal subsets of the system over the course of a project. Early i a project, ew executable files reduce project risk. As the project proceeds, later executable files are more robust or cotai more features tha previous executable files. Each ew iteratio moves you closer to the goal of deliverig a product that meets its requiremets. Developig iteratively helps make your project more predictable, lets you collect feedback early, helps you idetify ad elimiate risks early i the project, ad makes testig cotiuous throughout the project lifecycle. Maage requiremets. A requiremet is oe criterio for your project s success. Your project s requiremets aswer questios such as What do customers wat? ad What ew features must we absolutely ship i the ext versio? Most project teams work with requiremets. O smaller, less formal projects, requiremets might be kept i text files or messages. Other projects may use more formal ways of recordig ad maitaiig requiremets. Whe you maage requiremets, you ca uderstad how chaged requiremets affect your project. You ca effectively commuicate requiremets to all team members ad to stake holders. Effective requiremets maagemet helps your orgaizatio esure that its products meet their stated goals. Use compoet-based architectures. Software architecture is the fudametal framework o which you costruct a software project. Whe you defie a architecture, you desig a system s structural elemets ad their behavior, ad you decide how these elemets fit ito progressively larger subsystems. A compoet is a o-trivial, idepedet, ad replaceable part of a system that combies data ad fuctios to fulfill a clear purpose. You ca build compoets from scratch, reuse compoets you previously built, or eve purchase compoets from other compaies. Desigig a compoet-based architecture eables you to improve your project s predictability ad helps ehace maitaiability ad extesibility. 16 Ratioal Suite Tutorial

17 Model software visually. Visual modelig helps you maage software complexity. At its simplest, visual modelig meas creatig a graphical blueprit of your system s architecture. From this visual represetatio of your architecture, you ca quickly detect problems such as icosistecies ad lack of modularity. With a visual model, you have a powerful ad uambiguous commuicatio mechaism that your whole team ca use. Visual models help you improve commuicatios across your etire team. They help you detect icosistecies amog requiremets, desigs, ad implemetatios. They also help you evaluate your system s architecture, esurig soud desig. Verify your software s quality. Verifyig software meas testig what s bee built agaist writte requiremets. This icludes testig that the system delivers required fuctioality ad verifyig reliability ad performace. A importat beefit of iterative developmet is that you ca begi testig early i the developmet process. Testig every iteratio allows you to discover problems early i the developmet cycle ad to expose icosistecies amog requiremets, desigs, ad implemetatios. Cotrol chages to your software. It is importat to maage chages to requiremets ad code i a trackable, repeatable, predictable way. Chage maagemet icludes trackig ad hadlig chage requests; facilitatig parallel work; ad creatig processes for reliably reproducig software builds. Maagig chages to your project facilitates clear commuicatio. It helps you cotrol chage propagatio, ad defie ad repeat developmet processes. Welcome to Ratioal Suite 17

18 Ratioal Suite Ca Help To put these priciples to work, Ratioal Software offers Ratioal Suite, a family of market-leadig software developmet tools supported by Ratioal Uified Process. These tools facilitate work throughout a project s lifecycle. Ratioal Suite packages the tools ad the process ito several editios, each of which is tailored for specific practitioers o your developmet team aalysts, developers, ad testers. Aloe, these tools have helped orgaizatios aroud the world successfully create software. Itegrated together, they: Uify your team by ehacig commuicatio. Optimize idividual productivity by providig marketleadig developmet tools packaged i Suite editios. Each editio is tailored for oe of the major roles o your team. Simplify adoptio by providig a comprehesive set of itegrated tools that have simplified istallatio, licesig, ad user support plas. What s i Ratioal Suite? Ratioal Suite provides sets of tools tailored for every member of your team. Each Suite editio cotais team-uifyig tools ad tools desiged for a specific practitioer. The followig sectios describe these tools ad the Suite editios. Tools that Uify Your Team Each editio of Ratioal Suite cotais the followig tools to facilitate team commuicatio ad productivity: Ratioal Uified Process. A olie collectio of software best practices that guide your team through software developmet. Provides guidelies, templates, ad Tool Metors (istructios for applyig the guidelies to specific Ratioal tools) for each phase of the developmet lifecycle. Ratioal RequisitePro. Helps you orgaize, prioritize, track, ad cotrol chagig project requiremets. Ratioal ClearQuest. Maages chage activity associated with software developmet, icludig ehacemet requests, defect reports, ad documetatio modificatios. 18 Ratioal Suite Tutorial

19 Ratioal SoDA. Automatically geerates project documets by extractig iformatio from files you produce durig project developmet, icludig source code ad files produced by Ratioal tools. Formats the iformatio accordig to predefied templates. SoDA is itegrated with Microsoft Word for ease of use ad easy customizatio. Tools for Aalysts A aalyst s role is to: Represet the user s eeds to the developmet orgaizatio Determie what the system does Specify ad maage requiremets Ratioal Suite AalystStudio Ratioal Suite AalystStudio, the Ratioal Suite editio desiged for aalysts, cotais the team-uifyig tools (Ratioal Uified Process, RequisitePro, ClearQuest, ad SoDA) ad: Ratioal Rose (Modeler Editio). Eables visual modelig of architectures ad compoets usig the idustry-stadard Uified Modelig Laguage (UML). The UML is a laguage for specifyig, visualizig, costructig, ad documetig software systems. Tools for Developers A developer s role is to: Determie how the system works Defie architecture Create, modify, maage, ad test code Ratioal Suite provides two editios for developers: Ratioal Suite DevelopmetStudio ad Ratioal Suite DevelopmetStudio RealTime Editio. Welcome to Ratioal Suite 19

20 Ratioal Suite DevelopmetStudio Ratioal Suite DevelopmetStudio, the Ratioal Suite editio desiged for system developers ad desigers, cotais the team-uifyig tools (Ratioal Uified Process, RequisitePro, ClearQuest, ad SoDA) ad: Ratioal Rose (Eterprise Editio). Eables visual modelig of architectures ad compoets usig the idustry-stadard Uified Modelig Laguage (UML). Automatically implemets the framework of your code i Java, C++, Microsoft Visual Basic, ad other popular laguages. Because it is tightly itegrated with Microsoft VisualStudio, its roud-trip egieerig feature lets you automate the process of maitaiig cosistecy betwee a model ad its implemetatio. Ratioal Purify. Pipoits ru-time errors ad memory leaks i Visual C++ applicatio code. Ratioal PureCoverage. Idetifies which parts of your Java, Visual C++, or Visual Basic program have ad have ot bee exercised. Exposes testig gaps so you ca prevet utested applicatio code from reachig your users. Ratioal Quatify. Profiles your Java, Visual C++, or Visual Basic applicatio to help you idetify performace bottleecks i your code. Ratioal Suite DevelopmetStudio RealTime Editio Ratioal Suite DevelopmetStudio RealTime Editio is the Ratioal Suite editio desiged for practitioers who focus o real-time ad embedded developmet. This Suite editio cotais all the tools i Ratioal Suite DevelopmetStudio but replaces Ratioal Rose with Ratioal Rose RealTime. Ratioal Rose RealTime. Delivers a powerful combiatio of otatio, processes, ad tools to meet the challeges of real-time developmet. Usig Rose RealTime, you ca: Create executable models, allowig you to compile ad observe simulatios of your UML desigs o the host or target platform. The result is that you ca refie your desig early ad you ca cotiually verify quality. 20 Ratioal Suite Tutorial

21 Geerate complete, deployable executables i C or C++ directly from UML desig models targeted to real-time operatig systems. Geeratig these applicatios elimiates the eed for maual traslatio ad avoids costly desig iterpretatio errors. To lear more about Rose RealTime, see the olie tutorials available from the Rose RealTime Help meu. Tools for Test Egieers A test egieer s role is to: Esure that software meets all requiremets Create, maage, ad execute tests Report results ad verify fixes Ratioal Suite provides two editios for test egieers: Ratioal Suite TestStudio ad Ratioal Suite PerformaceStudio. Ratioal Suite TestStudio Ratioal Suite TestStudio, the Ratioal Suite editio desiged for test egieers, cotais the team-uifyig tools (Ratioal Uified Process, RequisitePro, ClearQuest, ad SoDA) ad: Ratioal Robot. Facilitates fuctioal testig by automatig record ad playback of test scripts. Allows you to write, orgaize, ad ru test suites, ad to capture ad aalyze the results. Ratioal TestFactory. Automates testig by combiig automatic test geeratio with source-code coverage aalysis. Tests a etire applicatio, icludig all GUI features ad all lies of source code. Ratioal Purify. Pipoits ru-time errors ad memory leaks i Visual C++ applicatio code. Ratioal PureCoverage. Idetifies which parts of your Java, Visual C++, or Visual Basic program have ad have ot bee exercised. Exposes testig gaps so you ca prevet utested applicatio code from reachig your users. Ratioal Quatify. Profiles your Java, Visual C++, or Visual Basic applicatio to help you idetify performace bottleecks i your code. Welcome to Ratioal Suite 21

22 Ratioal Suite PerformaceStudio Ratioal Suite PerformaceStudio is the Ratioal Suite editio desiged for test egieers who develop ad ru performace tests, ad for architects who wat to test their architectural desig early i the developmet process. PerformaceStudio cotais the team-uifyig tools (Ratioal Uified Process, RequisitePro, ClearQuest, ad SoDA), the tools i TestStudio (Robot, TestFactory, Purify, PureCoverage, ad Quatify) ad: Ratioal LoadTest. Helps you create real-world, multi-user performace tests for testig the performace ad reliability of e-busiess, multi-tier, ad database applicatios. Also helps you execute fuctioal tests faster by distributig those tests to multiple computers ad coordiatig the results. Ratioal PerformaceArchitect. Helps you test the performace of COM ad DCOM applicatios. With Ratioal PerformaceArchitect, you create Rose sequece or collaboratio diagrams, geerate virtual user scripts from your diagrams, ad the use PerformaceStudio to edit the script ad ru the performace tests. Ratioal Rose (Eterprise Editio). Eables visual modelig of architectures ad compoets usig the idustry-stadard Uified Modelig Laguage (UML). Automatically implemets the framework of your code i Java, C++, Microsoft Visual Basic, ad other popular laguages. Because it is tightly itegrated with Microsoft VisualStudio, its roud-trip egieerig feature lets you automate the process of maitaiig cosistecy betwee a model ad its implemetatio. To lear more about PerformaceStudio, see Gettig Started with Ratioal Suite PerformaceStudio. 22 Ratioal Suite Tutorial

23 For More Iformatio Ratioal Suite Eterprise O some projects, team members may perform may types of tasks. For example, o smaller projects, team members might perform more tha oe role. O larger projects, team members might move from task to task. It may therefore make sese to equip each team member of a orgaizatio with a full complemet of tools. Ratioal Suite Eterprise cotais all the tools i AalystStudio, DevelopmetStudio, ad TestStudio. So it ca accommodate the eeds of all members of your team. For more iformatio about Ratioal Suite ad the priciples of software developmet, see Itroducig Ratioal Suite. For more iformatio about the Uified Modelig Laguage, visit the UML Resource Ceter at: This Web site cotais UML iformatio, tips about gettig started with UML, ad a bibliography for further readig. Welcome to Ratioal Suite 23

24 24 Ratioal Suite Tutorial

25 RATIONAL SUITE TUTORIAL About this Tutorial This tutorial teaches you the basics of usig Ratioal Suite to pla, desig, implemet, ad test applicatios. It also poits you to additioal iformatio so that you ca lear more o your ow. Prerequisites Before cotiuig, make sure you have: A editio of Ratioal Suite istalled o your computer A valid licese for the software you ve istalled Determiig Which Ratioal Suite Tools Are Istalled Table 1, Ratioal Suite Tools, lists the Suite tools you will use i this tutorial. Table 1: Ratioal Suite Tools q Ratioal ClearQuest q Ratioal PureCoverage q Ratioal Purify q Ratioal Quatify q Ratioal RequisitePro q Ratioal Robot q Ratioal Rose q Ratioal SoDA for Word q Ratioal TestFactory q Ratioal Uified Process Exercise You may wat to mark this page so you ca refer back to it from later chapters. Place check marks i the table ext to the tools that are istalled o your system. To determie whether a tool is istalled, click the Start butto ad see whether the tool s ame is i the Programs > Ratioal Suite meu. 25

26 Some of these tools may ot be istalled o your computer. A tool may be excluded because of the Suite editio you bought. Someoe i your orgaizatio may have chose ot to istall other tools. Istallig the Tutorial Sample Applicatio ad Related Files Before you try the tutorial exercises, you eed to istall ad set up the files you will use. (The files are already o your system.) To istall the files: 1 Make sure you have 30 MB of free disk space. If you are usig Widows NT, make sure you have Admiistrator privileges so that you ca complete the setup successfully. 2 From the Start meu, choose Programs > Ratioal Suite > Ratioal Suite Tutorial > Setup. 3 Follow the istructios that appear o your scree. The files are istalled ito the directory c:\program Files\Ratioal\Classics Demo Tip: Resettig the Tutorial If you decide to restart the tutorial, reset the sample applicatio ad related files by ruig the istallatio procedure. For example, you might restart the tutorial to review material you ve already worked o. Registerig the Repository You use the Ratioal Admiistrator to group a set of projects associated with Ratioal Suite (for example, a RequisitePro database ad a Rose model). The Ratioal Suite termiology for such a group is a repository project. To register the repository project: 1 Start Ratioal Admiistrator by clickig Start ad choosig Programs > Ratioal Suite > Ratioal Admiistrator. 2 I the left pae of the Ratioal Admiistrator, right-click Repositories. From the shortcut meu, choose Register Existig Repository. 26 Ratioal Suite Tutorial

27 Registerig the Repository 3 I the Register Existig Repository dialog box, browse to c:\program Files\Ratioal\Classics Demo\ClassicsRepo ad click OK. The Admiistrator adds the path uder the Repositories headig. 4 I the left pae of the Admiistrator, right-click the path you just added. From the shortcut meu, choose Coect. Coectig to the Repository 5 I the Ratioal Repository Logi dialog box, use the default values (User ID is admi; Password is blak). Click OK. You have ow registered ad coected to the repository you will work with durig the tutorial. Keep the Ratioal Admiistrator ope for the ext task. Attachig the ClearQuest Database to the Repository I this tutorial, you work with a ClearQuest database that cotais the tutorial project s chage requests (defects ad ehacemet requests). Attach this database to the repository you just registered: 1 Check whether Ratioal ClearQuest is istalled o your system by referrig to Table 1, Ratioal Suite Tools, o page 25. If it is istalled, the you ca proceed with this sectio s istructios. If it is ot istalled, you caot use ClearQuest durig this tutorial. 2 From the Ratioal Admiistrator meu, choose Tools > Ratioal ClearQuest Maiteace Tool to display a ClearQuest wizard that helps with setup tasks. About this Tutorial 27

28 3 O the wizard s first page, uder Setup schema repository, use the default optio, Coect to Existig schema repository. Click Next. 4 O the Coect to A Existig Schema Repository page: Make sure the value i the Vedor field is MS_ACCESS. I the Physical Database Name box, browse to c:\program Files\Ratioal\Classics Demo\ClassicsRepo\ ChageRequests\CQMaster.MDB Click Next. 5 O the Save Curret Settig for Later Use page, make sure that Save currets settigs as Default is cleared. Click Fiish. 6 Review messages to cofirm that you have coected the ClearQuest database to the repository. Click Doe. 7 Quit the Ratioal Admiistrator. About the Work You Will Do I this tutorial, you implemet a small part of a large developmet project. Usig Ratioal tools ad process, you develop requiremets, create a visual model, code, ad test. This book guides you to the sectios that are most appropriate for you ad your role i your ow orgaizatio. Tutorial Backgroud I this tutorial, you work for Classics Ic., a growig chai of retail stores that sells classical music CDs. Your orgaizatio is workig o Versio 2 of ClassicsCD.com, a olie store where you ca buy classical music CDs. Your team uses Ratioal Suite. Durig the tutorial, you add oe ew feature to ClassicsCD.com. 28 Ratioal Suite Tutorial

29 A Note about the Applicatio I a real olie store, Web pages would load dyamically, based o iformatio stored i databases. The applicatio you work with durig the tutorial cotais static Web pages. These pages do ot chage i respose to user iput. I a typical project, you would create a prototype usig static pages ad later chage to usig dyamic pages. Orderig CDs Start by becomig familiar with ClassicsCD.com Exercise Start Classics ad order two CDs: 1 Start the applicatio: click Start ad choose Programs > Ratioal Suite > Ratioal Suite Tutorial > Classics CD Build 0. Your Web browser displays the first page of ClassicsCD.com. 2 O the home page, click Explore our storefrot. 3 O the storefrot page, click Catalog. 4 Scroll to the Mozart sectio (composers are listed alphabetically) ad click Mozart: Symphoie Nr. 34 to view details of that album. 5 O the album s page, click the shoppig cart to add the album to your order. The catalog page reappears. 6 At the top of the page, click the shoppig cart ext to Bach: Bradeburg Cocertos Fiishig the Purchase Exercise Now complete the purchase ad provide feedback to Classics Ic. 1 I the left colum of the page, click Shoppig Cart (you may eed to scroll to see it). 2 O the left colum of the Shoppig Cart page, click Cashier. Before you ca complete the order, you eed to log i. 3 I both the CustomerID ad Password fields, type jmoore ad click Submit. About this Tutorial 29

30 Notice that the Cashier page summarizes your order but does ot tell you whe the order will ship. 4 Scroll to the bottom of the page ad click Place Order. 5 Provide feedback to the compay by clickig Your Feedback at the bottom of the page. 6 O the feedback form, uder Dear ClassicsCD.com, type Whe I place a order, I wat to kow whe my order will ship. Uder My , type [email protected]. Click Sed. 7 Whe you have fiished, quit ClassicsCD.com. Discoverig What to Build I this tutorial, you will implemet the ehacemet you requested. Someoe i marketig received your feedback ad etered it ito ClearQuest, the tool that maages chage requests. I Chapter 10, Plaig the Next Iteratio, you work with ClearQuest. 30 Ratioal Suite Tutorial

31 How to Use this Tutorial You ca work through the etire tutorial to uderstad how Ratioal Suite fits ito your developmet eviromet. Or you ca work through oly those uits most appropriate to your role. Table 2, Tutorial Roadmap, presets our recommedatios. Table 2: Tutorial Roadmap Role Your Mai Tasks Recommeded Tutorial Uits Aalyst Represet the user Determie what the system does Specify ad maage requiremets Welcome to Ratioal Suite About this Tutorial Learig About the Ratioal Uified Process Creatig Requiremets Creatig a Use Case Report Plaig the Next Iteratio Developer Determie how the system works Defie architecture Create, modify, ad maage code Welcome to Ratioal Suite About this Tutorial Learig About the Ratioal Uified Process Creatig Requiremets Modelig the Ehacemet Creatig a Use Case Report Reliability Testig Plaig the Next Iteratio Test Egieer Esure requiremets are met Create, maage, ad execute tests Report results ad verify fixes Welcome to Ratioal Suite About this Tutorial Learig About the Ratioal Uified Process Creatig Requiremets Test Plaig Creatig a Use Case Report Reliability Testig Fuctioal Testig Plaig the Next Iteratio What s Next The ext uit itroduces you to the Ratioal Uified Process. You use this process to lear about work you will do i later uits. Let s get started! About this Tutorial 31

32 32 Ratioal Suite Tutorial

33 RATIONAL SUITE TUTORIAL Learig About the Ratioal Uified Process This uit itroduces you to the Ratioal Uified Process. I this uit, you familiarize yourself with the Uified Process ad read guidelies for the work you will perform i the ext uit. Audiece This uit applies to all members of a software developmet team. Gettig Your Bearigs I this uit, you use the Ratioal Uified Process. Refer to the tool chart you filled out (Table 1, Ratioal Suite Tools, o page 25) to determie whether the Uified Process is istalled o your system. If the Uified Process is ot istalled, you ca still beefit from readig this uit, but you will ot be able to perform the exercises. If the Uified Process is istalled, start it ow by clickig the Start butto ad the choosig Programs > Ratioal Suite > Ratioal Uified Process. What Is the Ratioal Uified Process? The Ratioal Uified Process is a software egieerig process that helps you: Produce high-quality software Meet the eeds of your ed users Work withi a predictable schedule ad budget The Uified Process serves as a persoal ad team-cetered guide through best practices for cotrolled, iterative software developmet. May orgaizatios worldwide have successfully used it for both small- ad large-scale developmet efforts. 33

34 Learig the Mechaics The Uified Process is implemeted as a olie guide ad kowledge base, which you view with a Web browser. The Uified Process ad Ratioal Suite The Ratioal Uified Process ca help you ad your team work more effectively. We recommed that you adopt all or part of it to support your developmet efforts. You ca, of course, successfully use Ratioal Suite without adoptig ay of the process. (You ca also use Ratioal Uified Process with projects that do ot use Ratioal Suite or its compoet tools.) Eve if you do ot follow the Uified Process, you ca use it as a source of iformatio about software egieerig. For example, it cotais topics to help you better uderstad Uified Modelig Laguage (UML) cocepts. This tutorial follows Uified Process guidelies. The Uified Process guides you through the full software developmet lifecycle: project maagemet, busiess modelig, requiremets maagemet, aalysis ad desig, implemetatio, testig, deploymet, cofiguratio maagemet, ad eviromet maagemet. Exercise From the Gettig Started widow, you ca avigate to pages cotaiig tips about the mechaics of usig the Uified Process. You ca also fid pages that provide startig poits for learig about the process itself. 1 O the Gettig Started widow, click Browsig the Process. Your Web browser displays the page, Navigatio Tools, which cotais a layout of the Uified Process. 2 Familiarize yourself with the user iterface by movig your mouse over the picture ad readig the tool tips that are displayed. 3 Optioally, retur to the Gettig Started widow ad read about other aspects of the Uified Process. 4 Leave your Web browser ope. 34 Ratioal Suite Tutorial

35 The Process at a Glace The first page of the Uified Process presets a rich visual represetatio that ca help you better uderstad the Uified Process. Exercise Retur to the first page: 1 I your Web browser, click Overview i the upper left corer of the tree browser. Returig to the Overview Page The overview of the Uified Process appears. This diagram represets empirical data collected by Ratioal Software. It shows that software developmet is best performed i a series of iteratios. Ratioal Uified Process Overview Learig About the Ratioal Uified Process 35

36 Over time, your software project will require differet types of focus ad resources. Notice, for example, that most of the work associated with requiremets happes early i the developmet cycle, but cotiues throughout a project. Testig, however, ca start early i the project, but typically becomes most itese at the ed of costructio. Key Cocepts The Ratioal Uified Process provides a quick summary of its most importat compoets. Exercise Read about the key cocepts of the Uified Process. 1 I the tree browser, expad Overview by clickig the + to its left. 2 Uder Overview, click Key Cocepts. (From ow o, we ll abbreviate these two steps as follows: Navigate to Overview > Key Cocepts. ) A ew Web page appears. The diagram at the top of the page shows the relatioships amog Ratioal Uified Process cocepts. 3 Uder the diagram, scroll to the first sectio, Software Egieerig Process, ad read it for a quick summary of the Uified Process. 4 Cotiue readig to lear about other key cocepts i the Process. To summarize, the Ratioal Uified Process defies the followig importat cocepts: A worker defies the behavior ad resposibilities of a idividual or a team of idividuals. Oe perso may act as may workers over the course of a project. A worker is resposible for a set of artifacts. A artifact is somethig a worker produces as the result of performig a activity. I the Uified Process, the artifacts produced i oe activity are ofte used as iput ito other activities. A artifact ca be small or large, simple or complex, formal or iformal. Examples of artifacts are: a test pla, a visio documet, a model of a system s architecture, a script that automates builds, or applicatio code. A activity is a uit of work that a worker performs. It is a set of ordered steps, like a recipe, for creatig a artifact. 36 Ratioal Suite Tutorial

37 Relatioship betwee a Worker, its Activities, ad Artifacts A workflow is the sequece of activities that workers perform toward a commo goal. The followig diagram shows a portio of the Requiremets workflow. Excerpt of Requiremets Workflow A workflow diagram serves as a high-level map for a set of related activities. The arrows betwee activities represet the typical flow of order betwee activities. You do ot have to adhere to the prescribed path. You ca always jump to activities that are ot coected by arrows. You ca also repeat a activity wheever you eed to (for example, if more iformatio becomes available). Learig About the Ratioal Uified Process 37

38 Explorig the Workflow Exercise Display the workflow diagram for Requiremets: 1 I the tree browser, avigate to Core Workflows > Requiremets to display the Requiremets workflow diagram. Durig this tutorial, you work o refiig the existig applicatio, ClassicsCD.com. Ratioal Uified Process provides guidace o how to ehace a existig system. 2 O the diagram, scroll to the bottom of the diagram ad click Refie the System Defiitio to display workflow details. The workflow detail shows the workers ivolved, the artifacts used as iput, the resultig artifacts, ad the activities that make up this part of the workflow. For more iformatio about ay of these elemets, click i that area of the diagram. Workflow Detail: Refie the System Defiitio (excerpt) 38 Ratioal Suite Tutorial

39 Startig with Actors ad Use Cases Whe you desig or ehace a system, the Uified Process recommeds that members of your team start by agreeig o the system s high-level behavior. To do so, you idetify actors ad use cases. Exercise Actors are the etities that iteract with your system. A actor is usually a perso (for example, a ed-user or admiistrator). It ca also be a exteral hardware or software system, for example, a cash register or warehouse system. Use cases describe how a actor uses ad iteracts with the system. More formally, a use case describes what services a system provides to a certai actor. You defie a use case by describig a complete sequece of actios that yields observable results of value to a actor. Use cases are a key cocept i the Uified Process. They ehace commuicatio across your team ad help you commuicate clearly with your users. Lear more about workig with use cases. 1 O the Refie the System Defiitio workflow, click Detail a Use Case. The Uified Process displays a page describig how to write a use case. It icludes details about the artifacts that you ll eed to get started ad the artifacts that result from the activity. It the provides a step-by-step descriptio of the activity. 2 Say you wat to lear more about use cases, ot just about how to write them. I the Resultig Artifacts sectio ear the top of the page, click Use Cases, completely described. This ew page provides a good overview of use cases, icludig a descriptio of how they re used, a outlie, ad resposible parties. Learig About the Ratioal Uified Process 39

40 Near the top of the page, there s a lik to a use case template. We recommed that you use this template, or aother template desiged by your group, to esure cosistecy ad completeess. This makes it easy for all stakeholders to locate ad uderstad importat project iformatio. 3 Click your browser s Back butto to retur to the Detail a Use Case page. 4 At this poit, you might wat to uderstad where you are i the Uified Process hierarchy. I the mai widow, click Where am I. The tree browser updates itself to show your curret locatio Workers ad Activities > Aalysts > Use-Case Specifier > Detail a Use Case. Tool Metors: Implemetig the Process Usig Ratioal Tools The Uified Process provides guidelies for all phases of software developmet. This sectio shows how the Uified Process uses Tool Metors to provide step-by-step istructios for implemetig Uified Process practices with Ratioal tools. To illustrate, we show you the istructios for the work we will do i the ext uit: defiig use cases. Exercise Read a Tool Metor to see how the Uified Process itegrates with Ratioal tools. 1 I the Uified Process, o the Detail a Use Case page, fid the Tool Metors sectio i the table ear the top of the page. 2 Click Usig Ratioal RequisitePro to Detail a Use Case. The Tool Metor starts with a statemet of purpose ad a overview, followed by a series of detailed steps. 3 I the overview, scroll to ad click Step 3, Mark requiremets i the Detailed Use-Case Specificatio. Sca through the istructios; you will perform a subset of these steps i the ext uit. 40 Ratioal Suite Tutorial

41 Learig about Developig for the Web The Ratioal Uified Process provides guidace for performig certai kids of work, icludig the kid of work you will do with ClassicsCD.com. Exercise Read about developig for the Web. 1 I the Uified Process, avigate to Overview > Roadmaps > Developig e-busiess Solutios. 2 Sca the guidelies to lear more about each phase of the developmet process. Summary For More Iformatio To lear more about the Ratioal Uified Process, read the topics o the Gettig Started page. (To retur to the Gettig Started page, click Gettig Started o ay Uified Process page.) Cleaig Up Whe you have fiished usig the Ratioal Uified Process, close it ad the Gettig Started widow. What You Leared i this Uit I this uit, you leared: The Ratioal Uified Process cotais best practices for software developmet. I Ratioal Suite, the Uified Process is recommeded but optioal. A workflow describes a set of related activities focused o meetig a goal. For each activity, a worker uses artifacts created i previous activities ad produces other artifacts. Early i the requiremets phase, you defie actors (users ad exteral systems that iteract with your system) ad use cases (services that the system provides to actors). Tool Metors provide explicit istructios for performig a Uified Process activity usig the appropriate Ratioal tool. Learig About the Ratioal Uified Process 41

42 What s Next I the ext uit, you work o the use case for the ehacemet request to ClassicsCD.com, Arrage Shipmet. 42 Ratioal Suite Tutorial

43 RATIONAL SUITE TUTORIAL Creatig Requiremets I this uit, you use Ratioal Rose ad RequisitePro to create a use case for the ehacemet you are implemetig. Audiece Gettig Your Bearigs This uit applies most directly to aalysts, but is relevat for all team members. I this uit, you use RequisitePro ad Rose. Refer to the tool chart you filled out (Table 1, Ratioal Suite Tools, o page 25) to determie whether RequisitePro ad Rose are istalled o your system. If they are ot istalled, you ca still beefit from readig this uit, but you will ot be able to perform the exercises. If they are istalled, start RequisitePro ow as follows (you ope Rose later i this uit): Click the Start butto ad choose Programs > Ratioal Suite > Ratioal RequisitePro. The RequisitePro Tool Palette ad Let s Go RequisitePro appear. Click Close o the Let s Go RequisitePro widow. The RequisitePro Tool Palette 43

44 Opeig the ClassicsCD Web Shop Project 1 O the RequisitePro Tool Palette, click Project > Ope. 2 I the Select a Project area, click Add. 3 I the Add Project dialog box, avigate to c:\program Files\Ratioal\Classics Demo\ClassicsRepo\ Project\ClassicsCDW\requisite\Requisite.RQS 4 Click Ope. The dialog box ow lists the ClassicsCD Web Shop project. The ext time you start RequisitePro, the project will be i the list ad you will ot have to add it agai. 5 Select ClassicsCD Web Shop ad click OK. 6 If you see the Project Logo dialog box, choose or type Pat ad click OK. The RequisitePro Tool Palette displays messages about its progress. Oce the project opes, the Tool Palette s status bar displays the message Ready. You are ow ready to work with the project. Why Worry About Requiremets? Oe defiitio of project success is that the product you deliver meets its requiremets. The formal defiitio of a requiremet is a coditio or capability to which the system must coform. More iformally, a requiremet describes a feature or behavior that a system must have. Where Do Requiremets Come From? As a aalyst, your job starts with gatherig the eeds of everyoe who has a iterest i your project your stakeholders. To gather eeds, you iterview users ad other stakeholders, read ehacemet requests, ad work with project team members. You ext determie which eeds should become project requiremets. 44 Ratioal Suite Tutorial

45 Maagig Requiremets Maagig requiremets is a systematic approach to: Fidig, documetig, orgaizig, ad trackig requiremets. Establishig ad maitaiig agreemet betwee the customer ad the project team o the system s chagig requiremets. Requiremets maagemet is challegig because requiremets chage throughout a project. For example, users may chage their mids about essetial features, or they may ot have articulated their wishes clearly i the first place. Competitors may release ew versios of their software ad you must respod by chagig project plas midstream. Chagig laws may affect your software. Whe you do t maage requiremets, feature creep ca slow dow ad complicate your project. RequisitePro RequisitePro is desiged to work for your etire team: Aalysts use RequisitePro to documet ad maitai requiremets. Developers use requiremets to desig architecture ad write more detailed specificatios. Test egieers use requiremets to desig tests ad check test coverage. Maagers use RequisitePro to defie project work based o available time, budget, ad persoel. RequisitePro makes it easy to write ad maage requiremets. It is itegrated with Microsoft Word ad is packaged with Word templates to help you get started quickly. Startig with a Use Case I Uit 2, About this Tutorial, you saw the ehacemet request that was etered i respose to your feedback. Oe of your team members has started work o the requiremet correspodig to your request. Creatig Requiremets 45

46 Why Work with Use Cases? Use cases describe system behavior i a commo laguage that everyoe o the team ca uderstad. Workig with use cases is a key uifyig mechaism i the Ratioal Uified Process. Use cases are importat to everyoe o the project: Exercise Aalysts use them to express how the system should behave. Use cases allow users to validate system behavior startig as early as the desig phase. Developers ad desigers ca start with huma-laguage ad graphical use cases. They elaborate them first ito architectural specificatios ad the ito classes. Testers ca elaborate test desigs based o use cases. Use RequisitePro to ope the use case documet. 1 O the RequisitePro Tool Palette, click Documet > Ope to display the Ope Project ad Documets dialog box. 2 I the Select Documets list, select Arrage Shipmet. Click OK. The RequisitePro Word Workplace opes ad displays the use case documet. This documet is based o a template provided with the Ratioal Uified Process. (I the previous uit, you saw, ad may have clicked o, a lik to this template.) 3 I the documet, scroll to Sectio 1, Arrage Shipmet. Text with double-uderliig idetifies requiremets. These use case requiremets, idetified by the prefix UC, are high-level requiremets that describe the system s behavior. 4 Read the Brief Descriptio ad Flow of Evets. Notice that the shippig date ehacemet has bee recorded (it starts with The warehouse... ) but it has ot yet bee idetified as a requiremet. This is a typical way of startig requiremets work. You use the familiar eviromet of Word to documet your requiremets. You use RequisitePro to idetify ad elaborate o your project s requiremets. You also idicate which requiremets are related (through paret-child or traceability relatioships). RequisitePro the tracks how chages to the system affect your requiremets ad how chages to requiremets affect your system. 5 For ow, miimize Word ad the RequisitePro tool palette. 46 Ratioal Suite Tutorial

47 How Does it Work? RequisitePro is both documet-cetric ad database-cetric ad relies o the stregths of both: The documet features provide a familiar eviromet (Word) for creatig descriptios ad commuicatig your work to project stakeholders. You ca start a requiremets documet either by importig existig Word files ito RequisitePro or by usig the RequisitePro Word Workplace. The database features help you orgaize your requiremets, prioritize your work, track requiremets chages, ad share iformatio with other Ratioal tools. To work with database features, you use the Views Workplace. How Does RequisitePro Hadle Requiremets? I the use case documet, the requiremets text (doubleuderlied) exists i the documet. The database also stores the requiremets text, alog with attributes (such as priority ad assiged-to) that help track the requiremet. Later i this uit, we work with RequisitePro database features. Cotiuig Use Case Work: Usig Rose I this sectio, you cotiue work o the use case a high-level descriptio of how a actor iteracts with the system as the first step i implemetig the feature requiremet. Startig Rose Rose is a visual modelig tool that uses the Uified Modelig Laguage (UML) ad is itegrated with commo code developmet eviromets. Exercise To start Rose: 1 From the Start meu, click Programs > Ratioal Suite > Ratioal Rose. Rose appears ad displays the Create New Model dialog box. 2 Quit the Create New Model dialog box. Creatig Requiremets 47

48 3 Cofigure Rose the first time you use it: From the Rose meu, select File > Edit Path Map. I the Symbol field, type CURDIR. I the Actual Path field, type &. Click Add. Click Close. These steps allow you to ope a Rose model o your machie eve if the model was created o a differet machie. 4 From the Rose meu, select File > Ope ad avigate to c:\program Files\Ratioal\Classics Demo\ClassicsRepo\ Project\ClassicsCDW\Rose 5 Select ClassicsCD_tutorial.mdl ad click Ope. 6 Rose asks whether to load subuits. Click Yes. Rose displays a hierarchical tree browser i the upper-left pae (the Rose browser). I the right pae (the diagram widow), it displays the logical view of the architecture showig how the top-level packages i the system iteract. Creatig a Use Case i Rose Now that you kow which feature to implemet, you wat to create a use case i Rose ad add it to a existig use case diagram. A use case diagram shows: The behaviors of a system. The use cases describe what the system does. The boudaries of a system. The actors represet exteral etities that iteract with the system. The relatioships amog use cases ad actors. 48 Ratioal Suite Tutorial

49 Exercise Add to the use case diagram. 1 I the Rose browser, expad Use Case View by clickig the + to its left. The expad cdshop. Notice the actors (stick figures) ad use cases (ovals) listed uder cdshop. 2 Double-click Mai uder cdshop to display the use case diagram. Maximize the diagram withi the Rose widow. Double-click Mai uder cdshop 3 Create the Arrage Shipmet use case: I the Rose browser, right-click cdshop. From the shortcut meu, choose New > Use Case. Immediately type its ame, Arrage Shipmet, exactly as show, ad press ENTER. If the use case does ot appear o the diagram, drag it from the Rose Browser to the diagram, placig it below Checkout. (You ca drag the blue ote out of the way.) 4 O the diagram, select the arrow betwee Checkout ad Order Server. Press DELETE to delete the arrow. 5 O the diagram toolbox (betwee the Rose browser ad the diagram widow): Click the Uidirectioal Associatio butto. O the use case diagram, drag from the ew Arrage Shipmet use case to the Checkout use case. Click the Uidirectioal Associatio butto. O the use case diagram, drag from the Arrage Shipmet use case to the Order Server actor. Creatig Requiremets 49

50 Portio of Updated Use Case Diagram Associatig the Rose Model with the RequisitePro Project Earlier i this uit, you opeed the Classics project i RequisitePro. I this sectio, you associate the Rose model you are modifyig with that project i RequisitePro. You also lik the use case you just created with the use case requiremet that already exists i RequisitePro. Exercise Associate the Rose model ad the RequisitePro project: Creatig a New Requiremet 1 O the use case diagram, right-click the Arrage Shipmet use case. From the meu, click Use Case Documet > Associate. 2 O the Associate Documet to Use Case Arrage Shipmet dialog box, select Arrage Shipmet. Click OK. RequisitePro appears, displays the Arrage Shipmet use case documet, ad highlights the Arrage Shipmet use case requiremet you saw earlier i this uit. The Arrage Shipmet use case is ow represeted both i words ad by a visual model. The use case is ow a sigle elemet. Arrage Shipmet is a established use case, but you still eed to idetify a requiremet for the ehacemet request. 50 Ratioal Suite Tutorial

51 Exercise Create the requiremet. 1 I the RequisitePro Word Workplace, scroll to the ed of the basic flow. Select the etire setece begiig The warehouse system respods... 2 From the Word meu, select RequisitePro > Requiremet > Create. RequisitePro displays the Requiremet Properties dialog box. 3 O the Attributes tab, from the Property list, select Basic Flow to idicate that this ew requiremet is part of the basic flow of a use case. 4 O the Hierarchy tab: From the Paret list, select <choose paret...>. From the Paret Requiremet Browser, select UC7: Arrage Shipmet. Click OK. 5 O the Requiremet Properties dialog box, click OK. RequisitePro uderlies the requiremet ad marks it as pedig. 6 From the Word meu, select RequisitePro > Documet > Save. Whe RequisitePro saves the documet, it fiishes creatig the requiremet. Scroll up to the ew requiremet ad verify that it has bee assiged the umber UC7.2. Lookig at Requiremets i the Database I this sectio, you use the RequisitePro database to view requiremets related to the ehacemet you are workig o. Wheever you work i a database, you use a view, which filters data i a specific format. RequisitePro works the same way. Exercise Ope a view ito the database, usig the Views Workplace. 1 I the Word Workplace, click RequisitePro > Widow > Show Views. The RequisitePro Views Workplace opes. 2 From the RequisitePro Views meu, click File > Ope View. Creatig Requiremets 51

52 3 Uder Attribute Matrix Views, select UC: All Use Cases ad click OK. The use cases i the left colum describe the fuctioal areas of ClassicsCD.com. The use cases are orgaized hierarchically, where each child requiremet is listed uder its paret. Paret requiremets are more geeral, while child requiremets describe more specific areas. To see childre of a use case, click o the + ext to its ame. 4 Verify that the ship-date requiremet was added by clickig the + ext to UC7: Arrage Shipmet. 5 Scroll to the right to see each requiremet s attributes ad their properties. Likig to Aother Requiremet So far, you have: Decided to implemet a ew ehacemet. I Rose, added a ew use case to the use case diagram. Liked the model to the RequisitePro project. Created a ew use case requiremet. Added values to the requiremet s attributes. You ow wat to lik the use case requiremet to aother type of requiremet, a feature requiremet. A system s feature requiremets are writte at a very high level ad form a foudatio for the etire system. Exercise Lik the use case requiremet to a feature requiremet: 1 From the RequisitePro Views meu, click File > Ope View. 2 Uder Traceability Matrix Views, select UC-Feat: Trace Matrix showig Features ad Use Cases ad click OK. The view displays, showig the etire hierarchy of requiremets. 3 From the Views workplace meu, choose View > Collapse All. 4 Alog the top row, expad FEAT1 by clickig the + uder it. 5 Expad UC7 by clickig the + to its left. 52 Ratioal Suite Tutorial

53 6 Right-click the cell at the itersectio of FEAT1 ad UC7. From the meu, select Trace To. A arrow appears i the cell, showig the lik relatioship. You have just used the RequisitePro traceability feature to create a lik from the use case requiremet, UC7, to the feature requiremet, FEAT1. I the ext sectio, you lear more about traceability. Traceability Liks ad Suspect Liks The matrix i the Views Workplace shows some of the liks betwee requiremets. These liks describe depedecies betwee requiremets. A arrow with a lie through it idicates that the lik is suspect. A lik becomes suspect whe a requiremet i the lik relatioship chages. A aalyst eeds to examie the chages, ad decide whether to edit the depedet requiremets before clearig the suspect lik. Creatig Requiremets 53

54 Other Requiremet Types So far, we ve discussed high-level feature requiremets ad more detailed use case requiremets. Some requiremets do ot led themselves to use cases, so RequisitePro supports other types of requiremets. For example, you ca defie requiremets for performace targets ad platform support. You ca also defie ew requiremet types. RequisitePro ca maage ay type of requiremet that you eed o your project. Whe Have You Fiished Gatherig Requiremets? Exteded Help Requiremets emerge from a series of commuicatios betwee aalysts ad project stakeholders (applicatio users, members of the marketig team, fuders, ad so o). As you capture requiremets, you check your work with the appropriate stakeholders. Whe the stakeholders ad your team come to agreemet, your iitial job of gatherig requiremets is doe. Of course, as the project progresses, you will cotiue to maage the requiremets, addig some, possibly removig others, ad respodig to chages. Exteded Help is a powerful feature of Ratioal Suite that provides liks to the Ratioal Uified Process ad to other iformatio. You use Exteded Help directly from the tools you use to accomplish your work. Exercise You ca see Exteded Help from ay RequisitePro widow: 1 O the Views Workplace meu, click Help > Exteded Help. The Ratioal Exteded Help widow opes. The widow has two paes. The left pae cotais a tree browser ad the right pae is blak. 2 Move the vertical divider to wide the left pae. 54 Ratioal Suite Tutorial

55 3 I the left pae, expad Tool Metors (click the + ext to it) ad double-click Detailig a use case. Exteded Help displays the same tool metor that you viewed i Uit 3, Learig About the Ratioal Uified Process. Read this tool metor to review the work you ve doe i this uit. Exteded Help provides iformatio about the higher-level tasks you may wat to accomplish. It gives you direct access to the Ratioal Uified Process from the Ratioal Suite tools. I additio, you ca add your ow orgaizatioal guidelies or stadards to Exteded Help. For more iformatio about this feature, o the Exteded Help browser (the left pae), avigate to About Ratioal Exteded Help > Exteded help overview. Summary For More Iformatio For more iformatio o gettig started with RequisitePro, start with Let s Go RequisitePro: from the RequisitePro Tool Palette meu, choose Help > Let s Go RequisitePro. For more iformatio about Rose, see Modelig the Ehacemet o page 67. Cleaig Up Quit Exteded Help. Quit RequisitePro by choosig Project > Exit from the RequisitePro Tool Palette. RequisitePro asks if you re sure you wat to close the project. Click Yes. Quit Rose by choosig File > Exit from the Rose meu. Whe Rose asks whether to save chages, click Yes. Creatig Requiremets 55

56 What You Leared i this Uit I this uit, you leared: A requiremet is a coditio or capability to which the system must coform. Maagig requiremets is a systematic approach to fidig, documetig, orgaizig, ad trackig requiremets. All members of your team beefit from usig RequisitePro to maage requiremets. RequisitePro is both documet-cetric ad database-cetric, allowig your team to beefit from the stregths of both. To create a use case, you work i Rose to add the use case to your model, the work i RequisitePro to add textual descriptios. You have fiished writig the first set of requiremets whe your stakeholders ad your team agree that you re doe. Exteded Help gives you immediate access to process ad task iformatio. You ca add your ow iformatio to Exteded Help. What s Next I the ext uit, you use the requiremets you idetified i this uit to get started o test plaig. 56 Ratioal Suite Tutorial

57 RATIONAL SUITE TUTORIAL Test Plaig So far, you have defied requiremets for the ClassicsCD.com ehacemet. You have ot yet modeled or implemeted code. However, you are ready to start test plaig. Audiece Gettig Your Bearigs This uit applies to test egieers. I this uit, you use Ratioal RequisitePro. Refer to the tool chart you filled out (Table 1, Ratioal Suite Tools, o page 25) to determie whether RequisitePro is istalled o your system. If RequisitePro is ot istalled, you ca still beefit from readig this uit, but you will ot be able to perform the exercises. If RequisitePro is istalled, start it ow by clickig the Start butto ad choosig Programs > Ratioal Suite > Ratioal RequisitePro. The RequisitePro Tool Palette ad Let s Go RequisitePro appear. Click Close o the Let s Go RequisitePro widow. The RequisitePro Tool Palette Note This uit assumes you are familiar with RequisitePro cocepts ad beefits. If you are ot, please read Uit 4, Creatig Requiremets, before cotiuig. 57

58 What Is Test Plaig? Opeig the ClassicsCD Web Shop Project Ope the ClassicsCD Web Shop project: 1 O the RequisitePro Tool Palette, click Project > Ope. If the Select a Project list cotais ClassicsCD Web Shop, skip to step 6. Otherwise cotiue with the ext step to add the project to the list. 2 I the Select a Project area, click Add. 3 I the Add Project dialog box, avigate to c:\program Files\Ratioal\Classics Demo\ClassicsRepo\ Project\ClassicsCDW\requisite\requisite.rqs 4 Click Ope. The dialog box ow lists the project ClassicsCD Web Shop. The ext time you start RequisitePro, the project will be i the list ad you will ot have to add it agai. 5 If you see the Project Logo dialog box, choose or type Pat ad click OK. 6 Select ClassicsCD Web Shop ad click OK. Oce the project opes, the Tool Palette s status bar displays the message Ready. You are ow ready to work with the project. Test plaig allows you ad your group to effectively measure ad maage test efforts over the course of the project. Durig test plaig, you idetify the types of tests you will perform, the strategies for implemetig ad ruig those tests, ad the resources you will eed durig testig. Test plaig starts early i the developmet cycle, as soo as you uderstad the iitial set of requiremets. As with developmet, test plaig is a iterative process. You will cotiue to pla testig throughout a project s lifecycle, as aalysts chage or elaborate o requiremets, ad as developers desig ad implemet code. 58 Ratioal Suite Tutorial

59 Risk Maagemet The recommeded strategy for test plaig is to focus o the riskiest areas of the project first. For example, you could idetify risks by cosiderig: The cosequeces of ot testig a specific part of a applicatio The cosequeces if a particular part of the applicatio does ot work properly The likelihood that a error will be discovered after the product ships The ramificatios if a user, rather tha a project member, discovers a error i the code Test Plaig ad the Tutorial I this uit of the tutorial, you perform a small piece of test plaig tracig test requiremets. You also look at a test specificatio for the ClassicsCD.com ehacemet. Workig with Test Requiremets You start test plaig by idetifyig test requiremets. You the associate test requiremets with their correspodig use case requiremets (for example, the use case requiremet you worked with i Uit 4, Creatig Requiremets ). A use case requiremet focuses o the details of system behavior. A test requiremet focuses o what to test i a specific area of the applicatio. Explorig Test Requiremets I this sectio, you look at the existig test requiremets for Classics. You work with a traceability matrix, which shows the relatioship betwee use case requiremets ad test requiremets. Exercise Look at the test requiremets for ClassicsCD.com. 1 From the RequisitePro Tool Palette, click Widow > Show Views to display the RequisitePro Views Workspace. 2 From the RequisitePro Views meu, click File > New View to display the New View dialog box. Test Plaig 59

60 3 I the View Type area, click Traceability Matrix. 4 I the Row Requiremet Type list, select UC: Use Case Requiremet Type. 5 I the Colum Requiremet Type list, select TR: Test Requiremet Type. Click OK. The view displays a expaded list of use cases. 6 Collapse all the use cases by clickig View > Collapse All. If you wat, resize the table s headig rows. Use Case Requiremets Related to Test Requiremets This table shows how the test requiremets are related to the use case requiremets. The turquoise arrows show traceability relatioships. For example, oe arrow shows that TR12 is traced to UC1. Notice that o test requiremet is traced to UC7. If Use Case 1 chages, a red slash is draw through the arrow ( ), idicatig that the traceability relatioship is suspect. A suspect relatioship meas that oe or both requiremets i the relatioship have chaged. A aalyst eeds to examie the chages, ad decide whether to edit the requiremets before clearig the suspect lik. 60 Ratioal Suite Tutorial

61 You eed to establish traceability at a high level oly. Durig test plaig, it is uecessary to establish test requiremets at lower levels of detail. Exercise Add a traceability lik for UC7. 1 O the view, right-click i the cell betwee UC7: Arrage Shipmet ad TR16: Use Case Arrage Shipmet. 2 From the meu, select Trace From. You have ow established a lik betwee the use case ad the test requiremet. Desigig Tests Each test requiremet describes a specific area of the applicatio to test. However, each area ca ecompass a broad class of situatios that you eed to test. For example, i testig a cash sales trasactio, you would probably test: Valid iput (the customer pays the exact price; the customer pays more ad eeds chage) Ivalid iput (the customer pays less tha the sales price; the sales clerk eters a ivalid part umber) How do you determie what to test? This part of test plaig test aalysis ad desig requires you to rely o your ow huma itelligece ad experiece. Startig with the Use Case Whe you desig tests, the first step is to examie the origial use case to uderstad how the system is supposed to behave. You the create test requiremets ad trace them to the use cases. Durig aalysis, you idetify the coditios you eed to test to verify that: Code implemetig the use case does what is iteded. Code implemetig the use case does ot do what is ot iteded. Test Plaig 61

62 Creatig Test Cases A test case describes the extet to which you will test a area of the applicatio. It lists the precoditios for performig a test, the iput to provide durig testig, the variables you will examie, ad the expected results of each test. May orgaizatios fid it useful to create a chart showig the results of the test aalysis ad desig. By examiig the chart, you quickly get iformatio about areas that may require further testig. Exercise Look at a sample test case. 1 O the RequisitePro Tool Palette, click Documet > Ope to display the Ope Project ad Documets dialog box. 2 I the Select Documets list, select Test Cases for Use Case Arrage Shipmet. (You may eed to scroll to see it.) Click OK. 3 I the documet, scroll to Sectio 1, Fuctioal Test Cases. This documet presets a test desig for the Arrage Shipmet use case. Read the first sectio for a overview of the tests to perform for this use case. 4 Scroll to the ext sectio to view a table describig the tests. Each test is liked to a test case ad describes ay prerequisites ad expected results. Cotiuig with Test Plaig Writig a test pla is a iterative process that starts early i the project. It cotiues as aalysts chage requiremets ad elaborate o use cases, as developers desig ad write code, ad as testers discover more areas or coditios to test. Test plaig occurs i parallel with other developmet efforts, icludig testig. As you work o your ow test pla, we suggest you cosider at least the followig topics, described i the remaider of this sectio: Risks ad resources Types of tests to perform Schedulig 62 Ratioal Suite Tutorial

63 Risks ad Resources Idetifyig risk is a importat part of test plaig. Oce you idetify the available testig resources, you eed to balace ievitable resource costraits with the project ad testig risks. As a result, you ca refie the testig strategy. We recommed that you prioritize tests as follows: Must test (high) You must ru this test to avoid severe risk or to idetify weak project areas early i the developmet cycle. You caot complete project testig without completig this test. Should test (medium) You should schedule this test, but i a resource cruch, could cosider ot ruig it. Could test (low) This test might be useful to ru, but is ot essetial to the project. Ru this test if you caot make further progress o other, more importat, tests. Wo t test (low) This test is ot part of the testig project. A test with this priority defies the boudaries of the test pla ad helps focus attetio o what will be tested. Types of Tests There are may types of tests to cosider as you create a test pla, icludig, but ot limited to: Fuctioal tests Does the applicatio meet its fuctioal requiremets? Use Ratioal Robot for fuctioal testig. Reliability tests Ca the applicatio ru without errors? Use Ratioal TestFactory for reliability testig. Performace tests Is the applicatio s performace acceptable uder varyig loads? Use Ratioal Suite PerformaceStudio for performace testig. Schedulig Part of creatig a test pla ivolves writig a schedule. You work with team leaders from other areas of the project to uderstad whe their cotributios will be ready for testig. You the eed to balace your origial schedule agaist the risks ad resources you idetified i order to arrive at the most effective schedule. Test Plaig 63

64 If you prioritized your tests as described i Risks ad Resources o page 63, make sure you at least schedule the must (high priority) ad should (medium priority) tests. If resources become more costraied over the course of the project, you ca sacrifice tests of lower priority without compromisig the absolute quality objectives expressed by the must tests. RequisitePro is itegrated with Microsoft Project so that you ca lik requiremets ad tasks o your project schedule. For more iformatio: 1 O the RequisitePro Tool Palette, choose Help > Cotets ad Idex. 2 I the RequisitePro Help Browser, o the Cotets tab, avigate (by double-clickig) to Wizards, Itegratios ad Compoets > RequisitePro Wizards > MS Project Itegratio Wizard. A Help topic appears, describig how to work with RequisitePro ad Microsoft Project. Summary For More Iformatio For more iformatio about test plaig: Read about test plas. Startig i the Ratioal Uified Process tree browser, click Artifacts > Test Set > Test Pla. Read Plaig Your Tests i Usig Ratioal Robot. For a more i-depth treatmet of test plaig, read Testig Computer Software (Vr Computer Library) by Cem Kaer ad others (ISBN: ). Cleaig Up Quit RequisitePro by choosig Project > Exit from the RequisitePro Tool Palette. RequisitePro asks if you re sure you wat to close the project. Click Yes. If you are prompted to save documets, click Yes. 64 Ratioal Suite Tutorial

65 What You Leared i this Uit I this uit, you leared: You ca start test plaig early i the project, after iitial requiremets are idetified. Test plaig is a iterative process, ecompassig project ad testig risks, evolvig product requiremets, available resources, ad project schedule. Part of test plaig ivolves creatig test requiremets ad relatig them to use case requiremets. Aalysis ad desig are importat compoets of writig effective tests. Prioritizig tests helps you focus your testig effort o the riskiest ad most importat areas of the applicatio to test. What s Next I the ext uit, you use Rose to work o a architectural model for the ehacemet you are workig o. Test Plaig 65

66 66 Ratioal Suite Tutorial

67 RATIONAL SUITE TUTORIAL Modelig the Ehacemet So far, you have defied requiremets for the ClassicsCD.com ehacemet. The test orgaizatio has started test plaig. I this uit, you cotiue to icorporate desigs for the ehacemet ito the ClassicsCD.com visual model. Audiece This uit applies to software desigers ad developers. Gettig Your Bearigs I this uit, you use Ratioal Rose. Refer to the tool chart you filled out (Table 1, Ratioal Suite Tools, o page 25) to determie whether Rose is istalled o your system. If Rose is ot istalled, you ca still beefit from readig this uit, but you will ot be able to perform the exercises. If Rose is istalled, start it ow: 1 Click the Start butto ad choose Programs > Ratioal Suite > Ratioal Rose. 2 If you did ot perform the exercises i Chapter 4, Creatig Requiremets, do the followig: Perform the steps uder Startig Rose o page 47. Resume this procedure at step 5. 3 I the Create New Model dialog box, click the Existig tab, ad avigate to: c:\program Files\Ratioal\Classics Demo\ClassicsRepo\ Project\ClassicsCDW\Rose 4 I the Model Files area, select ClassicsCD_tutorial.mdl. Click Ope. 67

68 Rose displays a hierarchical tree browser i the upper-left pae (the Rose browser). I the right pae (the diagram widow), it displays the logical view of the architecture showig how the top-level packages i the system iteract. 5 I the Rose browser, expad Use Case View by clickig the + to its left. You should see Mai ad cdshop. Use Case View, expaded What Is Visual Modelig? Visual modelig is the creatio of graphical represetatios of your system s structure ad iterrelatioships. The result is a blueprit of your system s architecture. A visual model: Is graphical, rather tha text-based, makig it easy to uderstad complex systems at a glace. Allows you to see relatioships amog desig compoets, so that you ca create cleaer desigs ad therefore write more maitaiable code. Helps you meet customer eeds because you base the visual model o project requiremets. Improves commuicatio across your team because you use a stadard graphical laguage for coveyig the system s architecture. Visual Modelig ad the Tutorial Ratioal Rose supports visual modelig. I Uit 4, Creatig Requiremets, you used Rose ad RequisitePro to create a use case. I this uit, you cotiue workig o the desig for the ehacemet. 68 Ratioal Suite Tutorial

69 Workig with a Sequece Diagram I this task you work with a sequece diagram, a visual represetatio of the steps through oe path i a use case. Project members ad other stakeholders ca use a sequece diagram (graphical represetatio), use case requiremets (text descriptio), or both to evaluate the project directio ad as a basis for their work. A use case ofte cotais more tha oe path. It always cotais a basic flow which describes the most commo path through the use case. It may cotai alterative flows which describe other paths, icludig error coditios. A sequece diagram shows how actors iteract with the system, ad i what order. Whe you first work o a sequece diagram, you ted to use huma-laguage labels. As you refie the system desig, you chage the diagram so that it idetifies: Classes Sets of objects that share a commo structure ad commo behaviors Messages Iteractios betwee classes Opeig a Sequece Diagram Start by lookig at a existig sequece diagram. Exercise Ope the sequece diagram ow. 1 I the Rose browser, avigate to cdshop > Checkout > Arrage Shipmet. 2 If you did ot perform the exercises i Chapter 4, Creatig Requiremets, do the followig: I the Rose browser, right-click cdshop. From the shortcut meu, choose New > Use Case. Immediately type its ame, Arrage Shipmet, ad press ENTER. Modelig the Ehacemet 69

70 3 You wat the sequece diagram to appear uder the Arrage Shipmet use case, so drag it to the use case: 4 Double-click the Arrage Shipmet sequece diagram to ope it. The sequece diagram appears. Tip: Click the had i the lower right corer of the diagram widow to see a bird s eye view of the diagram ad to easily repositio the widow s cotets. 5 Maximize the diagram, the resize it so you ca it all at oce. (You may eed to select View > Zoom Out to view the etire diagram.) This sequece diagram shows how the actors ad other objects i the applicatio commuicate with each other. A message ico, a horizotal, solid arrow betwee two vertical, dashed lifelies, represets each commuicatio. Items i a sequece diagram are arraged i chroological order. 70 Ratioal Suite Tutorial

71 Arrage Shipmet Sequece Diagram The first few messages mea that: 1 The Customer starts the use case by sedig a Submit message to the Cashier Servlet. 2 The Cashier Servlet seds a message to itself to verify whether the Customer is a valid member. 3 The Cashier Servlet the seds a verify message to the Member Ifo Server. 4 The Cashier Servlet the seds a createorder message to itself. Modelig the Ehacemet 71

72 Addig Messages for the Ehacemet I this sectio, you add messages to the sequece diagram for the ehacemet you are workig o. Exercise Startig o the sequece diagram: 1 O the diagram toolbox (betwee the Rose browser ad the diagram widow), click the Message to Self butto. 2 To place the message, click o the diagram o the Cashier Servlet lifelie (the vertical lie), just uder Message 6. Notice that Rose reumbers the messages o the diagram. 3 While the object is still selected, type getshipdate. The click the backgroud of the diagram. We are followig this amig covetio for objects: Names begi with a lower-case letter. Names do ot cotai spaces. Withi a ame, the first letter of each word is capitalized. 4 Create the secod message: O the diagram toolbox, click the Object Message butto. Click the Cashier Servlet lifelie uder getshipdate ad drag the message lie to the lifelie for Order Server. While the message lie is still selected, type getestimatedshiptime(order). Click i the backgroud of the diagram. (You ca resize the text box for the message ame so that the etire message fits.) 5 From the Rose meu, click File > Save to save the model. If you are prompted to save subuits of the model, click Yes. 72 Ratioal Suite Tutorial

73 The Fiished Sequece Diagram Publishig Part of the Model to the Web You have ow fiished workig o this part of the model. We recommed that you create a Web versio of this part of the model so that people o your team who have ot istalled Rose ca review the model ad give you feedback. Modelig the Ehacemet 73

74 Exercise Publish the model to the Web: 1 O the Rose meu, click Tools > Web Publisher to display the Rose Web Publisher dialog box. 2 I the Selectios list, double-click the check boxes ext to Logical View, Compoet View, ad Deploymet View to clear them. There should be a check ext to Use Case View. The illustratio shows a before (left side) ad after (right side) view of the checkboxes. 3 Next to the HTML Root File Name field, click... ad browse to c:\program Files\Ratioal\Classics Demo\Web Publish I the File ame field, type model ad click Save. 4 O the Rose Web Publisher dialog box, click Publish. Rose displays a progress idicator. Whe it disappears, the Web files are ready. 5 O the Rose Web Publisher dialog box, click Preview. A Web browser appears. It displays a widow whose layout is similar to the oe i Rose. 6 Explore the model. To see the sequece diagram you worked with i this uit, avigate i the left pae to Use Case View > cdshop > Arrage Shipmet > Arrage Shipmet. 7 Whe you have fiished, miimize or close your Web browser. The o the Rose Web Publisher dialog box, click Close. After Completig the Sequece Diagram Now that you have fiished this part of the model, there are a few additioal tasks to perform. I this tutorial, we summarize the tasks but do ot show you how to perform them. 74 Ratioal Suite Tutorial

75 Refiig the Objects I the sequece diagram, you idetify the objects ivolved with the use case. You ext idetify the classes to which the objects belog. You use Rose class diagrams to group related classes ad to elaborate o them. To see a class diagram, use the Rose browser to avigate to Logical View > com > ratioal > cdshop > busiess > Mai. Double-click Mai. From the Rose meu, select View > Fit i Widow to see the etire diagram. Each represetatio of a class shows you the class attributes ad operatios. (Double-click a class represetatio to see details about the class.) Oce you idetify classes, you revise the sequece diagram to use class ad operatio ames istead of the huma-laguage ames you origially assiged. Implemetig the Code You are ow ready to implemet code. From the diagrams you ve created, Rose Eterprise Editio ca create code that is cosistet with the use case ad the models you ve developed. This is called forward egieerig. Startig from the geerated code, you as a developer fill i details of the algorithm. To geerate ew code or to update existig code, choose a item from the Rose Tools meu. For example, to implemet code for the ehacemet you ve bee workig o, you would choose Tools > Java > Geerate Java. (Of course, if Java is ot istalled o your system, this operatio does ot complete successfully.) As soo as you start chagig code, your model will probably become out of date. It is tedious to maually update the model wheever the code chages. It is also udesirable to create a model that immediately becomes obsolete. Rose ca automate keepig the code ad the model cosistet. For example, from the Rose meu, you would choose Tools > Java > Reverse Egieer Java. This is called reverse egieerig. As you ca see from the Tools meu, Rose supports several laguages i additio to Java. These laguages iclude Visual C++ ad Visual Basic. Modelig the Ehacemet 75

76 Note Rose Eterprise Editio ca geerate code, update code, ad update models. Rose Modeler Editio, icluded i Ratioal Suite Aalyst Editio, does ot have these features. Modelig Data You ca use Rose to model relatioal databases. Ratioal Rose Data Modeler is a database modelig ad desig tool that uses UML (Uified Modelig Laguage). Data Modeler allows you to: Support most specific database fuctios, such as creatig tables, colums, idexes, relatioships, ad keys (primary ad foreig). Create colum costraits, ad both DRI (Declarative Referetial Itegrity) ad RI triggers. Create custom triggers ad their geerated trigger code. Advatages Advatages of usig Rose Data Modeler are: All your busiess, applicatio, ad data models are writte i the same idustry-stadard laguage, UML, ad tool, promotig cosistecy, traceability, ad ease of commuicatio. Data Modeler supports both forward ad reverse egieerig of relatioal databases, helpig to automate the process of keepig code ad models cosistet. Summary For More Iformatio For more iformatio about Ratioal Rose, see the UML Tutorial, available o the Ratioal Solutios for Widows Olie Documetatio CD. For more iformatio about Ratioal Rose RealTime, see the olie tutorials available from Rose RealTime olie Help. These tutorials address the eeds of Rose RealTime users at all levels. 76 Ratioal Suite Tutorial

77 For more iformatio about object-orieted aalysis ad desig, use Exteded Help. From the Rose meu, choose Help > Exteded Help. I the left pae of the Exteded Help browser, avigate to a topic uder Guidelies, for example, Guidelies > Desig Class. Cleaig Up Quit Rose. If you are prompted to save chages, click Yes. What You Leared i this Uit I this uit, you leared: Visual modelig meas creatig graphical represetatios of your system s structure ad iterrelatioships. I Rose, you use sequece diagrams to elaborate o paths through use cases. You the idetify classes ad messages to prepare for code geeratio. Ratioal Rose helps you create visual models for code ad data; geerate code; ad to keep the model sychroized with chaged code. From Rose, you ca also publish to the Web. Rose supports may laguages, icludig Visual Basic, Visual C++, ad Java. What s Next The visual model for the ehacemet is ow complete. I the ext uit, you create a report about the use case for the ehacemet. Modelig the Ehacemet 77

78 78 Ratioal Suite Tutorial

79 RATIONAL SUITE TUTORIAL Creatig a Use Case Report Now that you have exteded the Arrage Shipmet use case, you might wat to geerate a report cosolidatig all the iformatio about the use case. Such a report could cotai the sequece diagram from the visual model i Rose ad the correspodig basic flow from the use case i RequisitePro. I this uit, you use Ratioal SoDA to produce that report. Audiece Gettig Your Bearigs This uit applies to all members of a software developmet team. I this uit, you use Ratioal SoDA. I additio, Ratioal Rose ad Ratioal RequisitePro must be istalled o your system. Refer to the tool chart you filled out (Table 1, Ratioal Suite Tools, o page 25) to determie whether these tools are istalled o your system. If these tools are ot istalled, you ca still beefit from readig this uit, but you will ot be able to perform the exercises. If these tools are istalled, start SoDA ow by clickig the Start butto ad the choosig Programs > Ratioal Suite > Ratioal SoDA for Word. If you see a warig about eablig macros, make sure that you choose Eable Macros. Otherwise, you will be uable to use SoDA. Microsoft Word, cotaiig a additioal SoDA meu, starts. 79

80 What Is SoDA? SoDA automates the creatio of software documetatio. It extracts iformatio from software egieerig tools such as RequisitePro ad Rose. Usig Word templates, SoDA formats the iformatio it extracts ito a report. You ca choose from the may templates provided with SoDA, or you ca create your ow templates with SoDA s easy-to-use template creatio tool. Addig iformatio to a documet is easy because you just use Word to add text. SoDA preserves your text, so it is there the ext time you geerate the documet. Why Create a Use Case Report? A use case report gathers ito oe documet both text descriptios of expected system behavior (as described i use case requiremets) ad a diagram that shows how the system iteracts with actors. This report is helpful to early every team member: A aalyst ca show the report to customers ad other stakeholders. Together, they ca verify that the project is o the right track. These discussios ca be held early i the project, so that the aalyst ca address problems or gaps before, rather tha after, the project ships. A software egieer ca use the report s descriptio of expected system behavior to start writig egieerig specificatios. A test egieer ca use the report to desig tests for the use case. From the report, a test egieer ca idetify the steps to test ad determie which coditios to test. A techical writer ca start plaig documetatio, based o the report s descriptios of how actors iteract with the system. A usability egieer ca use the report to desig usability tests, possibly startig with paper prototypes. Creatig the Use Case Report To create the use case report, SoDA relies o a predefied template. The template gathers iformatio ad formats it ito a report. Note that if you have ot performed the exercises i Uit 6, Modelig the Ehacemet, you will ot be able to create the use case report. 80 Ratioal Suite Tutorial

81 Exercise Create the use case report by startig with the template: 1 I Word, ope c:\program Files\Ratioal\Classics Demo\ClassicsRepo\ Soda\RUP Use Case Report.doc Word displays the SoDA template cotaiig text, macro commads, ad aotatios. 2 To see the etire template, click Tools > Optios. O the View tab, uder Formattig marks (Word 2000) or Nopritig Characters (Word 97), select All. Click OK. (Remember to reset this settig if you prefer ot to see all formattig marks whe you work with Word.) Excerpt of SoDA Template 3 From the Word meu, click SoDA > Geerate Report. Word miimizes ad SoDA displays a progress idicator. After a short pause, Word restores itself ad displays the report. 4 Browse through the report. You see the requiremets you worked o i Uit 4, Creatig Requiremets ad the visual model of the system you worked o i Uit 6, Modelig the Ehacemet. Excerpt of SoDA Report Creatig a Use Case Report 81

82 Workig with SoDA Templates While workig with SoDA templates is beyod the scope of this tutorial, this sectio provides poiters to help you get started. Exercise To view the template tool for the template you worked with earlier: 1 I Word, re-display the file RUP Use Case Report.doc. 2 From the Word meu, click SoDA > Template View. 3 Word displays the SoDA Template View tool. You may wat to study how each lie traslates ito the template s macros. Summary For More Iformatio To get started with SoDA, from the Word meu, click Help > Help o SoDA. I the Help Topics widow, click SoDA Tutorial. Follow the istructios displayed o your scree. Cleaig Up Close the SoDA documets. If you d like, quit Word also. What You Leared i this Uit I this uit, you leared: SoDA automates the creatio of software documetatio by creatig reports based o templates. SoDA cotais a easy-to-use tool that assists you with template creatio. A use case report is useful to all members of your project. What s Next I the ext uit, you lear about usig Ratioal TestFactory to perform reliability tests. 82 Ratioal Suite Tutorial

83 RATIONAL SUITE TUTORIAL Reliability Testig The ClassicsCD Admiistrator ehacemet is implemeted ad test plaig has occurred. You are ow ready to test the ehacemet. I this uit, we discuss testig for reliability. I the ext uit, you perform fuctioal testig. Audiece This uit applies to testers ad developers. Reliability Testig Tools This chapter describes the followig automated testig tools: Ratioal TestFactory. Automates testig by combiig automatic test geeratio with source-code coverage aalysis. Tests a etire applicatio, icludig all GUI features ad all lies of source code. Ratioal Purify. Pipoits ru-time errors ad memory leaks i Visual C++ applicatio code. Ratioal PureCoverage. Idetifies which parts of your Java, Visual C++, or Visual Basic program have ad have ot bee exercised. Exposes testig gaps so you ca prevet utested applicatio code from reachig your users. Ratioal Quatify. Profiles your Java, Visual C++, or Visual Basic applicatio to help you idetify performace bottleecks i your code. What Is TestFactory? TestFactory optimizes the productivity of developers ad testers by reducig the maual effort required to test software. TestFactory is a Automated Testig tool that geerates scripts to thoroughly test Visual Basic, C++, ad Java applicatios. These scripts discover defects ad provide extesive code coverage. 83

84 You ca start usig TestFactory early i the developmet cycle, as soo as a user iterface is available to test. You use TestFactory throughout developmet to verify the reliability of each ew build. Overview of Process You use TestFactory as follows: 1 Istrumet the applicatio to gather iformatio about code coverage. 2 Map the applicatio to create a hierarchical list of UI cotrols. 3 Ru a Pilot to automatically geerate scripts that test the applicatio. The rest of this sectio discusses each of these steps ad provides poiters for usig TestFactory as a complemet to Ratioal Robot. Istrumetig the Applicatio You istrumet a applicatio so that TestFactory ca optimize the best scripts it geerates scripts that provide code coverage of your applicatio. Durig istrumetatio, TestFactory creates a ew versio of the applicatio s executable file but does ot permaetly alter source code. Ayoe ca istrumet a applicatio, but i may groups, the release egieer creates a istrumeted executable file for others to test. Mappig the Applicatio The ext step is to create a applicatio map. To create a map, TestFactory thoroughly explores the applicatio s user iterface ad gathers detailed iformatio about the user iterface ad its avigatioal pathways. TestFactory builds a comprehesive hierarchical applicatio map that it uses as the foudatio for automatic test geeratio. You ca build a applicatio map of the etire applicatio, or you ca icremetally iclude applicatio chages ito a existig map. 84 Ratioal Suite Tutorial

85 Oce the applicatio map is complete, TestFactory displays a Mappig Summary. Usig this report, you ca idetify chages to the applicatio s UI. Ruig a Pilot A Pilot uses the istrumeted applicatio ad the applicatio map to geerate a test script (the best script) that exercises as much of the applicatio as possible. As it builds the best script, the Pilot automatically ucovers severe program defects ad geerates defect scripts. Playig back a defect script allows you to reproduce a error i the applicatio. To create these scripts, TestFactory deeply explores the applicatio s user iterface ad source code. After creatig these scripts, TestFactory shows exactly which source code ad which user iterface objects its scripts test. Whe it has fiished, it displays a summary of the Pilot ru: You ca examie the best script both to read a huma-laguage outlie of the script ad also to see code coverage results. From a defect result, you ca quickly determie the lie of code o which the defect occurred ad you ca easily log a defect report ito ClearQuest. Test Suites: Puttig It All Together Use a Test Suite to orgaize scripts ad to ru them automatically as a group. I a Test Suite, you ca iclude: Scripts geerated by TestFactory best scripts ad defect scripts Scripts you record or write i Robot You ca ru a Test Suite locally o your ow computer or you ca use TestAccelerators to distribute scripts i a Test Suite to computers o a etwork, for example, i a test lab. Reliability Testig 85

86 Additioal Testig Tools Usig TestFactory with Ratioal Robot TestFactory complemets ad builds o Ratioal Robot features. By usig both tools, you ca develop ad ru regressio tests that validate specific, missio-critical paths through a applicatio. TestFactory automatically geerates tests that cover a etire applicatio. It takes advatage of the advaced object recogitio ad playback features of Robot. TestFactory also provides detailed coverage data o scripts created i Robot. As described i the ext uit, you use Robot to discover defects based o product requiremets. You ca use Robot to add verificatio poits to ehace a optimized TestFactory script. Ratioal Suite provides additioal testig tools that both developers ad testers use throughout the developmet lifecycle. These tools ru o Widows NT ad Widows 2000; they do ot ru o Widows 95 or Widows 98. Ratioal Purify Ru-time memory-referece errors ad memory leaks are some of the most difficult errors to locate ad the most importat to correct. They ofte remai udetected util triggered by a radom evet, so that a program ca appear to work correctly whe actually it s workig oly by accidet. Ratioal Purify is a comprehesive ru-time error detectio tool that works with Visual C/C++ programs. Purify ca fid memory errors i every compoet of your program, eve whe you do t have the source code. If Purify detects a error i a area of the applicatio for which the source code is available, it idetifies ad displays the commad that caused the ivalid memory referece. Purify ca also collect coverage data as you check your code for errors, pipoitig the part of your program that you have ot tested. Usig Purify's coverage data, you ca make sure that all your code is free of errors. 86 Ratioal Suite Tutorial

87 Purify Features Just-i-time debuggig provides istat access to the debugger Simply poit Ratioal Purify at your applicatio ad ru it Access editors to fix problems immediately Navigate easily through error messages Easy to uderstad error symbols: Error Warig Iformatio Error Locatio Reliability Testig 87

88 Ratioal PureCoverage To effectively test a applicatio, you eed to kow which parts of the applicatio were exercised durig a test ru ad which oes were missed. Without this iformatio, you ca waste valuable time editig, compilig, ad debuggig your software without actually testig the critical problem areas. With Ratioal PureCoverage, you ca quickly ad easily idetify the gaps i your testig of Visual C/C++, Visual Basic, ad Java programs. PureCoverage is especially useful as a compaio to Ratioal Purify: it ca tell you whether you are exercisig your code sufficietly for Purify to fid all of your memory errors. It is essetial to a automated testig eviromet. PureCoverage Features Simply poit Ratioal PureCoverage at your applicatio ad ru it Easily access all four aalysis widows Cotrol the collectio of coverage data Merge coverage statistics for multiple rus Navigate easily through coverage data displays The Coverage Browser provides a easy to use outlie view for fast aalysis of coverage data 88 Ratioal Suite Tutorial

89 Ratioal Quatify Ratioal Quatify quickly pipoits performace bottleecks i Visual C/C++, Visual Basic, ad Java programs. It takes the difficulty ad guesswork out of performace tuig by deliverig accurate, repeatable timig data for all the compoets of your program, eve whe you do t have the source code. Quatify gives you the isight you eed to write more efficiet code ad make ay program ru faster. It ca tur everyoe o your team ito a performace egieer. Quatify Features Simply poit Ratioal Quatify at your applicatio ad ru it Cotrol the collectio of profilig iformatio Compare executio time betwee two rus or merge executio time for multiple rus Drill dow to detailed performace data Reliability Testig 89

90 Summary For More Iformatio For more iformatio about: TestFactory. Read the tutorial, Gettig Started with Ratioal TestFactory, ad the TestFactory olie Help. Purify. Read Gettig Ahead with Purify ad the Purify olie Help. PureCoverage. Read Gettig Ahead with PureCoverage ad the PureCoverage olie Help. Quatify. Read Gettig Ahead with Quatify ad the Quatify olie Help. These books are all available o the Ratioal Solutios for Widows Olie Documetatio CD. What You Leared i this Uit I this uit, you leared: TestFactory automatically maps a applicatio ad geerates best scripts (which cover the most code i the least umber of steps) ad defect scripts (which reproduce ay errors that TestFactory fids). Use TestFactory startig early i the developmet cycle to test for reliability ad to discover severe defects i your applicatio. Use Test Suites to orgaize test scripts ad to ru them automatically as a group. Additioal testig tools iclude Purify (fids ru-time memory errors), PureCoverage (determies testig coverage), ad Quatify (idetifies performace bottleecks.) What s Next I the ext uit, you cotiue testig the ClassicsCD Admiistrator ehacemet. You use Robot to create a script, iclude the script i a existig Test Suite, ru the Test Suite, ad hadle errors discovered by the tests. 90 Ratioal Suite Tutorial

91 RATIONAL SUITE TUTORIAL Fuctioal Testig At this poit i the developmet process, developers have implemeted the ClassicsCD.com ehacemet (this work was doe outside of the tutorial). Test egieers have ru iitial reliability tests. I this uit, you perform fuctioal tests o the ehacemet. Audiece This uit applies to test egieers. Gettig Your Bearigs I this uit, you start by usig Ratioal TestMaager, which is istalled with Ratioal Robot. Refer to the tool chart you filled out (Table 1, Ratioal Suite Tools, o page 25) to determie whether Ratioal Robot is istalled o your system. If Ratioal Robot is ot istalled, you ca still beefit from readig this uit, but you will ot be able to perform the exercises. If Ratioal Robot is istalled, start TestMaager ow (later i this uit, you also work with Robot): 1 Click the Start butto ad choose Programs > Ratioal Suite > Ratioal TestMaager. 2 If the Ratioal Repository Logi dialog box appears, use these values: I the User ID ad Password boxes, type pat. Make sure the Repository Path box displays c:\program Files\Ratioal\Classics Demo\ClassicsRepo Igore the value i the Project field. Click OK. The Ratioal TestMaager appears. 91

92 What Is Fuctioal Testig? Fuctioal testig helps you determie whether a system behaves as iteded. The most atural way to test a system s behavior is to use its GUI to validate that the system respods appropriately to user iput. Testig ca focus o both the operatio ad the appearace of GUI objects. Start with Requiremets To determie how a system is iteded to behave, you start with requiremets. I Uit 5, Test Plaig, you worked with test requiremets that were based o use case requiremets. I the first part of this uit, you use Ratioal TestMaager to work with those same test requiremets. Creatig a Script Durig testig, you focus o plaig, recordig, ad ruig scripts. A script has the followig compoets: A set of properties, such as the type ad purpose of the script. Typically, you defie the script s properties durig plaig. A file cotaiig scriptig laguage commads. You geerate a script file whe you record activities with Ratioal Robot. Determiig Which Script to Work O The ClassicsCD.com system has several test requiremets, all related to use case requiremets. I Uit 5, you traced the Arrage Shipmet test requiremet to its use case requiremet. Now use TestMaager to determie which test requiremets still eed scripts. Exercise Use TestMaager to report o which test requiremets do ad do ot have associated scripts. 1 From the TestMaager meu, click Reports > Ru. 2 O the Ru Report dialog box, select Test Reqmt. to Script Plaig Coverage ad click OK. 92 Ratioal Suite Tutorial

93 Selectig a Report to Ru 3 O the Select Requiremet dialog box, click All requiremets of type ad the select TC Test Case Specificatio Requiremet Type from the list. (Scroll up to see it.) Click OK. Selectig a Requiremet Type The report appears, showig the status of test plaig. The left colum shows the test requiremets. As you ca see, some test cases have scripts plaed; others do ot. 4 We will focus o test case TC12 Arrage Shipmet Fuctioality. Scroll to that test case ow. Notice that there are o scripts plaed for the test case. Plaig the Script Now that you kow which test case eeds a script, go to the requiremets view i TestMaager. I the followig exercise, you use the itegratio betwee RequisitePro ad Ratioal Test to pla the script. Exercise Use TestMaager to look at test requiremets ad to pla a script. 1 From the TestMaager meu, click File > Ope Requiremets. 2 From the TestMaager meu, click View > Select Requiremet Type > TC Test Case Specificatio Requiremet Type to display test case specificatios. Fuctioal Testig 93

94 The Requiremets Hierarchy, listig test case requiremets (TC), appears. The test requiremets you see here are the same requiremets you saw i RequisitePro. I fact, TestMaager loads the requiremets directly from the RequisitePro database. 3 Right-click requiremet TC12 Arrage Shipmet Fuctioality. From the shortcut meu, click Pla > GUI Script. 4 O the Pla Script dialog box: I the Name box, type Show Ship Date. I the Descriptio box, type: Shows date that order will ship. Click the Related Assets tab ad verify that there is a lik to TC12. Click OK. I the Requiremets Hierarchy, a script ico appears below the test requiremet. You have ow plaed a script. It has properties associated with it (for example, the ame ad descriptio), but it does ot yet have code. Requiremets Hierarchy after Plaig a Script 94 Ratioal Suite Tutorial

95 Recordig the Script After plaig a script, you record it. Whe you record a script, Robot traslates the activities you perform ito scriptig laguage commads. (Robot uses SQABasic for its scriptig laguage. SQABasic resembles Microsoft Visual Basic ad cotais additioal commads tailored for automated testig). After you record a script, you ca reuse it, for example, i regressio tests. Scripts ad Modularity The script you will record tests the ClassicsCD.com ehacemet, Arrage Shipmet. You could record a script that starts the applicatio, eters a sale, ad the verifies the reorder. However, you ca t reuse such a script without modifyig it. Istead, you ca create a set of scripts that all start with the same steps ad coclude by testig differet parts of the applicatio. Fortuately, Robot lets you create short modular scripts. You ca combie a series of scripts ito oe shell script (a Test Suite). With this techique, you ca reuse the same script i differet tests. Startig ad Preparig Robot Exercise Prepare to use Robot. 1 From the TestMaager meu, click Tools > Ratioal Test > Ratioal Robot to start Robot. 2 From the Robot meu, click Tools > GUI Playback Optios. 3 O the GUI Playback Optios dialog box, o the Log tab, select the followig: Output playback results to log View log after playback Specify log iformatio at playback 4 Click OK. Fuctioal Testig 95

96 Is Iteret Explorer Istalled? You ca record the ew script oly if Iteret Explorer is istalled o your system. (It does ot eed to be your default browser.) If Iteret Explorer is ot istalled o your system, cotiue readig this chapter ad resume performig the exercises startig with Addig the Show Ship Date Script to a Shell Script o page 100. Gettig to a Startig Poit I this sectio, you reuse a script that has already bee recorded to get the applicatio to a appropriate startig place for recordig the Show Ship Date script. Exercise Replay a script that completes a sale: 1 From the Robot meu, choose File > Playback. 2 O the Playback dialog box, select Tutorial Shell Buy Beethove Ad Bach from the list (type the first few letters to fid it more easily). Click OK. Robot displays a Specify Log Iformatio dialog box, which allows you to specify how to store test results. 3 From the Build list, select Build 1. (Use the defaults for the other values.) Click OK. 4 If Robot displays a cofirmatio dialog box askig if you wat to overwrite the log, click Yes. Do ot iteract with the ClassicsCD.com applicatio while Robot plays back the Cash Sale script! If you see a message box that starts Do you wat Widows to remember..., wait. Robot will evetually cotiue. The script trasacts a sale with two lie items ad a paymet. At certai poits, the script compares values i the applicatio to a baselie value. Whe the script fiishes, the Ratioal LogViewer appears, showig the results of the test. All or almost all the comparisos (the verificatio poits) pass. I some cases, you may see a warig ext to a lie that says Uexpected Active Widow. This warig meas that durig the playback, a extra widow appeared o your scree. Robot oticed the widow but the widow did ot iterfere with the test results. 96 Ratioal Suite Tutorial

97 If Robot retured the warig, double-click o the warig lie to see a screeshot of the uexpected widow. Whe you have fiished, close the Image Comparator widow. 5 Close the LogViewer widow. Startig to Record the Show Ship Date Script You are ow ready to record the Show Ship Date script. Exercise Start recordig the script from the poit where the Buy Beethove ad Bach script fiished. 1 I TestMaager, o the Requiremets Hierarchy widow, rightclick the Show Ship Date script. From the shortcut meu, select Record. The GUI Record toolbar appears. The GUI Record Toolbar Pause Recordig Stop Recordig Ope Robot Widow Display GUI Isert Toolbar 2 Click the title bar of Iteret Explorer to make it the active widow. 3 Scroll to the bottom of the Iteret Explorer widow. Notice that the estimated ship date is ow displayed. Creatig a Verificatio Poit I the followig steps, you create a verificatio poit, which establishes a baselie value for a specific part of the applicatio. Whe you play back the script, Robot compares the value it fids to the baselie value you establish. Fuctioal Testig 97

98 Exercise Create the verificatio poit. 1 O the GUI Record toolbar, click the Display GUI Isert Toolbar butto. 2 O the GUI Isert toolbar, click the Object Data butto. The Verificatio Poit Name dialog box appears. 3 I the Name box, type Verify Ship Date, the click OK. 4 From the Select Object dialog box, drag the had poiter to the lie o the Iteret Explorer widow that starts We estimate that your order... The Select Object dialog box briefly disappears ad the reappears. Draggig the Had Poiter to the Iteret Explorer 5 Click OK to close the Select Object dialog box. 6 The Object Data Tests dialog box appears. Click OK. The Object Data Verificatio Poit dialog box appears, showig the text that was captured. 7 O the Object Data Verificatio Poit dialog box: From the Verificatio method list, select Fid Sub Strig Case Sesitive. Uder Select the rage to test, scroll to lie 32 ( We estimate that... ) ad click it so that it is the oly lie selected. Click OK to close the dialog box. 98 Ratioal Suite Tutorial

99 Workig with the Object Data Verificatio Poit Dialog Box You have ow created a verificatio poit. The ext time this script rus, it will verify that the text you captured still appears. You ca iclude ay umber of verificatio poits i a script. This script has oly oe. 8 O the Iteret Explorer widow, click Place Order. Fiishig the Recordig Sessio You ca ow fiish the recordig sessio. Exercise Perform the fial steps i the script: 1 O the GUI Record toolbar, click Stop Recordig. Robot displays the Show Ship Date script. 2 Optioal: read the script commads ad otice how the commads correlate to the actios you took whe you recorded the script. Fuctioal Testig 99

100 Addig the Show Ship Date Script to a Shell Script Recall that before you recorded the Show Ship Date script, you first set up the applicatio by ruig the Tutorial Shell Buy Beethove Ad Bach script. Durig actual testig, you would have to replay Show Ship Date repeatedly. However, you would wat to avoid goig through maual steps to set up the applicatio each time. Istead, you ca add the Show Ship Date script to a existig shell script. The shell script calls other scripts that set up ad shut dow the applicatio. Exercise Add the Show Ship Date script to the shell script. 1 From the Robot meu, click File > Ope > Script. 2 I the Ope Script dialog box, select Tutorial Shell Shop for CDs ad click OK. Robot displays the Tutorial Shell Shop for CDs script. This script calls other scripts; it does ot directly iteract with the applicatio. 3 Take oe of the followig steps, depedig o whether Iteret Explorer is istalled o your system: Iteret Explorer is istalled. I the space after CallScript "Tutorial - Proceed to Cashier", add the lie: CallScript "Show Ship Date" Addig a Lie to the Shell Script Iteret Explorer is ot istalled. A quote character precedes commeted code. Remove the quote character from the begiig of the gree lie, CallScript "Tutorial Show Ship Date for Netscape". (We have recorded a script for you that performs the work i the Show Ship Date script.) 100 Ratioal Suite Tutorial

101 4 From the Robot meu, click File > Save. The scripts ad shell scripts you develop form a set of regressio tests that you ru after every software build. The outcome of a particular test may chage durig subsequet iteratios as old defects are fixed ad ew defects ad other chages are itroduced. Playig Back the Script O a New Build While you were workig, the developers delivered a ew build of ClassicsCD.com. Exercise Ru the Test Suite o the ew build. Aalyzig the Results 1 From the Robot meu, click File > Playback. 2 Verify that the Playback dialog box selects the Tutorial Shell Shop for CDs script. Click OK. 3 I the Specify Log Iformatio dialog box, i the Build box, select Build 2. Click OK. 4 If Robot displays a cofirmatio dialog box askig if you wat to overwrite the log, click Yes. Resist the temptatio to iteract with the applicatio as Robot plays back the series of scripts. If you see a message box that starts Do you wat Widows to remember..., wait. Robot will evetually cotiue. Robot starts the applicatio, iteracts with it, captures data at verificatio poits, ad quits the applicatio. Whe it has fiished ruig the script, it displays the results of the test i the LogViewer. The LogViewer shows which verificatio poits passed ad which failed. The script you recorded, Show Ship Date, passes despite the UI chages i Build 2. However, the Cash Sale script has failures. Recall that whe you played back Cash Sale o Build 1, it passed. Fuctioal Testig 101

102 Hadlig a Itetioal Chage Exercise Ispect the failure o the third lie ad decide how to hadle it. 1 I the LogViewer, double-click the failure, Verificatio Poit (Logo). Selectig the First Failure The Object Properties Comparator for the logo appears, showig that the logo chaged from classicscdsplash.jpg to classicscdlogo.jpg. It turs out that this was a plaed chage ad results from the UI modificatios metioed earlier. I this case, you wat to chage the baselie so that the ext time the script plays back, it compares the logo to the ew value. (You chage the baselie whe a test fails because of a itetioal chage i the applicatio.) 2 From the meu, click File > Replace Baselie with Actual. O the cofirmatio dialog box, click Yes to direct Robot to perform the replacemet. The Comparator updates the baselie ad reports that there are o differeces. 3 Close the Object Properties Comparator. Hadlig a Real Error Exercise Ispect the secod failure ad determie how to hadle it. 1 I the LogViewer, uder Call Script (Tutorial Proceed to Cashier), double-click the ext failure, Verificatio Poit (Cart Cotets). The Object Properties Comparator appears. 102 Ratioal Suite Tutorial

103 O lie 2, the baselie shows that you were expectig to purchase a Beethove Symphoy, but the actual item placed ito your shoppig cart was a Mozart Symphoy. This is a real error. 2 Close the Object Properties Comparator. Reportig the Error To report the error, use ClearQuest, which is itegrated with Ratioal LogViewer. Exercise Report the error. 1 From the LogViewer meu, click Defect > Geerate. If the meu commad appears dimmed, ClearQuest is ot istalled o your system ad you caot complete this exercise. 2 If ClearQuest displays the Schema Repository User GUI dialog box, choose ad click OK. (This dialog box allows you to work with a database schema from the curret ClearQuest release or from a previous release.) 3 If ClearQuest displays a Logi dialog box, i both the User Name ad Password boxes, type pat. If the Database list is eabled, choose CLSIC: Ratioal Demo. Click OK. A Submit Defect dialog box opes. Red items are required: you caot submit the defect util all required fields cotai valid values. A tab with a red square idicates that the tab cotais required items. 4 I the Headlie box, type: Wrog item i shoppig cart 5 From the Severity list, select 2-Major. 6 O the other tabs, for example, Test Data, Ratioal Test has already filled i fields related to the test script. Fuctioal Testig 103

104 The Defect You Will Submit 7 Click OK to close the Submit Defect dialog box. I the LogViewer, the defect ID appears ext to the Cart Cotets failure. You have fiished testig this iteratio of ClassicsCD.com. Summary For More Iformatio For more iformatio about testig strategy, click Help > Exteded Help from a Ratioal Test tool meu. I the Exteded Help browser, read the articles uder Cocepts. To get started with Ratioal Test tools, read Gettig Started with Robot, available o the Ratioal Solutios for Widows Olie Documetatio CD. 104 Ratioal Suite Tutorial

105 To lear more about performace testig, see Gettig Started with Ratioal Suite PerformaceStudio. Cleaig Up Quit ay ope Ratioal Test tools. What You Leared i this Uit I this uit, you leared: Fuctioal testig helps you determie whether a system behaves as iteded. Ratioal Test helps you pla, develop, ru, ad aalyze fuctioal tests. You develop test scripts by iteractig with the applicatio usig Robot ad icludig verificatio poits i your scripts. You ca develop modular scripts, the use shell scripts to call those scripts. You reuse scripts each time developers deliver a ew software build. Robot makes it easy to address problems ad updates that are discovered durig testig. What s Next You are early fiished with the tutorial! I the ext uit, you pla the ext iteratio of ClassicsCD.com. Fuctioal Testig 105

106 106 Ratioal Suite Tutorial

107 RATIONAL SUITE TUTORIAL Plaig the Next Iteratio The ClassicsCD.com ehacemet is ow complete. You have fiished work o this iteratio. This uit describes the ext steps. Audiece This uit applies to all members of a software developmet team. Gettig Your Bearigs I this uit, you use Ratioal ClearQuest. Refer to the tool chart you filled out (Table 1, Ratioal Suite Tools, o page 25) to determie whether ClearQuest is istalled o your system. If ClearQuest is ot istalled, you ca still beefit from readig this uit, but you will ot be able to perform the exercises. If ClearQuest is istalled, start it ow: 1 Click the Start butto ad choose Programs > Ratioal Suite > Ratioal ClearQuest. 2 If ClearQuest displays the Schema Repository User GUI dialog box, choose ad click OK. (This dialog box allows you to work with a database schema from the curret ClearQuest release or from a previous release.) 3 I the ClearQuest Logi dialog box: I both the User Name ad Password boxes, type pat. From the Database list, choose CLSIC: Ratioal Demo. Click OK. ClearQuest displays two paes. The left pae lists a hierarchy of charts ad reports you ca view. The right pae is blak. 107

108 Assessig the State of your Project I Uit 9, Fuctioal Testig, you used ClearQuest to report a defect i the software. I this uit, you use ClearQuest charts ad queries to assess the state of your project. ClearQuest is a chage request maagemet tool that helps you track ad maage all the chage activities (such as defects ad ehacemet requests) associated with a project. ClearQuest stores its iformatio i a database, ad comes with a ready-to-use database schema (the fields i the database). ClearQuest is easy to chage; a admiistrator ca customize ad defie queries, fields, activities, ad states specific to your developmet process. Showig the Workload At the ed of a iteratio, you probably wat to review each project member s workload so that you ca most effectively allocate work for the ext iteratio. Exercise Display a chart showig workload. 1 I the left pae of ClearQuest, avigate to: Public Queries > Distributio Charts All Projects > Defects by Ower > State. Double-click this etry. Choosig the Chart, Defects by Ower ad State 108 Ratioal Suite Tutorial

109 ClearQuest displays the workload chart. Maximize the chart to see the details more clearly. Notice that Devo has just oe defect assiged. The turquoise bar o the left represets uassiged defects. 2 Click a bar to see the ower, state, ad umber of defects. 3 Double-click the turquoise bar (the leftmost bar) to list the defects summarized i that bar. ClearQuest displays a cofirmatio dialog box askig if you wat to create a query. 4 Click OK. ClearQuest lists the defects ad displays details about the selected defect. You ca edit the detailed defect. ClearQuest ca help you pla a ew iteratio. Now that you have listed the uassiged defects, you ca assig them (o the Mai tab) ad lik them to requiremets (o the Requiremets tab). So from geeral iformatio, you ca easily avigate to details. Assigig a Ehacemet Request Recall that you started the tutorial by lookig at a ehacemet request that you the implemeted. Now fid aother ehacemet request to implemet i the ext iteratio. Exercise Start by examiig the ehacemet requests: 1 I the left pae of ClearQuest, avigate to Public Queries > Uassiged ERs. Double-click this etry. 2 I the list at the top of the right pae, click CLSIC , curret member base with mothly specials to display the ehacemet request s details. 3 Optioal: Click the request s tabs to lear more about the request ad its history. 4 Click Actios, the select Assig. Notice that some fields tur white, idicatig that you ca chage them. Also, o tabs where you must fill i a field, a red square appears. 5 Click the Aalysis tab. Plaig the Next Iteratio 109

110 The Ower field is red, idicatig that a value is madatory. Recall that Devo does ot have a lot of assiged work right ow. 6 From the Ower list, select devo. 7 Click Apply. Other Plaig Activities Durig a iteratio, you usually work both to correct defects ad to implemet ehacemets. As part of plaig, you might also use RequisitePro or ClearQuest to idetify defects to implemet i the ext iteratio. Durig iteratio plaig, you ca produce a Ratioal SoDA report showig the defects ad ehacemets plaed for the ext iteratio. What Will Happe i the Next Iteratio? The ext iteratio will proceed much as this oe has. Oce it s plaed, the followig activities will traspire: A aalyst discusses plaed ehacemets with stakeholders. Usig RequisitePro ad Rose, the aalyst creates oe or more use cases ad supplies step-by-step details, icludig basic flow ad alterative flows. A test egieer uses Ratioal TestMaager to pla the tests for this iteratio. The egieer writes a test pla documet, develops test requiremets, ad desigs the tests. A developer uses Rose ad visual modelig techiques to describe how plaed ehacemets fit withi the architecture of the system. Ayoe o the team ca use SoDA to create a use case report. This report is useful durig discussios with stakeholders ad desig sessios. Developers use Rose to iitiate implemetatio of the ehacemet. Test egieers use TestFactory, Purify, Quatify, ad PureCoverage to verify the iteratio s reliability. 110 Ratioal Suite Tutorial

111 Test egieers use Ratioal TestMaager ad Robot to verify that the ehacemets meet requiremets that defects are fixed correctly, ad that o regressio failures have occurred. Meawhile, project ad group maagers use ClearQuest, SoDA, ad RequisitePro to assess that state of the project. Later, they use these tools to pla subsequet iteratios. Cofiguratio Maagemet This tutorial does ot discuss cofiguratio maagemet, a crucial compoet of ay software developmet eviromet. Cofiguratio maagemet is the process of cotrollig chages to, ad maitaiig the itegrity of, your project s code ad other artifacts. Ratioal ClearCase, the premier cofiguratio maagemet solutio, is the perfect complemet to Ratioal Suite because it is itegrated with Ratioal Suite tools ad with Microsoft Visual Studio. ClearCase provides a uified approach to maagig chage throughout the software developmet lifecycle. As part of a total chage maagemet solutio that spas cofiguratio maagemet, chage request maagemet, ad workflow automatio, ClearCase ca help you streamlie ad simplify the process of chage. Summary For More Iformatio For more iformatio about ClearCase, please see the followig Web page: To lear more about topics described i this tutorial, cosider takig a Ratioal Uiversity course. I these courses, you ca get hads-o experiece with a specific tool, or you ca lear more about software egieerig priciples (Object Orieted Aalysis ad Desig, Automatig Software Test, ad so o). To lear more about these courses, please see Plaig the Next Iteratio 111

112 Cleaig Up Whe you are ready, quit ClearQuest. What You Leared i this Uit I this uit ad tutorial, you leared: ClearQuest is a powerful tool that helps you maage ad moitor chage requests o your project. ClearCase is a importat tool that assists with cofiguratio maagemet. It is the perfect complemet to Ratioal Suite. What You Leared i this Tutorial Ratioal Suite uifies your team by ehacig team commuicatio. Ratioal Suite optimizes idividual team member productivity by providig market-leadig developmet tools. Ratioal Suite simplifies adoptio by providig a comprehesive set of itegrated tools that have simple istallatio, licesig, ad user support. Ratioal Suite supports the etire developmet life cycle ad the primary participats o a developmet team aalysts, developers, testers, ad maagers. What s Next Cogratulatios! You have fiished the Ratioal Suite tutorial. Your ext job is to fid out more about the tools you will use o your ext project ad to get to work! We hope that by usig Ratioal Suite, you will esure your ow cotiued success. 112 Ratioal Suite Tutorial

113 RATIONAL SUITE TUTORIAL Glossary activity A uit of work that a team member performs. actor Someoe or somethig, outside the system or busiess, that iteracts with the system or busiess. aalyst A perso who determies what the system does, specifies ad maages requiremets, ad represets the user s eeds to the developmet orgaizatio. artifact A piece of iformatio that is produced, modified, or used by a process; defies a area of resposibility; ad is subject to versio cotrol. There are may types of artifacts, icludig requiremets, models, model elemets, ad documets. automated testig A testig techique wherei you use software tools to replace repetitive ad error-proe maual work. Automated testig saves time ad eables a reliable, predictable, ad accurate process. class I object-orieted programmig, a set of objects that share the same resposibilities, relatioships, operatios, attributes, ad sematics. compoet A o-trivial, early idepedet, ad replaceable part of a system that fulfills a clear fuctio i the cotext of a well-defied architecture. 113

114 compoet-based architecture A desig techique i which a software system is decomposed ito idividual compoets. cofiguratio maagemet Helps teams cotrol their day-to-day maagemet of software developmet activities as software is created, modified, built, ad delivered. Comprehesive software cofiguratio maagemet icludes versio cotrol, workspace maagemet, build maagemet, ad process cotrol to provide better project cotrol ad predictability. developer A perso who determies how the system works; defies the architecture; ad creates, modifies, ad maages the code. Exteded Help A powerful feature of Ratioal Suite that provides liks to the Ratioal Uified Process ad ay customized iformatio you wat to add. forward egieerig The process of geeratig code from a Ratioal Rose visual model. See visual model. iterative developmet The process of deliverig a distict sequece of executable files accordig to a pla ad evaluatio criteria over the course of a project. Each executable file is more robust or cotais more features tha the previous executable file; each ew iteratio moves you closer to the goal of deliverig a successful project. method I object-orieted programmig, the implemetatio of a operatio or procedure. metrics The measuremets of project activity. 114 Ratioal Suite Tutorial

115 object I object-orieted programmig, a software package that cotais a collectio of data ad methods (procedures) for operatig o that data. Ratioal Admiistrator Tool that maages Ratioal repositories. For more iformatio, see Usig the Ratioal Admiistrator. Ratioal ClearCase Provides comprehesive cofiguratio maagemet, icludig versio cotrol, workspace maagemet, build maagemet, ad process cotrol. Ratioal ClearQuest A highly customizable Widows ad Web-based chage request maagemet tool that lets users track ay type of chage activity bug fixes, ehacemet requests, documetatio chages, ad so o throughout the software developmet lifecycle. Ratioal PureCoverage Automatically pipoits areas of code that have ot bee tested. Ratioal Purify Automatically pipoits hard-to-fid rutime memory errors i Widows NT applicatios. Ratioal Quatify Automatically pipoits performace bottleecks i Visual Basic, Visual C++, ad Java applicatios. Ratioal RequisitePro Helps teams easily ad comprehesively orgaize, prioritize, track, ad cotrol chagig requiremets of a system or applicatio. Ratioal RequisitePro does this through a deep itegratio with Microsoft Word ad a secure, multi-user database. Glossary 115

116 Ratioal Robot Helps with fuctioal testig by automatig record ad playback of test scripts. Lets you orgaize, write, ad ru test suites, ad capture ad aalyze the results. Ratioal Rose The world s leadig visual compoet modelig ad developmet tool; lets you model software applicatios that meet curret busiess eeds. Ratioal SoDA for Word Software Documetatio Automatio Overcomes the obstacles of cosolidatig data from differet developmet tools. Lets you automate the creatio of comprehesive software, systems, ad project documets from multiple sources. Ratioal Suite A easy-to-adopt-ad-support solutio that optimizes the productivity of aalysts, developers, ad testers ad uifies them, creatig highly effective software developmet teams. Ratioal Suite AalystStudio Editio of Ratioal Suite optimized for aalysts. Cotais the team uifyig tools Ratioal Uified Process, RequisitePro, ClearQuest, ad SoDA ad Ratioal Rose (Modeler Editio). Ratioal Suite DevelopmetStudio Editio of Ratioal Suite optimized for system developers ad desigers. Cotais the team-uifyig tools Ratioal Uified Process, RequisitePro, ClearQuest, ad SoDA plus Ratioal Rose (Eterprise Editio), Ratioal Purify, Ratioal Quatify, ad Ratioal PureCoverage. Ratioal Suite DevelopmetStudio - RealTime Editio Editio of Ratioal Suite optimized for system developers ad desigers of real-time or embedded systems. Cotais the team-uifyig tools Ratioal Uified Process, RequisitePro, ClearQuest, ad SoDA plus Ratioal Rose RealTime, Ratioal Purify, Ratioal Quatify, ad Ratioal PureCoverage. 116 Ratioal Suite Tutorial

117 Ratioal Suite Eterprise Editio of Ratioal Suite cotaiig all Ratioal Suite tools except Ratioal LoadTest. Ratioal Suite PerformaceStudio Editio of Ratioal Suite optimized for test egieers who develop ad ru performace tests. Cotais the team-uifyig tools Ratioal Uified Process, RequisitePro, ClearQuest, ad SoDA plus Ratioal Test tools, Ratioal Rose (Eterprise Editio), ad Ratioal LoadTest. Ratioal Suite TestStudio Editio of Ratioal Suite optimized for test egieers. Cotais the team uifyig tools Ratioal Uified Process, RequisitePro, ClearQuest, ad SoDA ad Ratioal Test tools. Ratioal Sychroizer Uses rules, either predefied or user-supplied, to give you a quick start o ew work. Creates or updates project items based o the existece of other items i your project, esurig that details do ot fall through the cracks. Ratioal TestFactory Automates reliability testig by combiig automatic test geeratio with source code coverage aalysis. Ratioal Uified Process A Web-eabled, searchable kowledge base that ehaces team productivity ad delivers software best practices via guidelies, templates, ad Tool Metors for all critical software developmet activities. real-time applicatio A applicatio or system with striget requiremets for latecy, throughput, reliability, ad availability. requiremet A coditio or capability of a system, either derived directly from user eeds or stated i a cotract, stadard, specificatio, or other formally imposed documet. Glossary 117

118 requiremets maagemet A systematic approach to elicitig, orgaizig, ad documetig a system s chagig requiremets, ad establishig ad maitaiig agreemet betwee the customer ad the project team. reverse egieerig The process of updatig a Rose visual model from code, so that the visual model ad code match. See visual model. risk The probability of adverse project impact (for example, schedule, budget, or techical). risk maagemet Cosciously idetifyig, aticipatig, ad addressig project risks ad devisig plas for risk mitigatio, as a way of esurig the project s success. roud-trip egieerig The ability to do both forward ad reverse egieerig as ofte as eeded. test egieer A perso who creates, maages, ad executes tests; esures that the software meets all its requiremets; ad reports the results ad verifies fixes. Tool Metor Step-by-step istructios o how to use a specific Ratioal tool to perform a activity described i the Ratioal Uified Process. traceability The ability to trace oe project elemet to other, related project elemets. Uified Modelig Laguage (UML) The idustry-stadard laguage for specifyig, visualizig, costructig, ad documetig software systems. It simplifies software desig, ad commuicatio about the desig. 118 Ratioal Suite Tutorial

119 use case A sequece of actios a system performs that yields observable results of value to a particular actor. A use case specificatio cotais all the mai, alterate, ad exceptio flows of evets related to producig the observable result of value. versio cotrol The process of trackig the revisio history of files ad directories. visio documet A documet that cotais a high-level view of the user s or customer s uderstadig of the product to be developed. visual model A graphic represetatio of a system s structure ad iterrelatioships. worker The role played by a idividual team member. workflow The sequece of activities performed i a busiess that produces a valuable result to a idividual actor i the busiess. Glossary 119

120 120 Ratioal Suite Tutorial

121 RATIONAL SUITE TUTORIAL Idex A activity 36, 113 actor 39, 113 aalyst 19, 113 AalystStudio 19, 116 architecture compoet-based 16 visual modelig 68 artifact 36, 113 automated testig 113 B best script 84 best script, TestFactory 85 budget ad predictability 33 C chage cotrol 17 child requiremet 52 class 113 class diagram 75 idetifyig i Rose 75 Classics istallig 26 ruig 29 ClassicsCD.com overview 28 ClearCase 111, 115 ClearQuest 18, 107, 115 ad Robot 103 assessig project status 108 attachig database to a repository 27 startig 107 code, implemetig 75 compoet 16, 113 compoet-based architecture 114 cofiguratio maagemet 111, 114 cotrollig software chages 17 D database ad RequisitePro 47 defect reportig 103 defect script, TestFactory 85 desigig compoet-based architecture 16 tests 61 developer 19, 114 developig software See software developmet DevelopmetStudio 19, 116 DevelopmetStudio - RealTime Editio 20, 116 diagram widow, Rose 48, 68 documet, i RequisitePro 47 E Eterprise Editio Ratioal Suite 117 Rose 20 error reportig 103 Exteded Help 54, 114 F forward egieerig 114 fuctioal testig 91 G GUI Record toolbar 97 H Help, Exteded 54 Idex-121

122 I implemetig code 75 istallig tutorial sample applicatio 26 istrumetig i TestFactory 84 iterative developmet 16, 114 ad Ratioal Uified Process 35 J Java ad PureCoverage 88 ad Quatify 89 ad Rose 75 L lik requiremets ad defects 109 suspect, RequisitePro 53 traceability, RequisitePro 53 LoadTest 22 LogViewer ad Robot 101 M maagig requiremets See requiremet, maagig maagig risk 59 maagig software chages 17 mappig a applicatio i TestFactory 84 memory leaks 86 method 114 metrics 114 Microsoft Project, ad RequisitePro 64 Microsoft Visual Basic ad PureCoverage 88 ad Quatify 89 ad Rose 75 Microsoft Visual C++ ad PureCoverage 88 ad Purify 86 ad Quatify 89 ad Rose 75 Microsoft Word ad RequisitePro 46 ad SoDA 80 Modeler Editio Rose 19 modelig visually See visual modelig O object 115 idetifyig i Rose 75 P paret requiremet 52 performace testig 89 PerformaceArchitect 22 PerformaceStudio 22, 117 Pilot ruig, i TestFactory 85 plaig a script, TestMaager 93 playig back a script 101 prerequisites of tutorial 25 process See Ratioal Uified Process project state, assessig 108 PureCoverage 20, 88, 115 ad Java 88 ad Microsoft Visual Basic 88 ad Microsoft Visual C++ 88 Purify 20, 86, 115 ad Microsoft Visual C++ 86 Q quality egieer, role of 21 quality, verifyig See testig Quatify 20, 89, 115 ad Java 89 ad Microsoft Visual Basic 89 ad Microsoft Visual C++ 89 R Ratioal Admiistrator 115 attachig ClearQuest database to a repository 27 registerig a repository 26 Ratioal ClearQuest See ClearQuest Ratioal LoadTest 22 Ratioal PerformaceArchitect 22 Idex-122

123 Ratioal PureCoverage See PureCoverage Ratioal Purify See Purify Ratioal Quatify See Quatify 20 Ratioal RequisitePro See RequisitePro Ratioal Robot See Robot Ratioal Rose See Rose Ratioal Rose RealTime 20 Ratioal SoDA See SoDA Ratioal Software, missio 15 Ratioal Suite 116 AalystStudio 19, 116 ad ClearCase 111 beefits 18 DevelopmetStudio 19, 116 Eterprise Editio 117 PerformaceStudio 22, 117 TestStudio 21, 117 tools 18, 25 Ratioal Suite DevelopmetStudio - RealTime Editio 20, 116 Ratioal Suite Sychroizer 117 Ratioal TestFactory See TestFactory Ratioal Uified Process 18, 33, 117 Exteded Help 54 overview 33 phases ad iteratios 35 startig 33 tool metor 40 real-time applicatio 117 RealTime Editio, DevelopmetStudio 20 RealTime Editio, Ratioal Suite 116 RealTime Editio, Rose 20 recordig a script, Robot 95 registerig a repository 26 reliability testig 83 reports, creatig with SoDA 80 repository attachig ClearQuest database 27 registerig 26 repository project 26 requiremet 117 ad chage 45 ad testig 92 ad TestMaager 92 ad visio documet 45 child 52 defiitio 44 maagig 16, 43, 45, 118 paret 52 test requiremet 59 types 54 RequisitePro 18, 43, 115 ad Rose 50 database features 47 documet features 47 itegratio with Microsoft Project 64 startig 43 test plaig 57 Tool Palette 43 Views Workplace 47, 51 Word Workplace 46, 47 resettig tutorial 26 reverse egieerig 118 risk 118 risk maagemet 59, 118 roadmap, tutorial 31 Robot 21, 91, 116 ad ClearQuest 103 ad TestFactory 86 GUI Record toolbar 97 playig back a script, Robot 101 recordig a script 95 reviewig test results 101 startig 95 Rose 67, 116 ad RequisitePro 50 browser 48, 68 class diagram 75 diagram widow 48, 68 Eterprise Editio 20 Java 75 Microsoft Visual Basic 75 Microsoft Visual C++ 75 Modeler Editio 19 startig 47, 67 Web publishig 73 Rose RealTime 20 roud-trip egieerig 118 ru-time errors 86 Idex-123

124 RUP See Ratioal Uified Process S schedule predictability 33 test efforts 63 script best script, TestFactory 85 creatig, TestMaager 92 defect script, TestFactory 85 plaig, TestMaager 93 playig back, Robot 101 recordig, Robot 95 shell 100 sequece diagram 69 ad use case 69 shell script 100 SoDA 19, 79, 116 ad Microsoft Word 80 overview 80 startig 79 template 82 software developmet commo problems 15 compoet-based architecture 16 cotrollig chage 17 iterative developmet 16 maagig requiremets 16 verifyig quality 17 visual modelig 17 software egieer, role of 19 SQABasic 95 suspect lik i RequisitePro 53 T test case 62 test egieer 21, 118 test plaig 57 ad use cases 61 creatig scripts 93 idetifyig risks ad resources 63 schedulig 63 test types 63 test requiremet 59 test suite 85 ad Robot 95 test, desigig 61 tester, role of 21 TestFactory 21, 83, 117 ad Robot 86 istrumetig 84 mappig a applicatio 84 overview 83 ruig a Pilot 85 testig ad requiremets 92 ad scripts See script coverage 88 fuctioal 91 memory leaks 86 performace 89 plaig activities 57 reliability 83 ru-time errors 86 verificatio poit 97 verifyig quality 17 TestMaager 91 ad requiremets 92 plaig scripts 93 reports 92 startig 91 viewig test requiremets 93 TestStudio 21, 117 tool metor 40, 118 Tool Palette, RequisitePro 43 tools i Ratioal Suite 18, 25 traceability 118 liks 53 tutorial ClassicsCD.com 28 overview 28 prerequisites 25 resettig 26 roadmap 31 sample applicatio 28 settig up 26 tool checklist 25 U UML 118 See Uified Modelig Laguage 19 Uified Modelig Laguage 19, 23, 118 Uified Process See Ratioal Uified Process Idex-124

125 use case 39, 119 ad sequece diagram 69 ad test plaig 61 ad visual modelig 46 beefits to team 46 report 79, 80 use case diagram defiitio 48 workig with 49 V verificatio poit 97 verifyig software quality See testig versio cotrol 119 view, RequisitePro 51 Views Workplace i RequisitePro 47 visio documet 119 ad requiremets 45 visual modelig 17, 67, 68, 119 implemetig code 75 maitaiig cosistecy with code 75 W Web versios of Rose models 73 Word Workplace i RequisitePro 47 worker 36, 119 workflow 37, 119 Idex-125

126 Idex-126