Difference between revisions of "Second Life Grid Glossary"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
IEEE-1471 looks slightly heavyweight at first glance, but it isn't in practice because it isn't a straightjacket. Its main benefit is in helping designers of system architecture to embrace the idea that interested parties ('''stakeholders''') each have their own concerns ('''viewpoints''') which need to be described in appropriate architectural '''views'''. An architecture itself is just an abstraction, and it is through the multiple views that this abstraction reveals how it solves the numerous (and frequently orthogonal) requirements. One view definitely doesn't fit all. (See [[Talk:Components_and_Roles|Talk]] for more.) | IEEE-1471 looks slightly heavyweight at first glance, but it isn't in practice because it isn't a straightjacket. Its main benefit is in helping designers of system architecture to embrace the idea that interested parties ('''stakeholders''') each have their own concerns ('''viewpoints''') which need to be described in appropriate architectural '''views'''. An architecture itself is just an abstraction, and it is through the multiple views that this abstraction reveals how it solves the numerous (and frequently orthogonal) requirements. One view definitely doesn't fit all. (See [[Talk:Components_and_Roles|Talk]] for more.) | ||
== | == Terms of discourse == | ||
Words with specific meanings within the project, defined so that discussions can be concise and misunderstandings fewer. | |||
;Agent | ;Agent | ||
: A entity (can be a real person or a bot) interacting with other agents eventually with a region. | : A entity (can be a real person or a bot) interacting with other agents eventually with a region. | ||
; Asset | |||
;Asset | |||
: some entity which can be transferred from agent to agent or from agent to region or from region to agent. It can be something like an object, texture, sound, link, landmark | : some entity which can be transferred from agent to agent or from agent to region or from region to agent. It can be something like an object, texture, sound, link, landmark | ||
: It's basically just a piece of data with a type | : It's basically just a piece of data with a type | ||
| Line 26: | Line 23: | ||
: The representation of an agent in a region (or somewhere else, like on the web) | : The representation of an agent in a region (or somewhere else, like on the web) | ||
; | ;Region | ||
: | : Some space. It can have any form. It can be grouped together with other regions. | ||
; Service | ; Service | ||
: A Web Services invocable resource which performs some task on behalf of a region | : A Web Services invocable resource which performs some task on behalf of a region | ||
; Stakeholder | |||
: Anyone who has a ''technical'' viewpoint that impacts on AWG work on system architecture. | |||
: Non-technical viewpoints exist and have validity, but do not fall within the current scope. | |||
; Utility | ; Utility | ||
: A Service, or collection of services which provides a utility which does not manifest as a region, agent or avatar within the virtual world. | : A Service, or collection of services which provides a utility which does not manifest as a region, agent or avatar within the virtual world. Examples: Currency, Identity, Asset Storage, Messaging, Presence, Topology Management. | ||
: Currency, Identity, Asset Storage, Messaging, Presence, | |||
; Viewer | |||
: A program which (possibly) controls an agent (eventually inside a region) | |||
; Viewpoint | |||
: A set of related concerns about the architecture, and the representations/modeling techniques, etc used to describe the architecture to address those concerns. Examples: Client viewpoint, Functional viewpoint, REST Services viewpoint, Scalability viewpoint, Network viewpoint, Manpower viewpoint. | |||
[[Category:Architecture Working Group]] | [[Category:Architecture Working Group]] | ||
Revision as of 23:48, 11 October 2007
Helping system designers speak a common language
Common understanding is achieved by discussing common mental models using a common language. IEEE-1471 helps considerably:
IEEE-1471 looks slightly heavyweight at first glance, but it isn't in practice because it isn't a straightjacket. Its main benefit is in helping designers of system architecture to embrace the idea that interested parties (stakeholders) each have their own concerns (viewpoints) which need to be described in appropriate architectural views. An architecture itself is just an abstraction, and it is through the multiple views that this abstraction reveals how it solves the numerous (and frequently orthogonal) requirements. One view definitely doesn't fit all. (See Talk for more.)
Terms of discourse
Words with specific meanings within the project, defined so that discussions can be concise and misunderstandings fewer.
- Agent
- A entity (can be a real person or a bot) interacting with other agents eventually with a region.
- Asset
- some entity which can be transferred from agent to agent or from agent to region or from region to agent. It can be something like an object, texture, sound, link, landmark
- It's basically just a piece of data with a type
- Avatar
- The representation of an agent in a region (or somewhere else, like on the web)
- Region
- Some space. It can have any form. It can be grouped together with other regions.
- Service
- A Web Services invocable resource which performs some task on behalf of a region
- Stakeholder
- Anyone who has a technical viewpoint that impacts on AWG work on system architecture.
- Non-technical viewpoints exist and have validity, but do not fall within the current scope.
- Utility
- A Service, or collection of services which provides a utility which does not manifest as a region, agent or avatar within the virtual world. Examples: Currency, Identity, Asset Storage, Messaging, Presence, Topology Management.
- Viewer
- A program which (possibly) controls an agent (eventually inside a region)
- Viewpoint
- A set of related concerns about the architecture, and the representations/modeling techniques, etc used to describe the architecture to address those concerns. Examples: Client viewpoint, Functional viewpoint, REST Services viewpoint, Scalability viewpoint, Network viewpoint, Manpower viewpoint.