Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • PUBLISHING a model - adding a TAG
    • need to document workaround - the only place to add a tag is from the publishing page; DO NOT HIT ENTER in the Model tags field. Type your tag if it is not in the list and then click someplace else on the UI; you should see a "tag added" notification

  • SESSION TIMEOUT (IST2) - right in the middle of an action, Please sign in pop up
  • WEB-ONBOARDING (IST2) - notification bell icon does not update when on-boarding fails; tried to onboard from the DS wiki page, dockerize step failed but notification bell icon never updated to indicate a new message
    • when Onboarding fails at the Dockerize step, the addition of the model is not rolled back (ie, model it not deleted), so the "error" model is displayed in MY UNPUBLISHED MODELS but the user can't do anything about it
  • MY MODELS - tiled view doesn't fill up space so user has to "See All" to see the rest of the models
  • Image Added
  • number of models displayed must be based on the "list" view  - still an enormous waste of screen real estate
  • Image Added

Other Issues

  • Design Studio requires installer/operator/Admin to onboard and publish DS Toolkit Models; models stored on DS wiki
  • Testing
    • Nobody from the "business" side (stakeholders) is writing UAT cases and doing UAT
    • Not all the requirements are in Jira user stories so the test team is not able to fully test functionality
    • installed instances act differently; need a definable, repeatable procedure to ensure standardization across test instances
      • Solution: Ken is working on the scripts and Ken/Bobbie the guide
    • Jira needs to be modified so test cases can be created under use stories; also need test management plugin so traceability matrix can be done inside Jira
      • Ken asked Akash? to look into this
  • Docs
    • Portal user guide is not being updated by Portal team when new functionality is added or existing is changed
    • Severe lack of explanation on what UI fields mean; for example: 
      • Deploy to Cloud databrokers area
      • Marketplace - Sort By - what the difference between Created Date, Recent, and Older because each displays a different sort order; plus what do Highest Reach and Lowest Reach choices mean?
    • Suggested solution:  each use story that impacts end user functionality must have a documentation task that is completed at the same time the code is committed; the test and docs team will verify the documentation and open a bug if it's missing or incomplete
  • Release process
    • not all components were promoted to  release
    • Solution:  update the PTL guide to include release activities so PTLs know they are responsible for promoting their components to the release nexus.
  • Test reports/weekly build release notes
    • they never listed what versions of the onboarding clients (Java, Python, R) were being used (ie, certified to work with platform version xxx), nor did they list *all* the libraries/versions (only the ones deployed as images that dont't need to be started.. but never, for example, the version of the common data services client or the nexus client, which are imported as libraries in the java source code...).
    • Solution: working with Ken/Sai and testing team to include this info this going forward
  • UI changes need to signed off to prevent churn from stakeholders
    • Major UI functionality, like the search - the need to have comprehensive requirements and design, and have them signed off by the stakeholders prior to implementation. OpenStack has the concept of a blueprint. Acumos could have a separate "blueprint" repo. Requirements/Design docs would be created in RST and along with supporting design images (both source and exported PNG**) pushed to gerrit like any other patch. Stakeholders and PTLs would have to review the blueprint in gerrit (great way to track comments) and +1 would indicate sign-off. Then the jira ticket would reference the requirement/design doc in the repo (no ppt decks or word docs attached to jira epics and user stories). 
      • ** can be used to create the diagrams. tspace incorporated it a while ago. the acumos wiki has the plugin. also there is a desktop version for mac, windows, linux