Complete Process Flow and Sample UI

Flow Details

• User Installs the JAS Application from marketplace.

• User navigates to the app screen.

• User adds the admin access token.

• User Configuration flow is started

• User adds the Inputs for explore phase

• Then the user can create the JAS Requirements.

• Then they can split the FIT and GAP requirements

• In the gap requirements we will be filling certain fields based on SAP standard templates

• Based on Functional area we will be creating EPIC

• Based on Functions/app transaction we will be creating the story.

• The requirements coming under these common epic and stories will be created under them

• User provides realization phase inputs

• Background job will run to do some actions post user input

Sample UI Design

1. Authorization Screen

Open

This is the first step of the process, we need these details for authenticating the api’s which we are going to use in the app.

2. Exploration phase

First we will be creating the project, for that the user needs to enter the project name and project key. The project will be created using Scrum project template since we are following sprints.

Sample UI for Start Explore function and getting details from the user

Open

Note: When we are creating the project it will automatically create the schemes, following are the schemes

• Permission Scheme

• Notification Scheme

• Workflow Scheme along with workflow with basic scrum template related status and transitions, this need to be manually edited according to SAP requirement.

• Issue types Scheme, but here since we have api for creating the issue types we will be creating the issue types mentioned in the following template

• Issue type screen scheme

• Screen Schemes

Once the project is created we will be starting the exploration phase by getting the following details from the user.

4. JAS requirements Creation.

• Once the project is created, the users can add the requirements as Jira issues in the created project.

• Once they have completed the process they will be changing the Status to “FIT / Gap“ issues.

• Once that is done, the user come to app screen to Analyze the requirement.

5. Analyze the requirement

• We will have a button in the app screen to start the analysis and to add the SAP related fields in the GAP issues.

The fields are following,

This we will be updating from SAP. Only for GAP issues we will be filling these details.

6. Creating EPIC, STORY and ISSUES

• Based on the common Functional App/Transaction field we will be creating the epics

• Based on common Functional area we will be creating the stories

• The issue will be created under them based on the WRICEF

7. Realization Phase

• Then we will be having a app section for doing the realization process. we will get the required parameters from the user and we will proceed with them.

API Details

Here the user will be editing the workflow which is created when the project is created, so the workflow will have the workflow scheme and it will have issue types associated with them.