Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Requirement
Requirement [+]
Title | Service functionality |
Identifier | SWIM-SERV-012 |
Requirement | A service description shall describe the functionality of the service as a list of functions and their associated real world effects. |
Rationale | The functions provide business and operational experts with a business view of the interactions with the service, without having to look at the interface details. |
Verification | Completeness: Verify that the elements are included. Consistency: Verify that the functions and real world effects are consistent with the operational needs. Correctness: Not Applicable. |
Examples/Notes | Note: A function is a type of activity describing the functionality of a service. Every function usually (but not always) can be mapped to service operations defined as a part of the service’s interface; i.e., functions provide a “business view” and service operations provide a “technical view” of a particular service activity. Note: A real world effect is an ultimate purpose associated with the interaction with the service. It may be the response to a request for information or the change in the state of some entities shared between the participants in the interaction. Example functions and real world effects: function | real world effect |
---|
Retrieve a list of flights | (Network Information sharing) | Retrieve information of a single flight | (Network Information sharing) | Provide Departure Planning Information (DPI) | NM systems updated with the information; NM systems publish the resulting flight update |
|
Level of Implementation | Mandatory |
Guidance
Examples
See the Service Functionality section within the Donlon TOBT Setting Service Description.