Software Engineering Methods
| Rakennetyyppi: | Opintojakso |
|---|---|
| Koodi: | IITS2002 |
| Tyyppi: | Pakollinen valinnainen (vaihtoehtoinen) / Ammattiopinnot |
| OPS: | IT 2017 |
| Taso: | Insinööri (AMK) |
| Opiskeluvuosi: | 3 (2019-2020) |
| Laajuus: | 5 op |
| Vastuuopettaja: | Moghadampour, Ghodrat |
| Opetuskieli: | Englanti |
Toteutukset lukuvuonna 2019-2020
| Tot. | Ryhmä(t) | Opiskeluaika | Opettaja(t) | Kieli | Lähiop. | Ilmoittautuminen |
|---|---|---|---|---|---|---|
| 2 | I-IT-3N | 7.1.2020 – 24.4.2020 | Timo Kankaanpää | Englanti | 54 h | 16.12.2019 – 14.1.2020 |
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 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.
Opiskelijan työmäärä
135 h, of which scheduled contact studies 70 h.
The assessment of student’s own learning 1 h is included in contact lessons.
Edeltävät opinnot / Suositellut valinnaiset opinnot
Object Oriented Programming.
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
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.
Arviointimenetelmät
Continuous assessment, the grade is based on homework exercises, project works and an examination.