Dacopan project MEETING MINUTES
Jan 26th, 2004
Meeting
Jan 23th, 2004, at 14:30.
Class room C476
Department of Computer Science
Teollisuuskatu 23, Helsinki
Attendance
Dimitri Korzun, instructor
Kirill Kulakov
Andrei Salo
Andrei Ananin
Mikhail Kryshen
Jonathan Brown, chairman
Carlos Arrastia Aparicio
Alejandro Fernandez Rey, secretary
Vesa Vainio
Jarkko Laine
Turjo Tuohiniemi, instructor
Juha Taina, supervisor
Absent
Jari Aarniala
1. Start
Mr. Brown started the meeting at 14:37.
2. Assessment of the situation
This is the first official meeting. A short introduction about
the product has been made to the group. Each group separately has
had some organizational meetings before.
3. Discussion
3.A - Group roles and organization:
- Jonathan Brown, as permanent group leader of the finnish
group, will be the whole group leader as the finnish group will
be closer to the client.
- The roles of the finnish group members are set, but are
temporary until the engineering process will determine a bit
more which are necessary. Roles from both groups will be
available on website of the project
<http://www.cs.helsinki.fi/group/dacopan> when exactly
determined. Personal information will also be available on the
web: name, age, role, some extra and probably photographs.
- The mean of communication for the moment will be email, using
a mailing list, for example
<ohtuk04-dacopan-list@cs.helsinki.fi>, and there will be a
contact person in each group. In one group, it will be Vesa
Vainio, and it will probably be Kirill Kulakov or Dimitri Korzun
in the other group. Emails should be addressed to a particular
email if wanted, but always also to the mailing list so as
everyone can see them, specially the instructors.
3.B - Technical issues and engineering tools:
- The need of a repository system (to share our work) and a
website (to show it) is agreed. The physical location of it
remains undetermined. The russian team offers that these will
be maintained in their university, because of large files slow
upload and/or download and for local folders issues. Also the
possibility of using 2 repositories and merging them is
considered. No definitive decision is taken about this point.
- Some Wiki system for fixed documents for web presentation
will be considered. This will allow to present consensed
document versions to the client and other interested people.
Some CVS repository system is also considered necessary, for
internal version control and file sharing.
- It was almost agreed that LaTex format will be used for
documentation. Some existing templates from the Department of
Computer Science of the University of Helsinki will be
translated to english and used.
- The conversion from LaTex format to HTML is considered, even
though the image and html links problems that are present.
It seems more convenient to everybody to convert LaTex
documents to PDF or PS format.
- UML modelling will be used for the design phase, but there is
also the possibility that it can be used for the requirements
analysis phase.
- The programming language preference will be decided later
after talking with the client, depending on specifications and
program division into modules. It seems wise for everybody that
Java, C++ and/or C would be the most probable languages,
specially Java.
- The process model that will be followed is considered. The
most mentioned is the waterfall model, but a decision was not
made yet. It seems wise to use it because it limits the
client's presence to the beginning of the process, and we don't
know his later availability.
- It seems important to decide which project plan will be used,
or at least a skeleton of it, without much precision neither,
as soon as possible. Some templates from the Department of
Computer Science of the University of Helsinki will probably be
used.
3.C - Other issues:
- Next meeting is determined for Tuesday 27.01.04 at 16h, which
aim will be merging two lists of questions for the client made
by each of the groups. The most important agreed questions will
be on the definitive list. The meeting with the client will be
that day at 16h30 until 17h quite probably. Other meeting will
take place on Thursday 29.01.04 at 9h.
- The name of the project/software is, for the moment, DaCoPAn.
The explanation will be available on the website, but is taken
from the name of the project itself.
4. Action points
- Email interchange of personal information for the website.
- DaCoPAn website building.
- Getting information about the LaTex templates that can be used.
- Getting information about CVS (University of Petrozavodsk team) and
Wiki (University of Helsinki team).
- Creating 2 lists of questions for next meeting (each list will be
completed by each group).
5. End
Mr. Brown ended the meeting at 16.
Go back to DaCoPAnDocumentation