Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Target releaseCasablanca
Epic
Document status
DRAFT
Document owner

Srinivasa Vellanki

Designer
Developers
QA

Goals

  • Enable Designers(Service Designer, VNF Owner or TechOps) to be able to Manage Workflows

Background and strategic fit



Assumptions

  • .

Requirements

#TitleUser StoryImportanceNotes
1Create a Workflow

As a Designer I want to be able to create a Workflow

Specify

  1. Name
  2. Description
  3. Input and Output Parameters (basic data-types)
  4. Workflow
Must Have


2Search Workflow

As a Designer I want to be able to search Workflows based on Name.

Must Have  
3List Workflows As a Designer I want to be able to see list of workflows, filter them along with and similar to other SDC entities like VF and Service in Catalog and Home Must Have  
4View Workflow

As a Designer I want to be able to view Workflow details like Name, Inputs, Outputs and the workflow

Must Have  
5Edit Workflow Definition

As a Designer I want to be able to create a new major version of the workflow and modify Name of the workflow, Input and Output Parameters (basic data-types) and the workflow.

Must Have  
6Edit Workflow Implementation

As a Designer I want to be able to create a new minor version of the workflow and modify the workflow.

Workflow Definition cannot be edited as part of Workflow minor version

  1. Name
  2. Description
  3. Inputs and Outputs
Must Have  
7Copy(Save As) WorkflowAs a Designer I want to be able to copy a workflow and save with a different Name. i.e., create a new workflow based on the data from an existing workflowNice to Have  
8Certify Workflow 

As a Designer I want to be able to certify a workflow for completeness.

  1. No broken ends
  2. More
Must Have  
9Distribute WorkflowAs a User (role configurable) I want to be able to distribute a workflowMust Have  
10Search Workflow API API to search workflows Must Have  
11Get Workflow API 

API to fetch workflow details like

  1. Name
  2. Description
  3. Inputs and Outputs
  4. Workflow Artifact Reference
Must Have  
12 Sub-FlowsAs a Designer I should be able to use a workflow as a sub-processNice to Have  

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome
Do we need to support categorization of workflows?
  

Not Doing

  • No labels