Opinto-opas

Tavoitteet

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

Sisältö

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

Oppimateriaalit

Lecture slides, material in Itslearning, linked web-based material and several local and remote applications

Opetusmenetelmät

Learning by doing: Attendance concerning the classes, doing assignments during the classes and homework and the sprint-based project work in small groups by applying Scrum

Tenttien ajankohdat ja uusintamahdollisuudet

There are no actual exams.

Pedagogiset toimintatavat ja kestävä kehitys

Using the existing devices, existing software and activity in the campus building in which the students already are with the high probability.

Toteutuksen valinnaiset suoritustavat

There is only one way of completion.

Opiskelijan ajankäyttö ja kuormitus

Classes 40 hours, assignments during the classes and personal homework and studying (35 hours), project work in small groups (60 hours) with reporting in Itslearning, total 135 hours

Sisällön jaksotus

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 apply version management (Git) in cooperation with others
- is able to apply Atlassian Jira Software tool for planning tasks, running Sprints and managing software requirements

Viestintäkanava ja lisätietoja

An oral communication is used during the classes. For the written communication Itslearning and e-mail are applied.

Arviointiasteikko

H-5

Arviointimenetelmät ja arvioinnin perusteet

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: 0 points = 0 grade, half of the points = 1 grade, max points = 2 grades (and linearly between the lower and the upper bounds)

Hylätty (0)

The student does not know how the knowledge or the methods or is not able to apply them on the level required in the criterion for grade of level 1-2.

Arviointikriteerit, tyydyttävä (1-2)

The student knows the basic concept of software engineering and knows some of the common design and planning methods of the discipline. The student is able to apply the knowledge and the methods in the simple given context. The student achieves the lower boundary of the points for the grade level concerning the course.

Arviointikriteerit, hyvä (3-4)

The student knows the basic concept of software engineering with its fundamental properties and knows all the common design and planning methods of the discipline. The student is able to apply the knowledge and the methods in the given context. The student achieves the lower boundary of the points for the grade level concerning the course.

Arviointikriteerit, kiitettävä (5)

The student knows the basic concept of software engineering with its fundamental properties and knows all the common design and planning methods of the discipline with the sovereign manners. The student is able to apply the knowledge and the methods in the any given context. The student achieves the lower boundary of the points for the grade level concerning the course.