1 / 9

Caroline Doust

Natural Cúram. Caroline Doust. Enterprise Architecture. Introduction. Knowledge is power. Purpose Natural Cúram

vidar
Download Presentation

Caroline Doust

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Natural Cúram Caroline Doust Enterprise Architecture

  2. Introduction Knowledge is power Purpose Natural Cúram When installing and customising Cúram there are things that make the process smooth and things that go against the grain and stop us gaining the benefits of the Cúram application. The former we refer to as Natural Cúram Natural Cúram

  3. Introduction Knowledge is power • The two components of Natural Curam • Implementing Cúram according to the generic business processes it naturally supports. • Implementing parts of Cúram’s functionality in ways that do not violate its architectural principles. • The first form is stronger and is discussed first. Natural Cúram

  4. Two Forms of Natural Knowledge is power • Strong Natural Cúram • We can implement Cúram functionality for: • particular functional modules or • we can implement Cúram for particular product delivery life cycles. • Both approaches are suitable for differing parts of the architecture. E.g. it makes sense to implement component functionality for Ministry master data such as client and provider and services. It makes sense to implement Cúram via particular product delivery life cycles for activity based functionality. E.g. unemployment and supplementary benefits or Case Investigation Management. Natural Cúram

  5. Two Forms of Natural Knowledge is power • Weak Natural Cúram • The weaker form of natural Cúram is implementation of Cúram functionality according to its architectural principles but outside of the context of Cúram’s own business processes. • Such an implementation is natural when the following are preserved: • The stateless application architecture. • The thin client architecture. • The Cúram standard navigation menus. • The Cúram defined relationships between business entities. • Entities are not created for data that can be stored in Cúram entities. I.e. Cúram capabilities are fully understood for the whole project scope before new entities are introduced. Natural Cúram

  6. Two Forms of Natural Knowledge is power Weak Natural Cúram The Downside Although such an implementation is natural in this weaker sense it still may not achieve significant business savings. It is at best an opportunistic way to get some Cúram functionality implemented. It should nevertheless be the absolute minimum for Cúram functionality implementation. The digitisation project would be the first example of this weaker form of natural Cúram. Previous projects did not meet even this standard. Natural Cúram

  7. Two Forms of Natural Knowledge is power Strong Natural Cúram The Downside It requires up front planning and programme management. We have to look at what Cúram can do for the organisation as a whole and divide its implementation into programmes of work that implement cohesive parts of Cúram functionality. We need an end-state Cúram architecture. It may require projects that don’t have a positive NPV within a programme that does. E.g Core Client. Natural Cúram

  8. Two Forms of Natural • Strong Natural Cúram • The Upside • If we plan our whole of Cúram implementation based on an end-state architecture: • We can implement Cúram in a most cost effective manner based on Programme based NPV rather than project based NPV’s. • We can implement for cross service functionality sharing and common business rules. E.g. Whatever channel the client uses they get the same consistent approach to eligibility and entitlement. • We can organise our MDM through the Cúram implementation. • We can influence Cúram Software to develop software to meet our future requirements before we come to create a solution for them ourselves. Knowledge is power Natural Cúram

  9. Methodology • Methodology • Cúram is a highly customisable solution framework that provides out of the box a generic set of business processes for running a typical Social Enterprise Organisation along with standardised customisation points around products, services, eligibility and entitlement. . • As such it requires a different style of application development process: • Upfront analysis is needed to identify Cúram functionality within the initial scope. This may modify the initial implementation scope by identifying natural scope reductions in some areas and extensions in others. • Detailed requirements are determined by a tension between necessary business process change and OOTB functionality. They cannot be specified without an understanding of Cúram’s capabilities and style of operation. • EPIC is a modified RUP process that seems to incorporate these considerations. Knowledge is power Natural Cúram

More Related