Personas / Actorshttps://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#architect

Architect

A technical lead for the migration project that can create and modify applications and information related to it.

Project Manager

New persona to create in Konveyor with this enhancement. A management lead for the migration project that can create and modify migration waves and assign applications to them but can only assign an owner and contributors to an application in the application inventory.

User Stories

Application owner and contributors

• As an Architect or a Project Manager I want to be able to associate a stakeholder to an application as its owner
• As an Architect or a Project Manager I want to be able to associate stakeholders to an application as contributors

Migration Waves Management

• As a Project Manager I want to be able to manage (create, edit, update, delete) migration waves
• As a Project Manager I want to assign start and end dates to migration waves
• As a Project Manager I want to assign stakeholders and stakeholder groups to migration waves
• As a Project Manager I want to assign applications to migration waves

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#migration-waves-searchability

Migration Waves Searchability

• As an Architect, Migrator or Project Manager I want to be able to search applications based on the Migration Wave they were assigned to

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#functional-specification

Functional Specification

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#updates-in-the-application-creation-view

Updates in the Application Creation view

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#related-use-cases

Related Use Cases

• AOC001
• AOC002

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#involved-personas

Involved Personas

• Architect

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#description

Description

The application creation view will include two new fields:

• Owner: Dropdown, single selection. The dropdown will include all available Stakeholders in the system. It would be good to make it searchable to avoid loading all stakeholders at once.

• Contributors: Dropdown, multiple selection. The dropdown will include all available Stakeholders in the system. It would be good to make it searchable to avoid loading all stakeholders at once.

 

Since the architect role is the only one allowed to create applications, Project Managers won't be able to access this view.

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#updates-in-the-application-edition-view

Updates in the Application Edition view

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#related-use-cases-1

Related Use Cases

• AOC001
• AOC002

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#involved-personas-1

Involved Personas

• Architect
• Project Manager

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#description-1

Description

The application creation view will include two new fields:

• Owner: Dropdown, single selection. The dropdown will include all available Stakeholders in the system. It would be good to make it searchable to avoid loading all stakeholders at once.

• Contributors: Dropdown, multiple selection. The dropdown will include all available Stakeholders in the system. It would be good to make it searchable to avoid loading all stakeholders at once.

 

It is important to note that Project Managers should only be able to edit the Owner and Contributor fields, and the rest of the fields should appear disabled. Architects will have full access.

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#migration-waves-management-1

Migration Waves Management

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#related-use-cases-2

Related Use Cases

• MWM001
• MWM002
• MWM003
• MWM004

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#involved-personas-2

Involved Personas

• Project Manager

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#description-2

Description

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#migration-waves-main-view

Migration Waves main view

A new option "Migration Waves" will be included in the left menu for the Developer Perspective. Clicking on it will navigate to the main view for Migration Waves. The view will revolve around compound expandable table with the following fields and sections per row:

• Name: Name of the migration wave. This field is optional and could appear empty.
• Start date: Start date for the migration wave.
• End date: End date for the migration wave.
• Application: Compound expandable section with a nested table that includes the list of applications assigned to the migration wave. Each row will have trashcan icon to remove the application belonging to the row from the list of assigned applications to the migration wave. Each row will include the following fields from the application:
  • Application name
  • Description
  • Business service
  • Owner

 

• Stakeholders: Compound expandable section with a nested table that includes the list of stakeholders associated with a migration wave. This list will be automatically populated with all the owners and contributors to all the applications assigned to the migration wave, and with any additional stakeholders that could have been associated directly to the migration wave on creation/edition or indirectly through the association of a determined stakeholder group. Just to clarify, if a stakeholder group is associated to a migration wave on creation/edition, all of its members will appear in this list. Each row will include the following fields:

• • Name
  • Job Function
  • Role: Owner, Contributor or empty if the stakeholder was associated directly or through a stakeholder group.
  • Email
  • Stakeholder groups: Groups the stakeholder belongs to.

 

• Status: Compound expandable section for the migration waves to reflect status data. This section is explained in depth in the related tackle-jira-integration enhancement. This section will only be displayed if there is at least one Issue Manager configured in the Konveyor instance

 

The different compound expandable sections can only be expanded when the value on the section is greater than zero:

 

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#create-new-waves

Create new waves

New migration waves can be created by clicking on the button "Create new" at the top section of the Migration Waves view. This will open a modal view with the following fields:

• Name: Optional. String with the name of the wave.
• Start date: Mandatory. Date picker.
• End date: Mandatory. Date picker.
• Stakeholders: Optional. Dropdown, multiple selection. Values will be the list of available stakeholders in the instance. Stakeholders to associate directly to the migration wave. When an application is assigned to a migration wave, all of its associated stakeholders get transitively associated to the wave. By associating them directly through this field, they will appear with no role in the Stakeholders compound expandable section, unless they are transitively associated by an application, in which case the role will be displayed.
• Stakeholder Groups: Optional. Dropdown, multiple selection. Values will be the list of available stakeholder groups in the instance. Stakeholder groups to associate directly to the migration wave. By associating a Stakeholder Group to a migration wave through this field, all the associated stakeholders in the group will appear with no role in the Stakeholders compound expandable section, unless they are transitively associated by an application, in which case the role will be displayed.

 

There are some considerations regarding the Start date and End date fields. First, the Start date date picker field won't show any dates in the past, as it makes no sense to create new migration waves happening before the present day. First day to be displayed, will be the present day, highlighted in light blue:

 

The End date date picker field will show the start date day that was picked and will leave a light blue highlight between that and the selected end date day.

 

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#edit-waves

Edit waves

Migration waves can be edited by clicking on the "Edit wave" option available in the kebab menu for each migration wave row in the main table from the Migration Waves view. Clicking on the button will open a view with the same fields as the migration waves creation view:

 

The "Stakeholders" field will only display the stakeholders that were associated directly to the migration wave, and won't include the transitive association of stakeholders coming from assigned applications. The same applies for the "Stakeholder groups" field.

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#manage-applications

Manage applications

The assignment of applications to migration waves will be managed as an option in the Migration Waves view. This option will be called "Manage Applications" and will be included in the kebab menu available in each migration wave row:

 

Clicking in the option will open a modal window with a table displaying all applications that haven't been previously assigned to another migration wave. This table should include the same filters available in the Application Inventory view except the "Migration waves" one:

 

The "Selected wave" field on top won't be modifiable and will only display the name or the range for the selected wave in case it doesn't have a name. As in the "Applications" compound expandable session from the main table in the Migration Waves view, the table will display the following fields on each application row:

• Application name
• Description
• Business service
• Owner

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#updates-in-the-application-inventory-view

Updates in the Application Inventory View

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#related-use-cases-3

Related Use Cases

• MWS001

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#involved-personas-3

Involved Personas

• Architect
• Migrator
• Project Manager

https://github.com/rromannissen/enhancements/blob/32748c4d184e6e9eac26b15ed66ba3382c6be666/enhancements/migration-waves/README.md#description-3

Description

The Application Inventory view should include an additional filter "Migration Waves". Values for the filter should be the available Migration Waves in the system and "Unassigned" for those applications that haven't been assigned to a Migration Wave yet.

Also, the expandable section for each application will include information about the assigned Migration Wave, if any:

 

This field should be visible in both the Assessment and Analysis tabs.