CS 330 Software Engineering Maintenance Teams
Requirements teams
Maintenance Team 1
Maintenance Team 2:c
Frank Gearhart (Leader)
Robert McDonnell
Thomas Navin
Philip Landry
Maintenance Team 3:
Maintenance Team First Assignment (Due 3/08/06)
Define the "software effort" for which you do your "maintenance".
It must have
- at least 200,000 lines of code,
- provide source code,
- have at least 4 developers involved (current or past),
- support win32 and one non-windows OS (Mac or inx),
- have a formal version control mechanism,
- have a formal bug tracking mechanism.
Turn a a proposed schedule for your second assignment.
Maintenance Team First Assignment (Due 4/3/06)
You will turn in document demonstrating that you have installed and
compiled your maintenance project on both OSs. You will choose one of
the bugs listed in the formal bug reports and "validate" them as a
bug, i.e. reproduce it.
Maintenance Final Assignment (Due 5/12/06)
This is extra credit, maximum value 60pts EC (divided between those on your team that go for it).
Using the project from your initial effort, find at least one formal
code-related bug, hypothesize it cause, validate the cause in the code
and (if possible) correct it. Point awarded will depend on the
difficulty of the bug, the effectiveness of your process in
finding/resolving it.
