3. Meeting Agenda 22 8 16

Mon 22/8/2016

• Group meeting agenda
• basic requirements that need to be fleshed out

Group Meeting Agenda

URGENT ACTION ITEMS

• Structural Design
  • Systems and subsystems
  • (Satvik)
• WBS diagram
  • (Brett)
• User Interface
  • Prototypes
  • (Brett)
• Data Structures
  • Database Design
  • (Ryan)
• User Stories
  • (Aden)
• Use case diagrams
  • (Aden)
• Timeline for project development
  • (Aden)
• Formal requirements
  • (Andrew)

REVIEW OF PROJECT STATUS

• 4/7 of the way to the deadline
• We have lost traction with little work being done in the past week

SCHEDULED AGENDA ITEMS

• Finalize the formal requirements
• Reviewing contributions of team members
  • Check work is done
  • Check quality and completeness

Minutes from last week

• Urgent action items where not completed
• New requirements added

  • Bug has a:

    • bug id
    • creation time stamp
    • short description (length up to us, doubles as "name")
    • last modified time stamp
    • component
    • product
    • version
    • operating system
    • bug_status
    • full comment system (with optional file attachment 1 MB max)
    • keywords
    • priority level
    • bug severity
    • target milestone (which version should it work for)
    • cclist (subscribed users to a bug)

  • Search subsystem must:

    • be sortable
    • have AND functionality
    • (example given was a table with "arrows" at the top to sort in that order)

  • Roles are:

    • Triage
    • Developer
    • Reviewer
    • Reporter (Any signed in user)
    • Admin
    • Unverified user (not logged in, READ ONLY)

  • UI should focus on functionality and agility

  • New user accounts go onto an admin "approve list" before activated (Prefered not core)