Study Guide

Learning outcomes

Student is able to
- define, implement and report an iterative project
- act in different roles of a software development project
- implement a HTML user interface following the design
- implement the business logic of a web application
- programmatically parse required data from a structured data set

Implementation and methods of teaching

Development project done in small groups to solve a given development task.

Timing and attendance

Most of the course work is done at times best suitable for the group members. Few compulsory sessions exist, the dates and times will be communicated in course Moodle page. Students are responsible in following these instructions.
Rough schedule/timing (subject to changes):
Week 38 Kick off, all students MUST participate. Check exact time from schedule!
Weeks 38 - 40: Project plan
Week 40: Project plan wrap up + kick off for the project work (compulsory for all students to participate)
Weeks 40 - 50 : Iterative project work in teams
Week 50: Final presentations to teacher, all group members MUST be present at session

Alternative completion methods

Similar project done and documented elsewhere.

Learning environment

Material & task with project timing delivered through Moodle.

Contents

Practical project work that utilizes tools, skills and methods learned on the two other courses in the same module.

Additional information for students: previous knowledge etc.

Basic programming skills: Passed or simultaneously participating an introductory programming course
Basic web technologies: HTML, CSS.

Assessment criteria

Group and personal performance in the project work, peer assessment & teacher assessment.
Grade 0 - 5

Evaluation is based on the observations of the supervisors made during the project and on the quality of the produced artifact.
First the whole group work is assessed on scale 0 - 5. This assessment considers with equal weights the technical performance and the metaskills of the group. The metaskills include, for example, project coordination, project reporting, following the plan and the progress, group behaviour when problems occur, share of roles and work within the group, internal and external communication and ability to present group work and products. The technical part of the assessment looks at the ability to make decisions between different technologies, mastering design methods and tools, documentation of the design and the product, selecting and mastering the tools and methods, version control, structure and quality of the program code and usability and maintainability of the application. The group evaluation form the basis for the individual assessment.
The individual assessment takes the group assessent as the basis and the individual performance can upgrade or downgrade it. Assessement is based on the peer assessment done between the group members, the role picked up by the student and commitment to take care of the corresponding tasks, activity as a member of the group and personal performance in the group presentation. In individual assessment also all those group assessment criteria are considered where the student individual commitment can be separated and observed.

Assessment scale

1-5

Failed (0)

Student did not properly participate in group work or did not show skills and knowledge required to project work

Assessment criteria: level 1 (assessment scale 1–5)

Student has participated in group work only partially OR the project work did not meet the minimum requirements but the student has been active in trying to help the group meet the requirements on the whole

Assessment criteria: level 3 (assessment scale 1–5)

The group result exceeds the minimum technical requirements and the role of the student in project group work has been equal or greater than that of the other students

Assessment criteria: level 5 (assessment scale 1–5)

The group result exceeds the minimum technical requirements in large scale and the role of the student in project group work has been very significant for the project group work