organization functions

ERIACT – USER GUIDE

EriACT Manual

2 | P a g e

SL. No Date Change Description Document

Version Authored By

Reviewed By

1 2012-12-14 Initial Draft 1 Tanushree Ghosh

2 2012-12-28 Details of EA and Eridoc incorporated

1.1 Tanushree Ghosh

3 2013-01-04 Project Closure incorporated 1.2 Tanushree Ghosh

4

5

6

EriACT Manual

3 | P a g e

CONTENTS

1 INTRODUCTION ...................................................................................................................................................... 5

2 ERIACT HOME PAGE ............................................................................................................................................. 5

2.1 WORKFLOW IN ERIACT FOR JIRA BASED PROJECT .............................................................................................. 6

3 PROJECT REGISTRATION AND SETUP ............................................................................................................. 7

3.1 PROJECT REGISTRATION ACTIVITIES IN ERIPRO ..................................................................................................... 7 3.1.1 EriPro .................................................................................................................................................................. 8 3.1.2 Program Creation .............................................................................................................................................. 9 3.1.3 Account Creation ............................................................................................................................................. 12 3.1.4 Project Creation ............................................................................................................................................... 16

3.1.4.1 Approve/Reject Project .............................................................................................................................................. 19 3.1.5 Add /Remove Projects to Program ............................................................................................................... 24 3.1.6 Access and Privilege Matrix........................................................................................................................... 28 3.1.7 Roles and User Categories for EriPro and EriPTT ..................................................................................... 32

3.2 PROJECT DATA FLOW ACTIVITIES IN ERIPTT ........................................................................................................ 36 3.2.1 EriPTT ............................................................................................................................................................... 36

3.3 CREATE SUB PROJECT IN ERIPTT ........................................................................................................................ 42 3.3.1 Creating Sub-Project with Project Type as PTT ......................................................................................... 42

3.3.1.1 Task Creation .............................................................................................................................................................. 44 3.3.1.2 Time booking in EriPTT .............................................................................................................................................. 48 3.3.1.3 Defect Logging ........................................................................................................................................................... 50

3.3.2 Creating Sub Project with Project Type as JIRA ........................................................................................ 51 3.3.2.1 High Level Task Creation ............................................................................................................................................ 53

3.4 PROJECT CONFIGURATION IN JIRA FOR SUB-PROJECT CREATED IN ERIPTT ..................................................... 57 3.4.1 Configure JIRA Dashboard ............................................................................................................................ 57 3.4.2 Manually Configuring JIRA ............................................................................................................................ 63

3.4.2.1 Configure JIRA issue Type schema containing matching issue Types in PTT .............................................................. 64 3.4.2.2 Configure JIRA Workflows .......................................................................................................................................... 68 3.4.2.3 Create JIRA subproject Types ..................................................................................................................................... 71 3.4.2.4 Create JIRA users and project lead ............................................................................................................................. 73 3.4.2.5 Create JIRA email notification scheme ....................................................................................................................... 75

3.4.3 View subproject ............................................................................................................................................... 78 3.4.4 View High Level Tasks against Sub Project ................................................................................................ 80 3.4.5 Sub task creation under high level task ....................................................................................................... 80

3.5 CREATE PROJECT MANUALLY IN ENTERPRISE ARCHITECT ................................................................................... 83 3.6 CREATE PROJECT MANUALLY IN HUDSON ............................................................................................................. 88 3.7 AUTOMATIC PROJECT CREATION IN TESTLINK ...................................................................................................... 89

3.7.1 Choosing project.............................................................................................................................................. 90

4 PROJECT COLLABORATION AND TRACKING ............................................................................................... 93

4.1 REQUIREMENT MANAGEMENT ................................................................................................................................ 93 4.1.1 Analyst captures Functional/non-Functional Requirements in EA ........................................................... 93 4.1.2 Synchronize requirements from EA with JIRA. ......................................................................................... 100 4.1.3 Design Related Task Created in JIRA ........................................................................................................ 105 4.1.4 Email Notification Sent to Designer ............................................................................................................ 105 4.1.5 Attach the UML model document against the requirement in EA .......................................................... 106 4.1.6 Upload requirement and design document in Eridoc ............................................................................... 107

EriACT Manual

4 | P a g e

4.1.7 Export XML Requirement File From EA ..................................................................................................... 111 4.1.8 ESB transforms the xml file and sends it via email to Test Manager..................................................... 113 4.1.9 Test Manager feeds the xml in TestLink manually.................................................................................... 114 4.1.10 Test team writes test cases against the imported requirements. ...................................................... 115

4.2 CHANGE MANAGEMENT ........................................................................................................................................ 116 4.2.1 Requirements added/updated in EA .......................................................................................................... 116 4.2.2 New/Changed requirements synchronized in JIRA from EA .................................................................. 117 4.2.3 Project Lead Assigning Coding Task (Low Level Task) ........................................................................... 117 4.2.4 Developer codes in eclipse and commits code in SVN ........................................................................... 118 4.2.5 Extract Requirements from EA .................................................................................................................... 120 4.2.6 ESB transforms the xml to TestLink ........................................................................................................... 121 4.2.7 Test Manager creates Test Cases against the new/updated requirements manually ......................... 122

4.3 DEVELOPMENT TRACKING .................................................................................................................................... 122 4.3.1 Low level task creation in JIRA ................................................................................................................... 122 4.3.2 Notification in Eclipse .................................................................................................................................... 122 4.3.3 Developer codes in Eclipse or any IDE & Commits in SVN.................................................................... 123 4.3.4 Log Work in JIRA .......................................................................................................................................... 125 4.3.5 Deployment Task Creation in JIRA ............................................................................................................. 128 4.3.6 Run Build Plan in Hudson ............................................................................................................................ 128 4.3.7 Test Team Executes Test Plan Against a Build No. ................................................................................. 133

4.4 TEST LIFECYCLE AND DEFECT MANAGEMENT..................................................................................................... 138 4.4.1 Test Manager get the requirements in xml format via email sent from ESB ........................................ 138 4.4.2 Import of requirement XMLs ........................................................................................................................ 139 4.4.3 Creation of folder for requirements ............................................................................................................. 141 4.4.4 Assigning requirements to test cases ........................................................................................................ 146

4.5 DEFECT MANAGEMENT......................................................................................................................................... 149 4.5.1 Mail Notification to Test Manager ................................................................................................................ 149 4.5.2 Login to test link ............................................................................................................................................. 149 4.5.3 Creation of Test Plan .................................................................................................................................... 150 4.5.4 Build ................................................................................................................................................................ 154 4.5.5 Assign users to test cases ........................................................................................................................... 154 4.5.6 Test execution by tester................................................................................................................................ 155 4.5.7 Update test results/ Defect Management .................................................................................................. 156 4.5.8 Developer gets a notification of work assignment in eclipse .................................................................. 160 4.5.9 Developer changes code and commits it to SVN ..................................................................................... 160 4.5.10 Resolve Issue in JIRA .............................................................................................................................. 160 4.5.11 Close Issue ................................................................................................................................................ 162 4.5.12 Reopen issue ............................................................................................................................................ 164

5 PROJECT METRICS REPORTING ................................................................................................................... 166

5.1.1 Project Manager Views Project derived KPIs in PTT ............................................................................... 166 5.1.2 All the defects and activity effort/schedule details are fetched from JIRA via ESB ............................. 171 5.1.3 Project Manager wants to check project Health in EriPro ....................................................................... 173 5.1.4 Project metrics data fetch from PTT to EriPro .......................................................................................... 176

6 PROJECT CLOSURE.......................................................................................................................................... 178

6.1.1 Project closure Audit is done In EriPro ....................................................................................................... 178 6.1.2 Project Status is changed to Closed in EriPro .......................................................................................... 178 6.1.3 Changed status is updated in PTT via ESB .............................................................................................. 179

EriACT Manual

5 | P a g e

