Home

TEMPPO Requirement Manager User Manual

1. Figure 125 Settings Telelogic DOORS DOORS user password and path to DOORS exe are needed for the start of connection to the DOORS server see chapter 2 5 1 With the field Parameters you specify e g the database connection as DOORS command line parameter data port server Specifies which DOORS database to use The parameter specifies the port that the server is using and the name of the server computer for example 36677 myserver Note that a DOORS 8 2 client can t use a pre 8 0 database server The path to DXL defines where TEMPPO copies DXL scripts needed for the DOORS communication 2 17 5 3 2 IBM Rational RequisitePro The version of RequisitePro can be changed here Page 90 User Manual TEMPPO V6 2 Edition January 2015 Description of Use IBM Rational RequisttePro User Interface Tree M Supported IBM Rational Requisite Pro versions i Mewsboard e Database Fl Requirement Management C70 C704 IBM Telelogic DOORS e Gh Rational Requisite Pro Please select the version of RequisitPra which is installed on your PC Restore Defaults Figure 126 Settings RequisitePro e Use Case RequisitePro is already installed If RequisitePro is already installed and TEMPPO is just installed TEMPPO gets the RequisitePro version from MS Windows registry and stores it In case of a not supported RequisitePro version the last supported one will be stored e
2. Requirement Manager Test Execution Sahdgina Planning and rePorting Organizer TEMPPO Requirement Manager User Manual Edition January 2015 Copyright Atos IT Solutions and Services GmbH 2015 Microsoft MS MS DOS and Windows are trademarks of Microsoft Corporation The reproduction transmission translation or exploitation of this document or its content is not permitted without express written authority Offenders will be liable for damages All rights reserved including rights created by patent grant or registration of a utility model or design Right of technical modification reserved User Manual TEMPPO V6 2 Edition January 2015 Contents Contents 1 THEFOQUCUION sssaaa a aaa Aaaa 6 2 Description OF USC accipe Ewa aana RT PREX RC RE C T RR 7 2 1 Create anew Requirement StruUctUre 25s oc Nd EIER Ee IDEEN a 7 2 2 Open an existing Requirement Structure eeeeseeeerneenn nnn 8 2 3 Create Ene Requirements eeevisc va ey vas vixwrUPisM ioter dV A NEE E PUES 9 2 29 1 Create manually oirnne a es ru vIAE vor u POR OPER PLU PED FRE EE CENE 9 LC ADUT eraa e 11 2 5 152 PISCO ponoc rini edes ebat ipid FAM E Des uM M p MIU ip 12 2i2 2 ImDpOLUDSg TOM CSV acir pati dX ped bip uoa Vou Dd bd n Patr duda 14 24 iEditRequiremelbltesusitasscuistiMume en poa aa cente DON EUM MN LEE 16 2 5 Import a whole Requirement Structure eeeeeeeeennn nn nennen 16 2o5uL IDOT trom RM TOOlsssauevvss
3. 2 12 1Merge If you updated a requirement structure from XML or csv with a faulty file you have the possibility to undo it by a merge of a previous version to the latest version Activate the version you want to have as new latest version and press the button Merge 2 12 2Delete A version can only be deleted if another version is activated You cannot delete the current activated version If you updated a requirement structure from an RM tool and you have to undo it you can select the version and press the button Delete 2 13 Split Requirement Structures Since huge manual requirement structures 10000 requirements on first level are uncomfortable to handle long loading periods for editing and assigning the split feature allows to move specific requirements to a new requirement structure Assignments to test cases are not affected by this process i e a newly created requirement structure is automatically assigned to all affected projects and test structures Page 54 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Only first level requirements are moved i e if a first level requirement is moved it is moved to the new requirement structure with its entire sub tree see example below Splitting is done over all version of a requirement structure The new requirement structure will have exactly the same version tree as its source Via Requirement Structure Split the split dialog is opened the
4. Figure 90 Reporting Load template file There is the restriction that you must save the dot file as xml TEMPPO supports only the XML format If Microsoft Excel is selected then you can define a header and footer within the settings see Figure 92 Please consider that Microsoft Word limits the width of pages to 22 inches http support microsoft com scid kb 3Ben us 3B95109 amp x 14 amp y 10 Title Page Here you can customize the title page of your report The Title page can contain a title a project name a status the name of the author and the current date You can also specify if the label should be visible Page 69 User Manual TEMPPO V6 2 Edition January 2015 Description of Use EK TEMPPO report setting for requirement structure i x Mame hen Report Setting El Settings eral gt Projecttitle Header Footer Text El Continucus Report Prajectname Praecname O l F Requirement i Requirement Status Projectstate Date Author Show labels Preview Cancel Figure 91 Reporting Title Page Header Footer You can customize the header and footer for your report There are buttons for using the defined keys for page number date time etc FK TEMPPO report setting for requirement structure x Mame New Report Setting ESettings EF General j sud Title Page To add a page number date time ar file insert position the cursor in the edit box and then
5. updatedrms selectable 0 coveredbytcs 5 lt DESCRIPTION gt lt CDATA lt htm1 gt lt head gt lt head gt lt body gt lt p gt import from XML file2 amp 160 lt p gt lt body gt lt html gt gt lt DESCRIPTION gt USER DEFINED ATTRIBUTE name Requirment attribute value high type 32 gt lt REQUIREMENT gt lt RS gt TEMPPO EXCHANGE 2 5 3 Update With this feature you can update requirement structures imported from e DOORS e Requisite Pro e XML e CSV There is a feature for undo a faulty update On the one hand you can merge any version to latest one in case of a manual requirement structure see chapter 2 12 On the other hand you can delete the latest requirement structure version if it is not used yet in test management in case of imported requirement structures from 3 party products see chapter 2 12 2 5 3 1 DOORS In TEMPPO Requirement Manager data imported from DOORS cannot be updated by a TEMPPO user DOORS requirements can be updated in DOORS and imported in TEMPPO or changed in latest The update function is the same as in 2 5 1 2 This function checks in the actual latest version see also 2 11 and updates the Page 34 User Manual TEMPPO V6 2 Edition January 2015 Description of Use new latest version of the requirement structure irrespective of the activated version By pressing the menu item Requirement Structure gt Update the requirement update pro
6. Rea Replace with Direction C Up Caze Sensitive Down Find Mest Find Mest Requirement Replace Replace Al List Occurrences Close Replace All in Requirement Figure 119 Find and Replace A requirement can be found via searching for its user defined ID name short description or description The search criteria can be specified using the wildcards 0 n arbitrary characters or and Exactly one arbitrary character and is case sensitive The replace function searches for the requirement and then the searched part will be replaced to the entered name The replace function is available for name short description and description Example You want to change the name of the requirements The part Requirement Should be changed to the German name Anforderung so you select Name in Search in and write in the text field for Requirement In the Replace with text field you write Anforderung A searching direction can be chosen too The searching algorithm starts from the selected node in the tree Is the tree root selected the whole tree is searched whatever direction is selected 2 17 4 1 Find There are two possibilities for finding requirements e Find Next With clicking Find Next the first requirement is searched and selected in the tree With the next click the next one is searched If there is no element anymore a message is shown see Figure 120
7. a ee Ce Aa Beto re you can use this requirement structure in TEMPPO you have to assign it to a project Do you want to do this now Figure 42 Assign requirement structure to project After pressing Yes the requirement structure is assigned to the project and a baseline V1 is created and the requirements cannot be changed in TEMPPO Requirement Manager The only way to change requirements is to do it in Enterprise Architect and update the requirements in TEMPPO Requirement Manager Mame Requirements Model Prefix Owner Testmanager Created 31 10 2014 12 04 29 Creator in Enterprise Architect XMI 2 1 Created in Enterprise Architect XMI 2 1 31 10 2014 12 04 29 Type Enterprise Architect XMI 2 1 Figure 43 Imported Requirement Structure 2 5 1 3 2 1 Enterprise Architect TEMPPO Data matching The following table gives a review about data matching from EA to TEMPPO Since EA has no individual field for Requirement ID user selects it during import In our example Alias is used All EA Properties and Tagged Values are matched to TEMPPO requirement attributes Page 29 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Enterprise Architect TEMPPO Requirement Manager Requirement ID Alias was selected as ID was selected as ID Short Description oe Name Description import Creator in EA Created in EA Remains an requir
8. au swem lbsrmwc A woms58 Zuletzt verw E Desktop 1 Eigene Dateien Ls Arbeitsplatz L Metzwerkum File name fitter Save Files of type m Document File xml Cancel Page 63 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Figure 83 Export dialog 2 14 9Import filter It is possible to import filters from XML either directly by pressing the button Import filter from XML A filter import is rejected if the filter contains specific requirement attributes that are not assigned to the requirement structure the filter is imported to An error message is displayed where the names of the NOT imported filters are listed The filter contents are checked and the import is only successful if the attributes match the ones of the selected requirement structure If the filter is not syntactically correct the import is cancelled and the user gets an information message 2 15 Evaluation 2 15 1Analysis The analysis feature is used to give you a quick overview about your requirement structure You create an analysis chart by selecting the node to analyze and activating Evaluation gt Analyse In the Analysis dialog you can set values for X Axis and group values on the Y Axis The following charts for displaying the data are possible e Horizontal bar chart e Horizontal bar chart 3D e Line chart e Stacked horizontal bar chart e Stacked horizontal bar chart 3D e St
9. Ability to check the status of an order LI FEATE Highly scaleable CI FEAT Ability to customize the P5 FEATS User registration good f FEAT5 E mail notification of new titles of ET FEATS Shipping Status E mail notification for Shoppers when new titles that ry FEATIA Use L Sud may interest them are added to the collection IL Use Legacy System CI FEAT15 Interactive quide to sit FEATE Highly scaleable EFI Vision Document m Highly scaleable to include many titles and effective searching through those titles This view onbly list the features that relate to the Web Shop system FEAT 7 Ability to customize the Web site FEAT1 Secure payment method gt Secure payment method Ready 11 requirements Figure 30 RequisitePro project There is an existing project in RequisitePro which is wanted to use in TEMPPO The import from RequisitePro can be started by pressing the menu item Requirement Structure Import From RM Tool This menu item is only enabled when no requirement structure is open This will cause the wizard shown in Figure 31 to be displayed The wizard assists you to import requirement data from an external Requirement Management Tool E ents from an RM too Steps Import requirement data from an RM tool 1 Introduction This wizard assists you to import requirement data from a provided RM tool Choose a R
10. Edition January 2015 Description of Use Figure 26 Requirement attributes The requirements which are not available in DOORS are not selectable and they are displayed grayed in TEMPPO Requirement Manager In the TEMPPO test management environment only selectable requirements are available for assignment to test packages or test cases The not selectable requirements are not visible in the test management environment In TEMPPO only the selectable requirements can be linked to test packages or test cases 2 5 1 1 1 Possible errors during the import eros O reion The server for DOORS can t be started A message is shown see Figure 27 Check if IBM Telelogic DOORS client is installed and correct the DOORS settings in the TEMPPO Requirement Manager settings Windows gt Settings An attribute is defined as requirement A message is shown see Figure 28 id and there are equal values or no for Open the file and do the changes for requirement id the requirements in DOORS which are described in the file example see Figure 29 and then import again TEMPPO i Please check Telelogic DOORS Settings Error during staring the DOORS server Cannot run program C Program Files x86 IBM Rationa DOORS 9 5 bin doors exes in directory CAUsersYatw112h9 temppoldxt CreateProcess error 2 Das System kann die angegebene Datei nicht finden Figure 27 Error Host not found TEMPPO Note X Due toa pr
11. gt Task List gt Show Figure 59 see also 2 6 Page 43 User Manual TEMPPO V6 2 Wi SiTEMPPO Testmanager Hannes TestProjekt O x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure New Test Structure System Test 10 M 4 NG Is No filter ow QJ Mew Test Structure E E New Test Package Jg New Texy General Attributes Test Steps E sustemsten Requirements New Texj B x New Test Package 1 Im Inherit ra ae ee ID Requirement Name Requirement structure a asa Wi New Test Case phangect 9n starting and quitting SITEMP 4 Tasklist New Test Structure V10 PROPAGATE Johannas RS V2 2V3 E lt gt PROPAGATE Huge Module 1 gt 2 B ba PROPAGATE Huge Module V2 2N3 d s m A Lf tc43181 Second Change Locks foun General Test Case ID tc43180 Requirement changed On starting and quitting SITEMP Text State open v Tester Closing Date Ok since version Reason of Creation changed lock Apply Discard Figure 59 After updating Task List 2 6 Task List A task list contains tasks each of which consists of a test case requirement pair The idea is that each task indicates a test case requirement combination which must be corrected The task list is assigned to a test structure and a given or latest version of the test structure Each entry is defined by a requirement the assigned t
12. of history entry With button Display all entries all history entries of all requirement structure versions can be loaded Action is depending on Property possible values e UDA add delete change e General change i Requirement Mani Requirement Structure Edit Evaluation Windows b Requirement Structure New Requirement Structure V bM 5 No filter J New Requirement Structure 1 New Requirement 2 New Requirement 1 op 2 1 name Testmanager General Changed description Testmanager General Changed name and coverage Testmanager Attribute Changed name and coverage 10 10 2012 10 03 10 10 10 2012 10 03 34 10 10 2012 10 03 34 Figure 11 History tab Within current requirement structure version the number of history entries loaded x can be configured in settings If there are more history entries the button Search next is still enabled und the next x lines can be loaded It also possible to view all history entries of all requirement structure versions by pressing the button Display all entries and save them to CSV file The comment can be configured to be mandatory in tab History when requirement structure is selected see Figure 12 For each requirement structure this mandatory flag can be set Page 13 User Manual TEMPPO V6 2 Edition January 2015 Description of Use If the mandatory flag is set on and requirement is saved a history commen
13. only requirements you want link to TCs Let s consider the following example where several requirements are created but some are still in state in work which is represented by the requirement attribute Req State see Figure 70 s m ad 1 V3 M 4 M e E nofiter i Planned coverage 1 999 3 test cases De 34 Required functions of the product i Enter number of test cases to be created linked in order to get a minimal coverage in test management Figure 70 Before applying a view If you want now to apply a view the current opened test structure version which has to be the latest one you have to select the root node and tab View A view can either be set by selecting an existing filter or define a logical expression Page 51 User Manual Edition January 2015 Fe 1 Introduction Rh 2 General description of the product H p 3 Detailed description of the product fe Ln 6 Load pp ee ee Figure 71 Create view TEMPPO V6 2 Description of Use Value When you press the button Apply all requirements which are not in view are displayed disabled grey a 1 Introduction EL 11 You can go somewhere E 12 Retrieve and Display News Categories 13 Settings e 14 Load News headlines per category a T 2 General description of the product i 3 Detailed description of the product features 88 31 Scope of deliver z 32 Sequences scenar
14. vT Define the sequence and size of columns by dragging in table header Short Description Red State mike type Preview Cancel Figure 95 Reporting Tabular Report 2 15 3 1 3 Chart Settings In the chart settings area you can customize the chart added to your report which represents the data of your test structure or your test suite in a graphical Way Data Selection Choose units for the x and y axis and optionally a value subdivision Orientation You can choose the orientation of the labels in the x axis Representation Data can be represented absolutely or relatively If Accumulate is activated data on y axis is displayed accumulated Time Settings If you select in x axis and or Group by a date time attribute you can configure the chart by setting a start and an end date Additionally the units days weeks months or years can be set For detailed description of charts see 2 15 1 2 15 3 2 Previewing and Saving You can either Preview the report that will be generated or immediately Save it to a HTML Word or Excel file Page 73 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 15 3 3 Import from XML For importing report settings press the button Import report setting from XML or TRP file and then the following file dialog opens In the file dialog you can set the type of file to xml After selecting a file and pressing
15. 03 02 2012 unit 12 pss Updated B none Requirements co Figure 85 Requirement analysis x axis Updated Page 65 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 15 2Progress Chart The progress chart feature is used to give you a quick overview about deltas of requirement structure versions You can view the progress from one to the next or more versions You create a progress chart by selecting the root node and activating Evaluation gt Progress Chart By selecting the button Select Versions Figure 86 is displayed where you have to select at least 2 versions to be compared Fj Select Versions X Tree style X ESA Phase 2b C Versions only C Labels only P348 Wachentiche Baseline KV ei Versions and Labels H5 Pr sentation 1D ein label ClearCase style Order TE G ascending E descending fg 15 editierbare Version Figure 86 Select versions After pressing OK the window is closed and Figure 87 is shown Fi Requirement Creation Progress X Chart E Data 50 45 Chart vertica Bar chart 40 Representation 35 absolute 3n C relative Orientation Requirements PJ nH 2n horizontal C wertical 15 W all I new 5 v changed ol Mm 5 ERE I deleted ya w10 W11 Wi4 Wii Requirement Structure Wall S new B changed B deleted Save as Close Figure 87
16. 12 48 25 Fl Continuous Report Fh Requirement Updated m Regui rit attribut iau MS Description Lpdator Preview Cancel Figure 89 Report settings overview The report functionality is divided into four main setting areas where each of them is subdivided into several parts The areas are described in the following chapters 2 15 3 1 1 General In the general settings area you define the rough layout and contents of your report Components Here you choose the components your report shall contain Dependent on your selection the tree is changed for doing the relevant settings The following components are available Title Page General Information about Test Structure Text Chart Additionally you have to select the Layout Continuous or Tabular and the Format for the report HTML Microsoft Word or Microsoft Excel If the format is Microsoft Word a template file can be defined loaded for e g header and footer in your report Page 68 User Manual TEMPPO V6 2 Edition January 2015 Description of Use x Mame NewReportSetting El Settings j ES gt Components Title Page v Title Page Eh Text H Continuous Report vw General Information of Requirement Structure Ei Requirement Iv Text Requirement MT M Char pe Continuous Tabular r Farmat C HTML f Microsoft Word Microsoft Excel Template Template PE
17. 3 8 Example Apply requirement updates eeeeeennnnn nne 42 zy MEDI ISU EUR D UU I ICTU 44 Zid iEXDOLL TO XM erra nia ind iuee cem eC enda cede Dp ento DE Dem nod bera ced dass 45 2 8 Assign Attributes to Requirement Structures ccceeeeeeeeeeeeseeseeeeeeeees 46 2 9 Assign Requirement Structures to project eeeseeeeernennne 47 2 10 B Regulrereltessssiesepeesues rixa a Dr Ie XP EUER PEDE ica EET resins 48 ZI SNewSbOSIAssensidnsstetei utc den pI UBER Emm bro dU E MEE DePUtE 49 DULS CWOebhslobl sossuunud campi prm EISE CM P E LL MM cenem me a ME 50 2 12 1 liie We SPEE 54 2 12 2 piri e rpm 54 2 13 Split Requirement Structures eeeessseeeeennnnnnnnm enhn nnn 54 2 14 Wt s ctebuecnd un erba ea wa wane M DIU EU DEPT UMEN ELE 56 2 14 1 W zsiiusisHil m Hm 56 User Manual TEMPPO V6 2 Edition January 2015 Contents ZI 2 CEE FIE ui anasnnnd emageeanatantatoniaai EA Dado 57 ZAG CANOE Fite a sd viia EN cos Miet a Decr o uns 59 2 14 4 Biz mr ME D ETT 60 2 015 Select FILES au plenam ds nt maa Latiae ossa M sd qa QUOC ds AVNE Eat RU UU 60 2 14 6 SOW Fels aumnececscarsued E ED EIU RPECDPR PI SDN EE EQUPEMUE NODE NEEDS 60 2 14 7 Define the filter criterion cceeeeeeee nnnm 61 2 14 8 EX DO PCCP mS 63 Z9 TAPO DEG ira ru bti ey pisa T uet odd E Vm d a uie tavi ddbn 64 2 55 JEVallidtlODbssesssiviE ure txt OUI IM IPEAT DI OU I PIOS IMINEONS c pEUi I PEE 64 ZAG ADA SiS web imeiERSiabcU sanitat
18. 38 Basic Flow INVALID SHOPPER ID USER ALREADY LOGGED ON Created in IBM RequisitePra 10 02 2010 00 00 00 Updated in IBM Requisite Pro QUIT QUIT SHOPPER NOT IDENTIF MODIFY ITEMS Short Description CHANGE OPTIONS Pre Condition Pre Condition Description shop For CD new requirement Brief Description Basic Flow SEARCH BY SELECTED CRITEI QUIT POSSIBLE NEW ACCOUNT NO NEW ACCOUNT NO MATCHING COs VIEW CURRENT ITEMS REMOVE ITEM ALLOW SUGGESTION OPTION Past Condition 2 UC Mew requirement Do be deleted Owner Testmanager Llpdator Testmanager Creator in IBM RegquisitePro Unknown Updator in BM RequisitePra Type IBM Requisite Pra Lock Apply Discard Figure 51 Requirement Manager Updated 2 5 3 3 Enterprise Architect In TEMPPO Requirement Manager requirements data imported from Enterprise Architect cannot be updated by a TEMPPO user Enterprise Architect requirements can be updated in Enterprise Architect and imported again in TEMPPO The update function works like the import function see 2 5 1 3 2 First export your changes in Enterprise Architect to an XML XMI file Afterwards start TEMPPO Requirement Manager and open the requirement structure latest baseline you want to update By pressing the menu item Requirement Structure gt Update gt From RM Tool the update wizard opens where you select e Tool EA Architect e XML XMI File e R
19. 8 0D atabase migration 281 1 1 1 2 Writing the Project Plan 3 9 License Server Connect 282 As an output of the test plan a Project Plan e g MS Project is written that contains tasks for all 3 10 BNotiication test activities Input for the plan is given by the 283 l general budget for testing activities 284 l estimated number of test cases to be developed 285 number of resources milestones 286 estimated effort of executing a test case 287 l bug analysis 288 regression testing testing fixed bugs effort 289 1 1 1 3 Defining Test Case Attributes 290 After the implementation phase you will have a lot of test cases even in small projects and it s very likely that you want to have just a few of your test cases bundled for test execution because ET n Usemame Administrator Exclusive edit mode Figure 49 DOORS Change requirements After changing the module in DOORS start the update process In the next figure see Figure 50 you can compare the latest version of requirement structure with the version before Binms testmansger OO O lolx Requirement Structure Edit Windows Requirement Structure Huge Module 1 V1 Ep Introduction i Eg Basics General Hif The Test Process E1 Description of Use Mame Huge Module 1 E The Test Process Phases Ee Multi user ability Owner Testmanager Updator ia General principles and user promp Hg Menu Reference ia Manager Creator RMS Kf Adm
20. A E E owner Testmanager a ano r4 Requirement Mame x Reg 2 ano X T Created lt 01 10 2010 AND Owner Testmanager AND Requirement Mame Regt AND Updated 01 10 2010 Hide Empty Subtrees Impact to selected Window Requirement 46 Apply Cancel Figure 80 Show Filter When clicking Apply Figure 80 is closed the selected filter is set in the activated window and the combo box in the toolbar shows the current filter When clicking Cancel Figure 80 is closed and the previous set filter remains unchanged 2 14 7Define the filter criterion The values of the following attributes can be used as described in Table 3 Planned coverage requirement name requirement short description requirement ID owner updater created updated UDAs and selectable if a requirement is in a view First of all you have to choose an attribute and an operator IN NOT IN If IN or NOT IN is selected the combo box value changes to a text field together with the button Then you can enter e Astring with a wild card or e Press the button for selecting several values After pressing the button Figure 81 is displayed and the attribute values are selected by moving them to the right Pressing OK applies the selection to the filter window The selected values are displayed separated by a comma Now the user can edit this line Page 61 User Manual TEMPPO V6 2 Ed
21. Description of Use Fi Import Requirements from an RM tool x Steps Choose the baseline and the view to import 1 Introduction 2 Choose a RM tool 3 Select a requirement document 4 Choose a baseline and a wiew Full Coverage Report Vie jal Features All Supplementary Requirements All Use Cases Features Mot Linked to Supplementary Regts Features Mot Linked to Use Cases Functional Requirements Coverage High Priority Features Mot Linked to Use Cases lt lt Prev Next gt gt Finish Cancel Figure 34 View selection Finish With pressing Finish the project is imported to TEMPPO A TEMPPO Requirement Manager 3424975 Learning Project Use Cases 1 ZI 4 INVENTORY NON AVAILABLE fi 5 INVALID INFORMATION fifa 6 NO RESPONSE fifa 7 ORDER PLACED fii 8 SUCCESS if 9 Check Order Status fi 10 Brief Description fii 11 Basic Flow if 12 TRACK PACKAGES fii 13 USER ALREADY LOGGED ON ff 14 INVALID CUSTOMER ID OR PASSWORD fifi 15 OPTIONS FOR DISPLAY fii 16 Pre Condition if 17 Purchase CD ff 20 INVALID SHOPPER ID fii 21 USER ALREADY LOGGED ON ff 22 QUIT ff 23 QUIT SHOPPER NOT IDENTIFIED fi 24 MODIFY ITEMS ff 25 CHANGE OPTIONS bar Name Learning Project Use Cases 1 Prefix UC Owner Testmanager Created 14 02 2012 14 54 30 Creator in IBM RequisitePro Created in IBM RequisitePro 14 02 2012 14 54 30 Type I
22. Find and Replace I X Lai r i 1 J Mo more occurences Found Figure 120 No more occurrences found Page 86 User Manual TEMPPO V6 2 Edition January 2015 Description of Use e List occurrences With the button List occurrences the searching result is shown in a list see Figure 121 When clicking a requirement in the list it s selected in the test structure tree Ei Name ee x ome Created Occur Testmanager 14 02 2012 13 52 28 Testmanager 14 02 2012 13 52 33 Figure 121 List occurrences 2 17 4 2 Replace There are also two possibilities for replacing e Replace At first a requirement is searched and selected The user has to click again for replacing the field and then searching the next one If the requirement is locked the requirement isn t changed i e the next requirement is searched e Replace All The selected field of all requirements is changed which contains the text After replacing all a message is shown see Figure 122 with the number of replaced requirements and number of requirements which couldn t be replaced because of locks etc Find and Replace X 1 4 Requirements are replaced AJ 0 Requirements coudn t be replaced Figure 122 Replace result The replace functionality is disabled if the user has not the right for changing requirements 2 17 5Settings TEMPPO differs between global and application specific settings 2 17 5 1 Global Settings For global setting
23. Requirement creation progress Page 66 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 15 3Reporting TEMPPO Requirement Manager offers a reporting feature which allows you to create flexible textual and graphical reports from your requirement structures A requirement structure report can be created from any node within the structure even from a single requirement Evaluation gt Report Selected Fi TEMPPO reporting settings d Personal Settings I Requirement Report Templ Testmanager 24 06 2012 12 27 56 Requirement Review Template 24 08 2012 12 23 03 3 Ip 5 Testmanager Word Report for Requirements Save Report Prewiewy Figure 88 Report settings With the buttons on the right side you can add change and remove settings e New Edit see 2 15 3 1 e Delete Setting s are deleted e Import from XML or TRP see 2 15 3 3 e Export to XML file see 2 15 3 4 With the buttons below you can save the report to a directory or create a preview After Pressing Save Report a file dialog opens where the directory has to be defined and then the report is created 2 15 3 1 New Edit When pressing the button New or Edit a new window opens to set the properties for creating a report Page 67 User Manual TEMPPO V6 2 Edition January 2015 Description of Use x Mame hen Report Setting 2 Owner Testmanager EF General L Tttle Page Created 24 08 2012
24. Use Case TEMPPO is installed and RequisitePro is updated If you update RequisitePro to a new version you have to change the version in settings dialog see Figure 126 Afterwards all TEMPPO applications have to be closed and a batch file changeReqProVersion bat has to be executed Page 91 User Manual Edition January 2015 3 Literature 1 User Manual TEMPPO user manual December 2014 TEMPPO V6 2 Literature Page 92 User Manual TEMPPO V6 2 Edition January 2015 Abbreviations Abbreviations 4 DB Database HW Hardware RM Requirement Management GUI Graphical User Interface SW Software DSN Data Source Name ODBC Open Database Connectivity UAI Universal Automation Interface Page 93 User Manual TEMPPO V6 2 Edition January 2015 Appendix 5 Appendix 5 1 DTD Schema for XML Import Requirement Structure See XML directory of TEMPPO s installation directory Page 94 User Manual Edition January 2015 A Apply 85 C CSV Import 14 Update 39 D Discard 85 DOORS Attributes 19 Baseline 18 Import 16 Module 18 Requirement ID mapping 19 Update 34 View 18 Enterprise Architect Export to XMI 25 Import 25 Update 38 Evaluation Analysis 64 Progress chart 66 Reporting 67 F Filter 56 Change 59 Create 57 Define criterion 61 Delete 60 Export 63 Import 64 Select 60 Show 60 Find and Replace 86 Find 86 Replace 87 H Hyperlink Create 82 Download 85 Edit 8
25. XML they can be also updated Changes in requirement name content short text Also deleted requirements are concerned Page 39 User Manual TEMPPO V6 2 Edition January 2015 Description of Use If requirements are imported from csv of course as a list and the list is transformed to a tree an update affects this tree 2 5 3 6 Result of update After updating a requirement structure a window is shown that informs you how many requirements were e Updated e Deleted e Changed x Requirement structure successfully updated 1 new requirements reqiO3 1 changed requirements regino 2 deleted requirements regi reqi01 o Figure 53 Update information 2 5 3 7 Apply requirement updates Requirement structures and test structures live in fully separated environments So it can be that a latest test structure version works with a not latest requirement structure version This is always the case after an update of a requirement structure An automatic update of the current test structure version to the latest requirement structure version may not be wanted by the user and would cause problems anyway e g if more than one user work on this version It s only possible to propagate to the latest requirement structure version So an update to the latest requirement structure version can only be made manually initiated Open the TEMPPO Test Management environment and open the project and test structure By pressing the menu
26. assignment or do nothing if the failure is DOORS sided and cannot be corrected in TEMPPO If all necessary actions are made the user can mark the entry in the task list as closed first lock then apply and click upon another task Task lists can be deleted in the task list window if all tasks are closed The task list has to be selected and via the context menu item Delete task list a confirmation window comes up Confirming with OK deletes the task list 2 Export to XML This feature allows exporting the entire requirement structure into an XML document When a requirement structure is open and the root node ora requirement is selected the menu item Requirement Structure gt Export to XML is enabled After entering a name the XML file is stored to the file system conforming to requstructure dtd Page 45 User Manual TEMPPO V6 2 Edition January 2015 Description of Use The requstructure dtd can be found in your TEMPPO XML directory The following window is shown after exporting successful x hy 2 j Requirement structure successfully exported Figure 61 Requirement structure Exporting When you plan to exchange test and requirement structures over databases via XML you have to be aware of exporting the correct version of a requirement structure 2 8 Assign Attributes to Requirement Structures For a chosen requirement structure attributes can be assigned to the requirement structu
27. hyperlinks Hyperlinks to the web to the file system and to upload can be created for the text field Description requirement structure requirement B Bold J Italic U Underline c2 Hyperlink gt Remove hyperlink create Edit hyperlink m Figure 110 Menu hyperlink For creating a hyperlink it is necessary to select at least one character in editable text fields and activate the context sensitive menu Hyperlink see Figure 110 which opens the Hyperlink window see Figure 111 z web c3 Fie EB Database LRL nttp Hat atas ner Figure 111 Hyperlink to the web You have the possibility to enter a link to the web specified by an HTTP address or to the file system see Figure 112 x amp B web S Fie Database File C Program Files TEMPPO 6 Ovogging properties i OK Cancel Figure 112 Hyperlink to the file system In case of changing drive letters moving file shares and other similar problems it may be better to upload the files to the database For referencing an upload you have 2 possibilities you can upload a new file or use an existing one and create a reference on it The philosophy of this concept is to upload a file only once and create more references on it if necessary Page 82 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Fi Upload Properties of logging properties X General Jogging properties nis Or
28. in his locked items and presses the button Save he will get the following message that the lock has been removed in the meantime Lock Exception l x fA Saving not possible because the lock was suspended by the administrator Figure 98 Lock deletion message When closing the window by pressing OK he can only discard his changes 2 16 4Show a lock state The locking state of the item is shown by Special padlock icon green locked by the current user yellow locked by another user Tool Tip Locked by lt user gt Fi TEMPPO Requirement Manager Testeri Import E B x Requirement Structure Edt Evaluation Windows Requirement Structure Import v2 Mo bk M I o nte General Attributes Requirement ID reati oo Mame mporto Owner Testmanager Llpdator Testmanager o 3 import2 Created 02 2012 09 36 35 Updated 02 2012 12 38 47 Type Manual Short Description shortd Description content Lock Zpplhy Discard amp 8480 EK amp RE Figure 99 Lock button 2 16 5Change an item Before you can change an item you have to press the button Lock see Figure 99 If the locking was successful the item can exclusively be changed by you The lock is automatically released if you e Select another item e apply discard changes Page 76 User Manual TEMPPO V6 2 Edition January 2015 Description of Use If locking wasn t successful after pres
29. menu is only enabled if the root node is selected Split requirement structure X Mask Far requirements to move way Mame of new requirement structure ay Requirements Case sensitive Cancel Figure 75 Split dialog A mask wildcards and are supported for requirements to be moved to the new requirement structure and the name for the new requirement structure can be specified When pressing OK the move process is started Before moving requirements the uniqueness of the requirement structure name and locks in affected test structures are checked no locks may exist If the checks pass the requirements will be moved otherwise a corresponding message is displayed and the process is terminated The following example illustrates the splitting process Requirement structure before splitting Requirement Structure NAV 001 NAV 002 NAVIGATION 003 MAP 001 DestliInput 001 MAP 002 Navi 004 RADIO 001 RADIO 002 Mask for requirements to move NAV Name of new requirement structure NAV Requirements Case sensitive no Requirement structures after splitting Page 55 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Requirement Structure RADIO 001 RADIO 002 NAV Requirements NAV 001 NAV 002 NAVIGATION 003 MAP 001 bestlnput 001 MAP 002 Navi 004 2 14 Filter Users can see their requirement structures in a filtered way by creating and selecting filters i e for the purpose
30. of test criteria etc Its contents are obligatory for all members of the test team For detailed information please refer to http se Hlt528565386m HIt528565386 siemens at stdsem e p desi ge2 htm 251 i 2 1 1 2 Writing the Project Plan 282 Asan output of the test plan a Project Plan e g MS Project is written that contains tasks for all test activities Input for the plan is given by the 283 l general budget for testing activities 284 estimated number of test cases to be developed 285 number of resources milestones 286 estimated effort of executing a test case 287 bug analysis 288 regression testing testing fixed bugs effort 289 2 1 1 3 Defining Test Case Attributes 290 After the implementation phase you will have a lot of test cases even in small projects and it s very likely that vou want to have just a few of your test cases bundled for test execution because 291 l you don t have the time to execute all of them and therefore you decide to execute the high priority ones only Pilger zin Exclusive edit mode H 2 3 General principles and u H 2 4 Menu Reference 3lManager 4 Administration Eae Usermame Administrator Figure 48 DOORS Before changing The module Huge Module is changed in DOORS and then should be updated in TEMPPO The requirement Introduction is deleted and the requirement Description of Use is renamed to How to Use see Figure 49 Page 35 User Ma
31. the active version which is again latest C Check In V1 Al ready requirements fad Merge 7 Delete Tree style Versions only _ Labels only Versions and Labels _ ClearCase style Order Q ascending descending Figure 73 CM Version tree after checking in and labeling Changes in the latest version of the requirement structure will now not affect All ready requirements E g when inserting a requirement it will only be available in the latest version of the requirement structure Page 53 User Manual TEMPPO V6 2 Edition January 2015 Description of Use You can see the active version of your requirement structure in the title bar of the requirement structure explorer Fi TEMPPO Requirement Manager Testmanager Import pm x Requirement Structure Edt Evaluation Windows HReguirement Structure Import v2 B E dm x M 4 b M e EE No iter General attributes Requirement ID reat oo Name morto Owner Testmanager Updator Testmanager i 3 import2 Created 14 02 2012 03 35 35 Updated 14 02 2012 12 38 47 Type Manual Short Description short Description contento Lock Appl Discard Figure 74 After check in 1 You can restore the version of a requirement structure by activating it in the versions dialog with button 2 Activate selected version You cannot change a requirement structure in a version which is not latest
32. 1 2 Refresh recursively iex paaa aa a 78 2 16 8 1 3 Refresh on certain user actions eee 78 2 17 Geheral DFIBDCIDISS oues usc RF uv orav du EM E E M M EMILE been ee IM MES 79 2 I7 1 INUIT SEIS CEION ippon thatch nace Sait a DTE canta EDIDIT cate pene 79 2 17 2 Hyperlinks and Uploads cioe coos caren Sada o a a di eqs 81 27 2 1 Create hyperlinKS iisseset eter saat via eee opua REDE MP Ead CREE 82 2 17 2 2 EGIC NY DECINKS ssa xui ecd dea ond e d adc vc b n reas ael 84 247 273 Remove NY PEAKS i xo docile dedo de dnd P Roc v OR ore UR reat Ck 84 PARU NP MIC Ais I OO I S TII T 85 ALA 3Applylhg 7 Discarding smrsm niin aT a 85 2 17 4 Flid abd Rebpld68 sers ea a Gb rum A Ora UR T de Up wd AUR 86 227 MEI DP eeere 86 PME EB Tace TC 87 2 17 5 jmdpsfcccc d A E T E E A E OOA 87 2h Jaded GlOD als SetUNGS arean aa rude EA tates aa 87 2705 SPCCING SEINO S wise 3 c254 aud sr DINI SON D eae E IM IE MAD DES KE 88 2 17 5 3 Reguirement Management said ssa Pole Sa dich pe E M MU E EVE 89 2 17 5 3 L ABM Telelogic DOORS rerainan PANI x VR dePPS Es 89 2 17 5 3 2 IBM Rational RequisitePro eeeeeeeeennn nnn nnn 90 3j JLIterature ccossucca on Ioan enc o o 6 CR RR RO C COR RR CER C RR CA ARR CR CR C RR RT 92 A ADDrevidtiols ussexeics sees GxVevIXUIRARVE EK EEEKRUE VATVEVITFAEERUD EF VEVEE EP MI MEE EIE 93 User Manual TEMPPO V6 2 Edition January 2015 Contents 5 ADDenaD6Giiiveie uve d
33. 2015 Description of Use 2 14 4Delete Filter You can delete an existing filter by pressing the delete filter button This button is only enabled if the selected filter is not the empty filter No filter After activating the Delete item button the reconfirmation window comes up x 3 Do you really wart to delete the selected filter Cancel TEMPPO Note X Ld CL Fiter was deleted After deleting a filter the No filter is highlighted in the list box 2 14 5Select Filter TEMPPO Requirement Manager offers a fast selection mode with the combo box in the toolbar possible filters can be set without opening the filter window 2 14 6Show Filter If no filter was set before opening the filter window the list box entry No filter is highlighted If a filter is set before opening the filter window the corresponding entry is highlighted When clicking on an entry in the list box the item is highlighted and its impact on the requirement structure is displayed Page 60 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Ei Fiter SS x Personal Filter 4 Ae My own requirements created before Testmanager 01 10 2010 13 08 08 XS SP Mew Fitter Testmanager 01302010132517 i l BF Ma filter Testmanager 01 10 2010 13 08 49 Selectable requirements Testmanager 01 10 2010 13 08 48 Fiter conditions read only Attribute Value gt i i Created ES for 10 2010 m 3 ano
34. 4 Remove 84 Hyperlinks 81 6 Index TEMPPO V6 2 Index L Locks Find 75 M Multi user 74 Lock 74 Newsboard 49 R Refresh Recursively 78 Whole requirement structure 77 Requirement Edit 16 Link 48 New 9 Tab Attributes 10 Tab General 10 Tab History 10 Requirement structure Assign attribute 46 Import 16 Split 54 Requirement Structure 6 Assign 47 Check in 50 Create 7 Export XML 45 Import from Requirement Management Tool 16 Import XML 31 Open 8 Update 34 RequisitePro Import 23 Project 24 Update 37 View 24 T Task List 44 Test Structure apply requirement updates 40 V Version 50 Delete 54 Page 95 User Manual Edition January 2015 Merge 54 X XML Import 31 Update 39 TEMPPO V6 2 Index Page 96
35. Architect Project Browser If the requirement engineer considers freezing a certain state of requirements to a baseline it has to be exported to XMI as well First of all you have to select the node Requirements Model and activate the menu item Export Model to XMI and the following figure is displayed where you can enter a path and XML file for saving the requirements model TEMPPO supports XMI 2 1 standard Export Package to XMI e 259 Requirements Model MPPO documents 3_Implementation manuals 6 2 User Manual EA Export xm m Export Type E XMI 1 1 Qa XMI 2 1 Other XML Formats Publish Progress Figure 37 Enterprise Architect Export to XMI After pressing the button Export the whole information is written to the XML file in the format of XMI 2 1 Page 26 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 5 1 3 2TEMPPO Requirement Manager Import XMI First of all start TEMPPO Requirement Manager and activate menu item Requirement Structure gt Import gt From RM Tool and the following figure is displayed Import Requirements from an RM toc Steps Import requirement data from an RM tool 1 Introduction This wizard assists you to import requirement data from a provided RM tool Choose a RM tool ji Select a requirement document Figure 38 Import wizard After pressing Next you can select your Requirement Management Tool ents from an RM toc Intreduction Choos
36. BM RequisitePro Mandatory history comment Description Appty Discard es Figure 35 Imported Requirement Structure 2 5 1 3 Enterprise Architect 2 5 1 3 1Enterprise Architect Export to XMI There is an existing project in Enterprise Architect which has to be used in TEMPPO The basis for integrating requirements in TEMPPO Requirement Manager is the so called EA Project Browser which contains the model of requirements The relevant object types are Packages yellow color and Page 25 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Requirements red color Other object types like Use case are not considered for an import to TEMPPO Project Browser Ox Bote d a id d amp 9 3 Model 4 Requirements Model 4 t Functional Requirements fa Funktionale Requirements CJ _Papierkorb E General Functional Requirements in Work 4 J Billing Invoicing J Collect Data 4 D Contract Management D Prepayment 22 Prepayment 1 fa Prepayment fa Prepayment Hierarchie E Create Prepayment contract in system SM Basic Requirement Stereotype REQ SM 00338 Payment modality Prepayment Z hler Inkasso C Payment Reminder eme SM Basic Requirement Stereotype REQ SM 00015 Invoice C Use Customer Information Service C Operational Management Events Status infos Actions OJ Installation und configuration J Market Progress a Non Functional Requirements Figure 36 Enterprise
37. D Son Note Values of the chosen attribute must be unique otherwise the import wil be canceled 2 Choose a RM tool 3 Select a requirement document 4 Choose a baseline and a view 5 Choose attribute as requirement ID Updator Figure 24 Attribute selection Columns in DOORS Import setting Attributes in view TEMPPO ID object identifier gt Level Level define no requirement Updator ReqID ID ReqID Updator ID object identifier is requirement ID ID object identifier gt Level Level define ReqID as ID ReqID requirement ID Updator Updator Level gt Level ReqID define no requirement ReqID Updator ID Updator ID object identifier is requirement ID Level gt Level ReqID define ReqID as Updator Updator requirement ID Table 1 Attributes from DOORS to TEMPPO After selecting the attribute which has to shown as requirement id in TEMPPO and then pressing Finish the requirement structure is imported The values of attribute which is specified as requirement id are checked if there are equal values or if there are no values If there are such requirements then the import is canceled and a log file is written where these cases are described see 2 5 1 1 1 Page 20 User Manual TEMPPO V6 2 Edition January 2015 Description of Use When the import was successful then the imported requirement structure and its requirements are shown in the tree Fi TEMPPO Requirement Manager T
38. Edit entries in the requirement structure Page 57 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Personal Filter 1 ny fi Testmanager 01 10 2010 13 08 48 A Ud Selectable requireme Testmanager 01 10 2010 13 08 48 s Filter conditions read only Attribute Value M e IEEE E ee ol 0 un n Iw Hide Empty Subtregs Impact to Selected Window Requirement 4B Apply Cancel Figure 77 Create new filter If you click the Create new filter button Figure 77 is shown The name of the filter is set by default with New Filter and the filter conditions can be entered The checkbox Hide empty subtrees is not available in TEMPPO Requirement Manager After creation of a new requirement it may happen that it disappears after saving if it doesn t match to a set filter Fi Filter Properties l x Mame hiy own requirements created before 1 10 Conditions Attribute Value i lt 01 10 2010 AND Owner Testmanager AND Requirement Mame Req Hide Empty Subtrees ores Figure 78 Filter Properties Page 58 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Pressing the Save Button the new filter is saved to the database if a new name was entered Otherwise the information window comes up TEMPPO Note i x 1 Fiter name already used Please enter a different name Remark Due to missing meta data assignment
39. M tool ji Select a requirement document 4 Choose a baseline and a view SE rri Figure 31 Requirement import wizard Introduction When pressing Next Figure 32 is shown in which you choose IBM RequisitePro is possible Page 23 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 4 Import Requirements from an RM too Introduction Choose a EM tool Sila ac rpcqu rcneni C A IBM Telelogic DOORS document 4 Choose a baseline and a view IBM ReguisitePro 7 9 Enterprise Architect XMI 2 1 Figure 32 Requirement import wizard Choose a RM Tool If you press Next the projects are read from the local registry Figure 33 x Steps Select a requirement document from the tree 1 Introduction 2 Choose a RM tool Username Unknown 3 Select a requirement disicument Password 4 Choose a baseline and a view p Learning Froject Use Cases E Learning Project Traditional E Project 1 za Prey Mex m Finish Figure 33 Requirement import wizard project selection If you select a project enter a valid account and password and press Next Figure 34 is shown where the available views are displayed With the view it s possible to use only a restricted number of requirements in TEMPPO and not the whole tree from RequisitePro Views also contain attributes which are imported too see Figure 34 Page 24 User Manual Edition January 2015 TEMPPO V6 2
40. Test Structure Apply requirement updates Figure 54 is shown All assigned and updated requirement structures are shown in the lists Select the requirement structures when the assignments should be updated By clicking Apply the test structure is checked in and then propagation is executed Page 40 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Wi Apply requirement updates X Huge Module Testmanager 14 12 2006 09 vz3 Apply Cancel Figure 54 Apply requirement updates Updating a requirement structure does not cause that a task list is created a task list 2 6 is created internally if the test structure is updated to the latest requirement structure version Deleted requirements are unassigned from the test cases If only a new column attribute is added to view in IBM Telelogic DOORS but requirements aren t changed When applying requirement updates these requirements are recognized as unchanged This means that no tasks are created for these requirements but the new version of requirement is used and all attributes are available in test structures If there is no implicit propagation to the latest requirement structure version Figure 55 is shown TEMPPO Note x l There is no Requirement Structure to apply tol Figure 55 No requirement structure for updating Page 41 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 5 3 8 Example Apply re
41. acked vertical bar chart e Stacked vertical bar chart 3D e Vertical bar chart e Vertical bar chart 3D For x axis you can select e Created e Owner e Planned Coverage e Updated e Updator e Self defined requirement attributes There is also the possibility to save the chart as jpg or png file by pressing the button Save As Figure 84 shows an analysis from a requirement structure displaying the number requirement for a requirement attribute Requirement state Page 64 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Fj Analysis E x gl Chart E Data X Axis 50 Y Axis a5 Group by Planned Coverage Updated Chart Lipdator 40 Requirement_priority Requirement_state 35 Orientation horizontal 30 C vertical 25 Representation absolute C relative Accumulate Time Settings Start 01 03 2012 El End 01 03 2012 mI implemented in work none open pending unit 12 psv Requirements Requirement_state B none oe Figure 84 Requirement structure analysis x axis requirement attribute Fj Analysis p x gl Chart E Data Y Axis Requirements 54 Group by V 48 Chart vertica Bar Chart E Iv Shaw D values Orientation 38 is horizontal vertical 30 Representation 24 absolute C relative Accumulate Time Settings Start for 08 2011 Es End n 03 2012 Fs 26 01 2012 27 01 2012 01 02 2012 02 02 2012
42. amed requirementnumber import3 type Manual shortdescription Inhalt Kurzbeschreibun createdrms updatedrms selectable 0 coveredbytcs 3 lt DESCRIPTION gt lt CDATA lt html gt lt body gt lt p style margin 0 gt Ge amp 228 nderte Beschreibung mit lt a href http www siemens at TEMPPO gt Hyperlink lt a gt lt p gt lt body gt lt html gt gt lt DESCRIPTIONS lt REQUIREMENT name New Requirement ADDED requirementnumber req41017 type Manual shortdescription createdrms updatedrms selectable 0 coveredbytcs 1 lt DESCRIPTION gt lt DESCRIPTION gt lt USER DEFINED ATTRIBUTE name Requirment attribute value high type 32 ie lt REQUIREMENT gt lt REQUIREMENT name New Requirementxcvxcv requirementnumber req41019 type Manual shortdescription createdrms updatedrms selectable 0 coveredbytcs 1 lt DESCRIPT TONS lt CDATA gt lt DESCRIPTION gt lt REQUIREMENT name New Requirement requirementnumber req41020 type Manual shortdescription createdrms updatedrms selectable 0 Page 33 User Manual TEMPPO V6 2 Edition January 2015 Description of Use coveredbytcs 1 lt DE SCRIPT TONS lt CDATA gt lt DESCRIPTION gt lt REQUIREMENT gt lt REQUIREMENT gt lt REQUIREMENT gt lt REQUIREMENT name import XML 2 requirementnumber import32 type Manual shoredescriaption createdrms
43. ator RMS Administrator Created RMS 28 08 2006 16 20 44 Updator RMS Updated RMS z Type Manual Short Description Description The following chapters are describing the locking in manual made Requirement Structure Huge Module 1 V3 m ALI Huge Module 1 fi How to Use Es Multi user ability Ee Lock modes c4 SITEMPPO provides f Manual lock fl Automatic lack Lio If you are working with m vnd amp amp On the other hand you sir fi This Feature can be config LH D Table uf ESMTable Locking modes in Efi Editing PE Ga 1196 off Figure101 Lock state Hp Find locks unlock of Showing a lock state fi Changing an item Ha Deleting an item wet 1 l 1 1 General Requirement Number Mame Owner Created Creator RMS Created RMS Type Short Description Description it 193 Table1 Locking modes in admin propertie Testmanager Updator 25 10 2006 09 56 42 Updated z Administrator Updator RMS eB 08 2006 16 20 44 Updated RMS z Manual Figure 58 Before and after update TEMPPO V6 2 Description of Use Open the test structure again and the requirement which is assigned to a test cases isn t the requirement of the latest requirement structure anymore Now you have to update the assigns Test Structure Apply requirement updates Then all changed assignments and new requirements are listed in a task list menu Test Structure
44. ayed in a list The multi selection mode is activated when more than one item is selected If a user selects at least 2 items the right side detailed view is completely empty The user can only activate the multi selection mode when he has the right A multi selection can be done by using different keys e Select all For selecting all press Ctrl and lt A gt The user can also activate the context menu Select All Figure 106 or the menu item Edit gt Select All Page 79 User Manual TEMPPO V6 2 Edition January 2015 Description of Use New d Find and Replace F3 shom Details Ctrl ts Tree b A Cut Cirlex Copy Ctrl C Paste Cirlev iri Paste betare 1 Order b JK Delete Delete n Refresh recursively Figure 106 context menu Select AII Requirement can be selected with Ctrl or with Shift After pressing Select all all sub trees of the requirements are marked Fi TEMPPO Requirement Manager Testmanager Import J l nm x Requirement Structure Edt Evaluation Windows Requirement Structure Import v2 M d b M e EE No nte J Import Oo mpoto zu ts 2 importi Er fi 3 impart2 3 1 Mew Requirement if 3 2 Mew Requiremert 1 Apply Discard Figure 107 Multi selected items By clicking context menu all possible actions are provided to the user 1 Meu Li Find and Replace F3 show Details Select All Cir As ts Tree b Cut Ct
45. by the current user Figure 102 Locks found in the database on starting quitting TEMPPO Requirement Manager 2 16 8Refresh 2 16 8 1 Refresh manually 2 16 8 1 1 Reloading the whole requirement structure You can reload the whole requirement structure by pressing the reload button go on top of the tree see Figure 103 This has the same effect as manually reopening the requirement structure Page 77 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Fi TEMPPO Requirement Manager Testmanager Import Requirement Structure Edt Evaluation Windows Requirement Structure Import v2 zb 2 import General view i G 3 impart2 Mame import Prefix Owner Testmanager Updetor Testmanager Created 14 02 2012 08 34 44 Updated 14 02 2012 12 23 22 Type Manual Description Lock Apply Discard Figure 103 Button Reload for reloading the whole tree 2 16 8 1 2 Refresh recursively You can refresh an item including all sub items by selecting the refresh recursive function in the context menu see Figure 104 Attention The selected item with all sub items will be completely re loaded from the database so it may take a long time i TEMPPO Requirement Manager Testmanager Import alec Requirement Structure Edit Evaluation Windows mm A Mew b Cl Findand Replace F3 Select ll Ctrl 4 ts Tree b fp 2 importi iew fii 3 imp
46. cess starts see chapter 2 5 1 The menu item is enabled when a requirement structure is opened and this requirement structure has the type for the RM tool Telelogic DOORS not Manual There is no preview or undo functionality when the wrong requirement structure is selected but the latest version is checked in before updating No changes are lost 2 5 3 1 1 Example for Updating Formal module Huge Project Huge Module current 0 0 DOORS E oj x File Edit View Insert Link Analysis Table Tools User Help Bars Sel x vl Sts B rz U ae tel ee ee a ER Standard view gt all evels IET 22s iGB y3 e sm m 5 Do 1 Ontroduction 28 Description of Use 2 1 The Test Process Phases 2 1 The Test Process Phase 274 2 1 1 Test Planning LE E idis Panning 275 The definition phase covers the tasks of 2 1 2 0T est Design 276 Writing the Test PI 2 1 30Test Case Implern A ng z d 2 1 4 I Test Case Executi 277 Writing the Project Plan amp 2 1 5 IE valuation 278 Defining Test Case Attributes 2 2 Multi user ability 279 2 1 1 1 Writing the Test Plan T pies ones 280 The test plan is an stdSEM document and writing is outside the scope of SITEMPPO However it s is 22 3 fishing the base document for all test topics during the development process and covers subjects like test requirements test management test documentation test goals end
47. click the desired button Header eee leader Footer Left j EL Continuous Report El Requirement Requirement Alle name Preview Cancel Figure 92 Reporting Header Footer Page 70 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 15 3 1 2 Text The text settings are relevant for the textual data contained in your report and also for how they are displayed General Text Settings First you can choose the Layout if you want your data displayed in continuous text or table format Furthermore you can set Format options Do not ignore information fields with empty values Do not generate heading numbers You can limit the size of your report by defining the depth absolutely You can use the slider to limit the reported requirement structure tree depth to a fixed level Fi TEMPPO report setting for requirement structure X Mame Men Report Setting ESettings Format Options GF General Tie Page ignore information fields with empty values Header Footer 24 i Generate Heading Mumbers Continuous Report i Requirement Limit depth of report Coo Requirement i Chart Preview Cancel Figure 93 Reporting General Text Settings Continuous Report Requirement Requirement Attributes You can specify which data your report shall contain With multi selection mode you can move several values to the right part of the window If you don t want to show w
48. d updates the new latest version of the requirement structure irrespective of the activated version By pressing the menu item Requirement Structure Update the requirement update process starts see chapter 2 5 1 The menu item is enabled when a requirement structure is opened and this requirement structure has the type for the RM tool Rational RequisitePro not Manual There is no preview or undo functionality when the wrong requirement structure is selected but the latest version is checked in before updating No changes are lost After updating the requirement structure a new version 2 is created In Figure 51 there is displayed the new requirement Some requirements are missing compared to V1 Page 37 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Fi TEMPPO Requirement Manager Testmanager Learning Project Use Cases 1 l Z ioj xi Requirement Structure Edt Evaluation Windows Requirement Structure Learning Project Use Cates 1 V2 M 4 b HM e EE uo iter i i Learning Project Use Cases 1 Hih 1 Check Order Status 2 Brief Description General Attributes i it 3 Basic Flow zb 4 TRACK PACKAGES Requirement ID Jug 0o fit 5 USER ALREADY LOGGED ON e B INVALID CUSTOMER ID OR PAS JUC Newrequirement 000000 zb 7 OPTIONS FOR DISPLAY zb 8 Pre Condition t hn J Purchase CO 2 10 Brief Description Created 14 02 2012 14 54 33 Updated 14 02 2012 14 54
49. e a RM tool 3 Select a requirement E F1 IBM Telelogic DOORS document 4 Choose attribute as CO a IBM RequisitePro requirement ID ED Enterprise Architect XMI 2 1 Figure 39 Requirement Management tool selection After selecting Enterprise Architect XMI 2 1 you have to press Next Page 27 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Introduction Choose a RM tool Select a requirement document 4 Choose attribute as requirement ID ITEMPPO documents 3 Implementation manuals6 2L ser Manual EA Export xmi 3 EN Figure 40 XMI file selection In the next step you have to press the button Browse in order to select the exported XML file After pressing Next you have to select an attribute EA property or tagged value which is used as TEMPPO requirement ID In our example the EA property Alias is used Choose an attribute to be used as requirement ID Introduction Note Values of the chosen attribute must be unique otherwise the import will be canceled Choose a RM tool 3 Select a requirement document Choose attribute as requirement ID Figure 41 Select requirement ID After pressing Finish you are asked if you want to assign this requirement structure to a project It is recommended to press Yes with the exception that you did not create any project Page 28 User Manual TEMPPO V6 2 Edition January 2015 Description of Use TEMPPO
50. e baseline and the view to import Intraductinn 2 Choose a RM tool 3 Select a requirement Baseline Latest Version not baselined document 4 Choose a baseline and a view Figure 22 Baseline and view selection Finish With the checkbox Use another attribute as requirement ID it s possible to use an attribute of the DOORS View as requirement ID When activating this checkbox the button Next is available see Figure 23 In the next step you can select an attribute which is use as requirement ID in TEMPPO see Figure 24 m L Steps Choose the baseline and the view to import Introduction 2 Choose a RM tool Select a requirement Baseline Latest Version not baselined document 4 Choose a baseline and a view View All requirements in state ready Requirement ID u Figure 23 Baseline and view selection Next In the next step you can select an attribute which is used as requirement ID in TEMPPO see Figure 24 The attribute s name has to be unique in this DOORS module The value of the specified attribute is shown in TEMPPO instead of the object number ID in DOORS But this object number is used as attribute So it means that the object number and the selected attribute have exchanged their functions Page 19 User Manual TEMPPO V6 2 Edition January 2015 Description of Use See Table 1 for effect of selecting an attribute for requirement ID Choose an attribute to be used as requirement I
51. ement attribute an requirement attribute Table 2 Data match 2 5 1 3 2 2 View concept TEMPPO Requirement Manager provides a view concept which enables you excluding requirements from a baseline This means that you do not want link all the requirements of this baseline to test cases For example you want to exclude all the requirements which are in state in work Such a view is created by applying a filter or specifying a logical expression to the requirement structure Figure 44 Requirement Structure View Page 30 User Manual TEMPPO V6 2 Edition January 2015 Description of Use If you select root node and tab View Figure 44 is displayed You can either select one of the existing filters and pressing Apply or an attribute and its value s that can be combined with logical operators AND OR In the lower area the result is displayed After pressing Apply the view is applied to the requirement structure All non matching requirements are disabled Here the question arises why they are visible at all Consider the following example A grandfather node is visible father not and child is visible Without any father the requirement could not be displayed in a tree S a 1 Functional m ef 1 Papierkorb lm ao 2 Billing ff 1 REQ SM 00015 m 2 Colect Data Fiter Dg No fitter PO amp e 4 Invoice jum da i s 5 Payment Heminde Object Type Y Requiremen
52. ent structure immediately This is necessary if you plan to import a test structure afterwards which contains requirements of the just imported structure At last the following information dialog is displayed CS 0x 1 2 J Requirement structure successfully imported Figure 46 Import successful 2 5 2 1 Possible errors during the import eros Rexton XML file doesn t match DTD schema Nothing is written to the database a error message is shown Correct the file 2 5 2 1 1Special cases Name of requirement structure exists Unique name is generated like _1 2 Message is shown see Figure 47 Requirement structure or requirement Object is created No message is doesn t exist shown ee TEMPPO Note Arequirement structure Import from DOORS with views 1 exists The imported one will be renamed For a later test structure import this can cause matching problems Figure 47 name of requirement structure already exists 2 5 2 1 2Example of an XML document lt xml version 1 0 encoding UTF 8 gt SIDOCTYPE TEMPPO EXCHANGE SYSTEM requslruccture dla gt SOTBMPPO VERSION VoU Build 05 2 lt TEMPPO EXCHANGE lt RS name Benutzerhandbuch version V3 rmstype Manual prefix prefix createdrms 21 12 2009 15 00 39 lt DESCRIPTION gt lt DESCRIPTION gt Page 32 User Manual TEMPPO V6 2 Edition January 2015 Description of Use lt REQUIREMENT name import XML ren
53. enu Requirement Structure New the window Requirement Structure Properties opens see Figure 1 A name description and an optional prefix can be filled in and by clicking the OK button a new structure is displayed see Figure 2 Page 7 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Fi TEMPPO Requirement Manager Testmanager Notepad Requirement Structure Edt Evaluation Windows Requirement Structure Notepad V4 General Vien Name Notepad Prefix Func_ Owner Testmanager Updator Created 13 02 2012 17 05 48 Updated Type Manual Description This requirement structure covers all the functional requirements Lock Appl Discard es Figure 2 Requirement Structure After pressing OK the new requirement structure is created and you are asked if you want to assign it to a project in TEMPPO Test Manager Of course a requirement structure can be assigned to more projects Please remark further that you can only link test cases to requirements of a checked in requirement structure baseline TEMPPO x 49 Before you can use this requirement structure in TEMPPO you have to assign it to a project tp Do you want to do this now Remark Do not forget to check it in Only frozen requirements can be linked to test cases Figure 3 Project assign request 2 2 Open an existing Requirement Structure When activating the menu Requirement Structure Open t
54. equirement ID mapping of an EA attribute to TEMPPO s Requirement ID And press Finish After that the tree and all requirements based on their content Page 38 User Manual TEMPPO V6 2 Edition January 2015 Description of Use e Name e Description e Short description are updated Changes in attributes new delete are not tracked as a requirement change 2 5 3 4 CSV If requirements have been imported from Excel csv they can be also updated in case of maintaining requirements is done in Excel Changed requirement name content short text attributes 7 CSV Update You can assign Excel attributes to TEMPPO ones Please activate the corresponding checkbox of an TEMPPO attribute and assign one by selecting an item from the combobox Remark New attribute values of UDAs will be automatically created in TEMPPO s meta data Requirement Requirement D ID v Name Name W Description Description Attributes Reg State Req State Figure 52 CSV Update Deleted requirements are not concerned since a deleted requirement can have child requirements which would not have any father anymore If requirements are imported from csv of course as a list and the list is transformed to a tree an update will keep this tree e The tree structure is NOT updated e Change requirements are updated e New requirements are added 2 5 3 5 XML If requirements have been imported from XML and are maintained in
55. est case and a text The text contains the reason why the requirement test case assignment could not be added to the DOORS DB The possible states of the assignments are e Open e Closed Page 44 User Manual TEMPPO V6 2 Edition January 2015 Description of Use E sirEPPO Testmanager i Project Test Structure Edit Test Execution Evaluation Tools Windows Help _ Test Structure Notepad System amp Acceptance Test System Test Y5 H 4 bk M 4 E o titer P ITI 5129 New Sy Open il Open normal General Attributes Preconditions Test Steps El i Open fie opened changes EEN Save M inherit LT Save E Save as E Ext no Ei Exi Yes tie open changes W 5 Edit Functions L Prin Functions FHL Search Functions a Hep System e E External interfaces of the product H Other product features required 4 Tasklist Notepad System amp Acceptance Test V5 Ex Task List new E 7 1234 R 1704 7 1234 R 2004 235 F 0815 General Test Case iD 1235 Requirement R045 Figure 60 Task List The lists are represented by a tree structure Each list consists of one or many entries All entries are marked as open the first time they are stored in the DB If the user clicks an entry the test case of this entry is selected in the test structure window The user now has the possibility to change the assignment delete it or create a new
56. estmanager Import from DOORS with views 5 Ei x Requirement Structure Edit Windows Requirement Structure Import from DOORS with views 5 1 M 4 bh M 4 E No Filter ww LL Import From DOORS with views 5 Lofft 1 gt gt Table El 2 Front Matter General Attributes 0 iiim 2 1 Software Requirements Specificatic D i 2 2 0 4 Requirement ID R 10 Ri 2 3 Import From Telelogic DOORS with pel fa 2 4 Distribution list Mame Document was created using the Following m ff 2 5 Mame talphab Department de fia 2 6 Hutzler Doris SV IIS REG Cwner Administrator Updator Administrator F m i i l Uppor 2 7 SITEMPPO S t SIS PSE KB C4 Hi 2 8 Document Management History of changes Creator in Telelogic DOORS Administrator Updator in Telelogic DOORS Administrator gt gt Table Persons authorized to make chang 12 Document was created using the Type Telelogic DOORS Microsoft Office Word 2003 Short Description Contents Iu 1 Introduction 422 1 1 Purpose of the dacument 4 Description l 2 Validity of the document 4 1 3 Definitions of terms and abbi 1 4 Relationship with other docu 1 5 Overview of the document e Detailed description of the req 2 1 Detailed description of produ J2 2 Viewsjin DOORS 4 of Lock Apply Discard Created 09 01 2008 12 31 17 Updated 09 01 2008 00 00 00 Created in Telelogic DOORS 21 08 2007 07 32 28 Updated in Telelogic DOORS 09 01 2008 11 16 22 Docume
57. etater eps riuwupidMusdxS sss admitido FEE rip ved 16 25 Ib DOORSusuiidpH ERIS MU EDDIE MM MEI eae DUIS 16 2 5 1 1 1 Possible errors during the import eeeeeeeese 22 2 5512 REJSIE PrO sra EE IUIS SOLO EU Co PI UD ED EE 23 2 5 1 5 Enterprise ATcHIte CE ui ipae ave rr SES wu ha Eb vada eU rr d 25 2 5 1 3 1 Enterprise Architect Export to XMI eere 25 2 5 1 3 2 TEMPPO Requirement Manager Import XMI 27 2 5 1 3 2 1 Enterprise Architect TEMPPO Data matching 29 2 9 29 2 2 NIC W COMCCD Gs2scsacnnses mi c2aessgncenesssaaeee ss sacnne say hareessenaens 30 Z5 JIWDOLE WOME camssueossasecaatunsnwansaassa sess essen onmniaeewnaanersasssaosans 31 2 5 2 1 Possible errors during the import cece ccc ee eee eeeeeeeeeeeeeeees 32 2 52 Spacia CASES vei ecc de suey OO een dE tel e b n a n d 32 2 5 2 1 2 Example of an XML document eeeeeeeeeennnnn nnn 32 Ze SPCHMMEE oi eet Sense kd sana eeeeeetaaeeas 34 Zadek DOOR cc TP d 34 2 5 9 14L Example for Upaatlrig ssxissvueis sida iota Dualo vaa da dt dv Der dua uns 35 25 942 REGUISICEP O aiaceaict ee tle eee oe sae saa EE M REID M teers LI 37 2 5 2319 EMMEDE Archie Esos mese a aeebedbde rA VINA RE DE ROTE NE ORAS 38 ENG E Gocce c EE 39 ZO AME n E 39 2 9 9 0 RESUIE OF UDGOSEbGucosstenti co alice pce a dif Gone add 40 2 5 3 7 Apply requirement updates eeeeeeeennn nennen 40 2 5
58. ey are automatically selected if their names match In the following example Name Description Owner and the requirement attributes Req State and Req priority are equal TBD exchange screen shot Bl Import CSV i You can assign Excel attributes to TEMPPO ones Please activate the corresponding checkbox of an TEMPPO attribute and assign one by selecting an item from the combobox Remark New attribute values of UDAs wil be automatically created in TEMPPO s meta data Figure 15 CSV import dialog Mandatory attributes Name and ID have to be assigned otherwise an import cannot be performed Fixed attributes like Description Short Description and Owner can be assigned to any Excel attributes If the owner is selected and the user is not available in TEMPPO the current importer is used as owner Attributes Any requirement attributes can be assigned with Excel attributes If a value to be assigned doesn t exist it will be created automatically Attribute names have to be exist in TEMPPO Req priorit If 2 or more values have to be assigned to an attribute Tem separate it in Excel with High Medium ZHigh Page 15 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 4 Edit Requirements Maybe the requirements changes after creation so you can edit them too After automatic or manually locking the requirement see 2 16 1 2 16 5 you can edit the requirement ID name short and long descr
59. gin is selected the time stamp of user s last logout is chosen Page 49 TEMPPO V6 2 Description of Use User Manual Edition January 2015 If a newsboard entry is activated the corresponding requirement is selected automatically except if one was deleted In the newsboard table the action new changed deleted requirement ID requirement name date of action and the person are shown If an item of newsboard is selected the corresponding one is also highlighted in the requirement structure iS Newsboard Import V2 Updated 26 03 2014 08 36 42 Updated 26 03 2014 08 36 42 26 03 2011 h 00 24 lo min 0 59 0 Changed since user defined Date Updator reqi00 i 14 02 2012 13 58 42 req101 reqi u req121 req117 req61 New Requirement Mew Requirement Before import 14 02 2012 14 09 18 14 02 2012 12 38 47 14 02 2012 13 58 42 14 02 2012 13 39 11 14 02 2012 10 40 28 E Testmanager Testmanager Testmanager 2 Testmanager Yi Testmanager E Testmanager E Testmanager E Testmanager Testmanager Testmanager E Testmanager E Testmanager reqi00 import 14 02 2012 09 35 37 E Testmanager fifi 2 reg101 importi E 8j 3 reg102 import2 83 1 reqi21 New Requirement Updator Testmanager Created 14 02 2012 13 52 29 Updated 14 02 7012 13 58 42 Type Manual Short Description Apply Discard Figure 69 Newsboard 2 12 Version Configuration management is a task that c
60. he following chapters are describing the locking in manual mode Page 74 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 16 2Edit FK TEMPPO Requirement Manager Testmanager Import EN E x Requirement Structure Edt Evaluation Windows e Requirement Structure Import v2 fi 2 importi fi 3 import ene bbls tan Locked by Testmanager Requirement ID reat nn Name mporto Owner Testmanager Llpdator Testmanager Created 14 02 2012 09 36 35 Updated 14 02 2012 12 38 47 Type Manual Short Description shortt Description contento Lok Apply Discard Figure 96 Lock state After locking the requirement you can edit the selected requirement 2 16 3Find locks unlock Z ure New Requirement 1 Testmanager 10 10 2012 10 06 13 New Requirement 10 10 2012 10 06 54 Figure 97 Requirement structure Find locks In principle TEMPPO RM only user locks are possible The following items can be locked e Requirement e Requirement structure root e Version Locks can be found either in the requirement structure or test suite e Requirement structure When activating the menu item Find locks menu requirement structure Figure 97 is displayed By selecting one or more locks and pressing the button Unlock selected elements locks can be removed Page 75 User Manual TEMPPO V6 2 Edition January 2015 Description of Use If the user still believes
61. he window Open Requirement Structure with name owner prefix creation date and version is displayed Page 8 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Fi Open Requirement Structure x ooe owe created version gt Anforderung 28 09 200 viD latest gt Anforderung 10 31 08 200 v1 latest amp Anforderung 20 01 09 200 v1 latest Anforderung 9 31 08 200 Yi First CSV import 05 10 200 v2 latest I csv impart II 05 10 200 v1 latest lil Demo R5 10 10 200 v2 latest INE doorsmodule 12 10 200 v1 latest Johannas R5 093 10 200 Y3 latest Mi Meine 25 09 200 Hew Requirement Structure O2 10 200 Release2 I Mew Requirement Structure 26 09 200 ue dad e New Requirement Structure t 1 07 10 200 Ye latest IN Mew Requirement SEruckure11111111111111 02 10 200 v1 latest Ib Petra 2 07 09 200 v4 latest b Petra Test 05 09 200 25 latest i RS 09 10 200 v1 latest ciranhsanich we 13 0n SI M Makart z Cancel Figure 4 Open Requirement Structure Exactly one requirement structure can be selected and is opened by clicking the Open button The name of the requirement structure is shown in the title bar of the main window Cancel closes the window and no requirement structure is opened Additionally a requirement structure version see Figure 4 can be selected if a non latest version should be
62. hich attributes your requirement has deactivate the checkbox above the list Page 71 User Manual TEMPPO V6 2 Edition January 2015 Description of Use FK TEMPPO report setting for requirement structure X Mame NewReportSetting El Settings EF General j d Title Page Header Footer Available Attributes selected Attributes I Requirement j EL Continuous Report Bg Requirement E uc Gwer Short Description la in view Preview Cancel FK TEMPPO report setting for requirement structure X Mame new Report Setting El Settings EF General Header Footer Available Attributes E Text E Continuous Report F Requirement Requirement Selected Attributes Preview Cancel Figure 94 Reporting Textual Settings Tabular Report You can specify the sequence of the columns by swapping the column headers and for defining the width of the columns in the report you have to move the border of the columns Page 72 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Fi TEMPPO report setting for requirement structure X Name NewReportSetting Settings General r Requirement Structure gt Requirements Attributes ee Tithe Page Header Footer Iv Requirement Iv Requirements Attributes Available Attributes selected Attributes Available Attributes Selected Attributes Short Description
63. iPRMCON DI YO EDER DO ERE da DERE NR NC ESPERE KV DFREER Edd E 94 5 1 DTD Schema for XML Import Requirement Structure 94 6 Ind6oudkssvs eaa ina VER EORR ERREUR MANU NE MER ERES ERR DUC DITE VU CUEREEEEREMRES RUE 95 Page 5 User Manual TEMPPO V6 2 Edition January 2015 Introduction 1 Introduction In the specification phase the definition of requirements is fundamental for every project defining the purpose exactly e g how the implemented software should work or which features should be implemented The organization of this information mostly occurs with documents In large projects there is mostly more than one document which specifies requirements because subprojects are built Now the requirement environment of TEMPPO allows managing the requirements in structure s So a requirement structure contains requirements which can contain further requirements Some time requirements changes in the life cycle of the project Requirements can be changed easily and can be saved versioned in the database TEMPPO Requirement Manager also provides the collaboration of TEMPPO with IBM Telelogic DOORS IBM Rational Requisite Pro and Sparx Systems Enterprise Architect For using the importing and updating feature the client for DOORS or RequisitePro must be installed where TEMPPO is used TEMPPO Requirement Manager RM has integrated following features Editing and administrating requirements together with attr
64. ibutes Version control including baseline and view concept Importing and updating requirement structures from DOORS RequisitePro or Enterprise Architect to TEMPPO see 2 5 1 ff Importing and updating requirement structures from an XML file Importing and updating requirement lists CSV file The requirement managers have access to test management data to make statements about the actual situation of the project progress and quality Therefore it s important to assign the requirements to the test packages or test cases in order to fulfill requirement tracing In the TEMPPO Administrator you can assign the requirement structures to the projects and then the requirements to test packages or test cases in the TEMPPO Test Manager with a read only access Page 6 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 Description of Use 2 1 Create a new Requirement Structure A requirement structure is the first created element in TEMPPO Requirement Manager You can either start by creating importing a new requirement structure from DOORS Requisite Pro Enterprise Architect CSV or a XML file or opening an existing one x General Mame Notepad Prefix Func_ Owner Testmanager Updator Created 13 02 2012 17 04 35 Updated Type Manual Description This requirement structure covers all the functional requirements Figure 1 Requirement Structure Properties When activating the m
65. ich exceeds the limit of 488 28 kByte gt Do you want to continue Figure 116 File size exceeds the upload limit 2 17 2 2 Edit hyperlinks If you select a hyperlink web file system upload and activate the context sensitive menu mouse over hyperlink and choose the menu hyperlink Figure 112 is shown where you can change the link into the web link into the file system upload 2 17 2 3 Remove hyperlinks If you select a hyperlink web file system upload and activate the context sensitive menu mouse over hyperlink and choose the menu remove hyperlink the hyperlink is removed But take care that an upload remains in the database To remove obsolete uploads see user manual administrator chapter 5 5 5 Page 84 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 17 2 4 Download If you select a hyperlink upload and activate the context sensitive menu mouse over hyperlink and choose the menu download Figure 117 is shown to select a directory for the file download Bj Select a destination directory f xj Look in E Eigene Dateien M F 3 4 O Aktien 85 Eigene Musik TUR C Artikel E Eigene Bilder verwendete O Audi C3 My Podcasts Perso O CC TestFactory My Received Files Downloads E Eigene videos Eigene Datenquellen 3 Nerovision Desktop O error Report201 21302130732 D Obsorge O gegl 0 0 O Ranorex A HP sap Eigene Dateien O I MO RA AT 23 Schl
66. igin CaProgram Files TEMPPO 6 OYogqging properties a Size 1 95 kByte Created 14 02 2012 14 01 00 Owner Testmanager References 0 Type Upload Description Figure 113 Upload properties Upload a new file You have to activate the Upload button to open Figure 113 for specifying a special name and description Additionally owner creation date size the number of references and the type are displayed x an iweb File Database Reference E Creal oe Figure 114 Hyperlink database Use an existing upload You have to activate tab database and press button create reference to uploaded file to open Figure 115 which shows all uploads of the database For creating a new reference on an existing upload you simply have to select it and click OK in Figure 115 and Figure 114 Page 83 User Manual TEMPPO V6 2 Edition January 2015 Description of Use F Uploads X Find launcher properties Testmanager 14 02 2012 14 02 33 2 10 kByte logging properties Testmanager 14 02 2012 14 03 06 1 95 k Byte uninstall og Testmanager 14 02 2012 14 02 51 2 67 kByte Figure 115 Uploads The upload limit of a file is set to 0 5 MB by default and is specified in the file admin properties dbsettings upload limit 500000 But it is only information Of course you can upload files that exceed that limit and or change this value in admin properties TEMPPO Note X You are about to upload a file wh
67. inistration Created 25 10 2006 09 56 13 Updated Created RMS 25 10 2006 00 00 00 Type Manual Description Lock Enim Discard Page 36 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Ei RMS LTestmanaoer ee iBi xi Requirement Structure Edit Windows Requirement Structure Huge Module 1 V7 E mpm E ga How to Use FFA The Test Process Phases General E ga Multi user ability FFA General principles and user promp Name Huge Module 1 E Menu Reference Ep Manager Owner Testmanager Updator Testmanager B Database Connection ti User management E ga Administration Creator RMS H Database Connection Created RMS 25 10 2006 00 00 00 amp g Test Automation Settings Hf Roles Type Manual Efi User management fe Customizing Metadata Wg Projects El Locks Hf Database migration EE License Server Connection ff Notification Created 25 10 2006 09 56 13 Updated 25 10 2006 13 49 38 Description Lock Enim Discard Figure 50 Compare before and after updating 2 5 3 2 RequisitePro With this feature you can update your requirement structure from TEMPPO to the project in RequisitePro Data imported from RequisitePro cannot be updated by a TEMPPO user RequisitePro requirements can be updated in RequisitePro and imported in TEMPPO or changed in latest The update function is the same as in 2 5 1 This function checks in the actual latest version see also 2 11 an
68. ion n lt aniei PUMA Sos aitcivin E 64 2 15 2 Progress Cl ae obeerohsanipv vind Voss AA E T det nines 66 2 15 3 R POrUNO senE Ai pM See chs eek ee ea cece 67 2 45 31 NOW 7 EdlUisscuss vies E EE dd dco E Pa ea vidc E RD dr e an ED UR 67 2 15 35 Vek Generalerna RIM E s EPI MI ED MM E IEEE 68 2 15 5 452 TEXE uisa ved senna snd uia dulc sana heen MIU wana MEET MEE 71 2 15 5 1 2 Cart Setiligssusescitoisuioa tui DEDI dH I br ISI DE bed 73 2A5 3 2 PFEVIEWING ANG SAVING ssesiesievpotdt km Ce oi nel c vane tC 73 2 15 3 3 MPO TFOM AM IS necs i i ee ce HP ect e va D cR AC Cl ces hears 74 2 15 34 TEXDOEEREOCEM E arrr orir deus TEIRERKIERUN poxSEPOSPPUP ILI EPT IIS aaen 74 2 15 PIUlti user abIlIU V ooi vacca Beaded Y es icd ache 1 atcp a eem x EE uro e Rees vines 74 2 16 1 LOCK MOGE S cuiii dt teen tatnen od Dont sar e p att ed a 74 Zola ATTI LIBETCT 75 2 16 3 FING IOCKS UIMOCK taaedane thos asa pe epa III Lehm TARIR 75 2010 4 S oWwalock State sant sencccsvdsisisdhantadad extre tuU eai ra EV A ur Koen anes 76 210 5 Change dll ICM auniiccanscans tiated ud oa ctetu san RD E A Gn be bg 76 2 16 6 Delete arn IteITisesivesesessepstsesssc rud uberi E Zea iaad adu Ta ierra rada 77 240 7 TIBa dnvalid IockKSuszoruod visinn adea A videt a dde rU e d ntux 77 2 16 8 Rel rese aedem Send radiata A se CU xu EHE aV PIT RUE 77 71670 1 Refresh manually sacres eein 77 2 16 8 1 1 Reloading the whole requirement structure 77 2 16 8
69. ios of interactions i Required functions of the product pu ir Aa a Created 20 11 20 Updated 20 11 201 Type Manual Description This requirement structure covers all the functional requirements TBD screen shot In the next step you have to check in the current requirement structure version Please activate the menu item Requirement Structure gt Versions and Figure 72 is displayed Initially there exists just one version of the requirement structure version 1 on the main line In TEMPPO every last version gets the Page 52 User Manual TEMPPO V6 2 Edition January 2015 Description of Use label latest signaling that the requirement structure in this version is checked out for editing LA Versions Edit properties of selected Edit L Check In Check in active version K Activate id Merge ZB Delete Tree style Activate selected version Merge to latest version 7 Labels only ON EIu ES Delete latest version 7 ClearCase style Order Change tree style Figure 72 CM Version tree before first check in If you check in the requirement structure by using the Check in active version button in the Versions dialog you have the possibility to specify a label All ready requirements Then the version tree looks like displayed in Figure 73 The requirement structure gets checked out immediately and version V2 is created The symbol Z amp signals
70. iption Fi TEMPPO Requirement Manager Testmanager Notepad a ioj x Requirement Structure Edt Evaluation Windows Requirement Structure Motepad 1 E x M 4 bh M e B No mter ALII Motepad gt lt A 1 Introduction E 2 General description of the product General Attributes H fij 3 Detailed description of the product ti 3 1 Scope of delivery Requirement ID Func rea26 Ba 3 2 Sequences scenarios of in i ia 3 3 User goals El fa 3 4 Required functions of the pre Eh fit 3 4 1 File Administration Do 55 411 New Ga 3 44 2 Open Created 14 02 2012 08 39 56 Updated 14 02 2012 09 06 07 88 3 4 1 3 Save ta 3 41 4 Exit WH ip 3 4 2 Edit functions short Description EH gs 3 4 3 Print functions E bia 3 4 4 Search functions Mame Mew Owner Testmanager Updator Testmanager Type Manual Description Notepad shall open a new document An existing document shall be stored or be lost Cancel shall also be possible Lock Apply Discard Figure 16 Editing requirements After editing click the button Apply for saving your changes 2 5 Import a whole Requirement Structure TEMPPO is able to generate a whole requirement structure with requirements and its information etc by importing 2 5 1 Import from RM Tool With this functionality you can import a requirement structure from a requirement management system 2 5 1 1 DOORS TEMPPO maintains IBM Telelogic DOORS a
71. item is enabled if a requirement structure is opened and a requirement is selected A new requirement is created before the selected one and a new name has to be entered The default name is New Requirement A requirement contains the following tabs e General In the tab General you can change the requirement s id and its name Furthermore you can fill in a short and a long description e Attributes In this tab Attributes specified in the Meta Data Editor can be set for requirements Before linking attributes to requirements you have to create them See Figure 6 ff e History In the tab History all changes are tracked Page 10 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 3 1 1 Attributes 4 Properties of New Entry CJ Req Type Blocker Cl Req Type High amp J Req Type Low E Req Type Medium Owner Testmanager Test Package i Created 17 11 2014 13 45 57 For Use of Test Case EE Test Suite Test Result v Requirement Description This attribute reflects the priority of the requirement Figure 6 Creating a requirement attribute After clicking OK the attribute is created and the user is asked if he wants to assign it to requirement structures TEMPPO CX 00e ae Figure 7 Assign requirement attribute to requirement structure After pressing Yes user has to select the requirement structures where he wants to add the attribute to a
72. ition January 2015 Description of Use No blank is allowed only a comma Fi Build In Clause X Assign selected values Figure 81 Selecting attribute values for IN NOT IN Attributes Operato Operator Operator Valu Value Wild e lt card allowed 3 Planned coverage Requirem ent name Requirem ent short descriptio n Requirem ent ID m um D ct N Updater Created Updated Requirem ent attributes i 1 Yes if operators IN NOT Il if operators IN NOT IN are selected Yes if a set of values can be selected Yes if editable is Yes Page 62 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Table 3 Attributes meanings The user can write free text that may also contain wildcards like x any number of characters any single character F Filter Properties Mame Mew Filter Conditions Attribute Value rmase J J mnemerteainwone J ano J X Created C wyrier Planned coverage Requirement ID Requirement Name short Description Req State IM Implemented In work AND Owner Testmanager AND Planned coverage 1 e Figure 82 Filter criterion 2 14 8Export filter It is possible to export filters to XML and import them again When either activating the menu Filter Export or pressing the button Export selected filters to XML Figure 83 is displayed and the filter can be saved Bi save
73. loaded 2 3 Create the Requirements After creating or opening the requirement structure can be filled in the following Ways e Build manually e Importing from CSV 2 3 1 Create manually The user has to create requirements manually Each requirement can have more requirements So you can build a clear arrangement of your requirements There are 4 Object types e Package is similar to a folder or place holder e Heading reflects a requirement without any content e Additional Text reflects a requirement with additional information to a requirement e Requirement real requirement Page 9 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 1 Real Requirement Requirement ID req3492 Name Real Requirement Owner Testmanager Updator Testmanager Created 17 11 2014 12 18 32 Updated 17 11 2014 12 18 41 Type Manual Object Type Requirement Apply Discard Figure 5 Requirement General With the menu item Edit New Requirement a new requirement is created below the selected requirement structure or requirement This menu item is enabled if a requirement structure is opened and the requirement structure or a requirement is selected A new child node is created below the selected one and a new name has to be entered The default name is New Requirement With the menu item Edit New Requirement Before a new requirement is created before the selected requirement This menu
74. ment import wizard Introduction When pressing Next Figure 19 is shown in which you choose IBM Telelogic DOORS Page 17 User Manual TEMPPO V6 2 Edition January 2015 Description of Use irements from an RM toc Choose a RM tool Select a requirement 1 IBM Telelogic DOORS document Z 4 Choose a baseline and a view C IBM RequisitePro 7 9 Enterprise Architect XMI 2 1 Fish Figure 19 Requirement import wizard Choose a RM Tool Then the server for DOORS starts and the following progress bar is shown Figure 20 Progress Figure 20 Starting server In the next window you select a module from the tree In the tree the projects and modules from DOORS are shown see Figure 21 Select a requirement document 4 Choose a baseline and a view iimport from DOORS with views Figure 21 Requirement import wizard selection After selecting a module and pressing Next Figure 22 is shown where the user can select a baseline or the latest version of the module Additionally the user has to select a view Page 18 User Manual TEMPPO V6 2 Edition January 2015 Description of Use With the view it s possible to use only a restricted number of requirements in TEMPPO and not the whole tree from DOORS Views also contain attributes which are imported too see Figure 26 With pressing Finish the module is imported to TEMPPO LA Import Requirements from an RM too Steps Choose th
75. nd thus the client for DOORS must be installed Page 16 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Import from DOORS with views current 0 1 in test1 Formal module DOORS A oj x File Edit view Insert Link Analysis Table Tools User Help Bar Se e IXxv sz s s3 B rz u t reaib attevets j j c bu x Import from DOORS with views a Table 1 Front Matter Gabi Firmen 35 Document Management 2 Administrator RO 04 36 History of changes 2 Administrator RDS Import from Telelogic DOI 68 Persons authorized to make changes 2 Administrator Rog Distribution list 69 Document was created using the following tools 2 Administrator R10 Name alphab D epartme 70 Microsoft Office Word 2003 2 Administrator Ril Hutzler DorisS ISREG 71 Contents 2 Administrator R12 SITEMPPO Support SIS 72 l Introduction 422 2 Administrator R13 Document Management 73 11 Purpose of the document4 2 Administrator R14 heart enne 74 12 Validity of the document 4 2 Administrator R15 Persons sdheindigms 75 13 Definitions of terms and abbreviations 4 2 Administrator R16 Document was created u 76 14 Relationship with other documents 4 2 Administrator R17 Microsoft Office ward 20 77 1 5 Overview of the document 4 2 Administrator R18 Contents 78 2 Detailed description of the required product features 4 2 Administrator R19 IIntrod
76. nt was created using the following tools Figure 25 Imported requirement structure with Views When there is an attribute specified as requirement id then the value of this attribute is shown for the ID see also in Figure 25 This specified id is also displayed in the TEMPPO test environment All imported attributes are shown in tab Attributes see Figure 26 KW TEMPPO Requirement Manager Testmanager Import from DOORS with views 7 Requirement Structure Edit Windows Requirement Structure Import from DOORS with views 7 V1 mod M 4 bk M E i fiter Import From DOORS with views 7 Hg 1 gt gt Table B a 2 Front Matter General Attributes 0 pia 2 1 Software Requirements Sp ti 2 2 0 4 f 2 3 Import from Telelogic DOO figs 2 4 Distribution list fiiy 2 5 Name alphab Departmer E Level 2 seas fifa 2 6 Hutzler Doris Sv 115 REG E Updator Administrator Li 2 7 SITEMPPO Support SIS PSE iid fifa 2 8 Document Management fil 2 9 History of changes p 2 10 gt gt Table DOORS ID IMP 58 bia Persons authorized to me 12 Document was created u Microsoft Office Word 20 Contents 1 Introduction 422 1 1 Purpose of the docun 1 2 Validity of Ehe docum 1 3 Definitions of terms a 1 4 Relationship with oth 1 5 Overview of the doce 2 Detailed description of 2 1 Detailed description c 2 Views in DOORS M Lock Apply Discard k User Manual TEMPPO V6 2
77. nual TEMPPO V6 2 Edition January 2015 Description of Use Formal module Huge Project Huge Module current 0 0 DOORS File Edit View Insert Link Analysis Table Tools User Help Bagr sel y x v e B z u Standard view e n levels sE m xx a Il ea lit CAPE E E WI REDE i v dex RR I Il WW Ill El Huge Module 1 Description of Use p 1 1 The Test Process Phase How to Use El 1 21Multi user ability 266 1 The Test Process Phases E 1 30General principles and u 274 E d 4 Menu Reference 1 1 1 Test Planning 20Manager 275 The definition phase covers the tasks of E 2 1 Database Connection 276 Writing the Test Plan EF 221User management 277 Writing the Project Plan E 3l dministration 278 Defining Test Case Attributes 3 1 IDatabase Connection eae 279 Am 3 2 Test Automation Setting 1 1 1 1 Writing the Test Plan 3 30Roles 280 The test plan is an stdSEM document and writing is outside the scope of SiTEMPPO However it s 3 4 0User management the base document for all test topics during the development process and covers subjects like test 3 5 ICustomizing Metadata requirements test management test documentation test goals end of test criteria etc Its 3 6 IProjects contents are obligatory for all members of the test team For detailed information please refer to 37 Locks http se Hlt528565386m HItS28565386 siemens at stdsem e p desi ge2 htm 3
78. o the projects so that the requirements are available for the test packages or test Cases Open the TEMPPO Administrator application and after connecting chose the tab Projects LA TEMPPO Administrator Testmanager MI y pF S 8 Demo Notepad E Fi System and Bug retests EH Fi d Figure 64 Assign Metadata Then click the button Assign Metadata see Figure 64 and then Figure 65 is opened In the tab Requirement Structure you can select the requirement structures for the selected project Page 47 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 7 Meta Data Editor Learning Project Use Ca Link test to require Import Molenpad Import from DOORS with vi VOEERESUNEOIRRS Import from DOORS wath vi Import from DOORS wath vi Learning Project Use Cases Figure 65 Assign requirement structure 2 10 Link Requirements Before you can link test cases to requirements you have to assign a requirement structure to the project For linking requirements start the TEMPPO Test Manager After opening the project and the test structure select a test package or test case and open the tab Requirements see Figure 66 Requirement Mame Requirement Structure Version Lock Apply Discard Figure 66 Link requirements The test case can inherit from the test package s requirements Additionally the selected tes
79. oblem with requirement ids the requirement structure could not be imported Far information read the error fle CALIsergvatw112h9 temppologumponDOORs 1416477728044 kx Do you want to open the error file now i amp l xi 11 01 2008 10 16 29 ID 32 Duplicate reg ID R s 11 01 2008 10 16 29 ID 33 No reg ID 11 01 2008 10 16 29 ID 36 Duplicate req ID ROS Figure 29 Error text file Page 22 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 5 1 2 Requisite Pro The RequisitePro client must be installed gt Rational RequisitePro Learning Project Use Cases FEAT Web Shop System Features E B xl T File Edit View Requirement Traceability Tools Window Help 8 x olele S llas vi Fly mi olg 1 7 Coverage Analysis PSI Requirements 1 3 Features and Vision B Web Shop Administrative System b FEAT1 Secure payment method C5 FEAT10 Ability to add remove Secure payment method F3 FEAT11 Ability to check on cu 65 FEAT12 Maintain customer inf CI FEAT13 Generate reports Web Shop System FEAT2 Easy browsing Easy browsing for available titles eI FEAT1 Secure payment metho FEAT3 Search by multiple criteria LI FEAT2 Easy browsing Ability to search for CDs by multiple criteria C5 FEAT3 Search by multiple crite cd FEAT4 Ability to check status FEAT 4 Ability to check status of an order z FEATS E mail notification of ne
80. of hiding requirements that are not of interest All fixed and user defined attributes can be used to define a filter criterion Filters are stored to the database and are user specific not global Set filters won t remain associated to a requirement structure after closing and reopening TEMPPO Requirement Manager 2 14 1Predefined filter Like TEMPPO Test Manager TEMPPO Requirement Manager provides a predefined filter The filter Selectable requirements is used for requirement structures imported and updated from 3 party tools For the reason of already filtered requirement structures by a view some requirements are displayed in gray color which means that they are not selectable They are displayed in the requirement structure because they could contain selectable requirements If you set the filter Selectable requirements all grayed requirements are not displayed Page 56 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Personal Filter 1 Testmanager 01 10 2010 13 08 49 X D Selectable requireme Testmanager 01 10 2010 13 08 48 Filter conditions read only Attribute Value selectable true E 4 k selectable true Iw Hide Empty subtrees Impact to selected Window Requirement 46 oO Apply Cancel Figure 76 Predefined filter 2 14 2Create Filter You can create a new filter using menu Edit Filter or using the Filter Combo box
81. open report setting is imported to TEMPPO 2 15 3 4 Export to XML For exchange you can export your report settings to an XML file Press the button Export report setting to XML file and then a file dialog opens After selecting the path and file name press Save Then the file is exported to XML 2 16 Multi user ability Multi user ability establishes an environment for working with several users in a parallel way on the same requirement structure It prevents unintentional overriding of changes manages the synchronization between viewed and stored data and avoids inconsistency if multiple users work on the same database Moreover it provides features to facilitate the collaboration in a team working on the same TEMPPO requirement structure Chapter 2 16 1 describes the behavior when locking and editing an item On the other hand chapter 2 16 8 illustrates the 2 possibilities of refreshing manual automatic Multi user ability is not supported for MS Access databases 2 16 1Lock modes TEMPPO provides 2 possibilities of locking items requirements e Manual lock e Automatic lock If you are working with manual lock mode you always have to press the button Lock before having the exclusive right to work on that item On the other hand you simply have to select an item and it is automatically locked if another user does not lock it This feature can be configured when activating the menu Windows gt Settings T
82. ort2 i 1 d ut Ctrl mpg OOOO O amp Import Cony Ctr c Eal Faste Ctrl fix amp Paste taforz er Testmanager Updator Testmanager I Order b bd 14 02 2012 08 34 44 Updated 14 02 2012 12 23 22 ra E Delete pe Manual Edit Fitter CtrhF bnr Refresh recursively Lock Apply Discard Figure 104 Refresh recursive menu also in the context menu 2 16 8 1 3 Refresh on certain user actions An item is automatically refreshed including its lock state and the presence of all direct children after the following actions e selecting in the tree view Page 78 User Manual TEMPPO V6 2 Edition January 2015 Description of Use e pressing the Lock button If these actions are done on an actually deleted item the following dialog is shown and the item is removed from the view x IN Cant find item in databasel Maybe the item was deleted by another user Figure 105 Deleted item information after trying to select or to lock 2 17 General principles 2 17 1Multi selection TEMPPO offers a feature for multi select requirements The multi selection mode can be used for e Deleting requirements e Cutting requirements e Copying requirements e Assigning attributes to requirements When the multi selection mode is activated the items aren t locked automatically They are only locked during the time for saving If items are locked by other users the changes are not applied to these items They are displ
83. osser Home C3 MBIIS Working il SharePoint Drafts Pr e Arbeitsplatz E m 3 Media Go B SharePoint Entw rfe C My Meetings B Sony Ericsson ed Download QI Files of type All Files v Cancel File name uninstall logder Figure 117 Destination selection 2 17 3Applying Discarding When working with requirement structures you can save your changes within requirements using the button Apply By pressing button Discard your changes will be undone after a confirmation message The buttons are only enabled if the selected node has been changed since it was loaded Fi TEMPPO Requirement Manager Testmanager Import Requirement Structure Edit Evaluation Windows Requirement Structure Import v2 M 4 b M E vo site J Import BR 1 importo ite NERIS General Attributes 3 import j Seen Fee Requirement ID Ireq1u1 fia 3 2 Mew Requirement 1 une moth 4 Owner Testmanager Llpdator Testmanager Created 14 02 2012 12 21 43 Updated 14 02 2012 13 58 41 Type Manual short Description shorti Description content changed Lock Apply Discard Figure 118 Apply Discard Page 85 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 17 4Find and Replace TEMPPO offers a find and replace mechanism With the menu item Edit gt Find and Replace Figure 119 is shown Fy Find and Replace B X Search in ame for
84. overs all phases in projects Supporting a large palette of CM tools from a very powerful but expensive one like ClearCase to a cheap one with restricted functionality would be a challenge For example ClearCase offers attributes for each administration unit VSS does not have such commands In TEMPPO it is possible to check in an entire requirement structure where whole means the hierarchical order of all requirements as well as their data In contrast to other CM tools where check in and check out are separate steps checking in a requirement structure in TEMPPO will check it out again i e a new editable version is created automatically Naturally you have the possibility to restore any version of the requirement structure that has been checked in Page 50 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Versioning is meaningful when you have to change extend your requirement structure due to version changes of your application A requirement structure is automatically versioned before an update from a RM Tool Versioning manually and apply a view You create and activate versions in TEMPPO Requirement Manager using Requirement Structure gt Version The following example should illustrate how the CM features of TEMPPO Requirement Manager works First of all you have the possibility to apply a view to a requirement structure which you want to baseline create new version A view is a filter which includes
85. quirement updates Test Structure Clemens test System Test V2 f d H gh Be No Fiter 7 Clemens test Mew Test Package pun Mew Test Case a fal New Test Case 1 S New Test Case 2 Inherit The following Huge Module 1 chapters are M New Test Case describing the General Attributes Test steps B futomation Requirements docking in manual model Figure 56 Assigned requirement The test case has assigned the requirement 1194 see Figure 56 Nevertheless this requirement is deleted in DOORS Figure 57 Formal module Huge Project Huge Module current 0 0 DOORS E zn File Edit View Insert Link Analysis Table Tools User Help M amp m xBumcmivixvistz B z U Standard view ej fan levels gt Xe oft x E Huge Module E 1 DHow to Use F OE IMulii user ability d n i 0 EE 1 1 1 Lock modes aam proper Tues 00 SITEMPPO provides 2 po Automatic llocking mode auto 00 e TAutomatic lock 00 Jf you are working with me 1194 iran chantore M describing the locking in manual mode nser sE sE wget Se Es zzg Bvije jmwi 050 0 v On the other hand you sir l This feature can be confic OP im gt gt Table v Table 1 Locking modes i 5 The following chapters are 0 1 1 2 0Editing 00 1 1 3 Refreshing 1 2 IGeneral principles and user pi i 1 3 0Menu Reference 20Manager Link Cut Copy Dele
86. re Open the TEMPPO Administrator application and after connecting chose the tab Metadata and then tab Requirement Structures A TEMPPO Administrator Testmanager 22 02 2012 10 03 48 16 02 2012 11 24 18 Me Customer requirements L1 13 02 2012 16 50 26 M Import 14 02 2012 09 34 44 Ke Import from DOORS with views 3424875 20 11 2014 11 20 50 IBM Telelogic DOORS ee Import from DOORS with views 1 248 20 11 2014 11 25 27 IBM Telelogic DOORS MP Learning Project Use Cases 1 i 14 02 2012 14 54 30 IBM RequisitePro fe Link test cases to requirement 14 02 2012 11 13 39 Manual gt Notepad Testmanager 13 02 2012 17 05 48 Manual e Notepad 1 2424875 17 11 2014 14 19 03 qe Requirements for user documentation Testmanager 14 02 2012 09 20 13 E SW requirements Testmanager 14 02 2012 09 20 49 Me User requirements Testmanager 14 02 2012 09 15 32 Figure 62 Assign attributes The assignment is made for each requirement structure Page 46 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 7 Meta Data Editor Figure 63 Meta data editor On the left side all available attributes are listed By clicking the buttons gt gt gt the attributes can be moved to right list box The assignments on the right are saved by pressing the button Apply 2 9 Assign Requirement Structures to project In the TEMPPO Administrator you can assign the requirement structures t
87. re 10 Bj Attribute value selection l x Attribute auai dy Audi ADR F FUNC REQ O06 ADR F FLNC REG OD8 amp gt Audi ADR F FUNC REO O09 H jM Audi ADR F FUNC REG 010 Find EE d Audi ADR F FUNC REQ O0 Audi amp gt CAR F GEME REG D11 S CAR F GENE REQ O12 amp gt CAR F GENE REG D13 S CAR F GEME REG D14 S CAR F GENE REQ 015 gt CAR F GEME REG D18 gt CAR F GEME REG D17 amp gt CAR F GENE REG D18 amp gt CAR F GEME REG D19 Sp CD F FUNC REQ 001 e Figure 10 Attribute value selection When the requirement structure is imported DOORS Requisite Pro attributes can t be assigned or deleted The default plan value for Planned Coverage is 1 and not editable 2 3 1 2 History In the tab History entries until the last check in are shown Page 12 User Manual TEMPPO V6 2 Edition January 2015 Description of Use If a requirement is selected and tab History is activated requirement history is Shown Only the entries until the last check in are shown The tab has the following columns e Date changed on e User changed by e Property possible values General UDA e Comment Comment of user If the mandatory flag for comment is set on and requirement is saved a history comment is popped up on apply see Figure 12 e Action possible values add change delete merge e Info additional information for changing reason e g which attribute was set e Version
88. requirement For presentation Testmanager 03 10 2014 10 02 08 New Requirement Structure Testmanager 30 10 2014 08 26 11 E Requirements Models 24 09 2014 11 43 23 Figure 8 Select requirement structure s If a requirement is selected and tab Attributes is activated you can enter Planned coverage for the number of test cases which have to be created in order to get a positive coverage This means that in the following example New Requirement has be linked to at least 3 test cases and the requirement is displayed covered in TEMPPO s requirement analysis The default value is 1 Page 11 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Additionally any requirement attribute can be assigned to the requirement Requirement Structure Edit Evaluation Windows E d 1 Introduction Ap 1 You can go somewhere m 2 PENSIO IE Lp 4 Load News headlines per ca E 2 General description of the produ B p 3 Detaled description of the produ Planned coverage 1 999 3 test Enter number of test cases to be created inked in order to get a minimal coverage in test manage ln 4 Required functions of the prc a ip 1 File Administration Figure 9 Requirement Attribute By specifying a sub string in the Find field you can easily navigate to the attribute s to be related to the requirements Multi select allows moving several values to the right part of the window see Figu
89. rl Copy Ctrl C Faste Ctrl V B Paste before 1 Order d JA Delete Delete Refresh recursively Figure 108 Context menu For selected items attributes can be assigned or deleted Page 80 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Fi TEMPPO Requirement Manager Testmanager Import E E Requirement Structure Edt Evaluation Windows 5 Requirement Structure Import v2 M 4 b M e EE No nte Attributes Planned coverage 1 999 1 test cases Enter number of test cases ta be created linked in order to get a minimal coverage in test Figure 109 Assigning attributes The color grey means that the attribute value is only assigned to a subset of the selected requirements On right mouse click the menu Assign to all requirements can be called Fi TEMPPO Requirement Manager Testmanager Import 7 loj x Requirement Structure Edt Evaluation Windows e Requirement Structure Import v2 M 4 bh M zs IIS Attributes Planned coverage 1 999 f test cases Enter number of test cases to be created linked in order to get a minimal coverage in test iw Req State Implemented CJ Req State Reviewed 2 17 2Hyperlinks and Uploads Generally you can mark text as e Hyperlink to the web e Hyperlink to a file e Hyperlink to an upload Page 81 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 17 2 1 Create
90. s some filters might not be usable in the apened project and therefore not visible After saving the new filter Figure 78 is closed and Figure 77 is shown The new filter is inserted and selected in the list box the filter criterion is displayed read only and the table visible hidden requirements is updated 2 14 3Change Filter You can change existing filters by pressing the edit filter button This button is only enabled when a filter is selected that is not the empty filter No filter LICHEN x Personal Fiter E My own requirements created bef z Testmanager 01 10 2010 13 24 02 AX New Filter Testmanager 01 10 2010 13 25 21 AF Mo filter Testmanager 01 10 2010 13 08 49 Selectable requirements Testmanager 01 10 2010 13 08 48 Filter conditions read only Attribute Value B Crested lt or 10 2010 ES a ann 4 owner Testmanager c mm a Requirement Mame xj Req zj Ens Created lt 01 10 2010 AND Owner Testmanager AND Requirement Name Regq Hide Empty subtrees Impact ta selected Window Requirement 46 Apply Cancel Figure 79 Open item properties Depending on the selected filter the conditions are displayed Filter name is read only filter conditions can be changed See Figure 78 If the filter is in use and was changed the changes are then applied to the requirement structure Page 59 User Manual TEMPPO V6 2 Edition January
91. s please refer to 1 chapter Settings Page 87 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 17 5 2 Specific Settings Specific settings e g tree display etc can be configured in the settings dialog in TEMPPO Requirement Manager This dialog is opened via Windows gt Settings On the left side there is a tree where the user can select the setting group which should be configured Above the tree there is a fast search field for more efficient navigation Enter a sub string a all matching settings are shown dal Database nun Database CDSN Chooser W Switches on off a database chooser window on TEMPPO Startup ls Timeout in seconds displaying DSM chooser r Locking iv Switches an aff to lock the whole requirement structure before checking in and to prevent check in if an item ix lacked Locking Made Locking made in requirement structure automatic C manual Restore Defaultz cuca Figure 123 Settings Fast search On the right side all single settings can be edited see Figure 124 Page 88 User Manual TEMPPO V6 2 Edition January 2015 Description of Use Settings x Tree I LIser Interface EE Automatic sawe Mewsbnard voi Database El Requirement Management HBM Telelogic DOORS BM Rational Requisite Pro v Save changes automatically suppress confirmation dialog gt Automatic numbering Ca Displays a
92. sing the Lock button you will get a dialog If the reason was that another user has deleted the item in the meantime the item is removed from the tree and Figure 100 is shown Reload the whole requirement structure x AN Cant find item in database Maybe the item was deleted by another user Figure 100 Item not found information 2 16 6Delete an item If you try to delete an item which itself or any of its children is locked you will get a dialog see Figure 101 and you cannot perform this deletion Moreover the item and all children are refreshed so you can see which one is locked Lock information X The item or any ch ild element iz locked Figure 101 Child element locked 2 16 7Find invalid locks On starting and quitting TEMPPO Requirement Manager the whole database is checked for any locks which were set by you Normally there should be no one left But if there is one see Figure 102 this is an invalid lock which can have two reasons Your last TEMPPO session terminated abnormally crash etc If so you should confirm the dialog by pressing Yes to remove all invalid locks TEMPPU Requirement Manager X Warning Found locks by the current user in database 1 Maybe another instance of TEMPPO Requirement Manager is running by the current user or TEMPPO Requirement anager wasnt previous shut dawn cleanly Do you want to remove the lacks ensure that no other TEMPPO Requirement Manager is running
93. t i 3 Use Customer Informa 4 Operational Managem B Bill 5 Installation und config Ell 6 Market Progress Object Type Requirement AND Active true i 2 Non Functional Requireme Dn Active true Figure 45 Requirement Structure Applied View As long as no TC is linked to any requirement in that baseline the view can be changed After linking one TC to any requirement the view is checked in to the baseline and cannot be changed anymore 2 5 2 Import from XML The XML Import can be started by pressing the menu item Requirement Structure Import From XML This menu item is only enabled when no requirement structure is open The XML document to be imported can then be chosen in a file dialog The XML document is checked against the DTD Document Type Definition Your XML file has to have the first line IDOCTYPE TEMPPO EXCHANGE SYSTEM requstructure dtd whereas requstructure dtd is the DTD file Otherwise the import will fail In your TEMPPO directory you ll find the DTD requstructure dtd Stages of Import 1 Parsing and validation of XML file checking of semantics and creation of new objects Page 31 User Manual TEMPPO V6 2 Edition January 2015 Description of Use 2 Saving new objects to the database 3 Reloading of the whole requirement structure from database When the import of a manual requirement structure is finished you will be asked whether you want to check in the requirem
94. t case can have associated requirements With the button New a new window opens where you can select requirements see Figure 67 In the combo box you select the requirement structure and below its requirements are shown If a requirement is already assigned it s Page 48 User Manual TEMPPO V6 2 Edition January 2015 Description of Use written in black but if there is a new assignment the requirement is written in grey 111 LinkZ Link test cases to requirement Figure 67 Requirement selection After selecting the requirements the selected ones are shown as a list see Figure 68 Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure Link test cases to requirements System Test V1 M 4 b M 6S B uomer v Link test cases to requirement 2 11 Newsboard The newsboard informs the user about changes done on the current requirement structure It can be opened by calling the menu item Requirement Structure Newsboard In Settings it can be configured that is it shown automatically after opening a requirement structure Since time is going on and newsboard doesn t poll user has to press the Refresh button to get the latest news The display of newsboard can be configured be setting last login last hour last day last week or user defined If user defined is selected a date with calendar and text fields for time hh mm and the Apply button are editable If last lo
95. t is popped up on apply Figure 13 H GH 1 New Requirement ffo 2 New Requirement 1 i Se amp Figure 12 Mandatory history comment Figure 13 History comment 2 3 2 Importing from CSV With CSV files several requirements can be imported to a requirement structure or requirement Depending on the selected node requirement structure requirement the requirements are imported as a list of children First you have to save your Excel file as csv and select a requirement or requirement structure root node Page 14 User Manual TEMPPO V6 2 Edition January 2015 Description of Use TEMPPO Requirement Manager Testmanager Notepad Feszenan Scr Eat Evan son ly Open ture Notepad V3 D New h No fiter Import gt from RM Tool Export from CSV le pro Update b from XML je proi to Versions 2021 Scope of delivery l 2q22 Sequences scenarios Name Notepad Spit 2923 User goals 2924 Required functions of tl Prefix Func_ Newsboard Owner Testmanager Updator Testmanager 3 Ha Created 13 02 2012 17 05 48 Updated 26 06 2013 16 55 58 Close Type Manual Description This requirement structure covers all the functional requirements Figure 14 Menu Import gt from CSV When activating the menu Test Structure gt Import Structure gt From CSV Figure 15 is displayed In that dialog you can assign Excel columns to TEMPPO attributes Th
96. te Requirements User defined ID feses General attrtxtes Test Steps IE Submit Change Proposal Properties Table properties Name New tie opened no changes Lock Gener Schlosser Dietmar Updator Schlosser Unlock Created 18 06 2004 1210 28 Updated 1210200 Type Manus C Automated Test Case LJ External rtertaces of the product in AD i o amaa doi er Sane wee Figure 57 Delete in DOORS After deleting the requirement structure in TEMPPO is updated Requirement Structure Update see Figure 58 Clear Suspicion Prit Functions J Search Functions J Help System Page 42 User Manual Edition January 2015 Firms Testmanager F Requirement Structure Edit Windows Requirement Structure Huge Module 1 V8 J Huge Module 1 Ef How to Use m4 Multi user ability E48 Lock modes onli SITEMPPO provides fim Manual lock f Automatic lock fi If you are working with me fi On the other hand you sir fim This Feature can be config f D Table if Tablel Locking modes in 582 following chapters are ly Editing Elf Refreshing eA General principles and user promp pH Menu Reference Ff Manager Fi Rms Testmanager Requirement Structure Edit Windows General Requirement Number i 194 Name The Following chapters are describing th Owner Testmanager Updator Created 25 10 2006 9 56 42 Updated z Cre
97. uction422 79 241 Detailed description of product features 4 2 Administrator R20 1 1Purpose of the docum 80 2 2 Views in DOORS4 2 Administrator R21 1 2Validity of the docume 81 12 3 Import process 5 2 Administrator R22 e enini 82 24 Update pracess 5 2 Administrator R23 i5 veran ofthe docu 83 2 5 Display in SiTEMPPO Requirement Manager 3 2 Administrator R24 2Detailed description of tl 84 2 6 Display in SiTEMPPO Administrator 5 2 Administrator R25 2 1Detailed description ol 85 2 7 Creation of test suite Filter 7R 2 Administrator R26 2 2 iews in DOORS4 86 2 8 Analyze 7 2 Administrator R27 2 3lmport process5 of 87 29 Reporting 8 2 Administrator R28 TEA ees ae Usemame Administrator E xclusive edit mode Figure 17 DOORS Requirement structure to be imported There is an existing module in DOORS which is wanted to be used in TEMPPO The import from DOORS can be started by pressing the menu item Requirement Structure Import From RM Tool This menu item is only enabled when no requirement structure is open This will cause the wizard shown in Figure 18 to be displayed The wizard assists you to import requirement data from an external Requirement Management Tool Import requirement data from an RM tool This wizard assists you to import requirement data from a provided RM tool Choose a RM tool 3 Select a requirement document Finish Figure 18 Require
98. utomatic numbering of requirements vw Ono for recursive numbering e g 1 2 3 L Delimiter tar numbering amp e d a Defines where numbering starts Display of requirements C Requirement ID C Requirement ID Name Mame Restore Defaultz Cancel Figure 124 Settings Via button Restore Defaults all settings of the selected setting group are restored to the default values Following settings can be configured in TEMPPO Requirement Manager e User Interface o Tree o Newsboard e Database settings e Requirement Management o IBM Telelogic DOORS o IBM Rational RequisitePro For Sparx System Enterprise Architect there are no configuration parameters For user interface database and notification settings please refer to 1 chapter Settings 2 127 913 Requirement Management 2 17 5 3 1 IBM Telelogic DOORS The User Password Path to the local DOORS and DOORS parameters can be edited Page 89 User Manual TEMPPO V6 2 Edition January 2015 Description of Use settings eee x IBM Telelogic DOORS I LUIser Interface Tree Mewshoard xm Database Requirement Management gE Telelogic DOORS IBM Rational Requi Paszward Path to local DOORS CsProgram Files Telelogic DOORS_ 8 23bin doors exe S Parameters asta 36677 matnzgp1 ga Server start timeout h 0 Seconds site Pro DOORS Server User administrator Restore Defaults JK Cancel

TEMPPO Requirement Manager User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents