Here are some of the considerations that affect the complexity of developing a particular Life Event that must read from, or write to, an evidence or participant-related data store in Cúram. These considerations should inform any analysis of Life Events development and any resulting estimates.
- Is the Life Event a Standard Life Event or a Round Tripping Life Event
- What information needs to be pre-populated into the IEG2 script?
- What Evidence data is read by the Life Event?
- What Evidence data is updated by the Life Event?
- What non-Evidence data is read/updated by the Life Event
- How many Programs/Case Types will be affected by the Life Event
- If a Life Event shares to multiple Cases, will those case types also share evidence with each other using Evidence Broker?
- Does a Life Event have associated Recommendations? If so, do they relate to Community Services, Government Programs or both?
Of these items dealing with Non-Evidence Entities presents the greatest challenge. Any Life Event that updates non-evidence entities will require developers with Java skills.