1 Introduction EriACT is a Software Development Life-cycle Collaboration Platform. Solution components and tools in EriACT are primarily aimed towards providing the PMO functionality from project registration till project closure. It is a plug and play platform that can accommodate multiple tools in order to seamlessly collaborate between planning, tracking and execution of delivery through the various phases of SDLC.

2 EriACT Home Page User needs to login to all the EGI web applications by first opening a Home page. To log into EriACT, click on the following link: http://sdlc-collab-qa.egi.ericsson.com:8080/EriACT

(NOTE: In EriACT, as Single Sign On has been implemented you do not need to undergo the login action for EriPro, EriPTT and JIRA. Once you login in EriACT you can access these three modules and no separate login is required)

The home page will contain: i. The links to all the applications/tools like:

EriPro

EriPTT

http://sdlc-collab-qa.egi.ericsson.com:8080/eriact

EriACT Manual

6 | P a g e

JIRA

SVN

Hudson

Testlink ii. The workflow of the SDLC collaboration is also depicted in this page

2.1 Workflow In EriACT for JIRA Based Project

1. A project is first created and approved in EriPro. 2. The project which is created in EriPro after being approved automatically flows with

its details to EriPTT. 3. Now the Project Manager needs to create a sub project under the master project in

EriPTT because sub project details automatically flow to JIRA. 4. Project Manager also creates high level tasks against the subproject in EriPTT which

also automatically flow to JIRA 5. Project Manager/ TL/ Concerned person creates subtasks in JIRA against every high

level task created in EriPTT 6. Assigned users can start a subtask, resolve it, close it, log effort against it, track time

in JIRA 7. All the tools are connected to LDAP

EriACT Manual

7 | P a g e

Level -0 – Operational Process Flow – Tools Suit

Proj

ect M

anag

erPr

ogra

m

Man

ager

Team

Lea

der

Team

Mem

ber

Deliv

ery

Exce

llenc

ePM

OE2

E Ar

chite

cts

Com

pone

nt

Arch

itect

sTA

S

JIRAEriPro Eri PTT Test Management Suit EA Tool

Start 1. Project Initiation

Approval

Approval

Approval

2. Project Creation

Project Attributes

(Release Planning) 3. Define Sub

Project

3.a Categorize and prioritize requirements in EA Tool to define scope

4. Define Phase( Model SI phases

present)

Define Start Date , End Date and

Planned Effort

4.a Define Start Date , End Date,

Planned Effort

5. Create Tasks5.a Define Start Date , End Date,

Planned Effort

Project , Sub Project ( release ) , Task

Attributes

6. Create Subtask for the High Level

Tasks such that each task is assigned to

each resource

6.a Assign resources

Define Start Date , End Date and

Planned Effort

7. Fill Actual Effort Spent, Start Date &

End Date for Assigned

Sub-Task and change Status

8. Monitor for Completion and closure of all Sub

Tasks

9. Close all assigned Sub-Tasks , All

actual efforts to checked on closure

10. Monitor closure of all Tasks assigned to a Team Lead . All Actual Efforts

against the Task is rolled-up from Sub Tasks.

Actual Efforts for each tasks

11.a Generate Quality Metrics

11.b Generate Program Metrics includes early

warnings

11.c Generate Rolled up High Level Program

Dashboard

Capture requirements

Capture Business requirements

Capture Standard requirements ( part

of the product )

Capture Customization and

configuration related requirements

Break requirements into Solution Stories or Component Use

cases

Generate Test cases

Execute Test Cases

Report Defects

4.b Capture review rework Planned effort

per phase

10.1 Monitor closure of all review and rework assigned to team

Lead. All actual Efforts Review & rework for the task is captured at

task level

3 Project Registration and Setup

3.1 Project Registration Activities In EriPro

EriACT Manual

8 | P a g e

All the formalities of Project Registration, documents repository, subproject alignment and code repository are done in EriPro. EriPro provides a management dashboard of the overall project health; - cost, schedule, delivery quality and resources. In EriPro the project status can be rolled up to get a management view at practice, vertical, customer and region level. The project which is created and approved in EriPro automatically flows with its details to EriPTT if the tool selected is EriPTT.

3.1.1 EriPro

1. In the EriACT Home page, click on the EriPro link so as to be directed to the EriPro Home page.

2. Fields for the selection of a Role will be generated. From the Role drop-down select the “Role” assigned to you and click Go button.

3. The following user home page will appear after the successful login with the welcome message (having the User name and his/her Role).

EriACT Manual

9 | P a g e

3.1.2 Program Creation

1. When you log in as a Program Manager the Program tab will be visible in the header menu.

2. When the Program tab is selected the following tasks can be performed which are also displayed as side menu:

i. Create Program: You can create a new Program by filling in the mandatory fields and the click on Save button.

EriACT Manual

10 | P a g e

a. A Program is created and will be available in the system only if it is approved by the DE Manager and SD & D PMO.

o To approve a Program, the DE Manager and SD & D PMO will log into the system and then click on the Program header tab. Then click on Approve Program on the left hand menu.

EriACT Manual

11 | P a g e

o Key in the Program Name and then click Search. o The Search Result will display the Program Name. Click on the Program

Name. o The following screen will be displayed.

EriACT Manual

12 | P a g e

3.1.3 Account Creation

1. This page displays a header navigation menu and based on the selection of the Header menu the left hand menu options will be displayed.

EriACT Manual

13 | P a g e

2. When the Account tab is selected the following tasks can be performed which are also displayed as side menu:

ii. Create Account: You can create a new Account by filling in the mandatory fields and the click on Save button.

EriACT Manual

14 | P a g e

a. An Account is created and will be available in the system only if it is approved by

the CSI & ADM Head. o To approve an Account, the CSI & ADM Head will log into the system and

then click on the Account header tab. Then click on Approve Account on the left hand menu.

o Key in the Account Name and then click Search. The following screen will be displayed.

EriACT Manual

15 | P a g e

o Select the Account Name so that a popup will be generated displaying

the Account details. Key in an Approval Comment and then click Approve to approve the project.

b. Once an Account is Approved, it can be seen in the Search / Edit Account

screen.

EriACT Manual

16 | P a g e

iii. Search/ Edit Account: You can also search for an existing Account and then also edit as required.

(Note: You cannot edit the Account Name)

3.1.4 Project Creation

1. Click on Project tab on the header menu so that the following task can be performed which are also displayed as side menu:

i. Create Project: A new form opens up for project creation. a. Fill in all the mandatory fields which are mostly self-explanatory and create

the project. (Note: Project Name Prefix and Project Name Suffix will constitute the Project name created.)

b. User needs to select Project Engagement Type as 'Internal Project' if the project is internal type. In this case no budget related data needs to be entered.

c. Tool Utilization- The following options are available as dropdown:

EriPro

EriACT Manual

17 | P a g e

EriProEriPTT

EriProEriPTTJIRA The selection of any particular tool is based on the following criteria:

o If the Planned Effort <= 1000ph, only EriPTT is selected o If the Planned Effort is more than 1000ph, both EriPTT and JIRA

is selected o Any project which should run for more than 6 months should use

PTT and JIRA, depending on their size.

d. Even after you create a project it will not appear into the system unless and until approved by PMO.

Note: If you select Engagement Type as other than 'Internal Project' then the Budget related (Financial) data needs to be entered in Finance page (after entering Project Details PM have to click 'NEXT' button and you will be redirected to Budget creation page). In such case once the project is created, the project needs to be approved by both the PMO and as well as CSI OD (Approves budget related data.). After being approved by both the Project would go live (Active).

ii. Project Name Generation: A Project Name constitutes of the following:

Project Prefix Name

Project Suffix Name a. The Project Prefix name constitutes of the following information:

o Project Type

EriACT Manual

18 | P a g e

o Company Trigram (displaying the Region Code) o Based on the selection of Region Code a Country Name will be

generated

EriACT Manual

19 | P a g e

iii. Search/ Edit Project: You can search for an existing project and then edit as required.

