Event Name
| Input & Output
| Summary of the Business Use Case
| |
00. New Legislature
| The Legislature data (which parliament, members leaving, members newly elected) (input)
Unregistered new members receive an invitation to register, with suitable roles; others are informed of their role changes (output)
| All the relevant data is entered in the voter archive and in the civic discussion platform. Affected users are informed by email.
| |
01. User Joins
| User data, including valid email address, password, etc. (input)
| A user account is created, email address is validated.
| |
02. User Leaves
| User account data and an explicit request to end the user registration (input)
An email confirming the de-registration (output)
| The user account is desactivated. Published answers and questions remain in the platform.
In addition a small amount of other information may be kept for the case the user decides to re-register.
| |
03. ROLE change
| An account and the roles that have to be added or removed from it (input)
An email to the account holder explaining the role changes, and its implications (output)
| The user account permissions are modified in accordance with the roles added or removed.
| |
04. ITEM create
| Details pertaining to the ITEM, for instance to whom the question is addressed, tags, and text (input)
| The user can edit the ITEM and its attributes until it is submitted.
| |
05. ITEM submit
| The ITEM's author (in case of Question or Answer) decides to submit it for moderation (input).
| An entry is added to the worklog for the moderators.
| |
06. ITEM decision
| The ITEM decision (clearance/blocking + motivation) (input)
| The ITEM's author is informed, and the action implied by the decision is performed.
| |
07. RELATION Registration
| The relation's data and type (input).
Account information and documents proving the relationship (output)
| The relation is registered and receives related permissions.
| |
08. RELATION Ends
| The date and details of the end of the relationship (input).
Proof of the end of the relationship (output). | The necessary documentation is produced and modifications in the system are performed.
| |
09. MP Update
| Relevant changes for the MP (input) (e.g., new mandate, end of membership, intra-legislature start of membership, ...)
| The changes are included both in the voter archive and the civic discussion forum.
| |
10. Time to update Voter Archive
| Required updates to the Voter Archive (input) (e.g. periodic publication of external mandates,...)
| The updates are included.
| |
11. Exclusion Question
| Target person or party, with motivation (input)
| An exclusion case is started, with the motivation it is made accessible to the Trustees.
| |
12. Exclusion Decision
| A decision or warning is served to the target person or party (output)
| In the case of an exclusion, the user account is disactivated. In the case of a warning, the warning is included in the internal log of the user.
| |
13. Time to draw PERIODIC report
| Period (month, year), and scope of the report (input)
Report (output)
| The report is created for use in press releases, for management reporting, or for inclusion in the website or articles.
| |