Software Engineering Methods
| Structure Type: | Study unit |
|---|---|
| Code: | ITTS3201 |
| Type: | Optional obligatory / Professional Studies |
| Curriculum: | TT 2018 |
| Level: | Bachelor of Engineering |
| Year of Study: | 3 (2020-2021) |
| Semester: | Spring |
| Credits: | 5 cr |
| Responsible Teacher: | Kankaanpää, Timo |
| Language of Instruction: | Finnish |
Courses During the Academic Year 2020-2021
| Impl. | Group(s) | Study Time | Teacher(s) | Language | Enrolment |
|---|---|---|---|---|---|
| 3001 | TT2018-3, TT2018-3A, TT2018-3B | 2021-01-04 – 2021-05-02 | Timo Kankaanpää | Finnish | 2020-08-17 – 2021-01-10 |
| 3002 | VY-2-ICAT | 2021-01-04 – 2021-05-02 | Timo Kankaanpää | Finnish | 2020-08-17 – 2021-01-10 |
| 3003 | TT2018V-3A | 2020-10-19 – 2021-02-28 | Harri Lehtinen, Timo Kankaanpää | Finnish | 2020-08-17 – 2020-09-11 |
Still need to take the course? See the courses during the academic year 2021-2022.
Learning Outcomes
The student will understand how to support and develop the operations of organizations by means of information systems. The student knows and understands the phases of a software project and the effect of development process models on the management of a software project. The student is able to apply the waterfall model or the agile software development. The student can utilize the essential UML modelling methods and recognizes the specification and design documents of a software project.
Student's Workload
135 h, of which scheduled studies 70 h at VAMK and 48 h at UVA.
Prerequisites / Recommended Optional Courses
Object Oriented Programming.
Contents
Basic skills: How information systems support the objectives of organizations. Software development process phases. Requirements analysis techniques. Requirements identification and prioritization. Software requirements specification documentation. Configuration management. Project management, dividing the software project into tasks. The differences between development process models. Using agile software development in project management (e.g. Scrum). UML use case diagram, class diagram, sequence diagram, and package diagram. Describing use cases. Software design (architectural and module design).
Supplementary skills: Information systems strategy. Mockup tools. Software project management tools. Project plan. UML Activity diagram, State diagram. Functional and technical specification. Design patterns. Version management, product management, quality assurance.
Recommended or Required Reading and Other Learning Resources/Tools
Material on the course Web site. Ohjelmistotuotanto / Ilkka Haikala, Jukka Märijärvi or Ohjelmistotuotannon käytännöt / Ilkka Haikala, Tommi Mikkonen.
Mode of Delivery / Planned Learning Activities and Teaching Methods
Problem-based learning.
Assessment Criteria
Grade 5: The student understands most course concepts and is able to apply them independently in software projects.
Grade 3: The student understands a considerable portion of course concepts and is able to apply them in software projects.
Grade 1: The student understands basic course concepts and is able to apply them in software projects.
Assessment Methods
Continuous assessment, the grade is based on homework exercises, project works and an examination.