Study Guide

Objective

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.

Content

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

Materials

Information about the materials are in Moodle.

Teaching methods

Contact teaching and independent work.

Student workload

3 cu * 27 h/cu = 81 hours, of which around one third is contact teaching and two thirds independent work.

Evaluation scale

1-5

Assessment criteria, satisfactory (1)

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

Assessment criteria, good (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.

Assessment criteria, excellent (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.

Assessment methods and criteria

Activities including case and exam.

Qualifications

No previous studies are required.

Objective

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.

Content

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

Materials

Information about the materials are in Moodle.

Teaching methods

Contact teaching and independent work.

Student workload

3 cu * 27 h/cu = 81 hours, of which around one third is contact teaching and two thirds independent work.

Evaluation scale

1-5

Assessment criteria, satisfactory (1)

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

Assessment criteria, good (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.

Assessment criteria, excellent (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.

Assessment methods and criteria

Activities including case and exam.

Qualifications

No previous studies are required.

Objective

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.

Content

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

Materials

Will be announced at the beginning of the course.

Teaching methods

Lectures, exercises and independent study

Student workload

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

Evaluation scale

1-5

Assessment criteria, satisfactory (1)

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

Assessment criteria, good (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.

Assessment criteria, excellent (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.

Assessment criteria, good (3)

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

Assessment criteria, excellent (5)

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.

Assessment criteria, approved/failed

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.

Qualifications

No previous studies are required.