3.1.4.1 Approve/Reject Project

Region Code

Region Code

Project Type

EriACT Manual

20 | P a g e

1. The Approve Project option is available only if you have logged in with PMO role.

i. Select the Approve Project link on the left hand menu. ii. The Search Project page will be displayed. iii. Enter the required values in the fields to search for the project you wish to

approve and click on the Search button. iv. The search result will be displayed.

EriACT Manual

21 | P a g e

v. Click on the project name so that the project details will be displayed. vi. In the Remarks field (mandatory field) enter a comment.

vii. Click on the Next button at the bottom of the page. viii. Finally click on the Approve button to accept or reject the project respectively.

EriACT Manual

22 | P a g e

2. If you click on the Reject button the project will be removed from the Approve Project list.

i. The Project Manager can now view this project in the Rejected Project list. ii. Click on the Update link to make the required changes.

EriACT Manual

23 | P a g e

iii. The Project Details screen will be displayed. Make the necessary changes in

accordance to the Remarks made. Finally click on the Save button.

EriACT Manual

24 | P a g e

(Note: It is mandatory to fill in the Remarks field to approve or reject a project) The DE team possesses power to determine the Tool Utilization for the project. Based on the Size of the Project the DE Team can reselect the Tool Utilization option- EriPro, EriPro EriPTT, EriPro EriPTT JIRA- before approving a project. It is required that the Project is approved by the CSI OD and DE. The procedure to be followed is the same as mentioned above.

3.1.5 Add /Remove Projects to Program

1. To Add/Remove Projects to Program log in as Program Manager.

2. Click on the Add/Remove Projects to Program link. 3. Enter the Program Name and search for the same. 4. A message will be displayed if no projects are mapped with the program yet.

EriACT Manual

25 | P a g e

5. Key in the Project related details and search for the project. 6. Click on the Link icon in the Link Project column.

7. The Project is now sent for approval for being linked to the program.

EriACT Manual

26 | P a g e

8. To approve a project being linked to a Program:

i. Login in as DE Manager ii. Click on the Program tab followed by clicking on the Approve/Reject Project

Movement link. iii. Click on the Approve icon.

EriACT Manual

27 | P a g e

iv. A popup will be generated. Enter a comment.

v. A message displays that the project is linked to the program.

EriACT Manual

28 | P a g e

3.1.6 Access and Privilege Matrix 1. Click on the Configuration tab on the header menu so that the following tasks can be

performed: i. Create User: As an Admin you can create a user. a. Click on Create User so that the following page will be generated.

b. All the fields displayed here are mandatory. c. Key in the Signum for User Name and then click on the Search button. d. If user is present in the system with that Signum then user information will appear

in edit mode. User can change information and save it. e. If user is not present in the system with that Signum then user can enter user

information and save it. New user is created in the system. f. After a successful user creation, an Auto-generated Email (EriPro-Admin) is

triggered to user with the login credentials to login in EriPro. g. Each users need to change his/her default password during the very first time

login in EriPro.

Note: There are default/dummy projects that are created for each approved Program/Account to map resources that are allocated for that particular Program/

Account. This Default/dummy project is used for Resource Mapping. These default/dummy projects cannot be linked with any other Account or

Program.

EriACT Manual

29 | P a g e

ii. User Role Mapping: Only Admin and Super User can have access for

providing User Role Mapping. a. Click on User Role Mapping so that the following screen will be generated.

b. Enter a Signum and click on the Search icon:

For a new user who has not yet been assigned a role click on Add Role button.

EriACT Manual

30 | P a g e

i. The Add Role section will be generated

ii. Select a Role from the Available Roles section iii. Forward the selected Role from the Available Roles section to the

Added Roles section

EriACT Manual

31 | P a g e

iv. Finally click on the Update Roles button.

For an existing user you can: v. Revoke the existing role vi. Assign a new role or Update an existing role.

(Note: No other Role can be associated with Admin, PMO/Management Roles. So no additional roles can be assigned)

EriACT Manual

32 | P a g e

3.1.7 Roles and User Categories for EriPro and EriPTT EriPro possesses the following categories with regards to Roles and User. Based on the Roles assigned, access permissions are provided to each role:

Serial No. Role Permission

1. Administrator (Admin) Is the Super user

Has access in all the Tabs except Resource tab

Can create new Users in the system

Can map User-Role/Access

Can create/edit Account and Project

Can perform Project Status insertion and Issue/Risk add or update

Can generate all the Reports

EriACT Manual

33 | P a g e

2. Management Has access to all the pages except User Creation page

Can perform all the tasks like Admin except user creation

Mostly management users can only access Reports

3. Vertical Head Have access in all the pages except Configuration and Resources

Can create/edit Account and Project under his/her Vertical


Can generate all types of Reports

Report will show all the Projects under his Vertical

4. Practice Head Same access as Vertical Head but only possesses access to Account/Project under his/her Practice

5. Engagement Manager Possesses same access as Vertical Head for one or more Verticals

6.

Account Manager (AM) Have access in all the pages except the Configuration and Resource

Can create/edit Account and Project under his/her Account

Can generate all types of Reports. Report will show all the Projects under his Account

7. Project Manager (PM) Cannot create/edit Project


Can generate all types of Reports

Report will show all the Projects managed by him/her

Cannot Create Opportunity like other users

8. Resource Deployment Manager (RDM)

Have access for Resource tab and Demand tab

Can perform excel file upload with predefined format

Can download resource information as an excel sheet

EriACT Manual

34 | P a g e

9. Project Management Office (PMO)

Can edit Project/ Account

Can Approve or Reject Project/Account after creation

After Approve/Reject an email is send to the Project/Account stakeholders

Cannot access Configuration pages

10. CSI Order Desk (CSI OD)

Have access like PMO users have

Approves new/ revised Budgets

11. CSI Super User (CSI SU)

Have access like ADMIN users have

Approves Financial cut-off Date for a certain budget

EriPTT possesses the following categories with regards to Roles and User. Based on the Roles assigned, access permissions are provided to each role:

Serial No. Role Permission

1. Vertical Head Can view/edit Task

Can perform functionalities like Time Booking, Defect Logging & Posting

Can access Bird’s Eye View Cannot access Configuration pages

Can only access project data under that vertical

2. Practice Head Can view/edit Task

Can perform functionalities like Time Booking,

