Course project

Course project (assignment) is required for all and completed in five phases. All phases of the course project must be demonstrated course project counseling according to schedule. The phase is officially accepted after the supervisor has marked his signature in Korppi (fields: HT1-HT4 - acceptance for Phase "0" is not marked explicitly). Every phase must be separately demonstrated to the supervisor, one phase at a time.

The goal for the course project is to practice use case -based modeling using UML on given subject or own idea. The modeling is applied to a hypothetical information system or independent software product.

"Example assignment" (partial - see also Finnish version).

Group size

It is preferred but not strictly required to do the course project in groups of 2-3 persons. Groups can be formed at the exercise sessions, or by the course mailing list.

Schedule

See also the detailed descriptions on each phase.

#	Phase	Content	Deadline
"0"	Select topic	Initial description of the domain and requirements for the system. You can also select the topic from example projects.	1.4.
1	Use cases	Textual use case descriptions (2-4, depending on the scope of the assignment and the detail used in use cases) and use case diagram. Activity diagrams (0-2 depending on the system) about the business process related to the system.	16.4.
2	Analysis	Analysis class diagram (domain model). Data dictionary. Collaboration diagrams of the use cases modeled in phase 1.	30.4.
3	Design I - static modeling	Detailed design class diagram (elaborated domain model and controller+boundary classes related to the modeled use cases). CRC cards of the most important classes of the system.	12.5.
4	Design II - dynamic modeling	Detailed design sequence diagrams (based on collaboration diagrams modeled in phase 2) and state diagrams (1-2 depending on the system).	28.5.

The final deadline (all phases completed and earlier parts possibly updated to get a constant model) for course project is 4.6.2010.

Course project supervision

Supervision is given in exercise groups and counseling (the general process is in most cases similar to course assignements in Programming 2 course). E-mail can be used for supplementary counseling as well.

Course projects for international students are primarily supervised by Vesa Korhonen (vesa.a.korhonen@jyu.fi).

Counseling times are booked from Korppi at latest one day before counseling.

At the counseling:

Think about questions and problems appeared with the assignment, ask the supervisor for help
The assignment must be located in WWW as noted in the Files-section of this guide.
Everyone of the course project group must be present
Mobile phone closed/silent
The critique posed by the supervisor is meant for positive guidance
The student is responsible to mark and apply the changes proposed by the supervisor

Note: The course assignment is not a part of your portfolio! The assignment is a learning situation, where the student attempts to design a system based on his own skills and knowledge. "Red marks" aren't marks of shame but hints about what should be rethought (and signs that your supervisor is interested in your work!).

Files

Each phase is saved to web page used by project group's member (mark the URL in Korppi). The assignment must be located at www during the counseling.

You can choose freely the applications used in the assignment (see the links). BOUML, StarUML, ArgoUML, UMLet and other UML tools are installed in the computer classes (see directories C:\UMLTools and C:\MyTemp\UML).

Should you decide to use BOUML for the assigment, a project template), is available with definitions to model views and diagram templates with correct drawing settings.

The assignment is stored in WWW. The URL directory root of the project pages must be marked in Korppi-system. The work should be "protected" from visitors by using a URL not publicly visible under web pages and not easily guessed. (cf. http://users.jyu.fi/~minurmin/jfskldof/oas/). More info about working with web pages in the first exercise group.

UML diagrams are stored to web pages as pictures. Permitted formats: PDF, EMF, WMF, EPS, PNG, GIF, or JPG.
Other documents are published as text files, HTML, PDF, or in the native format of the word processor (not recommended). Permitted formats: TXT, HTML, PDF, RTF, OpenOffice ODT, or Word DOC.
Original working files used in the production of UML diagrams and other documents can be kept under the pages, in a separate directory from "published" material.
Annotate the documents with starting date, author and - if necessary - important changes between versions.
Files returned for different phases should be separated in different directories or named such that the phase is clearly visible from the file name. This way it is easier to follow working progress and updates in UML models.
A separate index.html title page is not required. However, a description.html containing project group information and expanded description of the topic must be present.

Example of the page structure and possible files:

 |-description.html
 |
 |--workingFiles/
 |   |-note.txt
 |   |-dataDictionary.doc
 |   |-umlModel.uml
 |   |-testDiagram.violet
 |
 |--phase1/
 |   |-useCases.html
 |   |-useCaseDiagram.pdf
 |   |-processDiagram.pdf
 |
 |--phase2/
 |   |-dataDictionary.html
 |   |-classDiagram.pdf
 |   |-collaboration1.pdf
 |   |-collaboration2.pdf
 |
 |--phase3/
 |   |-crc.html
 |   |-classDiagram.pdf
 |
 |--phase4/
     |-sequenceDiagram1.pdf
     |-sequenceDiagram2.pdf
     |-stateDiagram.pdf