Hi Jem, I have added my suggestions for modifications to proposed definitions. Would you be able to include the mods as one input for the Wed discussion? For data federation, I added 'logical integration' I think the word 'contract' for a use case sounds rather too severe :-). My experience seem to suggest that a use case also has environment, goals etc. Please see below for modifications/additions. Ravi a. Data Federation: The logical integration of multiple services or data resources so that they can be accessed as if they were a single service. b. Use case: A use case captures all interactions of an agent or entity with a system and/or its constituents and the expected behavior of the parties as a consequence where such interactions are directed towards and relevant to achieving/meeting a specific explicit goal. Such a capture could also include the environment, context and modes salient to that interaction. c. Scenario: A scenario is a specific sequence or path of interactions from initiation to goal occurring within a particular environment and/or context and defined by a particular mode of usage. A use case may contain multiple scenarios. d. Mode: is a particular functioning condition or arrangement. -----Original Message----- From: owner-ogsa-wg@ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Treadwell, Jem Sent: Tuesday, February 07, 2006 8:28 AM To: ogsa-wg Subject: [ogsa-wg] Glossary definitions for discussion on Wednesday's telecon Hi, the three definitions below are the last that are planned for the OGSA Glossary v1.5, and will be discussed on Wednesday's call. Thanks to Andreas for providing the use case and scenario definitions, and to the OGSA-D team for data federation. Please let me know if you have any comments. Thanks, - Jem Data federation: The integration of multiple services or data resources so that they can be accessed as if they were a single service. Use case: A use case captures a contract between the stakeholders of a system about its behavior. Different sequences of behavior, or scenarios, can unfold, depending on the particular requests made and conditions surrounding the requests. The use case collects together those different scenarios. OGSA use cases are high-level and described in a casual style. They are not at the level of detail required for a formal requirements analysis but are meant to provide sufficient detail to inform the architectural definition process. Source: "Writing Effective Use Cases," Alistair Cockburn, Addison-Wesley Professional; 1st edition (January 15, 2000) Scenario: A use case scenario contains a sequence of steps showing how their actions and interactions unfold. OGSA scenarios are high-level and described in a casual style. See also use case. Source: "Writing Effective Use Cases," Alistair Cockburn, Addison-Wesley Professional; 1st edition (January 15, 2000) ________________________________ Jem Treadwell Hewlett-Packard Company 6000 Irwin Road Mount Laurel, NJ 08054 Phone: 856-638-6021 Fax: 856-638-6190 E-mail: Jem.Treadwell@hp.com