(NOTE: Every user can have one or more additional access along with his original access. Users having ADMIN / PMO / RDM / Management / CSI OD / CSI SU can't have delegated or additional accesses, as these Roles are considered as special Roles. One project is related to one PM, one account is related to one AM, one vertical is related to one VH, and one practice is related to one PH. AM/PM/VH/PH cannot have any one of the access of Admin, Management, PMO, RDM. Users can have delegated access to an entity or he can also own the entity, with his Primary Role of the respective Entity. (Like a VH can have delegated access to a vertical or else he can own the vertical)

EriACT Manual

35 | P a g e

Defect Logging & Posting


Can only access project data under that practice

3. Account Man-ager

Can view/edit Task



Can only access project data under that Account

4. Program Man-ager

Can view/edit Task



Can only access project data under that Program

5. Project Manag-er

Can view/edit Task



Can access only his sub-project data

6.

Team Lead Can view/edit Task



Can only access data related to that project

7. Team Member Can perform functionalities like Time Booking & Defect Logging

8. Admin Is the Super user

Has access in all the Tabs


Can map User-Role/Access Can create/edit sub-projects and task


9. Super Admin Is the Super user

EriACT Manual

36 | P a g e

Has access in all the Tabs


Can map User-Role/Access Can create/edit sub-projects and task


10. Management Can view/edit Task

Mostly management users can only access Reports

3.2 Project Data Flow Activities In EriPTT

Once a Project Registration Process is done in EriPro and based on the tool selection- EriProEriPTT/ EriProEriPTTJIRA-, the data will automatically flow to EriPTT. The Project Manager needs to create a sub project under the master project in EriPTT because sub project details automatically flow to JIRA. Project Manager also creates high level tasks against the subproject in EriPTT which also automatically flow to JIRA.

3.2.1 EriPTT Scope of this tool is tracking of all the attributes from Project level. After getting a project from EriPro, system can create sub-project (e.g.: Release 5, Release 6 etc.) for the newly created project. Tool can only manage data of Sub projects and of the Tasks created based on Phases. User can provide information of planned schedule and planned effort of subproject, phases and tasks, while actual data will be captured from Time Booking level All the data provided by the user in task level, can be rolled up to sub project level. Time sheet can be entered in task level. Only the actual effort is rolled up to subproject level from task level. EriPTT and EriPTTJIRA based project will come from EriPro to EriPTT. An authorized user for EriPTT will be able to login into the application only.

EriACT Manual

37 | P a g e

After selecting the Role, select the Project Type from the following options:

JIRA

PTT A. For small scale projects, we generally choose PTT.

1. Based on the selection of PTT the following screen will be displayed.

EriACT Manual

38 | P a g e

2. The project created in EriPro will automatically flow to EriPTT. To search for a created project enter the project name in the Search field.

EriACT Manual

39 | P a g e

B. For comparatively large scale project, select JIRA as an option. 1. Based on the selection of JIRA the following screen will be displayed.

EriACT Manual

40 | P a g e

2. The project created in EriPro will automatically flow to EriPTT. To search for a

created project enter the project name in the Search field.

EriACT Manual

41 | P a g e

3. Click on the project name to view the project details.

EriACT Manual

42 | P a g e

3.3 Create Sub Project in EriPTT

The Project Manager can create a sub-project in EriPTT by either selecting the Project Type as PTT or alternatively by selecting JIRA.

3.3.1 Creating Sub-Project with Project Type as PTT 1. Create sub project under the master project that you have created in EriPro. We

need to do this as the subproject details automatically flow into JIRA from EriPTT. 2. Click on the Sub-Project tab on the top header menu. 3. From the corresponding side menu generated click Create Sub-Project. The

following screen will be generated.

4. Fill in all the mandatory fields which are mostly self-explanatory and then click on

the Create button.

EriACT Manual

43 | P a g e

5. To view the Sub-Project created click on the View Sub-Project link on the side menu so that the following fields are displayed.

6. Fill in the fields and click on the Search button so that the corresponding search result will be displayed.

EriACT Manual

44 | P a g e

3.3.1.1 Task Creation

1. Click on the Task tab from the top header menu. 2. The corresponding side menu will be generated. 3. Select Create Task link from the side menu and fill in all the mandatory fields which

are self- explanatory.

EriACT Manual

45 | P a g e

4. For the following fields Team Lead, Task Assigned To, Functional Spec Reviewer,

Technical Specs Reviewer, Requirement Owner and QA Reviewer: i. Click on the button next to the above mentioned field ii. A popup will be generated where you can search for an assignee or a

reviewer.

EriACT Manual

46 | P a g e

(Note: To create a task you need to define the sub-project phase before creating the task)

Select Phase

1. Click on the Phase tab on the top menu and then click on the Edit Phase link on the left hand menu.

EriACT Manual

47 | P a g e

2. Enter the Account Name, Project, Sub Project and then click on the Fetch

Phases button.

3. Click on the Phase that you wish to define to get an expanded view of all the

fields.

EriACT Manual

48 | P a g e

4. Fill in all the mandatory fields and then click on the Save button.

3.3.1.2 Time booking in EriPTT

1. Click on Time Booking tab. 2. Select Account Name, Project Name, Sub-Project, Task, Date etc. to select the

project for which you wish to book time.

EriACT Manual

49 | P a g e

3. Click on the View button so that the Timesheet is fetched. 4. Then log effort against every day and save it.

EriACT Manual

50 | P a g e

3.3.1.3 Defect Logging

1. Click on the Defect Logging tab in the top navigation panel. 2. Fill in all the mandatory fields.

EriACT Manual

51 | P a g e

3. Click on the Create button to create the defect.

3.3.2 Creating Sub Project with Project Type as JIRA

1. Create sub project under the master project that you have created in EriPro. We need to do this as the subproject details automatically flow into JIRA from EriPTT.

2. Click on the Sub-Project tab on the top header menu. 3. From the corresponding side menu generated click Create Sub-Project. The

following screen will be generated.

EriACT Manual

52 | P a g e

4. Fill in all the mandatory fields which are mostly self-explanatory and then click on the Create button.

5. To view the Sub-Project created click on the View Sub-Project link on the side

menu so that the following fields are displayed.

EriACT Manual

53 | P a g e

6. Fill in the fields and click on the Search button so that the corresponding search

result will be displayed.

3.3.2.1 High Level Task Creation

EriACT Manual

54 | P a g e

1. Click on the Task tab from the top header menu. 2. The corresponding side menu will be generated. 3. Select Create Task link from the side menu and fill in all the mandatory fields which

are self- explanatory.

4. For the following fields Team Lead, Task Assigned To, Functional Spec Reviewer, Technical Specs Reviewer, Requirement Owner and QA Reviewer:

i. Click on the button next to the above mentioned field ii. A popup will be generated where you can search for an assignee or a

reviewer.

iii. Select a user from the search result generated.

EriACT Manual

55 | P a g e

(Note: To create a task you need to define the sub-project phase before creating the task)

Select Phase

1. Click on the Phase tab on the top menu and then click on the Edit Phase link on the left hand menu.

2. Enter the Account Name, Project, Sub Project and then click on the Fetch Phases button.

EriACT Manual

56 | P a g e

3. Click on the Phase that you wish to define to get an expanded view of all the fields.

4. Fill in all the mandatory fields and then click on the Save button.

EriACT Manual

57 | P a g e

3.4 Project Configuration in JIRA for Sub-Project created in EriPTT

Project Manager/ Team Lead/ Concerned person creates low level tasks in JIRA for the corresponding high level tasks in EriPTT. Assigned users can perform many activities in JIRA like start a subtask, resolve it, close it, log your effort against it, and track time in JIRA.

3.4.1 Configure JIRA Dashboard

1. Click on the JIRA link such that it opens in a new tab. 2. The JIRA dashboard will be displayed. You need to configure the dashboard with

some existing configuration done by the administrator.

3. Click on the dropdown from the Dashboards header menu. 4. Click on the Manage Dashboard option from the dropdown.

EriACT Manual

58 | P a g e

5. The Manage Dashboard screen will be displayed. 6. Click on the link Create new dashboard at the top right hand corner.

7. The Create New Dashboard screen will be generated. 8. Fill in the required details and click on the Add button to create a new dashboard.

For the field Start From you can either select: Blank Dashboard or System Dashboard.

EriACT Manual

59 | P a g e

i. If you select Blank Dashboard follow the steps mentioned below:

a. The Favorite Dashboard screen will display the newly created Dashboard. Select it.

b. Click on the Add Gadget link.

EriACT Manual

60 | P a g e

c. A popup is generated displaying the available gadgets.

d. Select and add the gadget. e. Select a project so as to map the dashboard with the project.

EriACT Manual

61 | P a g e

f. Repeat the process to add other gadgets as required.

Note: The above mentioned process is to be performed by the Project Manager. If the Team members wish to access the same Dashboard they need to perform the following process

9. From the left navigation panel click on the Search option.

EriACT Manual

62 | P a g e

10. Enter a value in the Search field to filter the search.

11. The search results are now displayed in the screen. Select the required dashboard

configuration type.

EriACT Manual

63 | P a g e

12. The selected dashboard configuration will be displayed. Click on the link “add it as a

favorite” to complete the configuration process of your dashboard.

3.4.2 Manually Configuring JIRA

Login in as an Administrator and then manually configure the following:

EriACT Manual

64 | P a g e

3.4.2.1 Configure JIRA issue Type schema containing matching issue Types in PTT

1. Click on the Issues tab in the top navigation panel. 2. From the dropdown select the Issue Types option.

3. In the left navigation select Issue Type Schemes. 4. Click on the Add Issue Type Scheme button.

EriACT Manual

65 | P a g e

5. The Add Issue Type Scheme screen will be generated.

EriACT Manual

66 | P a g e

6. Enter a Scheme Name, a Description and then click on the Save button at the

bottom of the screen.

7. The Issue Type Scheme will now be displayed in the Available Issue Types list.

EriACT Manual

67 | P a g e

8. To move an issue type from the Available Issue Types column to Issue Types for Current Scheme column, drag and drop the desired option. To Move all the Issue types from the list click on the Add All link.

EriACT Manual

68 | P a g e

9. Finally click on the Save button to save the selected Issue Type Schemes.

3.4.2.2 Configure JIRA Workflows

1. Click on the Projects tab and then select the project for which you wish to configure the workflow.

2. From the left hand navigation panel select Workflows.

EriACT Manual

69 | P a g e

3. The Workflows screen will be displayed with the JIRA default workflow selected. 4. At the right hand corner of the screen click on the Actions button. From the

dropdown select the Use a Different Scheme option.

EriACT Manual

70 | P a g e

5. The Associate Workflow Scheme to Project will be displayed. Select a Scheme from the dropdown and then click on the Associate button.

6. The Associate Workflow Scheme to Project screen is generated. For each task,

for instance Approval, Budgeting etc. configure the Task Management flow from the dropdown list.

EriACT Manual

71 | P a g e

7. After configuring click on the Associate button at the bottom of the screen.

3.4.2.3 Create JIRA subproject Types

1. Click on the Administration tab in the top navigation panel. 2. Click on the Project Categories link.

EriACT Manual

72 | P a g e

3. The Project Categories screen will be displayed.

EriACT Manual

73 | P a g e

4. Fill in the fields under the Add New Project Category section and finally click on the Add button.

3.4.2.4 Create JIRA users and project lead

1. Click on the User tab in the top navigation panel. 2. From the dropdown select the User option.

EriACT Manual

74 | P a g e

3. To create a user click on the Create User button at the top right hand corner of the screen.

4. The Create New User popup will be generated.

5. Fill in the mandatory fields to create a new user.

EriACT Manual

75 | P a g e

3.4.2.5 Create JIRA email notification scheme

1. Click on the Issues tab and select the Notification Schemes option from the dropdown list.

2. The Notification Schemes screen will be displayed. 3. Click on the Add Notification Scheme button.

EriACT Manual

76 | P a g e

4. The Add Notification Scheme screen will be displayed. Fill in the fields and click on the Add button.

5. Once the new Notification Scheme is created the Notification Scheme screen will be displayed.

6. Select an Event and click on the Add link to configure.

EriACT Manual

77 | P a g e

7. The Add Notification screen will be displayed. 8. Select an Event from the dropdown list. Select the type of user (either Single User

or Group) whom you wish to receive the notification.

9. Custom fields can also be selected and added.

EriACT Manual

78 | P a g e

3.4.3 View subproject 1. Click on the Projects tab on the top header menu. 2. A dropdown will display all the projects assigned to you.

EriACT Manual

79 | P a g e

3. Click on a project name. The Summary tab will display the project details. (Note: The project is the same as the subproject created in PTT)

EriACT Manual

80 | P a g e

3.4.4 View High Level Tasks against Sub Project High level tasks created in PTT will be visible in JIRA as Issues. So task “DESIGN” created in EriPTT for a subproject “TEST_MANUAL_DESIGN” will be visible under Issues.

3.4.5 Sub task creation under high level task

1. To create sub-task under the high level task created in EriPTT click on Issues and then from the left hand section select the project name from the dropdown in Project field and click on the Search button for the high level task created in EriPTT

EriACT Manual

81 | P a g e

2. To open a task with all its details entered in PTT click on the phase name displayed

in the Summary column.

3. Click on More Actions tab so that a dropdown will be generated. From the

dropdown select Create sub task option.

EriACT Manual

82 | P a g e

4. A Create Sub- Task popup will be generated fill all the mandatory fields which are

mostly self-explanatory.

EriACT Manual

83 | P a g e

i. In the field JIRA Requirement Id, enter the link for the requirements that are mapped with this sub task being created.

(NOTE: 1) If user creates a subtask with Label as "Rework", then the effort logged in this subtask will be included in the actual effort of the parent task of this subtask. 2) If the user creates a defect and effort is logged in this defect, then this effort will be included in the phase level and not in any Task level.)

