OO Behavioral Model Conceptual Specification

Link back to project page BF Alpha Project

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.

Computational Services

Order Request Manager

Overview

• 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

• Scope

  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

• Organization
• Assumptions and Dependencies
• Implementation Considerations

<Note – at the conceptual level, you may still have high level implementation issues to consider – eg what portions of a service a Responsible Party may wish to support; considerations around a variety of commissioning agents, etc>

Detailed Functional Model for Each Operation

Name

Description

Pre-Conditions

Conceptual Information Objects

Inputs

Outputs

Post-Conditions

Exception Conditions

Aspects left for Technical Bindings (optional)

Reference to Functional Profiles (optional)

Notes

Profiles

• Introduction
• Functional Profiles
• Information Profiles