Opinto-opas

Tavoitteet

Student is familiar with the basic knowledge of the software process. Student knows the different types of software project documentation. Student learns to use software development tools and methods.

Sisältö

Software life cycle models, agile methods, UML-modelling, requirements specification, testing and version control.

Oppimateriaalit

Tiedot käytettävästä materiaalista ovat Moodlessa.

Opetusmenetelmät

Lähiopetus ja itsenäinen työskentely.

Opiskelijan ajankäyttö ja kuormitus

3 op * 27 h/op = 81 tuntia, josta on varattu lähiopetukseen noin kolmasosa ja itsenäiseen työskentelyyn noin kaksi kolmasosaa.

Arviointiasteikko

1-5

Arviointikriteerit, tyydyttävä (1)

Student recognizes UML-models, testing plans and other types of software project documentation. Student knows how to create repository for version control.

Arviointikriteerit, hyvä (3)

Student can write a program from UML-model and is able test program with help of testing plan. Student is also able to write other types of software project documentation. Student is able to keep project's files updated with version control system.

Arviointikriteerit, kiitettävä (5)

Student can design and apply UML-models, testing plans and other types of software documentation for software project. Student is able to fork another student's projects with version control system.

Arviointimenetelmät ja arvioinnin perusteet

Aktiviteetit mukaanlukien case ja tentti.

Esitietovaatimukset

No previous studies are required.

Tavoitteet

Student is familiar with the basic knowledge of the software process. Student knows the different types of software project documentation. Student learns to use software development tools and methods.

Sisältö

Software life cycle models, agile methods, UML-modelling, requirements specification, testing and version control.

Oppimateriaalit

Tiedot käytettävästä materiaalista ovat Moodlessa.

Opetusmenetelmät

Lähiopetus ja itsenäinen työskentely.

Opiskelijan ajankäyttö ja kuormitus

3 op * 27 h/op = 81 tuntia, josta on varattu lähiopetukseen noin kolmasosa ja itsenäiseen työskentelyyn noin kaksi kolmasosaa.

Arviointiasteikko

1-5

Arviointikriteerit, tyydyttävä (1)

Student recognizes UML-models, testing plans and other types of software project documentation. Student knows how to create repository for version control.

Arviointikriteerit, hyvä (3)

Student can write a program from UML-model and is able test program with help of testing plan. Student is also able to write other types of software project documentation. Student is able to keep project's files updated with version control system.

Arviointikriteerit, kiitettävä (5)

Student can design and apply UML-models, testing plans and other types of software documentation for software project. Student is able to fork another student's projects with version control system.

Arviointimenetelmät ja arvioinnin perusteet

Aktiviteetit mukaanlukien case ja tentti.

Esitietovaatimukset

No previous studies are required.

Tavoitteet

Student is familiar with the basic knowledge of the software process. Student knows the different types of software project documentation. Student learns to use software development tools and methods.

Sisältö

Software life cycle models, agile methods, UML-modelling, requirements specification, testing and version control.

Oppimateriaalit

Will be announced at the beginning of the course.

Opetusmenetelmät

Lectures, exercises and independent study

Opiskelijan ajankäyttö ja kuormitus

80 h, of which scheduled studies 28 h and autonomous studies 52 h

Arviointiasteikko

1-5

Arviointikriteerit, tyydyttävä (1)

Student recognizes UML-models, testing plans and other types of software project documentation. Student knows how to create repository for version control.

Arviointikriteerit, hyvä (3)

Student can write a program from UML-model and is able test program with help of testing plan. Student is also able to write other types of software project documentation. Student is able to keep project's files updated with version control system.

Arviointikriteerit, kiitettävä (5)

Student can design and apply UML-models, testing plans and other types of software documentation for software project. Student is able to fork another student's projects with version control system.

Arviointikriteerit, tyydyttävä (1-2)

Student recognizes UML-models, testing plans and other types of software project documentation. Student knows how to create repository for version control.

Arviointikriteerit, hyvä (3-4)

Student can write a program from UML-model and is able test program with help of testing plan. Student is also able to write other types of software project documentation. Student is able to keep project's files updated with version control system.

Arviointikriteerit, kiitettävä (5)

Student can design and apply UML-models, testing plans and other types of software documentation for software project. Student is able to fork another student's projects with version control system.

Esitietovaatimukset

No previous studies are required.