3.5 Create Project Manually in Enterprise Architect

1. Once the Enterprise Architect has been launched the Open Enterprise Architect Project dialog is displayed.

2. This dialog contains a New Project button and a convenient list of Recent projects.

EriACT Manual

84 | P a g e

3. The New Project Button produces the same result as File / New.

4. A Create a New Project option is also available from the Start Page.

EriACT Manual

85 | P a g e

5. Select a suitable name and location for your new project.

EriACT Manual

86 | P a g e

(Note: Enterprise Architect projects contain a .EAP file extension.)

6. Upon saving, Enterprise Architect will create a new Project file and place it in the selected location. The project is then opened and the New Model wizard will display.

EriACT Manual

87 | P a g e

7. Select from the following technology: including UML, SYSML, TOGAF, SOMF and UPDM, from the left hand side panel.

8. Select one or more model types from the right hand panel.

(Note: Based on the selection of Technology a variety of Model types will be displayed from where you can select as required)

9. Upon clicking on the Ok button the new project will be created.

EriACT Manual

88 | P a g e

3.6 Create Project Manually in Hudson 1. First click on the ‘New Job’ option on the left top of Hudson interface as in the picture

below.

2. Give ‘job name’ and check the first option under ‘Job name’ and then ‘ok’

EriACT Manual

89 | P a g e

3.7 Automatic Project Creation in TestLink

1. Click on the Testlink link in the EriACT home page. 2. Enter the username and LDAP password

EriACT Manual

90 | P a g e

3.7.1 Choosing project

1. Select your Test Project from the navigation tree.

(Note: You can always change the active Test Project by selecting a different one from the drop-down list in the top-right corner.)

2. Alternatively you can also create a new Test Project :

a. Click on the Test Project Management link on the home page.

EriACT Manual

91 | P a g e

b. The Test Project Management page is displayed and click on the Create button.

EriACT Manual

92 | P a g e

c. For ‘Create from existing Test Project?’ select No to create a new Test Project.

d. Enter a unique name to the project.

EriACT Manual

93 | P a g e

e. The Admin can enable Requirement related functionality.

f. Enable Test prioritization to select appropriate testing set in limited time.

g. Enable Test Automation support as well as Inventory.

(Note: Creating a new Test Project requires "admin" rights.)

4 Project Collaboration and Tracking

4.1 Requirement Management

4.1.1 Analyst captures Functional/non-Functional Requirements in EA

1. Once the model structure is created, select a model type; for instance select Deployment model.

EriACT Manual

94 | P a g e

2. On clicking on the Create Package icon a dialog box will be generated.

3. Click Ok so that a New Diagram dialog box will be generated.

Click Create Package icon

EriACT Manual

95 | P a g e

4. Enter a Package Name and based on the selection in the left column corresponding options will be generated. For instance when we select UML Structural in the left hand column then we can select Package from the right hand section.

5. Click Ok so that a package will be created. 6. Select the Package and then click on the Create Element icon.

EriACT Manual

96 | P a g e

7. A New Element dialog box will be generated.

8. Key in a Name, for Type select the value as Requirement and for

Stereotype select Functional for functional requirements and Non-Functional for non-functional requirements.

i. To configure the options available for Stereotype:

Click Create Element icon

EriACT Manual

97 | P a g e

a. Click on the Settings option in the header navigation section.

b. From the dropdown select UML Types.

c. The UML Types popup will be generated. d. Fill in the value “Functional” for Stereotype and for the field Base

