Modeling Process Specification All information in integreat is stored within packages that are called Specifications

Transcription

1 Modeling Process Specification All information in integreat is stored within packages that are called Specifications When working with Team Projects the Specifications can be grouped in folders. You can create folders and sub-folders and management specification in them. 1. When a Team Project is opened you will see A B C A. Multiple knowledge area is presented at the top. If you click on the knowledge area it filters a list of specifications by that type. B. On the left side you will see folder management. Here you can create new folders/subfolders, rename the folders and delete folders. C. In the main area you can manage the specifications as well as load specifications using Load Specification

2 2. To create a new Process Specification click on New Specification and select Process Flows 3. Give the new specification a name and hit Enter. 4. To open the specification double click on the name or click on Open button. The specification will be checked out and opened in Visio layout. By default, root object i.e. Process will be created. 5. You are given more options to create new objects under User Login Process object from left side panel i.e. Wizard Manager. Let s first choose Display option.

3 A. When you click on Display button, you will see. A. Give display a title such as User Login Screen.

4 B. Select Add button to add display object. 6. Now select Operation button and add in a similar way (as described above) under display object User Login Screen. 7. For New User? Sign up here operation; reuse an existing process Register User Process.

5 A. When you select Reuse button, you will see Search Panel.

6 B. From Search Panel, user can search an object in the whole project by using any of the following search criteria: A. User can search an object by giving its name. B. User can search an object by selecting its type. C. User can search an object in a specific scope/folder. D. On selecting, it will search the object on the basis of above selected criteria. E. On selecting, it will link the Register User Process object to selected operation.

7 8. In a similar way as described above, add or reuse objects under Login operation and complete the whole process flow. A. Once the objects are created, you will see relation name between objects.

8 B. You can change the relation name by double clicking on the relation name. Q: What other related keyboard shortcuts are there? A: After selecting object button in left side panel: i. Shift-Enter will add the object under selected object. ii. Using Ctrl-Enter, you can add multiple objects of same type under the selected object at the same time. 9. To provide or edit the properties of objects, say process, select it. Click on Property Panel button on the toolbar. This is open up the property panel at the bottom. To collapse the property panel, click on the pin

9 Or select the Properties button on left side panel. This will open up the popup window. Click on the different tabs to manage related information. The DESCRIPTION tab supports rich text content where you can format text, insert bullet/numbers, tables and paste images in the field.

10 10. You can apply Color and Line formatting on Visio shapes. To apply formatting right mouse click on a shape. Select Fill Format / Line Format. Similarly you can create new objects or permanently purge the object. 11. To close the specification click the x marked at the top right. 12. To save the project click on File/Save Or click on the save icon. At this time the project is saved. On save the specification is checked-in and out so that versions of the specification are maintained in TFS. You can view User Login Process specification on Team Foundation Server. A. Open a browser window and enter the URL for web access.

11 B. Click on the CODE link. C. Click on the integreat folder.

12 D. The User Login Process specification is saved on the server in the team project repository.

13 13. To close the project, go to File menu and click on Close. 14. You may be asked if you want to save the project. Click on Yes. All open specification will be checked-in, work items published and project closed. Q: What would happen if I did not close some specifications? A: The specification would be checked-in and immediately checked-out as well as work items published before closing the problem. Next time when you open the same project the specification will be available to you as being checked-out by you. Others will not be able to check this specification until you check the specification in.

14 Generating Use Case and Test Case Documents 1. Select the HOME tab, and click Document Manager option. 2. Document Manager window will appear. Select Use Cases and Test Cases folder at left side panel. 3. You are given different variations of use case and test case documents on right side. Select any one of them, say CMMI 13 Detailed Use Case Document-Basic. Select document and click on the Generate button.

15 4. You will be asked to enter comments for generated document. 5. You will get this message box. Click on the document link to open it.

16 6. Here is the snapshot from the generated detailed use case document.

17 Generating and Publishing Test Cases to Team Foundation Server 1. Select the TEAM tab, and click the Publish Test Cases option. 2. It will publish the Test Cases to Team Project. At the end of publishing, it shows publishing results indicating the Number of Test Cases and their publishing status. 3. Open the Team project through Web Access, as described earlier. 4. Click on the Queries link.

18 5. To view test cases, click on Shared Queries Development and Testing Open Test Cases (on left side explorer). Test Cases are displayed on right side area. 6. Double click on the desired Test Case to view its details. The process flow steps are published as Shared Steps work items.

19