Dacopan project MEETING MINUTES
Feb 17th, 2004
Meeting
Feb 10th, 2004, at 16:15
Department of Computer Science, room C475
Attendance
Alejandro Fernandez Rey
Carlos Arrastia Aparicio
Jari Aarniala, secretary
Jarkko Laine
Jonathan Brown, chairman
Turjo Tuohiniemi, instructor
Vesa Vainio
1. Start
Mr. Vaino started the meeting at 16:18.
2. Assessment of the situation
The project plan is almost ready, last meeting size stimation was
the main topic and for this meeting is ready. Only the internal
schedule for the group in Helsinki is missing in the project plan.
In the following days the project plan should be delivered to the
supervisor and customer, but not the requirements document.
Last days had also revealed the need to change the format of the
scenarios.
3. Discussion
3.A - Networking scenarios and requirements.
The requirements contain too technical details and they should reflect
what the software does. The requierements document should be refined.
Restructure the contents on the scenarios and requirements is needed.
They should be modified to be more understandable to the readers.
In the scenarios should be added a subsection containing postponed and
additional scenarios
In the requirements document some sections are missing or incomplete, as
use cases, features, non functional requirements...
Two groups have been formed to work in the different areas of the
requirements document to have it ready as soon as possible.
The groups and tasks are the following:
Mr. Arrastia, Mr. Fernandez and Mr. Laine
- Scenarios
- Use cases
Mr. Arniala, Mr. Brown and Mr. Vaino
- Summarize requirements, work in the description of the
existing ones and add non-functional requirements.
- Gather visialization requirements for the animator.
The group from Petrozavodsk should be contacted to know their actual
situation and negotiate which parts they should do in this document. The
most important thing for them to fill in the requirements documents are
the requirements for the analyzer, but they need to have the scenarios
ready to extract some information about the header files from there.
Also a task to be done by both groups is work in the requirements in
between the animator and analyzer.
Requirements should be elaborated from the scenarios and then analyze
their feasability.
Also some requirements for the tcpdump files provided by the customer.
3.B - Schedule
The deadline to present the requirements document has ben moved,
because requierements document wonˇt be ready before February 27th
The time to do this will be allocated from the implementation phase
Requirements from Petrozavodsk group are needed before February 24th,
Tuesday. After the meeting held on that date there will be a cross
review of the requirements and the document with the changes made will
be sent to the client
3.C - Progress report
The project plan is almost done. The sections left to work in are
deciding about local schedule for the Helsinki group.
It was decided that the deadlines for final documents are the same as
the used for the global schedule.
Once this section is finished, the first version of the project plan
document will be frozen and sent to the supervisor.
4. Action points
- The groups created will work in the tasks assigned to finish the
requirements document as soon as possible.
- The Project Plan should be finished and delivered early in the
following days
- Mr. Vaino will e-mail the russian group to ask them about the
goals for the following days and based on this assign tasks to complete
the requirements.
5. End
Mr. Brown ended the meeting at 18:00
