Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Design for supplying partner scenario - add diagram for tech committee

Description

Add a diagram into the Requisition Splitting Extension Scenario wiki page to answer these questions:

  • show how is the entire implementation composed using some stock openlmis components and some custom-built components?

  • what git repos are used? in other words, in what "pieces" does this one scenario's extension need to be built?

  • what components are published to Maven or Docker Hub or similar? (identify which live in the public OpenLMIS core project ownership and what might be owned by an implementation team?)

  • what Jenkins jobs and other CI/CD needs to be spun up?

Present this to the Tech Committee and incorporate feedback. This ticket builds off of OLMIS-1234.

Acceptance Criteria

  • scenario now has a diagram (or equivalent) to address the questions above

  • present at tech committee and incorporate feedback/questions

Attachments

2

Confluence content

mentioned on

QAlity Plus - Test Management

Checklists

Activity

Josh Zamor 
December 6, 2016 at 11:48 PM

I updated the wiki with some verbage changes as well as the lucidcharts to update the diagrams.

Otherwise this looks great and I moved it to done. Thanks.

Brandon Bowersox-Johnson 
December 6, 2016 at 6:56 PM
(edited)

I have updated the Extension Scenario wiki page based on feedback from today's tech committee. Please review and let me know if there are any tweaks (or feel free to make direct edits in the wiki or to diagrams).

I've shared the LucidCharts with your VR email address. I'm also attaching the PNG files here.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Components

Sprint

Fix versions

Priority

Parent

Time Assistant

Created November 22, 2016 at 7:07 PM
Updated December 7, 2016 at 12:18 AM
Resolved December 6, 2016 at 11:47 PM