Study Guide

Objective

After completing the course the student can:
Describe different software development methodologies and evaluate their feasibility to software projects
Describe software development project phases
Understand and draw UML diagrams
Understand the importance of specification and planning to software development
Work in different phases of a software project

Content

Software development project
Specification, planning, programming, testing, deployment, and maintenance of a software project
UML modelling

Materials

Session slides and material, tools for every student (Git, Jira, Adobe XD etc.), required tools for your project (e.g. Visual Studio Code etc.). No reading material.

Teaching methods

In the study module, students will practice operating at the separate stages of the software project.
A software project is carried out from beginning to end in the group as an exercise: project planning, designing the software, programming of the software, testing and publishing.

International connections

A software project as a group work with Scrum method and 2 week Sprints.
Weekly teaching sessions and exercises guide students in software project tasks as well as help in developing their own software in the group.

Student workload

5 credit units in total, multiplied with 27 hours = 135 hours / student. The course runs about 14 weeks, which means that weekly studying hours are roughly 10 hours / week of which common sessions 2-3 hours / week and group work 7-8 hours / week.

Content scheduling

After the course, the student
- knows software project models and can estimate their suitability for the project at hand
- can operate at different stages of the software project
- understands the significance of planning, designing and testing in the software project
- is able to create software specifications (models with UML) and UI prototypes
- is able to exploit version management (Git) in cooperation with others
- is able to manage Atlassian Jira Software tool for running Sprints and managing software requirements

Further information

Prerequisites are basic programming skills with some language. Students develop a software as a group work, yet coding and programming is not the topic of the teaching sessions.

Traditionally, group works have been developed for real clients and user needs.
Customers act as Product Owners in the project.

Evaluation scale

H-5

Assessment methods and criteria

Grading with scale 0-5.

Group work is 60 % of the grade. To pass the course you need to pass the group work i.e. get at least half of the total points.
- Each sprint is evaluated with 0-2 points. There will be 6 Sprints in total. Passing the group work = min. 6 points.
- Sprint review, for example, 2 points (all tasks done in time, as requested, no weaknesses), 1 point (some shortcomings/omissions in answers), 0 point (not in time, some tasks missing, major faults).
- Points = Grade: 0-5 points = Failed; 6-8 points = 1; 9-10 points = 2; 11-12 points = 3 i.e. with the group work only, a student can get grade 3.

Active presence and/or returning exercises during the teaching session is 40 % of the grade.
- 1 point / session available, which is based on either presence or exercise returns during the session.
- With participating in sessions, a student can get 0-2 grades more on top of the group work grade
- Points = Grade: < 50% of total points = 0; 50-74% of total points = +1; 75-100% of total points = +2