Software Engineering Methods
Rakennetyyppi: | Opintojakso |
---|---|
Koodi: | TT00BI76 |
OPS: | TT V2022 |
Taso: | Insinööri (AMK) |
Opiskeluvuosi: | 3 (2024-2025) |
Lukukausi: | Kevät |
Laajuus: | 5 op |
Vastuuopettaja: | Kankaanpää, Timo |
Opetuskieli: | Suomi |
Toteutukset lukuvuonna 2024-2025
Tot. | Ryhmä(t) | Opiskeluaika | Opettaja(t) | Kieli | Ilmoittautuminen |
---|---|---|---|---|---|
3001 | TT2022-3, TT2022-3A, TT2022-3B, VY-2, VY-3 | 7.1.2025 – 30.4.2025 | Juha Papula | Suomi | 1.12.2024 – 13.1.2025 |
3002 | TT2022V-3, TT2022V-3A | 7.1.2025 – 17.5.2025 | Harri Sten | Suomi | 1.12.2024 – 13.1.2025 |
3003 | IT2022-3, IT2022-3A | 7.1.2025 – 30.4.2025 | Juha Papula | Suomi | 1.12.2024 – 13.1.2025 |
Osaamistavoitteet
The student will understand how to support and develop the operations of organizations by means of information systems. The student knows and understands the agile software process and learns the main activities (analysis, design, implementation, testing, deployment) as iterative and incremental process. The student understands the importance of identifying and managing the changing customer requirements and how the software process effect of the agility of the organisation. Student learns the most used languages for software analysis and design(UML). The results of the design are used for architecture and module design and for test driven development. Also the most common design patterns used for progressive web application front end and microservice back end will be discussed.
Opiskelijan työmäärä
135 h, of which 50 hours of scheduled contact teaching.
Edeltävät opinnot / Suositellut valinnaiset opinnot
Object oriented programming, Databases and open interfaces, Frond-end development,
Sisältö
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.
Opiskelumateriaali
Material on the course Web site.
Opetusmuoto / Opetusmenetelmät
Problem-based learning.
Arviointikriteerit
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.
Arviointimenetelmät
Weekly assignments 30%, weekly quizzes 30% team based project work 40%.