Sunday Meeting Agenda

Just getting some ideas together so we can make an agenda for the meeting. I'd like it to be organized and directly focused on our deliverables due Wednesday.
As far as times, post them in the times thread.

Agenda Topics

System Specifications Document
To Do
Assign a writer or group of writers. (1-3 total people, depending on how long the outline will be). Also assign another 2-3 people to proofread, etc.
Establish an outline of the document.
Plan a deadline (monday evening?) and distribute it for proofreading.
Have this group of 4-6 people meet on Tuesday to go over it before submission.


System Architecture Document
This document is going to take significantly more work.
To Do
Establish the groups
Within this, we need to:
- Explicitly define the role of each group.
- Determine the number of students needed for each group.
- Pick the students for these groups.
- These groups then will need to establish their HARDWARE requirements.

Once the groups are established and defined:
Have a member of each group write up the semantics of their component and the deliverables their group will provide.
Another member in this group should proofread these.

All these need to be compiled into a single document. Another two individuals will be needed there.




This (I believe) covers everything we need to do for this week. Again, this meeting should be the least technical, actual implementations aren't important quite yet.
Comments, suggestions, etc. are welcome, and this will be modified as needed.

-Ryan Bontreger

A couple of things:

I believe Dr. Brooks asked for a copy of the documents a day before class so he could have an idea what we were planning before class (so due Tuesday, not Wednesday). Can anyone back me up on this?

Also, I thought he said that the architecture document should be at the level of a .h file, which would mean that we would have to go into detail about interfaces and whatnot now, not later.

JDinger wrote:A couple of things:

I believe Dr. Brooks asked for a copy of the documents a day before class so he could have an idea what we were planning before class (so due Tuesday, not Wednesday). Can anyone back me up on this?

Also, I thought he said that the architecture document should be at the level of a .h file, which would mean that we would have to go into detail about interfaces and whatnot now, not later.

yeah, you were right on the "due tuesday" thing.


I may be mistaken, but I thought the component API document was the header files (due 2/4/09)