Skip to main content

Modern software development (5 cr)

Code: TT00CC52-3006

General information


Enrollment
19.08.2024 - 22.09.2024
Registration for the implementation has ended.
Timing
01.08.2024 - 31.12.2024
Implementation has ended.
Number of ECTS credits allocated
5 cr
Local portion
5 cr
Mode of delivery
Contact learning
Unit
Teknologia
Teaching languages
Finnish
Degree programmes
Bachelor’s Degree in Information and Communication Technology
Teachers
Jaakko Vanhala
Groups
TTM24SAI
TTM24SAI
Course
TT00CC52

Realization has 11 reservations. Total duration of reservations is 33 h 0 min.

Time Topic Location
Wed 28.08.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Teams opetus
Wed 04.09.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Itsenäinen työskentely ohjeistuksen mukaan
Wed 11.09.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Teams opetus
Wed 18.09.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Teams opetus
Wed 25.09.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Teams opetus
Wed 02.10.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Teams opetus
Wed 09.10.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Teams opetus
Wed 23.10.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Teams opetus
Wed 06.11.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Teams opetus
Thu 21.11.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Teams opetus
Thu 05.12.2024 time 17:00 - 20:00
(3 h 0 min)
Nykyaikainen ohjelmistokehitys TT00CC52-3006
Teams opetus
Changes to reservations may be possible.

Objective

Students will understand the different stages of software projects from specifications to testing. They will be able to use the required software and tools that are typically needed in agile project work.

Content

- Agile software development
- Requirement specifications and testing
- The aim and basic principles of version management
- Version management software
- Project version management and making modular versions
- Project change management
- Unit testing and test automation
- Time tracking
- Documentation and learning diaries in Markdown language
- UML: Class, Use Case and Activity diagrams
- Docker containers

Evaluation scale

0 - 5

Assessment criteria, excellent (5)

The students are able to apply their skills independently and use a variety of information to solve problems. They understand the various stages of a software and game project and can apply this knowledge in practice. The students are proficient in the use of version management. The student is able to model a system with UML Use Case and Activity diagrams.

Assessment criteria, good (3)

The students are able to select ways of working suitable for a game project based on acquired information and guidelines.
They are proficient in version management.
They work independently and responsibly in different tasks according to given instructions.

Assessment criteria, satisfactory (1)

The students know how to work in an appropriate manner under supervision, following given rules and instructions. They use appropriate software and tools for version management.

Objective

Students will understand the different stages of software projects from specifications to testing. They will be able to use the required software and tools that are typically needed in agile project work.

Execution methods

Lähiopetus: luennot ja harjoituskerrat

Accomplishment methods

Lectures
Assignments
Project work
Learning diary

Content

- Agile software development
- Requirement specifications and testing
- The aim and basic principles of version management
- Version management software
- Project version management and making modular versions
- Project change management
- Unit testing and test automation
- Time tracking
- Documentation and learning diaries in Markdown language
- UML: Class, Use Case and Activity diagrams
- Docker containers

Go back to top of page