This wiki has undergone a migration to Confluence found Here
Difference between revisions of "OO Behavioral Model Conceptual Specification"
Jump to navigation
Jump to search
| Line 54: | Line 54: | ||
Comment: | Comment: | ||
Describe any dependencies of the process being specified | Describe any dependencies of the process being specified | ||
| + | |||
| + | The parties supporting this process are the Order Request Manager and Fulfillment Manager, depicted below | ||
| + | |||
| + | [[image:OrderRequestManagmentConceptual.png]] [[image:FulfillmentManagementConceptual.png]] | ||
=Implemented Patterns= | =Implemented Patterns= | ||
Revision as of 20:16, 14 September 2011
Link back to project page BF Alpha Project
Contents
Executive Summary
Information Viewpoint
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.
Solution Specification
Scenario #1 - Simple Lab Order
Overview
Business Scenario
The event flow for a simple lab order is shown below
Contract Roles and Agents
The commissioning and responsible parties involved in this process include:
| Specification Reference | Commissioning System Role | Responsible System Role | Operation |
|---|---|---|---|
| Order Requestor (Placer in v2) | Order Request Manager | createRequest | |
| Order Request Manager | Fulfillment Manager | createRequest | |
| add | add | add |
Computational Viewpoint
The following sequence diagram depicts the interactions that support the above event flow
Service Dependencies
Comment: Describe any dependencies of the process being specified
The parties supporting this process are the Order Request Manager and Fulfillment Manager, depicted below
Implemented Patterns
Comment: Indicate the any patterns that apply to this process specification
