Software Engineering and ModellingLaajuus (5 cr)
Code: TE00BR84
Credits
5 op
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
Enrollment
01.06.2024 - 16.09.2024
Timing
02.09.2024 - 18.12.2024
Number of ECTS credits allocated
5 op
Mode of delivery
Contact teaching
Unit
Engineering and Business
Campus
Kupittaa Campus
Teaching languages
- Finnish
- English
Degree programmes
- Degree Programme in Information and Communication Technology
- Degree Programme in Business Information Technology
- Degree Programme in Information and Communications Technology
Teachers
- Sami Pyöttiälä
Groups
-
PTIETS22sepmPTIETS22 Software Engineering and Project Management
-
PTIVIS22OSoftware Engineering and Project Management
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
Lecture slides, material in Itslearning, linked web-based material and several local and remote applications
Teaching methods
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
Exam schedules
There are no actual exams.
International connections
Using the existing devices, existing software and activity in the campus building in which the students already are with the high probability.
Completion alternatives
There is only one way of completion.
Student workload
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
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 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
Further information
An oral communication is used during the classes. For the written communication Itslearning and e-mail are applied.
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: 0 points = 0 grade, half of the points = 1 grade, max points = 2 grades (and linearly between the lower and the upper bounds)
Assessment criteria, fail (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.
Assessment criteria, satisfactory (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.
Assessment criteria, good (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.
Assessment criteria, excellent (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.
Enrollment
26.07.2023 - 14.09.2023
Timing
04.09.2023 - 08.12.2023
Number of ECTS credits allocated
5 op
Mode of delivery
Contact teaching
Unit
Engineering and Business
Campus
Kupittaa Campus
Teaching languages
- Finnish
Seats
40 - 75
Teachers
- Sami Pyöttiälä
Groups
-
PTIVIS21OSoftware Engineering and Project Management
-
PTIETS21sepmPTIETS21 Software engineering and Project Management
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
Student workload
135 hours
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
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
Enrollment
01.06.2022 - 04.09.2022
Timing
29.08.2022 - 22.12.2022
Number of ECTS credits allocated
5 op
Mode of delivery
Contact teaching
Unit
Engineering and Business
Campus
Kupittaa Campus
Teaching languages
- Finnish
- English
Degree programmes
- Degree Programme in Information and Communication Technology
- Degree Programme in Information and Communications Technology
Teachers
- Kimmo Tarkkanen
- Sanna Määttä
Teacher in charge
Kimmo Tarkkanen
Groups
-
PTIVIS20OSoftware engineering and Project Management
-
PTIETS20sepmPTIETS20 Software engineering and Project Management
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