Case select “Requirement” and finally click on the Save button.

EriACT Manual

98 | P a g e

e. Repeat the same process for Non-functional Requirement.

9. Click Create so that a Requirement dialog box will be generated.

EriACT Manual

99 | P a g e

2. Key in the Requirement Details. You can also browse and upload UML file for requirement.

i. Select Files from the left hand navigation menu. ii. Browse and upload the required file.

iii. To view the uploaded file click on the Launch button.

EriACT Manual

100 | P a g e

iv. Click OK to complete the process.

4.1.2 Synchronize requirements from EA with JIRA.

Once all the requirements have been finalized for a project that has been created in EA, the requirements are automatically mapped with the corresponding project that has been created in JIRA.

1. Select and right click on the requirement file that you wish to export to JIRA.

EriACT Manual

101 | P a g e

2. Click on Extensions option so that the corresponding EA Connector for JIRA option is generated.

3. Mouse hover on this option so that the further options will be displayed.

EriACT Manual

102 | P a g e

4. To synchronize the requirements from EA to JIRA click on the Export to JIRA

option. 5. System Authentication dialog box will be generated where you need to key in

your User Id and Password and the click Connect.

6. The Element Import to JIRA dialog box will be generated.

EriACT Manual

103 | P a g e

7. Select the project name to which you wish to export the elements by selecting

from the dropdown against the field Export elements to Project. 8. Based on the selection of Export Elements to Project, the Select Types

Mapping options will be available. 9. Once the mapping type is selected, the files available will be displayed in the

Select elements to export/ synchronize section. 10. Check the Export ‘Linked Documents’ and then click on the Export button.

EriACT Manual

104 | P a g e

11. When the file is successfully exported a message will be displayed.

12. The exported requirement document will now be available in JIRA.

EriACT Manual

105 | P a g e

13. Similarly to import a requirement you need to select a package and then right click on it. Select Extensions and then click on the Import option. The Import elements to Project dialog box will be displayed.

4.1.3 Design Related Task Created in JIRA Project Lead creates design related task in JIRA and assign it to Designer.

Refer to 3.4.5

4.1.4 Email Notification Sent to Designer Designer gets email notification and creates UML models in EA against the requirement specified.

EriACT Manual

106 | P a g e

4.1.5 Attach the UML model document against the requirement in EA Designer attaches the UML model document against the requirement in EA. Synchronizes the requirement in JIRA.

EriACT Manual

107 | P a g e

4.1.6 Upload requirement and design document in Eridoc 1. Project Lead uploads the Requirement and Design document in Eridoc. Document

can be uploaded in Eridoc as follows:

a. Log into Eridoc and the following screen will be displayed.

b. Click on the Projects Sub-header on the left section of the screen so that all the project names are displayed.

c. Select a Project name and then click on Working or Draft in the right hand section to add or upload the requirement document.

d. Depending upon whether the requirement documents are configurable or not select CI, Non CI and Project Specification.

Select Working or Draft option

EriACT Manual

108 | P a g e

e. If the requirement document is configurable and for the Design phase then select Design.

f. To upload the Requirement documents click on the File header menu.

Then select New from the dropdown list and the select either Document or Folder in accordance to your need.

EriACT Manual

109 | P a g e

g. The New Document: Create screen will be generated where you need to

fill in all the mandatory fields by selecting from the dropdown and then click on the Finish button.

2. Alternately you can also upload the documents by importing the files. a. Select the Import option from the dropdown.

EriACT Manual

110 | P a g e

b. The Import: File Selection screen will be generated. To upload click on Add

Files / Add Folders button.

c. When the upload process is complete click on the Apply to All button.

EriACT Manual

111 | P a g e

4.1.7 Export XML Requirement File From EA 1. To export the requirements from EA in xml format, select the package and then right

click on it. 2. Select the Import/Export option.

EriACT Manual

112 | P a g e

3. Export Package to XMI dialog box will be generated.

4. Select a file name and then click on the Export button.

EriACT Manual

113 | P a g e

5. The View XMI button is activated once the export process is complete.

6. To view the uploaded file click on the View XMI button.

4.1.8 ESB transforms the xml file and sends it via email to Test Manager Once the requirement documents are transformed to xml format, an auto generated email is sent to the Test Manager to begin with the testing procedure.

EriACT Manual

114 | P a g e

4.1.9 Test Manager feeds the xml in TestLink manually

1. In the top navigation panel click on Requirement Specification tab. 2. Select the Test Plan so that the corresponding counterpart is generated in the right

hand section. 3. Under the Requirement Operations section click on the Import button.

4. Select the File Type as XML and the browse and upload the file.

Test Plan

EriACT Manual

115 | P a g e

5. The xml requirement files are now available under the Test Case

4.1.10 Test team writes test cases against the imported requirements.

To prove that a system is built as specified, testers use requirement based testing. For every requirement, they design one or more Test Cases. At the end of the test execution a test manager reports on the tests that are executed and the requirements that are covered.

EriACT Manual

116 | P a g e

4.2 Cha

nge Management

4.2.1 Requirements added/updated in EA

1. To add or update the requirements in EA, double click on the requirement file that is uploaded.

2. The Requirement dialog box will be generated. 3. Key in the additional requirements and then click OK.

EriACT Manual

117 | P a g e

4.2.2 New/Changed requirements synchronized in JIRA from EA After the requirement document is updated, export the same to JIRA. For details regarding the synchronization process refer to section 4.1.2.

4.2.3 Project Lead Assigning Coding Task (Low Level Task)

1. The Project Lead creates a coding task in JIRA and assigns it. 2. The Assignee logs into JIRA and then clicks on the Start Progress tab.

EriACT Manual

118 | P a g e

3. The Status of the task now changes from ‘Open’ to ‘In Progress’.

4.2.4 Developer codes in eclipse and commits code in SVN 1. The assigned user receives a mail notification and then starts coding in IDE

EriACT Manual

119 | P a g e

(Eclipse) against the particular task assigned.

2. After making the relevant changes in the code, the developer commits the changes made in SVN.

3. Right click on the source code a panel will be displayed. From the options displayed in this panel, select Team option and then select the Commit option.

(NOTE: While committing the code in SVN the developer will have to mention JIRA Task ID for the task assigned to him against while he has coded in the Comment section of SVN Commit.)

EriACT Manual

120 | P a g e

4.2.5 Extract Requirements from EA 1. This is the XMI file that is exported from EA.

EriACT Manual

121 | P a g e

2. After the XMI Requirement file is exported from EA, manually place the

requirement file in a remote EriACT server in the specified path: /root/EAITools/EA-TestLink/InputXML

4.2.6 ESB transforms the xml to TestLink

1. When the input XMI Requirement file is placed in the input path, ESB transforms the xml to TestLink compatible xml file generated in the following output path: /root/EAITools/EA-TestLink/OutputXML

EriACT Manual

122 | P a g e

2. A mail will be automatically triggered and sent to the Test Manager to begin with the testing process. The XML Requirement file will be enclosed as attachment in the mail.

4.2.7 Test Manager creates Test Cases against the new/updated requirements manually

4.3 Development Tracking

Assign a JIRA Development Task to a developer. Project Lead first creates a development task and then assigns the same to a developer. Links the development task to the JIRA functional/non-functional requirement task

4.3.1 Low level task creation in JIRA

A low level task (for instance: design Login page) is created in JIRA against a high level task (for instance: UI designing) created.

Refer to 3.4.5 for detailed process of low level task creation.

4.3.2 Notification in Eclipse

EriACT Manual

123 | P a g e

Once a development task is assigned to a user, he/she will receive notification in the Eclipse installed in his PC

4.3.3 Developer codes in Eclipse or any IDE & Commits in SVN. 1. The assigned user receives a mail notification and then starts coding in IDE

(Eclipse) against the particular task assigned.

EriACT Manual

124 | P a g e

2. After making the relevant changes in the code, the developer commits the changes made in SVN.

