Dacopan project MEETING MINUTES
Feb 27th, 2004
Meeting
Feb 27th, 2004, at 12:15
Department of Computer Science
Attendance
Carlos Arrastia Aparicio
Vesa Vainio, secretary
Jarkko Laine
Jonathan Brown, chairman
Jari Aarniala
Absent
Alejandro Fernandez Rey
1. Start
Mr. Brown started the meeting at 12:26.
2. Assessment of the situation
- Discussed the Petrozavodsk team's reply to the deadline proposal.
- Decided that we need to review the deadline after receiving
information that Mr. Kojo is not available.
- We need to assess the status of the requirements document and
see if we can meet the deadline.
3. Discussion
3-A REQUIREMENTS SPECIFICATION
- The status of the Requirements Specification document was reviewed
section by section. The result and the assigned responsibilities are
in the appendix A.
- Summary of discussion and responsibilities:
Section 1: Carlos will write some text for introduction.
Section 2: User requirements are almost ready. Vesa will have a
look at them.
Section 3: Vesa will write a section on non-functional requirements
for the animator. Jari will write the part about download size.
Section 4: Carlos is still making some changes, according to
suggestions by Vesa. Carlos will also include a note about
the omissions and simplifications in the scenarios.
Section 5: Carlos is also working on the Use cases.
Section 6: Jonathan and Jari are working on the encapsulation
animation. Vesa will see though the MSC text again and also
read the MSC text.
Section 7: This section was dropped according to Kirill's
suggestion, and relevant parts moved to 3 and 6.
Section 8: Viktor Surikov has made a good picture for high-level
architecture. Jarkko will fill in the Animator part in
the picture and also write sufficient text to explain the
picture.
- It was also decided that Jarkko will make the necessary changes so that
DIA files are not linked directly to documents, but EPS files are linked
instead.
3-B DEADLINES DISCUSSION
- It was decided that the deadline previously agreed with the
Petrozavodsk team (1st of March, 2000 hours) doesn't need to
be changed.
- It was decided that we postpone publishing the document until
we have had the chance to review it in the Tuesday meeting.
3-C MEETING EFFICIENCY
- Vesa raised an issue about the efficiency of the groups
meetings. It was concluded that at the beginning of the meeting
there was no agenda and nobody had a good understanding of the
status of the document that we needed to review.
- To remedy this situation it was concluded that the meetings
should start by making a prioritized agenda for the meeting.
- In addition, there should be clearer responsibilities on
reviewing the status of the project.
- It was concluded that for next meeting, everyone should be
ready to present the status for all the sections they are
working on.
3-D TRANSITION TO DESIGN PHASE
- It was decided that in the next meeting we will begin our
design phase. After some discussion it was concluded that
we will initially NOT concentrate on the design document,
but try to focus on the important issues in design, the
structure of the software etc.
4. Action points
- Mr. Brown:
* Get the Encapsulation animation text readable by Sunday
evening.
- Mr. Arrastia:
* Work on Intro, Net scenarios and Use cases.
- Mr. Aarniala:
* Work on the non-functional requirements and system requirements.
- Mr. Vainio:
* Make some changes in project glossary.
* Confirm the Petrozavodsk group's understanding of the deadline.
* Work on User requirements, Non-functional requirements and
System requirements
- Mr. Laine:
* Work on High-level architecture
* Make necessary changes so that the documents can be compiled
without X Window System.
* See to it that there are no internal contradictions in the document.
5. End
Mr. Brown ended the meeting at 13:55.
--------------------------------------------------------------------------
APPENDIX A: The suggested organization of the Requirements specification
document, the status of it and action points.
Section % done Actor
--------------------------------------------------------------------------
1. Introduction 0 Carlos
2. User requirements 95 Vesa
3. Problem domain 70 Vesa, Jari
4. Scenarios with variables 95 Carlos
5. Use cases 70 Carlos
6. System requirements 60 Jonathan, Jari, Vesa
7. Non-functional requirements section is dropped according to Kirill's suggestion
8. High level architecture 30 Jarkko
Back to DaCoPAnDocumentation