DaCoPAn Software Engeneering Project

- Home  - Overview  - Members  - Documentation 

- Resources/Links - Project Website

 

Meeting
        Feb 23th, 2004, at 14:00.

        Room 307
        Petrozavodsk State University
        Anohina st. 20, Petrozavodsk

Attendance
        Kirill Kulakov, group leader
        Andrey Salo
        Andrey Ananin
        Viktor Surikov
        Mikhail Kryshen, secretary
        Dmitry Korzun, instructor

Absent
        Nobody was absent.

1. Start
        Mr. Kulakov started the meeting at 14:10.

2. Assessment of the situation
        Local group meeting.

3. Discussion
        At the begining of the meeting, some organizational issues
        were discussed:
          - Helsinki group arrival to Petrozavodsk in May 2nd,
          - schedule: prolonging of the requirement analyzed stage,
          - inspection meeting planed for Feb 27th,
          - should we publish progress reports in web: ask supervisors.

        Project Plan document revision:
          - Mr. Ananin reports that the Working Environment section is
          done,
          - Mr. Salo discussed the Size Estimate section with
          Mr. Korzun,
          - Schedule: decided to prolong the Requirement Analyses
          stage for a week.
          - Local schedule: include tasks with responsible persons,

        Requirements Specification document revision:
          - Mr. Korzun suggested to leave only names of scenarios if
          the Common Requirements section,
          - the group discussed the need of having presentation
          comments in the protocol events file and decided to ask
          customer,
          - Mr. Kryshen will be responsible for monitoring and
          learning the scenarios section as a whole, while other group
          members will take some groups of scenarios,
          - suggestions on the scenarios priorities:
            o scenario 310: change priority to 3,
            o scenario 411: change priority to 1,
            o scenario 333: change priority to 1,
            o leave 1 application layer, 3 TCP, 1 UDP, and 1 network
            layer scenarios in the 1st priority group.
          - Mr. Ananin reviews the use cases made by the Helsinki
          group:
            o use cases should be related to the high-level model
            o suggested to move use cases out of the Problem Domain
            Model section to some other section,
          - Mr. Korzun made some notes on the English grammar and use
          of UML in the System Requirements section,
          - the group discussed the possible types of diagrams to use
          in the System Requirements section and possible

4. Action points
        Mr. Kryshen will monitor risks, make a list of variables
        that the analyzer should calculate.

        Mr. Kulakov will ask supervisors about publishing progress
        reports at the web, coordinate the schedule with Mr. Brown,
        add responsible persons to the local schedule,

        Mr. Surikov will draw the high-level architecture diagram.

        Everyone continue working on the system requirements assigned
        earlier.

5. End
        Mr. Kulakov ended the meeting at 15:45.