SuperGlossary

From ESEEWiki

Jump to: navigation, search

Attributes in italics on top are important general descriptors. Attributes in bold on the bottom are open issues that must be resolved.

Contents

Entities

Document

  • For voting and editing purposes, has all of the properties of a Section, but has properties that a Section does not.
  • Four permission categories implemented as relationships between Document and Group: View, Modify-Direct, Modify-Propose, Approve-Vote.
  • One document can have several groups granted one or more of the permission categories.
  • Example for Document01:
  • View: Anonymous
  • Modify-Direct: None
  • Modify-Propose: Committee01
  • Approve-Vote: Committee01
  • If one or more groups is set for Modify-Propose, there must be at least one group set for Approve-Vote, since proposals must be approved somehow.
  • Can be created by any Member, subject to deletion by Administrators.
  • Extra Feature: Allow group voting to remove documents?
  • Should we allow Anonymous to be assigned to anything other than View? Then that document will act as more of a true wiki, as anyone can edit it.

Section

  • Changes are approved when all Groups in each approval stage have approved the change.
  • Members of Groups with Modify-Direct on a Document can add sections directly.
  • Members of Groups with Modify-Propose on a Document can propose the addition of a section.

Group

  • Contains entities of type Member, who are added and removed by Administrators.
  • Is granted, via relationship with Document, permission to execute certain actions on Documents.
  • Can have from zero to many of such relationships granted at any one time.

User

  • The basic person entity of the system.

Roles

User: Guest

  • Logs onto the system anonymously.
  • Depending on the settings at the time, Guests will usually only be able to view documents.

User: Member

  • Can have the roles of Chair and/or Administrator.
  • Is added to Groups by Administrators.
  • The action rights of a Member are determined by the permission categories of Documents that their Groups are in.
  • Can create Documents on the system.

User: Member: Chair

  • works within the structure set by the administrator
  • There is only one Chair defined in the system at any one time.
  • Chairs are appointed by Administrators from the pool of Members (which includes Administrators).
  • Chairs are able to relinquish their control and appoint the next Chair.
  • Three voting possibilities: (1) Chair opens vote and sets time limit at which time voting ends, (2) Chair opens and closes vote directly, (3) Chair opens the vote and the system automatically closes it when there is enough information to determine the outcome. Give them all three options? Didn't we agree on some default for that, for the purposes of core functionality implementation?

User: Member: Administrator

  • sets the structure in which the chair and members work
  • Links Documents and Groups via permission categories.
  • Adds and removes Members from Groups.
  • Can remove Documents, and is the main moderator for new documents created by Members.
  • Deals somehow with deprecated proposals

Group: Anonymous

  • The Anonymous group cannot be deleted, and no one can add or remove members from it.
  • It contains everyone who may log into the system, whether Members or Guests.

Voting

  • Dimension: From chair inputs all votes to everyone logs on and votes on the system
  • Default Case: everyone logs on and votes on the system.

Iteration

  • Documents/Sections/Modification
  • Proposed Revisions
  • Authentication
  • Voting