CS 481 - Team 49 Meeting Minutes Weekly Team Meeting Friday, September 7, 2007 10:30 - 11:20 am JEB 324 Recorder: Brandon Riggers -------------------------------- Meeting Summary This meeting consisted of Bill Junk addressing the status of our project and discussing the upcoming Concept Proposal. Bill talked briefly about a fair distribution of work, the team's (our) project task list, and the meeting with Bruce in person on Thursday (9-6). He then spent the rest of the meeting discussing what we needed to have ready for, and accomplish with the Concept Proposal. Attendees Brandon Riggers, Shruti Upadhyaya, Peter Brown-Hayes, Travis Thoroman, Bill Junk Topics Discussed Bill began the meeting by getting our accomplishments during the week, and mentioned that he expected we'll log more hours next week (on the CS 481 PRS). Peter also mentioned at the beginning of the meeting the team getting card access to JEB and the CSAC computer lab (JEB 211), and distributed forms for Bill to sign. Bill continued by saying there was about a 3-to-1 ratio between the high and low marks of individual hours worked that week within our team, and gave us three scenarios to avoid: - A team member trying to "ride free." - A team member being shunted or cut out of having opportunities to work. - A team member who "runs with too much," deciding to work independently. Everyone should be given "equal chunks of stuff" that would contribute. Bill moved on to Thursday's meeting with Bruce, mentioning that we may want to pursue the development option of discovering an already-written or -used turmoil tool established by Subversion. He also gathered from the meeting that one of the most important things with our project is correlation between the turmoil history. Our task list was the last topic before Bill began discussing our Concept Proposal. He talked about how we needed to be laying out things that need to be done in the next week or two, and pointed out that we've assigned few tasks that haven't already been completed. We also need to reflect the uniqueness of our project in our tasks, and start to "make it our own" now that we know a little more. The Concept Proposal will be a Powerpoint 2003 presentation. Bill addressed the bullets on the general CS 481 web page concerning a team's Proposal: - Customer motivation and vision: We should be able to handle this after our meeting with Bruce. - Solution requirements: We need to address accuracy, consistency, performance, and reliability. (Bill reminded us of the need to not let our crash.) - Use cases: We need to articulate one or more use cases, which would include the kind where Bruce runs program. We should also mention here something about the need for a quick turnaround with a response when a user checks work into the repository and introduces new turmoil. - Architectural approach: This should include a diagram of our environment, and the three options we talked about with Bruce in Thursday's meeting. We should be able to take a "general stab" and pictorialize the environment. We can at least talk about how the architecture could look, and should present a picture of what we're contending with. - Testing strategy: We can start small, but we'll need to test large- scale. We should try to automate our tests as much as we can, and add to the test suite as we find defects. - High level schedule: This will include a layout of the expectation (at the least) of what the first release is going to do. - Risk assessment: Two kinds of risk assessment exist: technical and non- technical. - Technical - Difference in Perl interpreters - How Subversion tracks the changes, and would this change the results? - Non-tech. - Our customer is in Boise, and we're relying heavily on email. (Bruce is very responsive though.) - Illness. This happens about every semester, and we'll have to re-prioritize in response. Someone will have to step in. -- Other risks include if our dedicated machine "goes belly-up." We need to present how we plan on minimizing the impact of these risks. (i.e. A strategy to handle risks.) Other information about the Proposal presentation includes: - Only one person will do the presenting (speaking), but he or she can defer to someone else. - The slides need to be posted on the web site before the meeting. - Bruce will be on the phone. - The page numbers need to be on the slide set. - We need to have a good idea of when we're going to see some executable result. Bill also mentioned that we need to start thinking/discussing the legal, ethical, and social aspects of the project. Bruce and the team members (individually) have the rights to the product. The meeting ended with discussion of how our project exemplifies engineering because more evaluation and investigation is involved. Bill assured us of the value of experience with this. Lastly, it was mentioned that projects written in scripting languages have more defects, and we'll formally record when we're making the real tool.