Difference between revisions of "OO Behavioral Model Conceptual Specification"
m (moved Lab Order Conceptual Specification to OO Behavioral Model Conceptual Specification: Incorrectly named at first)
Revision as of 17:43, 12 September 2011
Link back to project page BF Alpha Project
- 1 Executive Summary
- 2 Information Viewpoint
- 3 Solution Specification
- 4 Implemented Patterns
- 5 Contractual Semantics and Issues
- 6 Computational Services
Analysis Information Model
Comment: Provide links to the Analysis Information Model for the domain
The following classes were derived from the storyboards and use cases.
Scenario #1 - Simple Lab Order
Contract Roles and Agents
Contractual Semantics and Issues
Order Request Manager
- Service Description and Purpose
Comment What is the service? Why do we care? Articulation of the Business purpose of the specification Description of the functional capabilities in business terms
Comment Describe the overall potential scope of the service. Are any items being specifically excluded from the scope? Why?
- Reason why the service is necessary
Comment Rationale for creating this specification. Consumer viewpoint and the value offered by the work product
Links to Use Cases/ Storyboards
- (optional, depending on detail in interop business scenario section
Structure of the Service
Comment Elaborate any logical groupings that emerge from the usage scenarios
- Assumptions and Dependencies
Comment Upon what services does this specification depend (underpinning infrastructure, other HL7 services, etc. Are there any key assumptions that are being made?
- Implementation Considerations
Comment Relevant and representative examples of deployment scenarios. Consider representation formalism and the intended audience, not necessarily rigorously expressing the content in UML. This specification in the real world (e.g., relationships to existing infrastructure, other deployed services, dependencies, etc.). Consider the ways that information bindings will be realized through the operations. If necessary, outline a strategy for this binding.
Detailed Functional Model for Each Operation
Conceptual Information Objects
Aspects left for Technical Bindings (optional)
Reference to Functional Profiles (optional)
- Functional Profiles
- Information Profiles