This wiki was in read-only mode for many years, but can now be edited again. A lot of information will need to be updated.
Register Group Namespace: Difference between revisions
Grans Remedy (talk | contribs) New page: {{DesignDocument}} == Register Group Namespace == The purpose of this use case is to describe the process used to register (create) a new group namespace (organisation). |
category link |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{Specification}} | ||
== | == Introduction == | ||
The purpose of this use case is to describe the process used to register (create) a new group namespace (organisation). | The purpose of this use case is to describe the process used to register (create) a new group namespace (organisation). | ||
[[Image:UseCase_Register_Group_Namespace-sml.png|Use Case diagram]] | |||
The diagram shows the requirements and rules the use case is responsible for (via the <<realize>> stereotype). | |||
== Pre-conditions == | |||
None | |||
== Post conditions == | |||
A new group namespace has been created with the actor identified as its founder. | |||
== Requirements and rules realized == | |||
* ''RQ1 Namespace names must be unique''<br /> | |||
The system shall prevent a namespace name from being registered if one with the identical name already exists. | |||
* ''BR1 Prevent the use of reserved namespaces''<br /> | |||
The system shall prevent a namespace from being registered if it is identical to that of a reserved name. | |||
* ''RQ2 Namespace names cannot be identical to a player name other than that of the founder''<br /> | |||
The system shall prevent a namespace name from being registered if it is identical to that of a registered player other than the one the actor has logged in with. | |||
* ''RQ3 The player who registers a namespace shall be its founder''<br /> | |||
The system shall grant founder status to the player who first registers the namespace. | |||
* ''RQ4 Only registered players shall be permitted to register a namespace''<br /> | |||
The system shall prevent unregistered players from registering a new namespace. | |||
== Flow of events == | |||
The flow of events describes the main actor actions and system responses in the execution of the use case. | |||
[[Image:Activity_Register_Group_Namespace-sml.png|Activity diagram showing flow of events]] | |||
== Messages == | |||
<properties> | |||
Step:= EX-1 | |||
Condition:= Unregistered player | |||
Message Number:= Err 1 | |||
Message Text:= You must log-in with your BZFlag call sign (user name) in order to register a new namespace. | |||
</properties> | |||
---- | |||
<properties> | |||
Step:= EX-2 | |||
Condition:= Invalid namespace name | |||
Message Number:= Err 2 | |||
Message Text:= The namespace name is not valid. It must be unique and cannot be the same as another BZFlag user name. | |||
</properties> | |||
---- | |||
<properties> | |||
Step:= BF-4 | |||
Condition:= Successfully added new namespace | |||
Message Number:= Msg 1 | |||
Message Text:= The namespace has been registered successfully. | |||
</properties> | |||
[[Category:Group Manager]] | |||
Latest revision as of 03:05, 5 December 2016
|
This page contains a specification 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. |
Introduction
The purpose of this use case is to describe the process used to register (create) a new group namespace (organisation).
The diagram shows the requirements and rules the use case is responsible for (via the <<realize>> stereotype).
Pre-conditions
None
Post conditions
A new group namespace has been created with the actor identified as its founder.
Requirements and rules realized
- RQ1 Namespace names must be unique
The system shall prevent a namespace name from being registered if one with the identical name already exists.
- BR1 Prevent the use of reserved namespaces
The system shall prevent a namespace from being registered if it is identical to that of a reserved name.
- RQ2 Namespace names cannot be identical to a player name other than that of the founder
The system shall prevent a namespace name from being registered if it is identical to that of a registered player other than the one the actor has logged in with.
- RQ3 The player who registers a namespace shall be its founder
The system shall grant founder status to the player who first registers the namespace.
- RQ4 Only registered players shall be permitted to register a namespace
The system shall prevent unregistered players from registering a new namespace.
Flow of events
The flow of events describes the main actor actions and system responses in the execution of the use case.
Messages
<properties> Step:= EX-1 Condition:= Unregistered player Message Number:= Err 1 Message Text:= You must log-in with your BZFlag call sign (user name) in order to register a new namespace. </properties>
<properties> Step:= EX-2 Condition:= Invalid namespace name Message Number:= Err 2 Message Text:= The namespace name is not valid. It must be unique and cannot be the same as another BZFlag user name. </properties>
<properties> Step:= BF-4 Condition:= Successfully added new namespace Message Number:= Msg 1 Message Text:= The namespace has been registered successfully. </properties>