3. Right click on the source code a panel will be displayed. From the options displayed in this panel, select Team option and then select the Commit option.

(NOTE: While committing the code in SVN the developer will have to mention JIRA Task ID for the task assigned to him against while he has coded in the Comment

section of SVN Commit.)

EriACT Manual

125 | P a g e

4.3.4 Log Work in JIRA 1. For a sub-task assigned to you, first go the sub-task details page.

EriACT Manual

126 | P a g e

2. Click on the Start Progress tab so that the status of the subtask is converted to In Progress.

3. Click on the More Actions tab so that a dropdown will be generated. 4. Select Log Work option from the dropdown generated.

EriACT Manual

127 | P a g e

5. A popup will be generated where you need to log in the time spent to do the task assigned.

6. The Work Log details are displayed at the right hand corner of the screen.

EriACT Manual

128 | P a g e

4.3.5 Deployment Task Creation in JIRA

A high level Deployment Task is first created in EriPTT. Against that high level task created in EriPTT create a Deployment Task in JIRA.

For Sub task creation refer to 3.4.5

4.3.6 Run Build Plan in Hudson 1. Deployment Manager gets the task assignment email and runs the build plan in

Hudson. 2. Under ‘Source Code Management’ select ‘Subversion’ then write down

Repository URL

3. After that under Build select Invoke Ant then select configured ‘Ant version’ and write down the relative path of builf.xml file in the ‘Build File’ text box.

EriACT Manual

129 | P a g e

EriACT Manual

130 | P a g e

4. Now save the configuration.

EriACT Manual

131 | P a g e

5. Click on the ‘Build Now’ to build the project as shown in the following screen.

EriACT Manual

132 | P a g e

6. After successful deployment of the build in Hudson, Test Manager will get an email (system generated) with the ‘Build No.’

EriACT Manual

133 | P a g e

4.3.7 Test Team Executes Test Plan Against a Build No.

1. Click on the Test Execution tab on the top navigation panel. 2. Click on the Create a New Build link.

3. Create a new Build screen will be generated.

a. Enter a build Title and a Description

EriACT Manual

134 | P a g e

b. Check the checkboxes against Active and Open

c. Select a Release Date for the build.

4. Click on the Create button.

5. A new build is created and is displayed with all the details.

6. Select the build so that the Test Case Execution screen is generated.

7. When the Test Case Execution page is generated select a Build from the drop down box.

EriACT Manual

135 | P a g e

8. If you want to see only a few test cases instead of the whole tree, you can choose which filters to apply. Click the Apply button after you have changed the filters.

9. Click on a test case in the tree menu.

EriACT Manual

136 | P a g e

10. Initially the Result displayed for Test Execution is “Not Run”.

11. There can be three different scenarios:

i. Result selected is “Passed”. After selecting a result click on Save and move to next button

EriACT Manual

137 | P a g e

ii. Result selected is “Failed”. After selecting a result click on Save and move to next button

EriACT Manual

138 | P a g e

iii. Result selected is “Blocked”. After selecting a result click on Save and move to next button

4.4 Test LifeCycle and Defect Management

4.4.1 Test Manager get the requirements in xml format via email sent from ESB

For details refer to Section 4.2.4

EriACT Manual

139 | P a g e

4.4.2 Import of requirement XMLs

1. To import requirement xmls select the Test Suite where you wish to import the requirements.

2. Click on the Import button under the Requirement Operations heading.

3. The Import Requirements section is now generated.

EriACT Manual

140 | P a g e

4. Browse and select then click Upload file.

EriACT Manual

141 | P a g e

4.4.3 Creation of folder for requirements

1. Click on Requirement Specification on the header menu. 2. Select a Test Suite. 3. In the right hand section click on Create button to create a new folder for

requirements.

4. Key in the Document ID, Title, and Scope and also select a type from the dropdown.

EriACT Manual

142 | P a g e

5. Click on the Save button to create the requirement folder.

Creation of sub folders for requirements

1. Click on the Test Suite in the left counterpart of the screen.

EriACT Manual

143 | P a g e

2. In the right hand counterpart of the screen click on the Create button.

3. A number of fields are generated. Fill in the fields with the necessary information. 4. Finally click on the Save button.

5. A new sub-folder- “Design2:Test_Design”- for requirements is created.

EriACT Manual

144 | P a g e

Creation of test suite

1. Select the Test Project from the dropdown list. 2. Click on Test Specification in the top navigation panel.

EriACT Manual

145 | P a g e

3. Select the Test Project in the left hand section.

4. Click on the Create button so that Create Test Suite section is generated.

EriACT Manual

146 | P a g e

4.4.4 Assigning requirements to test cases

1. After selecting the project click on the Assign Requirements link under the Requirement Specifications section.

2. Choose a Test Case in tree at the left.

EriACT Manual

147 | P a g e

3. The combo box with list of Requirements Specifications is shown at the top of the work area.

4. Choose a Requirements Specification Document if more than one is defined. TestLink automatically reloads the page.

5. A middle block of work area lists all requirements (from chosen Specification),

which are connected with the test case. Check the checkbox to mark the requirements which are covered by this test case and then click the button Assign. These new assigned test cases are shown in the middle block Assigned Requirements.

EriACT Manual

148 | P a g e

6. We can unassign it also by clicking Unassign.

EriACT Manual

149 | P a g e

4.5 Defect Management

4.5.1 Mail Notification to Test Manager On successful build in Hudson the build no. will get inserted in the Testlink and also an email will be sent to Test Manager mentioning the build no.

For execution of testing, we need latest build of code. Build number will be automatically populated from Hudson. After build is done, an automatic mail will be sent to test manager to inform him that the build is populated in TestLink and he can test it now.

4.5.2 Login to test link

1. Click on the Testlink link in the EriACT home page. 2. Enter the username and LDAP password

EriACT Manual

150 | P a g e

4.5.3 Creation of Test Plan

1. Click on the Project tab from the navigation header menu. 2. Click on Test Plan Management link in the right hand section under Test Plan.

3. To create a new Test Plan create on the create button.

EriACT Manual

151 | P a g e

4. The Test Plan Management page will be generated.

a. Enter a build Title and a Description

b. Check the checkboxes against Active and Open

c. Select a Release Date for the build.

5. Click on the Create button. 6. A new Test Plan is created and is displayed with all the details.

EriACT Manual

152 | P a g e

7. Click on the Test Specification in the top navigation panel. 8. Select the Test Case which you want to add to a test plan. 9. Click on the Add to Test Plans.

10. The Add Test Case Version To Test Plans section is generated.

EriACT Manual

153 | P a g e

11. Check the checkbox next to the Test Plan that you wish to add to the Test Case. 12. Finally click on the Add button.

EriACT Manual

154 | P a g e

4.5.4 Build

Refer to section 4.3.7

4.5.5 Assign users to test cases

1. To assign test cases to respective testers so that they can start testing click on the Project tab in the top navigation panel.

2. Click on Assign Test Case Execution link.

3. Choose a Test case or Test Suite to test.

EriACT Manual

155 | P a g e

4. Select a planned tester from the dropdown list.

5. Click the 'Save' button to submit assignment.

4.5.6 Test execution by tester

Refer to Section 4.3.7

EriACT Manual

156 | P a g e

4.5.7 Update test results/ Defect Management

1. If the Test Execution Result is “Passed”, then no more action is required for

that test case. 2. If we choose failed, a Bug management icon will appear. Click on it.

3. A popup will be generated.

EriACT Manual

157 | P a g e

4. Alternately click on the link Access to Bug Tracking System (JIRA). 5. In a new window Create Issue (JIRA) will open up.

6. Click on the Next button. 7. The Create Issue page will be generated. 8. Fill in all the mandatory fields and create an Issue.

EriACT Manual

158 | P a g e

9. An Issue is created and a JIRA Requirement Id is generated. (NOTE: The JIRA Requirement Id and JIRA Bug Id are the same)

EriACT Manual

159 | P a g e

