This wiki is archived and useful information is being migrated to the main bzflag.org website

Difference between revisions of "Group management system functional requirements"

From BZFlagWiki
Jump to: navigation, search
Line 12: Line 12:
 
This overview shows the use cases able to be completed by each actor. It describes which types of actors will be able to carry out specific tasks or objectives supported by the system.
 
This overview shows the use cases able to be completed by each actor. It describes which types of actors will be able to carry out specific tasks or objectives supported by the system.
 
[[Image:Use_Cases_Overview.png|Use cases]]
 
[[Image:Use_Cases_Overview.png|Use cases]]
 +
 +
 +
== Use Cases ==
 +
Use Cases describe the functional requirements of the system from the end users perspective, where each use case is a goal or purpose the user has in using the system.
 +
 +
1. [[Register Group Namespace]]

Revision as of 08:21, 4 April 2011

Picture Frame.png This page contains the design document for an enhancement or feature. It is a work of collaborative development, and may not represent the final design. If you are not part of the development or design group, please post comments and suggestions on the talk page and not in the middle of the design.

The functional requirements for the Group Management System will be detailed in the following sections with Use Cases and other UML models.


Actors

An actor is a representation of a role performed when interacting with the system.

Description of actors of the group management system


Use Case Overview

This overview shows the use cases able to be completed by each actor. It describes which types of actors will be able to carry out specific tasks or objectives supported by the system. Use cases


Use Cases

Use Cases describe the functional requirements of the system from the end users perspective, where each use case is a goal or purpose the user has in using the system.

1. Register Group Namespace