1. Meeting Agenda 8 8 16

Uses data from tests as created by systems administrator

Frameworks(front end)
Structural Design
- Systems and subsystems
WSP diagram
Establish Goals
Basic documentation so far (why have we chosen c++?)
User Interface
Data Structure
Paper prototypes to show customer for feedback
Design of the interactive process by which users access program
- User Stories
- Use case diagrams (formalisation of existing)
Ask more questions
- Can developers reassess data levels?

How important is the user experience? Is a GUI necessary?
- Function over looks. GUI is non core but wanted.
Who manages moving from one state to another?
- Bug states are managed by different roles:
  - Triage: Sets severity, then moves it to;
  - Developers: Implements solution, then moves to;
  - Reviewers: Review solution, then close.
Can users hold multiple rolls?
- No
Who is each bug assigned to?
- All come as open bugs for triages to see.
What constitutes a user? What do they have? Public/private data?
- Username/password/email
How safety critical are the projects that will run on the system?
- "****" for passwords, not much else
Is this for a specific requirement or is it general?
- General open source projects
Where is the "enclosed data"?
- Uploaded on the 2/8/2016
Are we allowed to use frameworks/engines/libraries/databases?
- Yes, but we must make the back end

User identification
Different user levels
What makes up a bug?
Search Subsystem
Reporting Subsystem (analytics)
Login system
- "*****" passwords
Users at minimum created by admin. Preferred method is a "SIGN UP/NEW USER BUTTON"

Provide feedback