Meeting with James 4th may - hamstar/Braincase GitHub Wiki

Agenda

1. Further discuss Core Wiki Page (9.0) Use Cases
2. Confirm 8. Access Control Use Cases
3. Discuss Acceptance Tests

###Actions from previous meeting on 20th April

1. Complete initial set of requirements
2. Partially completed
3. Implement priority's given by Client
4. Completed
5. Find a way to manage requirements
6. Will be using Github "Issues"
7. Read the book to find out how acceptances tests are done
8. Couldn't find anything in the book about acceptance tests
9. Complete Use Cases for interface
10. Partially Completed

Minutes

• Need to read the article on PKBs from James
• Read PKB and Backups articles on Wikipedia
• Expand on github tags to add Acceptance Tests
• Expand on github tags to add Design Decision/Rationale for justification of requirements
• Explain structure of github issues in req spec
• The level of Access Control required right now is:
  • Private
  • Public Read Only
  • Public Edit
• Make sure to record the format of backups in the architecture doc
• Read something on Acceptance Tests
• Create Vision Wiki Page

##Issues

• Vision for the Software
  • Need to create a vision for the software of about 1000 words
  • Need to include this near the front of the reqs spec (prob under intro title)
• How to add secure access (SSL/HTTPS)
  • What is the impact on the architecture?
• How to implement backup security
  • Different backup style depending on target

Actions for this meeting

1. Create Vision for the Software
2. Determine how to add secure access
3. Determine how to implement backup security
4. Expand github tags
5. Read articles and wiki pages
6. Read something on ATs
7. Complete req spec