Update Membership Request

From BZFlagWiki
Revision as of 17:06, 5 December 2016 by Zehra (Talk | contribs) (category link)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Picture Frame.png 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.


This use case describes the process a group manager will use to approve or decline a request from a player to join a group.

Use Case diagram

The diagram shows the requirements and rules the use case is responsible for (via the <<requirement>> stereotype).



Post conditions[edit]

The membership request has been updated.

Requirements and rules realized[edit]

RQ11 Track the status of membership requests
The system shall store and track the status of membership requests.

  • BR19 Record change in request status

The system shall record the change in status from 'pending' to 'actioned', and optionally a note, for each request when one of the groups managers has indicated the outcome of the request.

  • BR20 Record request result

The system shall record the result of each request which shall be either 'approved' or 'declined', along with the date of the decision, the manager who made it and optionally a note.

  • BR21 Membership request information

The system shall record the player, date, group and optionally a note from the player for each membership request.

  • BR25 Actioned requests cannot be updated

The system shall prevent a request which has already been actioned from having its result changed.

RQ14 Viewing membership requests
The system shall enable players to view the requests they have submitted.

  • BR22 Group managers view all requests

The system shall enable group managers to view all requests, both pending and actioned, for the groups they manage.

RQ16 Format of request list
The system shall format the list of membership requests according to the following rules: BR23, BR24

  • BR23 Group by namespace

The system shall enable the actor to view the requests belonging to each namespace separately.

  • BR24 Filter by status

The system shall enable the actor to filter the requests by status; viewing only those 'pending', 'resulted', or both.

RQ15 Notify player of changes
The system shall notify the player who submitted the request of any change in its status.

Flow of events[edit]

The flow of events describes the main actor actions and system responses in the execution of the use case.

Activity diagram showing flow of events


Step: BF-3
Condition: Actor indicated update request
Message Number: MSG-1
Message Text: Please confirm that you want to <approve | decline> this request.

Step: BF-7
Condition: Request updated
Message Number: MSG-2
Message Text: The membership request has been updated, and the player notified of the result.