1. 1 ECCF Training Computationally Independent Model (CIM) ECCF Training Working Group January 2011

2. 2 Outline Introduction What is a CIM? Artifacts Viewpoints Template Example: Molecular Annotation service Enterprise Viewpoint Information Viewpoint Computational/Behavioral Viewpoint Engineering/Implementation Viewpoint Summary

3. 3 What is a CIM? Computationally Independent Model (CIM) Detailed analysis document that specifies a given business capability Scope is limited to the service(s) being specified CIM development is iterative Artifacts are refined over time Based on artifacts developed during the requirements analysis phase CIM specification contains Service capabilities Traceability to requirements Service information model Service behavioral semantics

4. 4 CIM Artifacts CIM development is an iterative process Artifacts are refined during development

5. 5 RM-ODP Viewpoints for the CIM Enterprise Viewpoint Business objectives Core functional and non-functional requirements Analysis models and service capabilities Constrained domain analysis model (DAM) Information Viewpoint Information model containing the entities used by the service Computational/Behavioral Viewpoint Service capabilities and constraints Interactions with and dependencies on other services Engineering/Implementation Viewpoint Functions required to support the computational components

6. 6 Service Definition Principles Service Specifications: shall be well-defined and clearly scoped shall have well-understood requirements and responsibilities Services: should have a unity of purpose (e.g., fulfilling one domain or area) Note: services themselves may be aggregated will be specified sufficiently to address functional, semantic, and structural interoperability It must be possible to replace one conformant service implementation with another meeting the same service specification while maintaining functionality of the system.

7. 7 NCI CBIIT CIM Template 1.Overview and business case 2.Business storyboards 3.Detailed functional model 4.Profiles 5.System implementation details 6.Conformance and compliance 7.Appendix A: Relevant standards 8.Appendix B: References 9.Appendix C: Glossary 10.Appendix D: Cross reference tables The CIM template is available at

8. 8 Example: Molecular Annotation (MA) Service The Molecular Annotation (MA) service will be used to illustrate CIM, PIM, and PSM specifications in this training Purpose: Capabilities to retrieve molecular annotations that may be integrated with user-facing applications Information associated with genes Biological functions and classifications Genetic variants Physical location Associated diseases and agents The MA CIM is available at

9. 9 Outline Introduction Enterprise Viewpoint Scope, vision, and business objectives Use cases and storyboards Process analysis model Information model Business policies and rules Other functional and nonfunctional requirements Information Viewpoint Computational/Behavioral Viewpoint Engineering/Implementation Viewpoint Summary

10. 10 Enterprise Viewpoint Artifacts Scope, vision, and business objectives Use cases and storyboards Process analysis model Information model Business policies and rules Other functional and nonfunctional requirements

11. 11 Scope, vision, and business objectives The business objective can be captured using the ODP concept of community contract, expressing a joint agreement between key stakeholders involved in using an e-health system in improving health care delivery. The stakeholders are modeled as roles in the community. The expression of community is at a fairly high level, essentially defining a business context (scope) from which more detailed organizational, informational, and behavioral relationships (at the CIM level) will be defined. Note that this community contract can cover relationships between stakeholders that are important for defining business context, but which go beyond concerns of their direct interaction with the e- health system. This kind of relationship is relevant when expressing a storyboard in a more structured way. how doc'd (template, incl mapping to template section 1.1-1.3)

12. 12 Scope, vision, and business objectives Example: MA Service

13. 13 Use cases and storyboards what is it (eccf ig) how doc'd (template, incl mapping to template section 2)

14. 14 Use cases and storyboards Example: MA Service

15. 15 Process analysis model what is it (eccf ig) how doc'd (template, incl mapping to template section) see def in table 2.3.1.2 – why not in behav or comp VP?

16. 16 Process analysis model Example: MA Service

17. 17 Information model what is it (eccf ig) how doc'd (template, incl mapping to template section) see def in table 2.3.1.2 – why not in info VP?

18. 18 Information model Example: MA Service

19. 19 Business policies and rules what is it (eccf ig) how doc'd (template, incl mapping to template section) where map into template?

20. 20 Business policies and rules Example: MA Service

21. 21 Other functional and nonfunctional requirements what is it (eccf ig) how doc'd (template, incl mapping to template section) where map into template?

22. 22 Other functional and nonfunctional requirements Example: MA Service

23. 23 Enterprise Viewpoint Exercise: Patient Outcomes Data Service include example from Patient Outcomes Data Service

24. 24 Outline Introduction Enterprise Viewpoint Information Viewpoint Domain Information Model (DIM) Dynamic Schema Invariant Schema Computational/Behavioral Viewpoint Engineering/Implementation Viewpoint Summary

25. 25 Domain Information Model (DIM) what is it (eccf ig) how doc'd (template, incl mapping to template section)

26. 26 Domain Information Model (DIM) Example: MA Service

27. 27 Dynamic Schema what is it (eccf ig) how doc'd (template, incl mapping to template section)

28. 28 Dynamic Schema Example: MA Service

29. 29 Invariant Schema what is it (eccf ig) how doc'd (template, incl mapping to template section)

30. 30 Invariant Schema Example: MA Service

31. 31 Information Viewpoint Exercise: Patient Outcomes Data Service include example from Patient Outcomes Data Service

32. 32 Outline Introduction Enterprise Viewpoint Information Viewpoint Computational/Behavioral Viewpoint Roles Functional Profile Capabilities Engineering/Implementation Viewpoint Summary

33. 33 Roles what is it (eccf ig) how doc'd (template, incl mapping to template section)

34. 34 Roles Example: MA Service

35. 35 Functional Profile what is it (eccf ig) how doc'd (template, incl mapping to template section)

36. 36 Functional Profile Example: MA Service

37. 37 Capabilities what is it (eccf ig) how doc'd (template, incl mapping to template section)

38. 38 Capabilities Example: MA Service

39. 39 Computational/Behavioral Viewpoint Exercise: Patient Outcomes Data Service include example from Patient Outcomes Data Service

40. 40 Outline Introduction Enterprise Viewpoint Information Viewpoint Computational/Behavioral Viewpoint Engineering/Implementation Viewpoint Inventory of software platforms and environments Deployment/architecture requirements and constraints Reference to enterprise architecture patterns Summary

41. 41 Inventory of platforms what is it (eccf ig) how doc'd (template, incl mapping to template section)

42. 42 Inventory of platforms Example: MA Service

43. 43 Deployment requirements what is it (eccf ig) how doc'd (template, incl mapping to template section)

44. 44 Deployment requirements Example: MA Service

45. 45 EA Patterns what is it (eccf ig) how doc'd (template, incl mapping to template section)

46. 46 EA Patterns Example: MA Service

47. 47 Engineering/Implementation Viewpoint Exercise: Patient Outcomes Data Service include example from Patient Outcomes Data Service

48. 48 Outline Introduction Enterprise Viewpoint Information Viewpoint Computational/Behavioral Viewpoint Engineering/Implementation Viewpoint Summary

49. 49 Summary of Artifacts list of artifacts for the CIM Not all artifacts are required for every service Determined by the scope of the service specification

50. 50 References NCI SAIF IG NCI CBIIT SAIF Best Practices, Policies, and Patterns NCI Enterprise Service (NES) Specification