Difference between revisions of "AWG Use Cases"

From Second Life Wiki
Jump to navigation Jump to search
(added some identity related use cases)
(added agent related use cases)
Line 40: Line 40:


=== Agent related Use Cases ===
=== Agent related Use Cases ===
==== Administrative Use Cases ====
* User creates a new agent
* User deletes an agent
* User edits an agent profile
==== Information Use Cases ====
* User retrieves profile information about an agent
* User retrieves identity information about an agent (age, RL info, what about permissions here?)
==== Basic Use Cases ====
* Agent logs in
* Agent logs out
==== Inventory Use Cases ====
* return inventory for an agent
* store inventory for an agent
* manage inventory (update, move, sort ...)


=== Region related Use Cases ===
=== Region related Use Cases ===

Revision as of 13:54, 16 September 2007

This page will hold all sorts of use cases and should be some brainstorming place. Please add use cases in the form "<Role> <Action>" like "User logs in". If it's a requirement such as "The system needs to support OpenID" write it like that. For now we should aim at one-line descriptions for an overview. For more detailed explanations make the use case a link and explain it there.

Use Cases of the existing system should be marked with an (*) for now.


Some possible futuristic scenarios

(add here what scenarios are completely different but maybe should still be possible with this new architecture. This is mainly to get our thinking broader. These can also be described by some bullet points and from these we should later on construct use cases).

EVE Online like setup

  • regions are solar systems
  • avatars do not (yet) exist and agents are represented by space ships (some sort of avatar)
  • objects are planets, space stations, asteroids, etc.
  • regions are connected by portals
  • regions do not have a predefined size
  • objects on regions are mostly fixed
  • most of the transactions will be from agents to agents (might be bots)

Google Earth like setup

  • There are layers of objects/information on one defined region (=earth)
  • A viewer can decide which layers to load/show
  • Agents do not necessarily be represented in a region
  • one could think of these layers as layered regions maybe


Use Case Capturing

We use the defined Roles and Components. "User" refers to an so far undefined entity. This might be some web service client querying for data.

Identity related Use Cases

  • User creates a new identity
  • User updated identity
  • User deletes identity
  • User retrieves identity information
  • User adds a verification method to an identity (age, real name, financial, part of a company, ...)


Agent related Use Cases

Administrative Use Cases

  • User creates a new agent
  • User deletes an agent
  • User edits an agent profile

Information Use Cases

  • User retrieves profile information about an agent
  • User retrieves identity information about an agent (age, RL info, what about permissions here?)

Basic Use Cases

  • Agent logs in
  • Agent logs out

Inventory Use Cases

  • return inventory for an agent
  • store inventory for an agent
  • manage inventory (update, move, sort ...)

Region related Use Cases

Viewer related Use Cases