PLACE:
Professor Junk's office
TIME:
2:30 PM
ATTENDEES: Professor Junk
James Cooper
Jamie Marconi
Sam Gerlach
TOPIC: Team Status
Vision Statement
----------------
Professor Junk stated that our current Vision Statement is not quite
complete. What we have now is more about what we envision as
our
strategy, rather than Professor Frincke's grand scheme. The beginning
of
our Product Summary could be recrafted to provide an adequate Vision
Statement.
This task has been assigned to James Cooper.
Product Summary
---------------
Professor Junk said that our Product Summary is decent.
Team Values
-----------
Meetings:
Professor Junk did not like the first statement about meetings (Each
member of the team is expected to attend every meeting possible.)
Also,
he says we may not need to meet twice a week.
Responsibilities:
We need to place more emphasis on the fact that the work will be divided
EQUALLY.
Team Leader:
Professor Junk said that the last stint of team leader is a very important
one. We have decided to randomly choose the person for this role
well in
advance.
Problem Resolution:
Professor Junk liked the fact that we are encouraging individual
responsibility for resolving problems. We need to keep a business-like
attitude, as opposed to "emotional outbursts."
Sam Gerlach has been assigned to revising the Team Values.
Risk Analysis
-------------
Professor Junk said that our second risk (a small group) is not a risk.
This could be a bonus. Also, there is nothing that we can do
about it.
Professor Junk also advised that we reformat our risks into a table.
This
table will include: the risk, the actionee, the level of risk,
and when
it is to be resolved.
Sam Gerlach will revise the Risk Analysis.
Requirements
------------
We didn't focus on the requirements extensively. However, Professor
Junk
said that we should put them into more of a document format.
Also, they
should be written in statements that can be used as foundations for
test
cases.
Jamie Marconi has been assigned the task of revising the Requirements.
Schedule
--------
Professor Junk said that our schedule is a good high-level example.
Now
we need to revise it for the proxy walk through. This means we
need to
have 15-20 tasks laid out for the walk through.
James Cooper will revise our schedule.
Walk Through
------------
Professor Junk advised that we need to separate the documents for the
walk
through. We need to document the tests that we run and the features
that
we are implementing. Since our project is a little more internal,
than
external, we need to be able to show that we are accomplishing our
goal.
We will implement this as a group.
Testing
-------
Professor Junk stated that Professor Oman wants/requires automated
regression testing. This includes unit level and system level.
In
addition, we need some kind of bug tracking system. We were encouraged
to
log all bugs, no matter how small. Rigorous documentation is
required.
Jamie will write up the test plan and we have already set up Gnats to
track our bugs.
Questions
---------
Jamie asked if we could electronically submit our notebook. Professor
Junk said he would get back to us on this. It is harder for him
to grade
this way.
We asked Professor Junk to explain file environments. These were
described as any internal or external files significant to the project.
Jamie asked for a more detailed explanation of the Data Dictionary.
We
were told to document anything that we added or modified. We
can
reference the previous CS481 notebook for existing code.
We needed a better explanation of architectural design. Professor
Junk
said we should have a block diagram of how our program's parts interface
with each other.
Professor Junk said if we have questions, we can reference the CS480
descriptions of the notebook.