Home

TEMPPO Requirement Manager User Manual

1. Requirement _ nell fest Execution Sahagina Planning and rePorting Organizer TEMPPO Requirement Manager User Manual Edition March 2013 Copyright Atos IT Solutions and Services GmbH 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 0 Edition March 2013 Contents Contents MER Tu ee et Ta WEE 5 2 DESCHDUOMO USE e T 6 2 1 Create a new Requirement Structure ccccceecccssececeeeseeeeeseeeeeeeeeeseeeeseeeesseeesaaees 6 2 2 Open an existing Requirement Gtruchure 7 2 3 Create the Requirements ccccccccseccceeccseccceeecececeuceseeecsueeseeessaeessueeseeessuseneeeseas 8 2 3 1 Create MaAMUANY m 8 2 3 2 AMO O gille bt dau 11 2 3 2 1 Example ol a Oto EE 13 2 3 2 2 Possible errors during the mmport 13 2A EE TROOPS Misc c 14 2 5 Import a whole Requirement Structure cccccccceececeeeceeeeceeeeceeeseeeeceeeeeeeseneese
2. 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 3 This function checks in the actual latest version see also 2 11 and updates the new latest version of the requirement structure irrespective of the activated version Page 27 User Manual TEMPPO V6 0 Edition March 2013 Description of Use By pressing the menu item Requirement Structure gt 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 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. ff 39 Post Condition UC New requirement Da be deleted Lock Angie Discard Figure 33 Imported Requirement Structure 2 5 2 Import from XML The XML Import can be started by pressing the menu item Requirement Structure gt Import gt 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 gt 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 2 Saving new objects to the database 3 Reloading of the whole requirement structure from database Page 24 User Manual TEMPPO V6 0 Edition March 2013 Description of Use When the import of a manual requirement structure is finished you will be asked whether you want to check in the requirement 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 SS hh x v Requirement structure successfully imported Figure 34 Import successful 2 5 2 1 Possible
4. Server start timeout h 0 Seconds Path ta DL EES Pu Restore Defaultz Figure 104 Settings Telelogic DOORS User password and DOORS path 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 74 User Manual TEMPPO V6 0 Edition March 2013 Description of Use rr x IBM Rational RequisitePro User Interface Tree Supported IBM Rational RequisitePro versions ie Please select the version of RequisitPro which is installed on your PC Database El Requirement Management oO C roi HIEM Telelogic DOOR Restore Defaults Ok Cancel Figure 105 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
5. User Manual Edition March 2013 TEMPPO V6 0 Description of Use 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 isst day The display of newsboard can be configured be setting last login logout is chosen 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 login is selected the time stamp of user s last 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 26 03 2014 08 36 42 26 03 2011 Changed since user defined req101 reqi02 Changed req121 Deleted req117 Deleted req61 Deleted req100 Requirement structure Import v2 M 4 M ww B noster DE 2 reg101 importi E 8j 3 reg102 import2 3 1 req121 New Requirement Requirement ID req121 Figure 56 Newsboard h 00 24 10 New Requirement New Requirement Before import import Date 14 02 2012 13 58 42 14 02 2012 14 09 18 14 02 2012 12 38 47 14 02 2012 13 58 42 14 02 2012 13 39 11
6. 2 16 2Edit Fi TEMPPO Requirement Manager Testmanager Import l nm sl Requirement Structure Edt Evaluation Windows e Requirement Structure Import v2 Gene Dellen do Locked by Testmanager Requirement ID reat nn Mame importo A 3 import2 Owner Testmanager Llpdator Testmanager Created 14 02 2012 09 36 35 Updated 14 02 2012 12 38 47 Type Manual Short Description shorto Description contento lock Apply Discard Figure 77 Lock state Page 59 User Manual TEMPPO V6 0 Edition March 2013 Description of Use After locking the requirement you can edit the selected requirement 2 16 2 1 Show 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 E TEMPPO Requirement Manager Tester Import E B x Requirement Structure Edt Evaluation Windows Requirement Structure Import V2 Mo 4 bk M EI onte sl fia 2 imparti General Attributes Af 3 import Requirement ID reat DU Mame morto Cwner Testmanager Llpdator Testmanager Created 02 2012 08 35 35 Updated 02 2012 12 38 47 Type Manual Short Description shortd Description content Lock Apply Discard amp Bu Se Se amp Re Figure 78 Lock button 2 16 2 2 Change an item Before you can change an item you have t
7. C3 My Received Files C Downloads 5 Eigene Videos Eigene Datenquellen B NeroVision O errorReport20121302130732 9 Obsorge C geql 0 0 C Ranorex OO HP sap O I Mo RA AT Schlosser Home O MEIS Working P SharePoint Drafts C3 Media Go B SharePoint Entw rfe C3 My Meetings C3 Sony Ericsson Arbeitsplatz gt e File name uninstall logder Download Ie MP Files oftype lal Files v Cancel Figure 96 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 Page 68 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Fi TEMPPO Requirement Manager Testmanager Import E nm sl Requirement Structure Edt Evaluation Windows e Requirement Structure Import v2 Sj xj H 4 b M E vo nite sl 2 Import BRR 1 importo Ge STAT General Attributes 3 import i Gh 3 1 New Requirement Requirement ID reqt n fia 3 2 Mew Requirement 1 une moth 4 Owner Testmanager LIpdator Testmanager Created 14 02 2012 12 21 45 Updated 14 02 2012 13 58 41 Type Manual Short Description short Description a changed Lock Apply Discard Figure 97 Apply Discard 2 17 4Fi
8. Testmanager S Requirements for user docume Testmanager 14 02 2012 09 20 13 14 02 2012 09 20 49 14 02 2012 09 19 32 E SW requirements Testmanager User requirements i Testmanager e 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 10 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Additionally any requirement attribute can be assigned to the requirement E TEMPPO Requirement Manager Testmanager Notepad m x Requirement Structure Edt Evaluation windows Requirement Structure Notepad X4 l Ioj xi Ho d e M EI Mo nite sl i ctio General description of the product General Attributes ER G 3 Detailed description of the product features if 3 1 Scope of delivery D 3 2 Sequences scenarios of interactior Planned coverage 1 899 fal test cases G 3 3 User goals Elf 3 4 Required functions of the product Enter number of test cases to be created finked in order to get a minimal coverage in test management Fb ffi 3 4 1 File Administration ool 3411 Mew B 341 2 Open Attribute
9. read only Attribute Value gt i i Created ES for 10 2010 m e ano A E E owner sl D Testmanager D a ano sl K E Requirement Mame sl Reg sl 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 69 Show Filter When clicking Apply Figure 69 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 69 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 2 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 Them you can enter e A string with a wild card or e Press the button for selecting several values After pressing the button Figure 70 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
10. 14 02 2012 10 40 29 14 02 2012 09 35 37 Name Mew Requirement Owner Testmanager Created 14 02 2012 13 52 29 Type Manual min 0 59 0 Updator Testmanager E Testmanager E Testmanager Testmanager Testmanager E Testmanager E Tesimanager E Testmanager E Testmanager D Testmanager Testmanager Testmanager E Testmanager Updator Testmanager Updated 14 02 2012 13 58 42 Page 42 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 2 12 Version Configuration management is a task that covers 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 Versioning is meaningful when you have to change extend your requirement structure due to version changes of your application A requirement stru
11. 2 14 3 Change FINCK EE 51 2144 Delete IRE Tm 52 2 145 Select PIE ooo te Pee on teen Pea e EPI ne ee ee cree 52 2 14 0 ONOW FINSE EE 52 214 7 Denne TVS HEEN o3 21449 EXPONO P TL 99 HE MDOE UE 56 2 rt civi eT 56 User Manual TEMPPO V6 0 Edition March 2013 Contents 2E ANAS HR PER a a 56 2 15 2 Progress E E 58 2 15 UEL 59 Aene MEME re Mine UT 59 210 2 zo et 59 24621 lt OMOW A lOCK SIAC ic eti mieten ee ohio cuite testet f tele sebo tese 60 2 10 22 Change an En EE 60 21623 Delete anien EE 61 24624 FING IDVAIG JEE 61 2 10 97 Reres WEE 61 2 19 9 T le ET EC ia Dota eta desaci a Ra eta addi AT 61 2 16 3 1 1 Reloading the whole requirement structure nannannnnnennnnnenneneennnnnn 61 216 3 1 2 Refresh FecursiVely nantres eege ee da Dua Dua Eie bte RR Dad UNE 62 2 16 3 1 3 Refresh on certain user achons 62 2 1 7 General principles ous UD ses er eee nee eee eee 63 ZA FA MURRSEIGCUO qe tm 63 2 17 2 Hyperlinks and Uploads ssrcrissnesienstisnneree Eaei 65 CN e Create el in 65 CEN MM ECICMYOCTINIKS opacities t Tm 68 24 2 9 REMOVE nyDellI S discesa edt esa eiat esas edema aolet esas tema diat esas adt eua dat equas 68 237 21 DOWNI EE 68 2 17 3 Applying Discardmg 68 AA JFING and e e 69 2 e s MI oo e rcp 71 Mr E REICO EDS 71 ZEE MEM emm 72 2d Ok CIS Ee NR ETE TET ERE 72 2 1 7 52 OPECIN SO EE 72 2 17 5 3 Requirement Management 73 See IBM TelelogiG DOORS saisi ees 73 2 17 5 3 2 IBM Ra
12. Administrator R20 1 1Purpose of the docum 80 2 2 Views in DOORS4 2 Administrator R21 beri of deisde 81 23 Import process 5 2 Administrator R22 ER 82 24 Update process 5 2 Administrator R23 1 4Relationship with othe L m s uM 3 Bvarnsui ofthe docu 83 EL 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 EK Creation of test suite Filter 7R 2 Administrator R26 2 2Views in DOORS4 86 2 8 Analyze 7 2 Administrator R27 2 3lmport process of 87 2 9 Reporting 8 2 Administrator R28 A mm WP NUI c g Usemame Administrator Exclusive edit mode Figure 15 DOORS Requirement structure to be imported There is an existing module in DOORS which is wanted to use in TEMPPO The import from DOORS can be started by pressing the menu item Requirement Structure gt Import gt From RM Tool This menu item is only enabled when no requirement structure is open This will cause the wizard shown in Figure 16 to be displayed The wizard assists you to import requirement data from an external Requirement Management Tool Al Import Requirements from an RM Steps Import requirement data from an RM tool 1 Introduction This wizard assists you to import requirement data from a provided RM tool z Choose a RM tool 3 Select a requirement document 4 Choose a baseline and a v
13. E Jul xi Requirement Structure Edt Evaluation windows e Requirement Structure Import V1 M 4 bh M e S wo nter sl JJ Import General attributes i Ga import Requirement ID eo OU Mame wem Owner Testmanager Updator Testmanager Created 14 02 2012 09 36 35 Updated 14 02 2012 09 36 35 Type Manual short Description short Description cantent Lock Apply Discard Figure 12 Requirement Structure before and after importing 2 3 2 1 Example of a CSV file Req100 importO Content shortO Req101 importi contenti shorti Req102 import2 content2 short2 2 3 2 2 Possible errors during the import eros Remhon The syntax of the CSV file isn t correct Nothing is written to the database a message see Figure 6 is shown Correct the CSV file to be imported Page 13 User Manual TEMPPO V6 0 Edition March 2013 Description of Use May there is a comma instance of a semicolon Duplicate IDs Change IDs TEMPPO Note X an 1 Only O of 3 requirements are imported due ta duplicates Figure 13 Error with CSV file 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 2 2 you can edit the requirement ID name short and long description E TEMPPO Requirement Manager Testmanager Notepad l Z ml x Requirement Structur
14. a requirement document 4 Choose a baseline and a view cas Private ID Cheose attribute as requirement ID Test ld Figure 22 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 RegID requirement ID Updator Updator Level 2 Level RegID define no requirement RegID Updator ID Updator ID object identifier is requirement ID Level 2 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 Page 18 User Manual TEMPPO V6 0 Edition March 2013 Description of Use the import is canceled and a log file is written where these cases are described see 2 5 1 2 When the import was successful then the imported requirement structure and its requirements are shown in the tree EK TEMPPO Requirement Manager Testmanager Import from DOORS with views 5 l m rj x Requirement Structure Edit Windows Requirement Structu
15. ability 266 1 The Test Process Phases D 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 9 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 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
16. 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 1 Special cases Name of requirement structure exists Unique name is generated like _1 2 Message is shown see Figure 35 Requirement structure or requirement Object is created No message is doesn t exist shown TEMPPO Note X a Arequirement structure Notepad exists The imported one will be renamed we For a later test structure import this can cause matching problems Figure 35 name of requirement structure already exists 2 5 2 1 2 Example of an XML document lt xml version 1 0 encoding UTF 8 gt lt DOCTYPE TEMPPO EXCHANGE SYSTEM requstructure dtd gt TEMPPO VERSION V6 0 Build 05 7 gt STEMPPO EXCHANGE RS name Benutzerhandbuch version V3 rmstype Manual prefix prefix createdrms 21 12 2009 15 00 39 lt DESCRIPTION gt lt DESCRIPTION gt lt REQUIREMENT name import XML renamed requirementnumber import3 Page 25 User Manual TEMPPO V6 0 Edition March 2013 Description of Use type Manual shortdescription Inhalt Kurzbeschreibun createdrms updatedrms selectable 0 coveredbytcs 3 SDESCRIELION 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 g
17. 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 39 there is displayed the new requirement Some requirements are missing compared to V1 Page 30 User Manual TEMPPO V6 0 Edition March 2013 Description of Use E TEMPPO Requirement Manager Testmanager Learning Project Use Cases 1 Requirement Structure Edt Evaluation Windows Requirement Structure Learning Project Use Cases 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 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 CDs Owner Testmanager Ll
18. one will be stored e 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 105 Afterwards all TEMPPO applications have to be closed and a batch file changeReqProVersion bat has to be executed Page 75 User Manual Edition March 2013 3 Literature 1 User Manual TEMPPO user manual March 2012 TEMPPO V6 0 Literature Page 76 User Manual TEMPPO V6 0 Edition March 2013 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 77 User Manual TEMPPO V6 0 Edition March 2013 Appendix 5 Appendix 5 1 DTD Schema for XML Import Requirement Structure See XML directory of TEMPPO s installation directory Page 78 User Manual Edition March 2013 6 Index A Apply 68 C CSV Import 11 Import example 13 Update 31 D Discard 68 DOORS Attributes 17 Baseline 16 Import 15 Module 16 Requirement ID mapping 17 Update 27 View 16 E Evaluation Analysis 56 Progress chart 58 F Filter 48 Change 51 Create 49 Define criterion 53 Delete 52 Export 55 Import 56 Select 52 Show 52 Find and Replace 69 Find 71 Replace 71 H Hyperlink Create 65 Download 68 Edit 68 Remove 68 Hyperlinks 65 M
19. the view to import Intraduction Choose a RM tool l Select a requirement Baseline Latest Version not baselined document Choose a baseline and a view ement ID use object ID O select another attribute Figure 20 Baseline and view selection Finish With the checkbox select another attribute 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 21 In the next step you can select an attribute which is use as requirement ID in TEMPPO see Figure 22 L4 Import Requirements from an RM toc Choose the baseline and the view to import Select a requirement Latest Version not baselined document Choose s baseline and a view Figure 21 Baseline and view selection Next In the next step you can select an attribute which is used as requirement ID in TEMPPO see Figure 22 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 Page 17 User Manual TEMPPO V6 0 Edition March 2013 Description of Use that the object number and the selected attribute have exchanged their functions Choose an attribute to be used requirement ID Introduction Note Values of the chosen attribute must be unique Choose a RM tool Select
20. with name owner prefix creation date and version is displayed Page 7 User Manual TEMPPO V6 0 Edition March 2013 Description of Use x wm oe created vem B Anforderung 28 09 200 viD latest ISS Anforderung 10 31 08 200 vi latest b Anforderung 20 01 09 200 v1 latest b Anforderung 9 31 08 200 v1 First I Cu import 05 10 200 v2 latest csv import II 05 10 200 v1 latest IM Demo R5 10 10 200 v2 latest doorsmodule 12 10 200 v1 latest Johannas HS 09 10 200 v3 latest Mx Is Meine 25 09 20D E Mew Requirement Structure Q2 10 200 ege ISS New Requirement Structure 26 09 200 sae Mew Requirement Structurel 1 02 10 200 v2 latest bs Mew Requirement Structure 1111111111111 02 10 200 vi latest b Petra z 07 09 200 v4 latest Mb Petra Test 05 09 200 v25 latest b ns 03 10 200 v1 latest Jii irnn anir we 12 200 WA Takat a 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 loaded 2 3 Create the Requirements After creating or opening the req
21. 3 1 1 Example for Updating Formal module Huge Project Huge Module current 0 0 DOORS x Oj x File Edit View Insert Link Analysis Table Tools User Help Br sel x vl aa B 7 u Pads Seo Standard view sl lat ewe Se 2 SS SS lr B Tea Gm Il ne tl 1 Ontroduction E 20Description of Use E The Test Process Phases 2 1 The Test Process Phase 274 2 1 1 Test Planning ii SEN lie 275 The definition phase covers the tasks of B 21 30Test i zu Writing the Test Plan F 2 1 4 Test Case Executi 277 Writing the Project Plan GL 2 1 5 0E valuation 278 Defining Test Case Attributes E 2 2 IMulti user ability 279 2 1 1 1 Writing the Test Plan ia Tien eger 280 The test plan is an stdSEM document and writing is outside the scope of SITEMPPO However it s is 22 3 fefieshing the base document for all test topics during the development process and covers subjects like test requirements test management test documentation test goals end of test criteria etc Its T 24 iMm Heisrencs contents are obligatory for all members of the test team For detailed information please refer to H 3IManager http se Hlt528565386m HItS28565386 siemens at stdsem e p desi ge2 htm El 4 Administration 281 2 1 1 2 Writing the Project Plan 282 Ae an 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
22. MPPU Requirement Manager X Warning Found locks by the current user in database i 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 by the current user Figure 81 Locks found in the database on starting quitting TEMPPO Requirement Manager 2 16 3Refresh 2 16 3 1 Refresh manually 2 16 3 1 1 Reloading the whole requirement structure You can reload the whole requirement structure by pressing the reload button ge on top of the tree see Figure 82 This has the same effect as manually reopening the requirement structure Page 61 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Fi TEMPPO Requirement Manager Testmanager Import Requirement Structure Edt Evaluation Windows Requirement Structure Import v2 q RE Monter e Reload the whole tree General Viem n 3 import2 Name Import Prefix Owner Testmanager Updator Testmanager Created 14 02 2012 09 34 44 Updated 14 02 2012 12 23 22 Type Manual Description Lack Apply Discard Figure 82 Button Reload for reloading the whole tree 2 16 3 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 83 Attention The selec
23. Name ITIT I fifa Menu Reference ES Manager Owner Testmanager Updator Testmanager fl Database Connection lf User management E ga Administration Creator RMS Hf Database Connection H a Test Automation Settings Hf Roles Type Manual ai Ca User management ai G Customizing Metadata ai G Projects ER Locke Hf Database migration ER License Server Connection Ga Notification Created 25 10 2006 09 56 13 Updated 25 10 2006 13 49 38 Created RMS 25 10 2006 00 00 00 Description Lock Enim Discard Figure 38 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 and updates the new latest version of the requirement structure irrespective of the activated version By pressing the menu item Requirement Structure gt 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
24. Values Lug 34 1 3 Save Add attribute 8j 3 4 1 4 Exit Eh fij 3 4 2 Edit functions D n 3421 Undo EE 34 23 Copy if 34 2 4 Paste tia 34 2 5 Delete if 3 4 2 5 Select all ia 34 2 7 Time Date ooh 3 4 2 8 Word Wrap fi 3 4 2 9 Set Font Eb fii 3 4 3 Print functions 3431 Page Set m age setup sl Lock Apply Discard 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 Figure 10 E Attribute value selection i x Attribute auai D S Audi ADR F FUNC REG ODB PN kj amp gt Audi ADR F FUNC REG O07 amp gt Audi ADR F FUNC REQ O08 amp gt Audi ADR F FUNC REO O09 H gt Audi ADR F FLINC REG D10 amp gt CAR F GEME REG D11 gt CAR F GENE REQ 012 amp gt CAR F GENE REG D13 p amp gt CAR F GEME REG D14 Sx CAR F GENE REQ 015 gt CAR F GEME REG D18 gt CAR F GEME REG D17 gt CAR F GENE REG D18 amp gt CAR F GEME REG D19 amp p CD F FUNC REQ 001 ewes 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 2 Importing from CSV With CSV files several requirements can be imported to a r
25. X Delete M Tree style C Versions only Activate selected version C Labels only Versions and Labels C ClearCase style Merge to latest version r Order ascending C descending Delete latest version Change tree style Figure 58 CM Version tree before first check in Additionally you can add a so called view to the checked in version baseline A view is either a filter which is created when working with requirement structures or a self created logical expression in tab view SI FK TEMPPO Requirement Manager Testmanager Import Requirement Structure Edt Evaluation Windows e Requirement Structure Import S51 l m x JJ Import f 1 import Ses inport General Attributes Planned coverage 1 999 bh lest Cases Enter number of test cases to be created linized in Attribute Values E Ren State Implemented x Figure 59 Filter All implemented requirements If you want to test only a subset of all requirements e g all implemented requirements see Figure 59 change to tab view select a filter and press the button Apply to set it to the current view When pressing the button Refresh you see how many requirements are in and not in the view Page 44 User Manual TEMPPO V6 0 Edition March 2013 Description of Use LIT HEN x Label view Edit ER IR All implemented requirements we Apply Check In Attribute Va
26. Z amp Activate selected version You cannot change a requirement structure in a version which is not latest Page 46 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 2 12 1 Merge 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 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 exactl
27. an see their requirement structures in a filtered way by creating and selecting filters i e for the purpose 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 Page 48 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 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 LICHEN x Personal Fiter 1 E Mo filter Testmanager 01 10 2010 13 08 49 Ka EZ Selectable requireme Testmanager 01 10 2010 13 08 49 ej 2j Filter conditions read only Attribute Value Wl SSS ee Ai ge p EL ELL lm selectable true Iw Hide Empty subtrees Impact to selected Window Requirement 46 Apply Cancel Figure 65 Pred
28. and quitting SITEMP 4 Tasklist New Test Structure V10 PROPAGATE Johannas RS V2 2V3 E lt gt PROPAGATE Huge Module 1 gt 2 B ke 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 46 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 test 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 36 User Manual TEMPPO V6 0 Edition March 2013 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 g id Open normal Jl Open fle opened changes Z4 Save E Ext no Ei Exi Yes tie open
29. applied to the requirement structure Page 51 User Manual TEMPPO V6 0 Edition March 2013 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 M Do you really wart to delete the selected filter Cancel TEMPPO Note X Ld d LJ 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 52 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Ei Fiter S x Personal Filter 4 vu 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
30. be installed Import from DOORS with views current 0 1 in test1 Formal module DOORS ioj x File Edit View Insert Link Analysis Table Tools User Help Se shee xX l e nel BZ ao eal Er IE E o m rea Aleves ru Fe ivr wl e Gm ID ooo Mengt Ule WE es E Kand IN Ill Import from DOORS with views a gt gt Table ER 1 Fron Matar 35 Document Management 2 Administrator RO Software Requirements S 04 36 History of changes 2 Administrator ROS Import from Telelogic DOI 68 Persons authorized to make changes 2 Administrator ROS 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 DorisSV ISREG 71 Contents 2 Administrator R12 SITEMPPO Support SIS 72 1 Introduction 422 2 Administrator R13 SE 73 11 Purpose of the document4 2 Administrator R14 Sidi ing 74 11 2 Validity of the document 4 2 Administrator R15 Persons audhomedin ma 75 13 Definitions of terms and abbreviations 4 2 Administrator R16 p 76 14 Relationship with other documents 4 2 Administrator R17 Microsoft Office Word 20 77 Des Overview of the document 4 2 Administrator R18 Contents 78 12 Detailed description of the required product features 4 2 Administrator R19 Tintroduction422 79 21 Detailed description of product features 4 2
31. 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 37 DOORS Change requirements After changing the module in DOORS start the update process In the next figure see Figure 38 you can compare the latest version of requirement structure with the version before Ee Doss EE lolx Requirement Structure Edit Windows Requirement Structure Huge Module 1 V1 ER Introduction i ER Basics General a 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 G Manager Creator RMS Kf Administration Created 25 10 2006 09 56 13 Updated Created RMS 25 10 2006 00 00 00 Type Manual Description Lock Enim Discard Page 29 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Ei Rms Doten EE BER Requirement Structure Edit Windows Requirement Structure Huge Module 1 V7 E ES Huge Module 1 f How to Use ER The Test Process Phases General pHe8g Multi user ability ER General principles and user promp
32. bute is shown for the ID see also in Figure 23 This specified id is also displayed in the TEMPPO test environment All imported attributes are shown in tab Attributes see Figure 24 Page 19 User Manual TEMPPO V6 0 Edition March 2013 Description of Use E TEMPPO Requirement Manager Testmanager Import from DOORS with views 7 n sl Requirement Structure Edit Windows Requirement Structure Import from DOORS with views 7 V1 i l H d e H 4 No Filter we J Import From DOORS with views 7 Lal 1 Table Elli 2 Front Matter General Attributes TEE Software Requirements Sp D A Attribute values Import ER Telelogic Doo E DOORS ID IMP 59 Distribution list Name alphab Deparkmer CZ Level 2 Hutzler Doris 5v I I5 REG F Updator Administrator SITEMPPO Support SIS PSE Document Management History of changes Persons authorized to me 2 12 Document was created u 13 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 dac 2 Detailed description of 2 1 Detailed description c 2 views in DOORS 4 a Lack Apply Discard k Figure 24 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
33. changes i mi Edt Functions ai 2 Print Functions WHL Search Functions I Hep System e E External interfaces af the product H E Other product features required 4 Tasklist Notepad System amp Acceptance Test V5 Ga Task List new Ze 1234 R 1704 7 1234 R 2004 General Test Case iD 1235 Requirement R 8H5 Figure 47 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 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 or a requirement is selected the menu item Requirement Structure Export to XML is enabled After entering a nam
34. cture is automatically versioned before an update from a RM Tool Versioning manually 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 There is a requirement structure CSV import which has already requirements see Figure 57 Fi TEMPPO Requirement Manager Testmanager Import q S ioj x Requirement Structure Edt Evaluation Windonws Requirement Structure Import V1 E Ei X M vr M wo nite sl i 1 import fis 2 importi General view G 3 Import Mame mort Prefix Owner Testmanager Updator Testmanager Created 14 02 2012 09 34 44 Updated 14 02 2012 12 21 43 Type Manual Description Lock Apply Discard Figure 57 Before check in Before importing a CSV file the requirement structure should be checked in Page 43 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 1 Consider the requirement structure displayed in Figure 58 Initially there exists just one version of the requirement structure version 1 on the main line In TEMPPO every last version gets the label latest signaling that the requirement structure in this version is checked out for editing xl Label view ES Eat Edit properties of selected version C Check In FI Activate et Merge Check in active version
35. e the XML file is stored to the file system conforming to requstructure dtd Page 37 User Manual TEMPPO V6 0 Edition March 2013 Description of Use The requstructure dtd can be found in your TEMPPO XML directory The following window is shown after exporting successful x i 2 J Requirement structure successfully exported Figure 48 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 structure Open the TEMPPO Administrator application and after connecting chose the tab Metadata and then tab Requirement Structures Fi TEMPPO Administrator Testmanager 1 inl x Database e Roles users Metadata L7 Projects B Locks License Test Levels Test Categories si Attributes E3 Uploads Si Requirement Structures ET User Fielda fa X Si geegent ES Customer requirements Testmanager 13 02 2012 16 50 26 Manual ES Import Testmanager 14 02 2012 09 34 44 Manual egen T T TU 13 02 2012 17 05 48 Manual Re Notepad 1 Testmanager 14 02 2012 10 32 11 Manual I Requirements for user document Testmanager 14 02 2012 09 20 13 Manual E Gm requirements Testmanager 14 02 2012 09 20 49 Manual S User r
36. e 45 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Biversions Edit csv import zm Release 1 Check In LE V2 editable version uus ig berge A Delete Label View Tree style C Versions only C Labels only Versions and Labels C ClearCase style Order Ce ascending C descending Figure 62 CM Version tree after checking in and labeling Changes in the latest version of the requirement structure will now not affect Release 1 E g when inserting a requirement Second the new requirement will only be available in the latest version of the requirement structure see Figure 63 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 E IO x Requirement Structure Edt Evaluation Windows Requirement Structure Import V2 l mi x NM d bk oH 4 EI vo nte sl CERN General Attributes D n 3 importz Requirement ID reat DU Name importo Owner Testmanager Updetor Testmanager Created 14 02 2012 03 35 35 Updated 14 02 2012 12 38 47 Type Manual Short Description Short Description contento Lock Apply Discard Figure 63 After check in 3 You can restore the version of a requirement structure by activating it in the versions dialog with button
37. e Edt Evaluation Windows Requirement Structure Motepad V1 f m gl sl M 4 b M e BE wc fter sl ALI Notepad gt fi 1 troduction 2 General description of the product General Attributes E i 3 Detailed description of the product D n 3 1 Scope of delivery Requirement ID Fune reg ss sss s s G 3 2 Sequences Scenarios of in l G 3 3 User goals EE 3 4 Required functions of the pre Eb i 3 4 1 File Administration 85 SERGE fifa 3 4 1 2 Open Created 14 02 2012 08 39 55 Updated 14 02 2012 09 06 07 88 3 4 13 Save D Rf 341 4 Exit EH Gi 3 4 2 Edit functions Short Description EF Si 3 4 3 Print functions EH fia 3 4 4 Search functions Mame Me Owner Testmanager Updator Testmanager Type Manual Description Notepad shall open a new document An existing document shall he stored ar be lost Cancel shall also be possible Lock Apply Discard Figure 14 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 Page 14 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 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 Telelogic DOORS and thus the client for DOORS must
38. e Properties When activating the menu 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 6 User Manual TEMPPO V6 0 Edition March 2013 Description of Use E 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 Apply Discard ea 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 Please remark that you can only link test cases to requirements of a checked in requirement structure baseline TEMPPO i X 4 Before you can use this requirement structure in TEMPPO you have to assign it to a project G Do you want ta 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 gt Open the window Open Requirement Structure
39. eated before the selected one and a new name has to be entered The default name is New Requirement 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 Page 9 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Fi Properties of Req Type i X General Details Req_Type Created 012 09 13 34 For Use of Test case Owner Testmanager Test Package Type Attribute Tazi Suite Test Resutt Ive Requirement Description This attribute reflects the type of requirement If itis a real requirement ar anly a header es 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 x A d j You have created new meta data Do you wart to assign that meta data to a requirement structure now 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 requirement 5S assign Meta Data to Requirement Structure X Please select the requirement structure you would like ta assign the new meta data 13 02 2012 15 50 26 13 02 2012 17 05 48 Testmanager
40. efined filter 2 14 2Create Filter You can create a new filter using menu Edit Filter or using the Filter Combo box Edit entries in the requirement structure Page 49 User Manual TEMPPO V6 0 Edition March 2013 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 lee El P e Iw Hide Empty Subtregs Impact to Selected Window Requirement 4B Apply Cancel Figure 66 Create new filter If you click the Create new filter button Figure 66 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 E 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 67 Filter Properties Page 50 User Manual TEMPPO V6 0 Edition March 2013 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 d Fite
41. eleted ya w10 Vi Vid W15 Requirement Structure Wall S new B changed B deleted Save az Close Figure 76 Requirement creation progress Page 58 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 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 3 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 The following chapters are describing the locking in manual mode
42. els irt Apply Discard Figure 86 Multi selected items By clicking context menu all possible actions are provided to the user Hew V Find and Replace F3 Show Details Select All Cir As ts Tree b d Cut Ctriex Copy Ctrl C Faste Cru ipi Paste before 1 Order 7A Delete Delete Refresh rezursively Figure 87 Context menu For selected items attributes can be assigned or deleted Bi TEMPPO Requirement Manager Testmanager import Bx Requirement Structure Edt Evaluation Windows Requirement Structure Import v2 M 4 b M e EI 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 Page 64 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Figure 88 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 E TEMPPO Requirement Manager Testmanager Import E 2 ml x Requirement Structure Edt Evaluation Windows e Requirement Structure Import v2 M d bk M e EE c nte sl Attributes Planned coverage 1 999 1 test cases Enter number of test cases to be created finked in order to get a minimal coverage in test iw Req State Implemented CJ Req State Reviewed Assign to all
43. equirement structure or requirement Depending on the selected node requirement structure requirement the requirements are imported as a list of children The CSV file has to have 4 columns Page 11 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 1 Requirement ID 2 Name 3 Description 4 Short description Attention The fields have to be separated with a semicolon see 2 3 2 1 The import of a CSV file can be started by pressing the menu item Requirement Structure Import From CSV This menu item is only enabled when a requirement structure is opened and the requirement structure or a requirement is selected The file to be imported can then be chosen in a file dialog After the file selection the progress bar for importing is shown xj V Importing document structure ZU mem Figure 11 Importing CSV Progress bar The new requirements are created as a list Result of import Page 12 User Manual TEMPPO V6 0 Edition March 2013 Description of Use FK TEMPPO Requirement Manager Testmanager Import Ei oj xj Requirement Structure Edit Evaluation Windows Requirement Structure Import V1 M 4 MW II wo ter sl is G 1 Before import General Wiew Mame Import Prefix Owner Testmanager Updator Created 14 02 2012 08 34 44 Updated Type Manual Description Lock Apply Discard E TEMPPO Requirement Manager Testmanager Import
44. equirements Testmanager 14 02 2012 09 19 32 Manual Figure 49 Assign attributes The assignment is made for each requirement structure Page 38 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Zi Meta Data Editor n x Attributes Requirement E Find Available values New Entry Regattr test ya ae a 2 Figure 50 Meta data editor On the left side all available attributes are listed By clicking the buttons 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 to 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 E TEMPPO Administrator Testmanager B Database e Roles E Users Metadata 7 Projects B Locks License 2 8 De Xx Figure 51 Assign Metadata Page 39 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Then click the button Assign Metadata see Figure 51 and then Figure 52 is opened In the tab Requirement Structure you can select the requirement structures for the selected project E Meta Data Editor yy xj Test Levels BR Test Cateacries s Attributes E3 Uploads tii Requi
45. equirements together with attributes Version control including baseline and view concept Importing and updating requirement structures from DOORS or RequisitePro 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 5 User Manual TEMPPO V6 0 Edition March 2013 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 or a XML file or opening an existing one Fi Requirement Structure Properties 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 Cancel Figure 1 Requirement Structur
46. eractive quide to sit FEATE6 Highly scaleable Non Funcl 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 FEAT 1 Secure payment method E Secure payment method AN requirements Figure 28 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 29 to be displayed The wizard assists you to import requirement data from an external Requirement Management Tool Page 21 User Manual TEMPPO V6 0 Edition March 2013 Description of Use l Ei Steps Import requirement data from a RM tool 1 Introduction This wizard assists you to import requirement data From a provided RM tool 2 Choose a RM tool 3 Select a requirement document ec Prey Next Finish Cancel Figure 29 Requirement import wizard Introduction When pressing Next Figure 30 is shown in which you choose IBM RequisitePro is possible Fi Import Requirements from an RM tool E x steps Choose a RM tool _ Introduction 2 Choose a RM tool 3 Select a requirement C Kj 16M Telelogic DOORS docu
47. ess 14 2 5 1 mporn rom RM TOOL ec Ec 15 2 5 1 1 DOES Serene Metre Rene nee are Ren ee Mains QAI MAN usen as 15 2 5 1 2 Possible errors during the mmport 20 2 5 1 9 miseriis T TM 21 2 9 2 HMO OVE MOMMA ah sitis rus rude opes bau CRUR Ve RC BUS usu G Qua biu Ut reu e Ora tiene BUE tcu Gua tas BUE Oma E DA 24 2 5 2 1 Possible errors during the mmport 25 2 5 2 Special 63565 EEN 25 29 22 Example ofan AVE COCUMEIT esset eege Een 25 2 9 9 DOG uis can LUE ILI NIMM D IM M cU DEUM M I 27 2 5 3 1 DOORS IIR III M I See ahaa eats Sees oo a 27 Zoro Al Example Tor Tee Ed re EE 28 2 5 3 2 RegUISHEPTO syrror 30 2 5 3 3 EEN EN 2 5 3 4 PA Mc rmm 32 2 5 3 5 EES 32 2 5 3 6 Apply requirement updates cc ccccccceccceececeeeeeeeseueeseeeeeeeeseueeseeeseueesaees 32 2 5 3 7 Example Apply requirement updaies 34 26 WAS EEN 36 2 MEE bios quio Pd Ntc cp M eee 3 2 8 Assign Attributes to Requirement Structures cccccecccseeeceeeeceeeseeeeceeeeseeeeaeeesaees 38 2 9 Assign Requirement Structures to Droe 39 2 00 Bee e en Tu pa veruni ves ak vertu ce ta tert niccd tat test va taki ted Ut iai 40 2 11 Wis icleerifeM m 41 2a cio RE 43 212 Pp 47 2122 MD CCS uot E ELDER I LI MI IM LO EE IO E ES 47 2 13 Split Requirement Structures risistitu inasin anaia aa aia aati 47 SNE ER 48 24 1 e Et te BUCH 48 214 2 Greate TEE 49
48. f Find locks unlock fia Showing a lack 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 Za 10 2006 09 56 42 Updated z Administrator Updator RMS eB 08 2006 16 20 44 Updated RMS z Manual Figure 45 Before and after update TEMPPO V6 0 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 Task List Show Figure 46 see also 2 6 Page 35 User Manual TEMPPO V6 0 Edition March 2013 Description of Use E SiTEMPPO Testmanager Hannes TestProjekt A xl Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure New Test Structure System Test 10 M 4 KN w E No filter w IO 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 C Inherit ra EE ID Requirement Name Requirement structure Ee I New Test Case phangect 9n starting
49. gh Priority Features Mot Linked to Use Cases lt lt Prev Next gt gt Finish Cancel Figure 32 View selection Finish With pressing Finish the project is imported to TEMPPO Page 23 TEMPPO V6 0 Description of Use User Manual Edition March 2013 Bl x E TEMPPO Requirement Manager Testmanager Learning Project Use Cases 1 Requirement Structure Edit Evaluation Windows Requirement Structure Learning Project Use Cases 1 V1 G Brief Description Basic Flow INVENTORY NON AVAILABLE INVALID INFORMATION NO RESPONSE ORDER PLACED SUCCESS Check Order Status Brief Description General Meu Mame Learning Project Use Cases 1 Pretix uc Owner Testmanager LIpdatar Created 14 02 2012 14 54 30 Updated Basic Flow USER ALREADY LOGGED ON INVALID CUSTOMER ID OR PA OPTIONS FOR DISPLAY Pre Condition Creator in IBM RegquizitePro Created in IBM RequisitePro 14 02 2012 14 54 30 Type IBM RequisitePra View Al Use Cases Description Purchase CD Brief Description Bazic Flow INVALID SHOPPER ID USER ALREADY LOGGED ON QUIT QUIT SHOPPER NOT IDENTIF MODIF ITEMS CHANGE OPTIONS Pre Condition Pre Condition shop For CD Brief Description Bazic Flow SEARCH BY SELECTED CRITEI QUIT POSSIBLE NEW ACCOUNT NO NEW ACCOUNT Ni MATCHING CDs fi 36 VIEW CURRENT ITEMS r g 37 REMOVE ITEM p 38 ALLOW SUGGESTION OPTION
50. hen either activating the menu Filter gt Export or pressing the button Export selected filters to XML Figure 72 is displayed and the filter can be saved Bisave 05 Save in E SiTemppo CD sl E E 3 Zuletzt verw E Desktop Gi Eigene Dateien sr Arbeitsplatz L Netzwerkum File name ES Save Files of type m Document File xml Cancel Page 55 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Figure 72 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 disp
51. icate req ID ROS Zeile 1 Spalte 1 Figure 27 Error text file 2 5 1 3 Requisite Pro The RequisitePro client must be installed gt Rational RequisitePro Learning Project Use Cases FEAT Web Shop System Features Bl x T File Edit View Requirement Traceability Tools Window Help 81 x Ola e S cease v x vz el moles e Coverage Analysis FSi Requirements Features and Vision E13 Web Shop Administrative System b FEAT1 Secure payment method Functional I FEAT10 Ability to add remove Secure payment method 3 FEAT11 Ability to check on cu CI FEAT12 Maintain customer inf C3 FEAT13 Generate reports FEAT2 Easy browsing Functional 23 Web Shop Sistem Easy browsing for available titles 5 FEAT1 Secure payment metho FEAT3 Search by multiple criteria EI FEAT2 Easy browsing Ability to search for CDs by multiple criteria t3 FEAT3 Search by multiple crite us FEAT4 Ability to check status FEAT 4 Ability to check status of an order Functional CJ FEATS E mail notification of ne Ability to check the status of an order I FEATE Highly scaleable FEAT Ability to customize the FEATS User registration good f FEATS E mail notification of new titles of Functional E mail notification for Shoppers when new titles that may interest them are added to the collection FEAT 14 Use Legacy System FEAT15 Int
52. iew Figure 16 Requirement import wizard Introduction Page 15 User Manual TEMPPO V6 0 Edition March 2013 Description of Use When pressing Next Figure 17 is shown in which you choose Telelogic DOORS DEET La Import Requirements from an RM tool Steps Intraduction Chonse a RM tool eae F IBM Telelogic DOORS document 4 Choose a baseline and a view E amp IBM RequisitePro Fish Figure 17 Requirement import wizard Choose a RM Tool Then the server for DOORS starts and the following progress bar is shown Figure 18 Figure 18 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 19 Introduction z Choose a RM tool Select a requirement document a Choose a baseline and a view Figure 19 Requirement import wizard selection After selecting a module and pressing Next Figure 20 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 16 User Manual TEMPPO V6 0 Edition March 2013 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 24 With pressing Finish the module is imported to TEMPPO Ei i from an R Choose the baseline and
53. is given by the 283 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 259 l 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 you 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 EK of Exclusive edit mode 2 3 0General principles and u u semame Administrator Figure 36 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 37 Page 28 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Formal module Huge Project Huge Module current 0 0 DOORS File Edit View Insert Link Analysis Table Tools User Help Mee sel y x v e B z u Standardview fallevels z Se ee xe CB vs eg ic dE ae wee a m e El Huge Module 1 Description of Use p 1 1 The Test Process Phase How to Use El 1 21Multi user
54. k 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 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 42 is shown TEMPPO Note Ei Li l There is no Requirement Structure to apply tol Figure 42 No requirement structure for updating Page 33 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 2 5 3 7 Example Apply requirement updates Test Structure Clemens test System Test V2 f d H gh Be No Fiter e Clemens test c 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 43 Assigned requirement The test case has assigned the requirement 1194 see Figure 43 Nevertheless this requirement is deleted in DOORS Figure 44 Formal
55. laying 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 Stacked 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 73 shows an analysis from a requirement structure displaying the number requirement for a requirement attribute Requirement_state Page 56 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Fj Analysis E l 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 e horizontal 30 C vertical 25 Representation 20 Ce absolute C relative 15 Accumulate 1 Time Settings Start 01 03 2012 Ed End D 0 3 2012 mI implemented in work none open pending unit 12 psv sl Requirements Requirement_state B none oe Figure 73 Requirement structure analysis x axis requirement attribute Fj Analysis x gl Chart E Data Y Axis Requirements sl 54 Group by V 48 Chart vertica Bar Chart D E Iv Shaw D values Orientation 38 is horizo
56. lue Activate id Merge JA Delete fw mesas SI mme SIT sl Foz Implemented Tree style C Versions only Labels only Versions and Labels Requirements in view C ClearCase style Requirement Ge 2 Ce ascending 1 descending Figure 60 Requirements in view If you check in that requirement structure with a view the requirement structure looks like follows requirements not in view are not displayed or displayed grayed if they cover child requirements Fi TEMPPO Requirement Manager Testmanager Import i E n sl Requirement Structure Edt Evaluation Windows Requirement Structure Import V1 i 1 importa 89 2 EEN General View Af import Attribute Value en eee A zo OX Req State Implemented Lock Apply Discard Figure 61 Checked in requirement structure with view In the test structure you link test cases exactly to those requirements which are in the view Requirements which are not in the view do not become visible in the test structure 2 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 Release 1 Then the version tree looks like displayed in Figure 62 The requirement structure gets checked out immediately and version 2 is created The symbol Ze signals the active version which is again latest Pag
57. ment Choose a baseline and a view BM RequisitePra Prev Figure 30 Requirement import wizard Choose a RM Tool If you press Next the projects are read from the local registry Figure 31 Page 22 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Fi Import Requirements from an RM tool E X Steps Select a requirement document from the tree 1 Introduction 2 Choose a RM tool Username Unknown 3 Select a requirement dise Password 4 Choose a baseline and a wiew p amp Learning Project Use Cases E Learning Project Traditional E Project 1 za Prey Next m Finish Figure 31 Requirement import wizard project selection If you select a project enter a valid account and password and press Next Figure 32 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 32 Fi Import Requirements from an RM tool X Steps Choose the baseline and Ehe view to import 1 Introduction z Choose a RM tool 3 Select a requirement View jal Features D All Supplementary Requirements Al Use Cases Features Not Linked to Supplementary Regts Features Not Linked to Use Cases document 4 Choose a baseline and a wiew Full Coverage Report Functional Requirements Coverage Hi
58. module Huge Project Huge Module current 0 0 DOORS E zn File Edit View Insert Link Analysis Table Tools User Help Neel ASelolzx leslp Z7 U a Standard view ej fan levels DI A ox E Huge Module E 1 DHow to Use F CG 11 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 TAutomatic lock 00 Jf you are working with me 1194 SE chantore M describing the locking in manual mode nser sE sE wget Se Pl 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 Delete Requirements User defined ID feses General attrtxtes Test Steps IE Submit Change Proposal Properties Table properties Name New ie 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 ny See deeg egent Figure 44 Delete in DOORS After deleting the requirement structure in TEMPPO is updated Requirement Structure gt Update see Figure 45 Clear Suspicion L Prit Functi
59. nard v Save changes automatically suppress confirmation dialog Database El Requirement Management HBM Telelogic DOORS IBM Rational Requisite Pro gt Automatic numbering Ca Displays automatic numbering of requirements vw Ono for recursive numbering eg 1 2 3 L Delimiter tar numbering amp e d a Defines where numbering starts gt Display of requirements C Requirement ID C Requirement ID Name Mame Restore Defaultz Cancel Figure 103 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 user interface database and notification settings please refer to 1 chapter Settings 2 17 5 3 Requirement Management 2 17 5 3 1 IBM Telelogic DOORS The user password path to the local DOORS and a parameter can be edited Page 73 User Manual TEMPPO V6 0 Edition March 2013 Description of Use IBM Telelogic DOORS User Interface LTree DOORS Server i Mewsboard s EES m Database User Administrator 7 Requirement Management Password i ogie DOORS BRA Rational Requisite Pra Path to local DOORS CsProgram Files Telelogic DOORS_ 8 23bin doors exe Gi Parameters asta 36677 matnzgp1 ga
60. nd and Replace TEMPPO offers a find and replace mechanism With the menu item Edit gt Find and Replace Figure 98 is shown F Find and Replace X Search in Name sl for Rea Replace with Direction C Up IT Caze Sensitive Ce Down Find Mext Find Mest Requirement Replace Replace Allin Requirement Replace ll List Occurrences Close Figure 98 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 Page 69 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 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 Page 70 User Manual TEMPPO V6 0 Editi
61. ntal 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 03 02 2012 unit 12 pss D Updated B none Requirements co Figure 74 Requirement analysis x axis Updated Page 57 User Manual TEMPPO V6 0 Edition March 2013 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 75 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 P8 Wachentiche Baseline KV ei C VWersions and Labels 8 Pr sentation i ClearCase style 9D ein label Order TE G ascending E descending fg 15 editierbare Version Figure 75 Select versions After pressing OK the window is closed and Figure 76 is shown x Chart E Data 5 45 Chart vertica Bar Chart zu Representation 35 absolute Gn E 30 C relative E 25 Orientation C Ke 2D horizontal C vertical 15 10 W all EI P 5 ri changed D Zeep RE E E E E v d
62. o press the button Lock see Figure 78 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 If locking wasn t successful after pressing 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 79 is shown Reload the whole requirement structure LI x AN Cant find item in database Maybe the item was deleted by another user Figure 79 Item not found information Page 60 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 2 16 2 3 Delete 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 80 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 e The item or any child element iz locked Figure 80 Child element locked 2 16 2 4 Find invalid locks On starting and quitting TEMPPO Requirement Manager the whole database is checked for any locks which where set by you Normally there should be no one left But if there is one see Figure 81 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 TE
63. on March 2013 Description of Use 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 99 Find and Replace x A 1 Ma more occurences Found Figure 99 No more occurrences found e List occurrences With the button List occurrences the searching result is shown in a list see Figure 100 When clicking a requirement in the list it s selected in the tree LICHEN E D ome Deet ocoure Testmanager 14 02 2012 13 52 28 Testmanager 14 02 2012 13 52 33 Figure 100 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 101 with the number of replaced requirements and number of requirements which couldn t be replaced because of locks etc Page 71 User Manual TEMPPO V6 0 Edition March 2013 Description of Use x 1 4 Requirements are replaced 0 Requirement
64. once and create more references on it if necessary Fi Upload Properties of logging properties l X General Jogging properties tal Origin CaProgram Files TEMPP 6 OYogqging properties a Size 1 95 kByte Created 14 02 2012 14 01 00 Owner Testmanager References 0 Type Upload Description Figure 92 Upload properties Upload a new file You have to activate the Upload button to open Figure 92 for specifying a special name and description Additionally owner creation date size the number of references and the type are displayed Page 66 User Manual TEMPPO V6 0 Edition March 2013 Description of Use x an iweb File Database Reference E Creal ores Figure 93 Hyperlink database Use an existing upload You have to activate tab database and press button create reference to uploaded file to open Figure 94 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 94 and Figure 93 xj Find Nam ge created sze 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 94 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 informa
65. ons Search Functions J Help System Page 34 User Manual Edition March 2013 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 Ca Lock modes Cp 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 Gen Editing Elf Refreshing ER 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 Creator 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 Sai 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 ps This Feature can be config LH D Table uf ESMTable Locking modes in Efi Editing E Gi 1196 off Figure101 Lock state
66. pdator Testmanager Creator in IBM RegquisitePro Unknown Updator in BM RequisitePra Type IBM Requisite Pra H ff 29 REMOVE ITEM fi 30 ALLOW SUGGESTION OPTION Ga 31 Post Condition 32 UC Mew requirement fi 33 Da be deleted Lock Apply Discard Figure 39 Requirement Manager Updated 2 5 3 3 CSV If requirements have been imported from Excel csv they can be also updated in case of maintaining requirements is done in Excel Change requirement name content short text Also deleted requirements are concerned 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 Page 31 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 2 5 3 4 XML If requirements have been imported from XML and are maintained in XML they can be also updated Changes in requirement name content short text Also deleted requirements are concerned 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 5 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 reqiu 3 1 changed
67. quirements Cutting requirements Copying requirements 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 displayed 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 85 or the menu item Edit gt Select All 1 Mew C Find and Replace F3 shon etailz ts Tree b db Cut Copa op Ctrl c a Paste Ctri V iri Paste before 1 Order b ra Delete Delete n Refresh recursively Page 63 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Figure 85 context menu Select All Requirement can be selected with lt Ctrl gt or with lt Shift gt After pressing Select all all sub trees of the requirements are marked Fi TEMPPO Requirement Manager Testmanager Import B JE x Requirement Structure Edt Evaluation Windows Requirement Structure Import v2 Mo 4 bk M I wo nte sl el S _import
68. quirements see Figure 54 In the combo box you select the requirement structure and below its requirements are shown If a requirement is already assigned it s written in black but if there is a new assignment the requirement is written in grey Fi Requirement selection p x Link test cases to requirement M mp Mame Reguirement Structure eqi11 Link Link test cases to requirement Find H f reoi10 Link b 3 req112 Link3 7 H eer Figure 54 Requirement selection After selecting the requirements the selected ones are shown as a list see Figure 55 Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Link test cases to requirements System Test v1 M 4 b M IS Mo filter sl Mal Link test cases to requirements EE 1 Demo Test Package 1 1 Demo Test Case General Attributes Test steps E Automation Requirements History Plan Execution History Inherit Requirement ID Requirement Mame Requirement Structure req111 Link Link test cases to vir x Dema Test Case requirement x S Lock Apply Discard es Figure 55 Requirements 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 Page 41
69. r name already used Please enter a different name Remark Due to missing meta data assignments some filters might not be usable in the apened project and therefore not visible After saving the new filter Figure 67 is closed and Figure 66 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 E 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 D lt D or 10 2010 ES a ann D 4 owner D Testmanager c mm D E Requirement Mame sl Req sl Del Created lt 01 10 2010 AND Owner Testmanager AND Requirement Name Deco Hide Empty subtrees Impact ta selected Window Requirement 46 Apply Cancel Figure 68 Open item properties Depending on the selected filter the conditions are displayed Filter name is read only filter conditions can be changed See Figure 67 If the filter is in use and was changed the changes are then
70. re Import from DOORS with views 5 V1 O M 4 b M E No Filter k EQ Inport From DOORS with views 5 Loli 1 o Table E 2 Frank Matter General Attributes D n 2 1 Software Requirements Specificatic e Ot Requirement ID HI Import From Telelogic DOORS with 4 Distribution list Mame Document was created using the Following P Mame alphab Department 6 Hutzler Doris Sv IIS REG Owner Administrator Updator Administrator 2 SITEMPPO Support SIS PSE KB C4 D Document Management 8 History of changes Creator in Telelogic DOORS Administrator Updator in Telelogic DOORS Administrator gt gt Table Persons authorized to make chani 2 Document was created using the Type Telelogic DOORS Microsoft Office Word 2003 Contents 1 Introduction 422 1 1 Purpose of the document 4 Description 1 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 2 Detailed description of the req Z l Detailed description of produ 22 viewsin DOORS 4 of Lock Emly Discard k Created 09 01 2008 12 31 17 Updated 09 01 2008 00 00 00 Created in Telelogic DOORS 21 09 2007 07 32 28 Updated in Telelogic DOORS 09 01 2008 11 16 22 Short Description Document was created using the following tools Figure 23 Imported requirement structure with Views When there is an attribute specified as requirement id then the value of this attri
71. rement Structures T User Fields Find Swailable values ES Customer requirements Selected values Notepad User requirements t Import t Motepad 1 Requirements for user documentation Su requirements e Figure 52 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 53 W TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Tools Windows Help _ Test Structure Link test cases to requirements System Test V1 M 4 b M we E No filter sl d Link test cases to requirements E 1 Demo Test Package Oh V Demo Test Case General Attributes Test Steps BJ 4tomation Requirements History Plan Execution History Inherit Path Requirement ID Requirement Name Requirement Structure Description Lock Apply Figure 53 Link requirements Page 40 User Manual TEMPPO V6 0 Edition March 2013 Description of Use The test case can inherit from the test package s requirements Additionally the selected test case can have associated requirements With the button New a new window opens where you can select re
72. requirements lli IP Apply Discard 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 2 17 2 1 Create 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 7 Italic U Underline cz Hyperlink a Remove hyperlink creat eat pei Figure 89 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 89 which opens the Hyperlink window see Figure 90 Page 65 User Manual TEMPPO V6 0 Edition March 2013 Description of Use z web c Fie B Database URL nttp Hat atos pel Figure 90 Hyperlink to the web You have the possibility to enter a link to the web specified by an HT TP address or to the file system see Figure 91 x web File Databaze File C Program Files TEMPPS 6 OYogging properties i OK Cancel Figure 91 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
73. requirements reqi00 2 deleted requirements Feb reqiu co Figure 40 Update information 2 5 3 6 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 Test Structure gt Apply requirement updates Figure 41 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 32 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Wi Apply requirement updates X Huge Module Testmanager 14 12 2006 09 vz3 Apply Cancel Figure 41 Apply requirement updates Updating a requirement structure does not cause that a tas
74. s coudn t be replaced Figure 101 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 settings please refer to 1 chapter Settings 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 ry xj od Database m Database OSN Chooser Switches on off a database chooser window on TEMPPO startup ls Timeout in seconds displaying DSM chooser Locking iv Switches an aff to lock the whole requirement structure before checking in and to prevent check in if an item is lacked Locking Mode Locking made in requirement structure Ce automatic C manual Restore Defaultz Cancel Figure 102 Settings Fast search On the right side all single settings can be edited see Figure 103 Page 72 User Manual TEMPPO V6 0 Edition March 2013 Description of Use settings eee x Tree User Interface 2 L Mt Automatic sawe 2 Mewsb
75. 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 2 Possible errors during the import eros Rextn The host for DOORS can t be found and A message is shown see Figure 25 so the connection can t be opened Check if Telelogic DOORS client is installed and correct the DOORS settings in the TEMPPO Requirement Manager settings Windows Settings An attribute is defined as requirement A message is shown see Figure 26 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 27 and then import again Page 20 User Manual TEMPPO V6 0 Edition March 2013 Description of Use TEMPPO Exception n xj Error Hast not Found Figure 25 Error Host not found x i Due to a prablem with requirement ids the requirement structure could not be imported A For detailed information read the error File C Documents and Settings atw10905 temppolloghimportbOORS1 199879602307 log Do vau want to open Ehe error File now i Cancel gl xi 11 01 2008 10 16 29 ID 32 Duplicate req ID R s 11 01 2008 10 16 29 ID 33 No reg ID 11 01 2008 10 16 29 ID 36 Dupl
76. separated by a comma Now the user can edit this line Page 53 User Manual Edition March 2013 No blank is allowed only a comma Fi Build In Clause X Find Selected values lt Available values Analysed Implemented In work Reviewed Assign selected values Figure 70 Selecting attribute values for IN NOT IN Attributes Operato Operator Operator lt gt lt gt Planned coverage Requirem ent name Requirem ent short descriptio n Requirem Y ent ID ome v Created Updated Requirem ent attributes Yes if operators IN NOT IN are selected Yes if a set of values can be selected 3 Yes if editable is Yes D ct N TEMPPO V6 0 Description of Use Wild card allowed 3 Page 54 User Manual TEMPPO V6 0 Edition March 2013 Description of Use Table 2 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 sl 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 71 Filter criterion 2 14 8Export filter It is possible to export filters to XML and import them again W
77. t lt body gt lt htm1 gt gt lt DESCRIPTION gt lt REQUIREMENT name New Requirement ADDED requirementnumber req41017 type Manual shortdescriptaons createdrms updatedrms selectable 0 coveredbytcs 1 lt DESCRIPTION gt lt DESCRIPTION gt SUSER DEFINED ATTRIBUTE name Requirment attribute value high type 32 gt lt REQUIREMENT gt lt REQUIREMENT name New Requirementxcvxcv requirementnumber req41019 type Manual shortdescription createdrms updatedrms selectable 0 coveredbytcs 1 SDESCRIPTION lt CDATA gt lt DESCRIPTION gt lt REQUIREMENT name New Requirement requirementnumber req41020 type Manual shortdescription createdrms updatedrms selectable 0 coveredbytcs 1 SDESCRIPTIION Page 26 User Manual TEMPPO V6 0 Edition March 2013 Description of Use t CDATA gt lt DESCRIPTION gt lt REQUIREMENT gt REQUIREMENT REQUIREMENT REQUIREMENT name import XML 2 requirementnumber import32 type Manual shortdescription createdrms updatedrms selectable 0 coveredbytcs 5 lt DE SCRIPTION lt CDATA lt html1 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 html1 gt gt lt DESCRIPTION gt USER DEFINED ATTRIBUTE name Requirment attribute value high type 32 gt lt REQUIREMENT gt lt RS gt
78. ted item with all sub items will be completely re loaded from the database so it may take a long time Fi TEMPPO Requirement Manager Testmanager Import Requirement Structure Edit Evaluation Windows Er TN Mew Cl Find and Replace F3 Select ll Ctrl i 1 importo 7 fi 2 import DG Tree d i 3 import So S dh Cut Crlex Copy Ctri c Eal Faste Ctr fix B Raste before er Testmanager Updator Testmanager li Order P Eq 14 02 2012 08 34 44 Updated 14 02 2012 12 28 22 K e Delete pe Manual Edit Filter Ctri E bn Refresh recursively lock ppl Discard Figure 83 Refresh recursive menu also in the context menu 2 16 3 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 62 User Manual TEMPPO V6 0 Edition March 2013 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 database Maybe the item was deleted by another user Figure 84 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 Deleting re
79. tion Of course you can upload files that exceed that limit and or change this value in admin properties TEMPPO Note i x You are about to upload a file which exceeds the limit of 488 28 kByte 9 ep Do you want to continue Figure 95 File size exceeds the upload limit Page 67 User Manual TEMPPO V6 0 Edition March 2013 Description of Use 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 91 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 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 96 is shown to select a directory for the file download Kj Select a destination directory x Lookin Eigene Dateien x Em Fe Zuletzt verwendete Dl on imm Desktop Eigene Dateien a Eigene Musik 53 artikel 2 Eigene Bilder CO Audi C3 My Podcasts O CC TestFactory
80. tional RequisitePro ccccccecccsecseeeseeeceeeeeeeseeeseeeseeseeeneeenes 74 SEN OCURRE E 76 e EE e e EE e CC 77 e ADDON p eee 78 5 1 DTD Schema for XML Import Requirement Structure 78 NOG doeet Ed 79 Page 4 User Manual TEMPPO V6 0 Edition March 2013 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 and IBM Rational Requisite Pro 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 r
81. uirement 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 Page 8 User Manual TEMPPO V6 0 Edition March 2013 Description of Use F SiTEMPPO Requirement Manager Strasser Johanna manual oj x Requirement Structure Edit Windows Requirement Structure manual V1 i 7 Ga 1 New Requirement 059 RC TE General Attributes 2 New Requirement 1 D Eie Renner Requirement ID mres Name New Requirement Owner Strasser Johanna Updator Strasser Johanna Created 20 08 2009 11 50 20 Updated 20 08 2009 11 50 20 Type Manual Short Description Description 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 item is enabled if a requirement structure is opened and a requirement is selected A new requirement is cr
82. ulti user 59 TEMPPO V6 0 Index Lock 59 N Newsboard 41 R Refresh Recursively 62 Whole requirement structure 61 Requirement Edit 14 Link 40 New 8 Tab Attributes 9 Tab General 9 Requirement structure Assign attribute 38 Import 14 Split 47 Requirement Structure 5 Assign 39 Check in 43 Create 6 Export XML 37 Import from DOORS 15 Import XML 24 Open 7 Update 27 RequisitePro Import 21 Project 23 Update 30 View 23 T Task List 36 Test Structure apply requirement updates 32 V Version 43 Delete 47 Merge 47 View 44 View 44 X XML Import 24 Update 32 Page 79
83. y the same version tree as its source Via Requirement Structure Split the split dialog is opened the menu is only enabled if the root node is selected Split requirement structure X Mask Far requirements to move aye Mame of new requirement structure Nav Requirements Case sensitive Cancel Figure 64 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 Page 47 User Manual TEMPPO V6 0 Edition March 2013 Description of Use The following example illustrates the splitting process Requirement structure before splitting Requirement Structure NAV 001 NAV 002 NAVIGATION 003 MAP 001 Dest5nput ood 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 Requirement Structure RADIO 001 RADIO 002 NAV Requirements NAV 001 NAV 002 NAVIGATION 003 MAP 001 Destinput 001 MAP 002 Navi 004 2 14 Filter Users c

TEMPPO Requirement Manager User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents