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

Version 1 Next »

Target release4.0.0
Epic 
Document statusDRAFT
Document owner

Todd Greenstein

DesignerNitin Motgi
Developers 
QA 

Goals

  • Improve the user experience for the CDAP UI for existing and new users
  • Enable faster ramp-up for new users of the CDAP UI
  • Add additional functionality to the CDAP UI

Background and strategic fit

When logging into CDAP three things need to be immediately apparent:

  • What can I do?
  • What am I currently doing? 
  • What have I completed?   

Improving the CDAP UI will facilitate a more comprehensive user interface that is customizable, will provide faster time to value, and ease friction for adding new capabilities into the system.  

Assumptions

  • The new CDAP UI will likely be written in React
  • The Hydrator and Tracker Extensions will remain in Angular 1.x 
  • The navigational experience, and security 
  • All requirements are deterministic based on security

Requirements

 

#TitleUser StoryImportanceNotes
1(Plus Button)/App StoreAs a CDAP User I want to be able to add new capabilities to the platform from a centralized repository. I want newly added capabilities to include calls for action for fast accessibility.P 0 
2Faceted Search

As a CDAP User I want to be able to search on user and system tags, and filter the results based on additional criteria. Example: Show all runs with failures in the last 12 hours.

P 0 
3Customizable User PerspectiveAs a CDAP User when I've built a search query that I like, I want to be able to bookmark this for repeatable viewing.P 0 
4Create Dataset WorkflowAs a CDAP User I would like a better step by step experience for creating a Dataset, that I can then use elsewhere in the platform. I want to be able to edit this Dataset in the future.  
5Improved Navigation with "fast action Jump"As a CDAP User I want to be able to view entities in the platform as either "card/tile" or in a list format and drill into those entities quickly based on further actions available to those entities.P 0 
6Improved Resource VisibilityAs a CDAP User I would like insights into: Live Info, Container Info, Underlying system info for the platform and be able to navigate to those quickly.P0 
7Artifact ManagementAs a CDAP User I want to be able to manage my artifacts from the UI.  
8Edit MetadataAs a CDAP User I want to be able to update metadata from the UI.  
9Namespace ConfigurationAs a CDAP User I want to be able to configure/map/manage namespaces from the UI.  
10Secured Key ManagementAs a CDAP User I want to be able to manage secure keys from the UI.  

User interaction and design

Mockups are forthcoming

Questions

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

QuestionOutcome
How will we manage state between multiple front end frameworks? 
How will we manage security between multiple front end frameworks? 
What is the "default" view when looking at resources? Tile view/resource center? 
Should a tooltip style tutorial be enabled for "first time" log into CDAP? 

Not Doing

  • Not migrating existing extensions to a new framework
  • No labels