Dacopan project                                MEETING MINUTES
                                               Mar 2nd, 2004

Meeting
        Mar 2nd, 2004, at 16:15

        Department of Computer Science

Attendance
        Carlos Arrastia Aparicio
        Vesa Vainio
        Jarkko Laine
        Jonathan Brown, chairman
        Jari Aarniala
        Alejandro Fernandez Rey, secretary


1. Start

Mr. Brown started the meeting at 16:21.

2. Assessment of the situation

   The requirements specfication document will be published by tomorrow, 
   so as it can be shown to Mr. Kojo. It's almost completed by the time of
   the meeting. All parts have been completed by each member and as well 
   by the Petrozavodsk group.
   
3. Discussion
   
   Agenda for today:
   - review of the requirements specification document status.
   - review of the proposal of the Petrozavodsk group on networking 
     scenarios priorities.
   - Vesa's role in the communications with the Petrozavodsk group.
   - ideas on planning the design phase.

   3-A REQUIREMENTS SPECIFICATION DOCUMENT STATUS
   
   The status of the Requirements Specification document was reviewed
     again section by section.
   
   Section 1 (Introduction): Finished.
   
   Section 2 (User requirements): Finished, but it will be made explicit 
      which of the user requirements are optional.
   
   Section 3 (Problem domain model): Finished, even though some points about 
      portability, and maintanability of the code could be added in the 
   non-functional requirements subsection.
   
   Section 4 (Networking scenarios): Some changes on the priorities of the 
   networking scenarios based partially on the proposal of Mikhail Kryshen 
   (Forum Documents>The scenarios>Reply #6 on: Feb 27th, 2004, 3:42pm) will 
   be made. Networking scenarios 101 and 421 will be assigned priority 3. 
   The aim is to limit the size of the project by considering some networking 
   scenarios as not compulsory.
   
   Section 5 (Use cases): Some parts contain errors that will be corrected 
   (pages 22 and 24). The term "level of detail" should be replaced by "sets of 
   variables". These changes will make this section closer to the actual ideas 
   presented in the animator system requirements.
   
   Section 6 (System requirements): There will be several main sections instead 
   of just one.
      
   Section 7(System requirements: Protocol events file): This section seems 
   complete.
          
   Section 8 (High-level architecture): Basically finished, even though some 
   points about the diagram are still unclear. They will be fixed.

   
   3-B VESA'S ROLE IN THE COMMUNICATIONS WITH THE PETROZAVODSK GROUP

   When an urgent question is issued by the Petrozavodsk group which needs to 
   be answered within a short delay, Vesa will take charge of answering it or 
   presenting it to the Helsinki group, depending on the delay and the times of 
   the meetings of the Helsinki group. Vesa's answer will be authorized, but 
   could be overridden by an Helsinki group decision, if necessary.
   The aim will be to have the questions issued by the Petrozavodsk group 
   answered, and as soon as possible.
      

   3-C REVIEW OF THE PROPOSAL OF THE PETROZAVODSK GROUP ON NETWORKING SCENARIOS 
   PRIORITIES
   
   This issue was treated during the review of the requirements specification 
   document. See point 3-A above.
      
   3-D IDEAS ON PLANNING THE DESIGN PHASE
   
   Some general ideas were mentioned about the design phase preparation, 
   specially about the format of the intermediate file, and the responsability 
   and division of work in the intermediate file format design. A deeper sight 
   is still needed, as no tasks were defined.


4. Action points

   - No clear assignment of tasks was done. The different corrections on the 
   requirements specification document will be done by every member.
   Maintainability section will be added by Jari, use cases and networking 
   scenarios will be fixed by Carlos, Vesa will specify which non-functional 
   requirements are optional and Jarkko will take charge of the structure 
   of the document (division of section 6), diagram in section 8, and 
   publishing the final document.
   
   - In next meeting, some planning of the review should be done, maybe by 
   distributing tasks between the members of the group to assure that the 
   document is complete, has no contradictions,... That is some quality 
   assurance.
   
   - The planning of the design phase could also be initiated, as well as some 
   ideas on the intermediate file format.
   
   
5. End
        Mr. Brown ended the meeting at 18:28.

---

Back to DaCoPAnDocumentation