Dacopan-jatkoprojektin tapaamiset

Suunnittelukokous 

Päivämäärä: (perjantai) 25.02.2005, klo 8:30-10:00
Paikka: DK109 (Exactum, Helsingin Yliopisto)
Sihteeri: Tomi Korkki


The new priorities in more detail. The four priorities above classify the
importance of each described functionality and requirement in the requirements
document.
 
Priority 1, Must be implemented: These are functionalities and requirements
that have been assessed as being critical in order to have a successful
completion of the project. They are defined by the Customer.
 
Priority 2, Preferrably implemented: These functionalities and requirements are
to be implemented if feasible; this assumes that the time constraints and
existing code allow for such. These are suggestions made by the Customer.
 
Priority 3, Optional: These functionalities and requirements are to possibly be
implemented if time allows. These are generally improvements the group has
come up with on it's own.
 
Priority 4, Not to be implemented: These are functionalities and requirements
that have been determined to be non-critical or not feasible to implement due
to time constraints and/or issues with code. Possibly left to be implemented by
later continuing Dacopan projects.