Meeting with james 15th june - hamstar/Braincase GitHub Wiki

Agenda

• Show layered architecture diagram
• Show the software review
• Show the vision

###Actions from previous meeting on 8th June

• Create another layered architecture diagram showing hardware and how components interact
• Use Software Methodology in Software Review
• https://docs.google.com/a/telescum.co.nz/document/d/1nHdgJBOYmLEnQ4XRGvANRlhxXHb3rTz0hg1_427naUk/edit
• Make changes to the vision, add references (not complete)
• https://github.com/hamstar/Braincase/wiki/Vision

Minutes

1. Personal Repository should be high priority
2. Requirements can include decisions that affect the choice of architecture software

Software Review

1. This should include architecture like Linux, PHP, Apache etc
2. Think of a blank slate representing the system boundaries
3. We need to pull external software from outside the boundary into it
4. However we need a process to vouch for the validity of having that software in it
5. That process needs to be a methodology
6. Every component needs to follow that methodology
7. Think of it like a job interview for each software component

##Issues

Actions for this meeting

1. Make changes to the Software Review
2. Make changes to the Vision
3. Complete the requested use cases as below:

Use Cases

For each user type we must write a single paragraph use case for each feature category.

User types:

• Academic
• Data survivability
• Ability to mind map
• Version control
• Publish Formatted Documents
• Ability to expose knowledge through a website
• Engineer
• Data survivability
• Ability to mind map
• Version control
• Publish Formatted Documents
• Ability to expose knowledge through a website
• Software Developer
• Data survivability
• Ability to mind map
• Version control
• Publish Formatted Documents
• Ability to expose knowledge through a website
• Musician or Artist
• Data survivability
• Ability to mind map
• Version control
• Publish Formatted Documents
• Ability to expose knowledge through a website
• Student
• Data survivability
• Ability to mind map
• Version control
• Publish Formatted Documents
• Ability to expose knowledge through a website

Categories:

• Data survivability
• Ability to mind map
• Version control
• Publish Formatted Documents
• Ability to expose knowledge through a website

For example for Student and Data Survivability: A student uses Braincase at school however when he leaves the school he is unable to use the server that Braincase is on. Because he exported his data before he left, he was able to deploy Braincase at home and continue using the software and his data.