Dacopan project                                MEETING MINUTES
                                               Feb 5th, 2004

Meeting
        Feb 5th, 2004, at 8:15

        Department of Computer Science, room C475
        Teollisuuskatu 23, Helsinki

Attendance
        Dmitry Korzun, instructor
        Kirill Kulakov
        Andrei Salo
        Andrei Ananin
        Mikhail Kryshen

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

Absent
   Nobody was absent.

1. Start
        Mr. Brown started the meeting at 8:25.

2. Assessment of the situation
        The project plan is quite complete, even if some extra work must still
        be done. The requirements elicitation process is still on. This meeting
        is meant to prepare tomorrow's meeting with the customer Mr. Kojo,
        discuss project plan missing points and take pictures of the members of
        the project for the project website. A forum has been recently added to
        the website.

3. Discussion

   3.A - Project plan:

     - The schedule and organization parts of the project plan must be
     completed.
     - The change log must not be so large.
     - The Helsinki group must make an estimation of the animator using
     functional points and LOC (Lines Of Code) basing its estimation in
     division in modules, analog programs comparison and Parkinson's law.
     - Some detailed explanation about the roles must be added (Section 2.6).
     - Information about the communication means and the use of each must
     also be added. It is proposed that the mailing lists are used for
     time critical matters and the forum for other less important issues.
     - The monitoring and reporting section will be expanded with working
     procedures.

   3.C - Requirements elicitation:

     - The list of scenarios should be used to find explicit and implicit
     variables. Those variables (such as TCP states, for instance) could
     be included in the intermediate file issued by the analyzer. We must
     ask Mr. Kojo for the exact variables that must be calculated by the
     analyzer and which are provided by the tcpdump logs.
     - The group that will elaborate a preliminary list of the scenarios
     to be presented to Mr. Kojo is composed of: Mr. Kryshen, Mr. Vainio,
     Mr. Arrastia, Mr. Brown and Mr. Fernandez. The list should be ready
     for next meeting with the customer. The group should also gather
     questions on the scenarios.
     - A question about the application layer is discussed during the
     meeting. It isn't clear if Mr. Kojo said that he only wanted
     HTTP over TCP and DNS lookups over UDP. This issue should be
     presented to Mr. Kojo in next meeting.
     - Talking about DNS lookups brings into discussion the feasibility
     of animating a third party such as DNS Server. It seems to some
     members that the idea of a pop-up window isn't very appropriate, as
     it will give to the user the impression of an error or an exception
     event. It is mentioned that other ways are possible, and it will be
     taken into account later on, in the design phase. This issue seems
     important for DNS lookups and ARP requests/replies. Maybe this
     information could be included in intermediate file somehow. It seems
     important as well that a third party could be a good later extension
     of the program.

   3.B - Others:

     - A glossary of terms related to the project must be accomplished.
     It could be installed in TWiki, and each member collaborate in its
     elaboration. The principles of this glossary should be consistency and
     uniqueness. It could also be added to the project plan.
     - The abbreviations used in the working hours documents must be
     accesible through TWiki, and the term "RE", standing for Requirement
     Engineering, should be included.
     - A description of the project must be included in the website (not
     only in TWiki). This has already be done by Mr. Arrastia.
     - Pictures are taken of the present members.
     - Some informal meeting for next week is discussed.


4. Action points

   - Mr. Kulakov and Mr. Brown will take care of the schedule part of the
   project plan.
   - Extra changes can be done by all members to the organization part.
   - The above mentioned group will take care of the scenario list.

5. End

   Mr. Brown ended the meeting at 9h47.

---

Go back to DaCoPAnDocumentation