10. Enter the JIRA Bug id and click on the Add bug button.

11. The process of mapping the defect between Testlink and JIRA is complete.

EriACT Manual

160 | P a g e

4.5.8 Developer gets a notification of work assignment in eclipse For details refer to section 4.2.4

4.5.9 Developer changes code and commits it to SVN For details refer to section 2.4.4

4.5.10 Resolve Issue in JIRA Once the issue or bug raised is resolved, you need to resolve the issue in JIRA. You need to log work on a daily basis but you can resolve an issue only after it is completed.

1. In the Issue Details page click on the Resolved tab.

2. A popup will be generated. 3. Select a value for the Resolution field from the dropdown.

EriACT Manual

161 | P a g e

4. Provide a Comment and the click on the Resolve button. 5. The Status is now changed to Resolved.

EriACT Manual

162 | P a g e

4.5.11 Close Issue

1. Once the Status is changed to Resolved a new tab Verify is generated.

2. After verifying the process click on the Verify tab so that the Status is converted to Verified.

EriACT Manual

163 | P a g e

3. Once issue is verified, the Closed tab is generated. 4. Click on the Closed tab to close the issue. 5. A popup is generated.

6. Enter a Comment and click on the Closed button.

EriACT Manual

164 | P a g e

7. The Status is changed to Closed.

4.5.12 Reopen issue

1. Once the Status is changed to Resolved you can reopen an issue by clicking on Reopened button.

EriACT Manual

165 | P a g e

2. A popup is generated.

3. Key in a Comment and click on the Reopened button. 4. The Status becomes Reopened.

EriACT Manual

166 | P a g e

5 Project Metrics Reporting

5.1.1 Project Manager Views Project derived KPIs in PTT

1. To view the Project derived KPIs the Project Manager logs in. Click on the Bird’s Eye View tab in the navigation panel.

EriACT Manual

167 | P a g e

2. Key in the details and the click on the Refresh button. The following activities

are performed when the Refresh button is clicked: i. Account & Program tagging with a project to synchronize EriPTT and

EriPro. ii. To add budgets in existing Projects, to update the Planned Effort in

PTT Posting needs to be used. iii. Posting is used to update Team Size. iv. Posting is used to update the Project Status. v. It updates all the project related information in PTT which is changed

in EriPro. vi. "Refresh" is used to fetch data from JIRA as well as to rollup Actual

data from Time Booking / Defect to Task, Phase and Sub-Project level and calculate the KPIs of Task/Phase/Subproject.

3. The Sub-Project KPIs and Phase KPIs will be generated.

EriACT Manual

168 | P a g e

4. To view the details of the Phase KPIs click on the phase whose details you

wish to view.

EriACT Manual

169 | P a g e

5. The Task KPIs will now be generated in tabular form.

6. The JIRA Sub-Task KPIs will now be generated in tabular form.

EriACT Manual

170 | P a g e

7. Click on the Go button at the bottom of the page to view the updated data.

EriACT Manual

171 | P a g e

5.1.2 All the defects and activity effort/schedule details are fetched from JIRA via ESB

1. To view the details of the activity effort click on the JIRA Issue Key link.

2. The JIRA Issues screen will be generated in a new tab.

EriACT Manual

172 | P a g e

3. Similarly for defects details click on the Defect Id link under the Internal Defects section.

4. JIRA Issues (Bugs) screen will be generated in a new tab.

EriACT Manual

173 | P a g e

5.1.3 Project Manager wants to check project Health in EriPro

1. The Project Manager logs into EriPro and then click on the Report tab. 2. Click on the Project Summary so that the following screen will be generated.

EriACT Manual

174 | P a g e

3. To generate a Project Summary Report key in a value in the fields and click

on the View Report button.

4. The Summary Report displays the RAG (Red Amber Green) Status. RAG indicator guidelines for Schedule, Quality and Cost.

EriACT Manual

175 | P a g e

a. Schedule PFB the schedule formula and its impact in ERIPRO screen Schedule for Sub Project = A * Planned Effort * B where, % of Completion of work (A) = [((Actual End date - Actual Start Date) - (Current date - Actual start date)) / (Actual End date - Actual Start Date)]*100 and Schedule Slippage (B) = [(Actual End date - Planned End date) / Planned effort in days] Sub project schedule(S) = [S*8.5/Planned effort(S)]*100 For project [(S1+S2) / Planned Effort (1+2)]*100 red=>5% amber=0<=5% green=<0% Conditions : If no task/phase/subproject are in closed state then no actual end date will come, in such a scenario the system will show a Grey status for that pro-ject. Rest all conditions are same for Red, Amber and Green.

b. Quality

Calculate based on aging of Defects (external)

Red = Age of all Open Critical defects > 7 calendar days OR Age of all Open Major defects > 14 calendar days

Amber = Age of all Open Critical defects > 3 calendar days & <=7 calen-dar days OR Age of all Open Major defects > 7 calendar days & <= 14 calendar days

Green = # Open Critical or Major defects = 0 OR ( Age of all Open Critical defects <= 3 calendar days AND Age of all Open Major defects <= 7 cal-endar days )

EriACT Manual

176 | P a g e

Gray: ((Current Date – Actual Start Date) / (Planned End Date – Planned Start Date))*100 < 10

If project is staff aug then project will be in always gray

c. Cost = [(Actual – Plan) / Plan]*100

Red = >15

Amber = >10 and <=15

Green = <10

Based on above 4 meter the summary report will be displayed.

RAG for Schedule and Delivery Quality would be calculated from values rolled up from PTT. RAG for Cost would be calculated from value from EriPro. RAG for Resource Quality would be based on the responses by the Project Manager

5.1.4 Project metrics data fetch from PTT to EriPro

1. The Project Manager logs into EriPro and then click on the Project tab. 2. Click on the Project Metrics so that the following screen will be generated.

EriACT Manual

177 | P a g e

3. To generate a Project Metrics fill in the Project Name and Sub-Project

ID/Name 4. The Project Information section will now be generated along with the Phase

wise details. 5. Click on the Results link. 6. The expanded view of the Results will be displayed. Click on the Click

Metrics Analysis Report to generate a report

EriACT Manual

178 | P a g e

Note: Metrics data will be populated from PTT for "dev & deployment type”. For PTT based project, actual data will be rolled up from PTT time booking page as well as defect logging page to phase level and for JIRA based project actual data will be rolled up from JIRA to phase level of PTT application. Rest data need to be entered by the user in PTT and all the data will be flowed to EriPro. In EriPro there will be no data entry screen for "dev & deployment type".

6 Project Closure For project closure in EriPro the following process needs to be followed:

1. Log in as DE Team and raise an OTRS ticket to close the project. 2. Then one batch job will run to close the subproject in EriPTT. The batch is

generally run at 12 AM every day. 3. An auto-generated email will be sent to JIRA and Testlink admin to close the

workflow forcefully.

6.1.1 Project closure Audit is done In EriPro To finally close a Project in EriPro all the sub-projects and tasks that have been created for that particular project needs to be closed EriPTT, JIRA etc.

6.1.2 Project Status is changed to Closed in EriPro Finally when the status of a particular project is updated to Closed in EriPTT, JIRA etc the

EriACT Manual

179 | P a g e

status of the project will be updated to Closed in EriPro.

6.1.3 Changed status is updated in PTT via ESB

1. Based on the access permission login and click on the Sub-Project tab in the top navigation.

2. In the left navigation click on Edit Sub-Project.

3. Key in the details and then click on the Search button. 4. The Sub-Project List will be generated.

EriACT Manual

180 | P a g e

5. Click on the Sub-Project link so that the Edit Sub-Project screen will be

generated.

EriACT Manual

181 | P a g e

6. To close the Project click on the dropdown for Status field. Select the Closed option from the dropdown and click on the Update button at the bottom of the screen.

organization functions

Documents

project creation

project type

project closure

sub project

approvereject project

project data flow activities

tanushree ghosh

program creation