Meeting with James 27th July - hamstar/Braincase GitHub Wiki

Agenda

1. Set date and time for Progress Review in week 3 (Times on AutOnline)
2. Set some deadline dates for next stages of project. (Ie completion of review, initial prototype etc)

###Actions from previous meeting on 6th July

1. Complete requirement specification

• https://docs.google.com/document/d/11fnvUs20jYlUr92D3JaiuVDmfjOHpwZmrA1Q1oDXG7s/edit

1. Complete Software Review Methodology.

• https://docs.google.com/a/telescum.co.nz/document/d/1nHdgJBOYmLEnQ4XRGvANRlhxXHb3rTz0hg1_427naUk/edit#heading=h.wfcdty816410

1. In relation to above, Make changes noted in last meeting: https://github.com/hamstar/Braincase/wiki/Meeting-with-james-6th-july

Minutes

• Project Review is set for 1st August 1530
• Need to do twice as much work this semester because it is 30 points worth
• Not seeing the quantity of work required at the moment
• 12 weeks, could do 3 iterations of 4 weeks each.
• Some Dates
• 24th August for last day of planning and research phase.
• Project due in week 15.

Software Evaluation

• Diagrams look good
• Evaluation of components is good
• Break out "Create proposed system" step into another diagram look at adding something like
• evolve architecture
• incorporate new ideas from component review
• review architectural design alternatives
• identify problems with architecture
• establish new architectural sketch
• Create proposed system is not different first time round still justification for how we came up with architecture
• referencing sources on how to do architectural design
• referencing requirements which led to that choice
• "matching requirements against world of known architectures"
• Add detail of how the first architecture sketch came to be
• research of architectures
• suggestions by James
• categorizing the types of software

##Issues

• Architecture is wrong because it names components

Actions for this meeting