Skip to:

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

Create shipment domain

Description

As a system administrator, I need OpenLMIS to create a Shipment Domain for all the shipment file instructions to be stored so that I can call shipment data for the POD, R&R, and other processes.

This appears to be more of a design ticket. Look at v2 (however much is implemented there) to recreate the functionality, but we don't want to copy the design there, but design in a OO way.

If there is no functionality in v2, we'll need to find that high-level diagram of how shipments should work.

Acceptance Criteria

  • Creation of activity diagram of how shipment data is retrieved from ERP and stored in OpenLMIS

  • Creation of class diagram of shipment domain (should at least have a shipment domain object showing its properties AND behavior)

Attachments

1

relates to

QAlity Plus - Test Management

Checklists

Activity

Show:

Łukasz Lewczyński January 10, 2017 at 8:15 AM
Edited

It is not problem to 'pause' work on this ticket. I created only one diagram and today I wanted to start work on another (class diagram). Here is the link to the activity diagram: https://review.openlmis.org/cru/FEOLMIS-808. Also I added it to this ticket in case the link will be broken.

Brandon Bowersox-Johnson January 9, 2017 at 6:45 PM

Hi , it appears we had a misunderstanding about this ticket and OLMIS-1370. We didn't put these tickets on the Backlog page because these tickets aren't a high priority for version 3.0. We didn't want you to put these in the sprint and start work on these. So we are hoping you can "pause" work on this ticket, remove it from the sprint, and move on to the next priorities. I'll also send an email in case we need to talk about what the other priorities are.

I also just noticed that these tickets were marked as blockers for OLMIS-1555, but they do not actually block it (they are just related), so I changed it to related.

Chongsun Ahn December 16, 2016 at 11:14 PM

If that is the case, and there are no detailed activity and class diagrams for shipments, then I think part of the acceptance criteria for this ticket should be creating those diagrams. Then this should be one of the first things to work on for this epic.

Mary Jo Kochendorfer December 16, 2016 at 11:11 PM

Could be. The separation of these tickets came from the estimation exercise. There was a diagram drawn and made in Gliffy (which I cannot open) at the epic level.

Chongsun Ahn December 16, 2016 at 10:58 PM

This ticket seems more like "let's do the other tickets in this epic in a way to design the shipment domain in an object-oriented way".

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

Details

Assignee

Reporter

Labels

Story Points

Original estimate

Time tracking

3h 30m logged3d 4h 30m remaining

Components

Priority

Parent

Time Assistant

Created August 31, 2016 at 6:01 PM
Updated February 8, 2023 at 1:30 PM