Administracja Centralna Uczelni - Wymiana międzynarodowa (S2)
Sylabus przedmiotu Software engineering:
Informacje podstawowe
| Kierunek studiów | Wymiana międzynarodowa | ||
|---|---|---|---|
| Forma studiów | studia stacjonarne | Poziom | drugiego stopnia |
| Tytuł zawodowy absolwenta | |||
| Obszary studiów | — | ||
| Profil | |||
| Moduł | — | ||
| Przedmiot | Software engineering | ||
| Specjalność | przedmiot wspólny | ||
| Jednostka prowadząca | Katedra Inżynierii Oprogramowania | ||
| Nauczyciel odpowiedzialny | Łukasz Radliński <lradlinski@zut.edu.pl> | ||
| Inni nauczyciele | |||
| ECTS (planowane) | 4,0 | ECTS (formy) | 4,0 |
| Forma zaliczenia | zaliczenie | Język | angielski |
| Blok obieralny | — | Grupa obieralna | — |
Formy dydaktyczne
Wymagania wstępne
| KOD | Wymaganie wstępne |
|---|---|
| W-1 | Basic knowledge and skills in object-oriented programming. |
Cele przedmiotu
| KOD | Cel modułu/przedmiotu |
|---|---|
| C-1 | Possess knowledge and obtain practical skills in software requirements engineering and designing. |
| C-2 | Usage of techniques and tools for development process where outcomes from one stage flow to subsequent stages. |
| C-3 | Practicing individual and team-based work in a software project. |
Treści programowe z podziałem na formy zajęć
| KOD | Treść programowa | Godziny |
|---|---|---|
| laboratoria | ||
| T-L-1 | Introduction to requirements engineering and software designing | 1 |
| T-L-2 | Gathering customer/user requirements | 1 |
| T-L-3 | Writing user and system specifications | 3 |
| T-L-4 | Software analysis and modelling | 4 |
| T-L-5 | Software designing – architectural and design patterns | 3 |
| T-L-6 | Data design, user interface wireframing and design, processing design, prototyping | 3 |
| 15 | ||
| projekty | ||
| T-P-1 | Creating documentation with requirements specification and software design | 15 |
| 15 | ||
| wykłady | ||
| T-W-1 | Introduction to requirements engineering and software designing | 2 |
| T-W-2 | Gathering customer/user requirements | 1 |
| T-W-3 | Writing user and system specifications | 2 |
| T-W-4 | Software analysis and modelling | 4 |
| T-W-5 | Software designing – architectural and design patterns | 3 |
| T-W-6 | Data design, user interface wireframing and design, processing design, prototyping | 2 |
| T-W-7 | Introduction to validation and verification | 1 |
| 15 | ||
Obciążenie pracą studenta - formy aktywności
| KOD | Forma aktywności | Godziny |
|---|---|---|
| laboratoria | ||
| A-L-1 | preparing for lab classes | 3 |
| A-L-2 | participation in lab classes | 15 |
| A-L-3 | completing lab exercises at home | 7 |
| A-L-4 | preparing for credits | 3 |
| A-L-5 | consulting during office hours | 2 |
| 30 | ||
| projekty | ||
| A-P-1 | working on project tasks | 15 |
| A-P-2 | completing a project at home | 40 |
| A-P-3 | consulting a project during office hours | 5 |
| 60 | ||
| wykłady | ||
| A-W-1 | participation in lectures | 15 |
| A-W-2 | literature reading | 7 |
| A-W-3 | preparing for credit | 7 |
| A-W-4 | taking part in credit | 1 |
| 30 | ||
Metody nauczania / narzędzia dydaktyczne
| KOD | Metoda nauczania / narzędzie dydaktyczne |
|---|---|
| M-1 | Informative lecture with demonstration |
| M-2 | Lab exercises |
| M-3 | Project |
Sposoby oceny
| KOD | Sposób oceny |
|---|---|
| S-1 | Ocena podsumowująca: Individual exercises |
| S-2 | Ocena podsumowująca: Individual or group project |
| S-3 | Ocena podsumowująca: Test with open questions |
Zamierzone efekty kształcenia - wiedza
| Zamierzone efekty kształcenia | Odniesienie do efektów kształcenia dla kierunku studiów | Odniesienie do efektów zdefiniowanych dla obszaru kształcenia | Cel przedmiotu | Treści programowe | Metody nauczania | Sposób oceny |
|---|---|---|---|---|---|---|
| WM-WI_2-_null_W01 Explains main terms in requirements engineering and designing | — | — | C-1 | T-W-3, T-W-2, T-W-6, T-W-5, T-W-1, T-W-4, T-W-7 | M-1 | S-3 |
| WM-WI_2-_null_W02 Describes process and techniques used in requirements engineering and designing | — | — | C-1 | T-W-3, T-W-2, T-W-6, T-W-5, T-W-1, T-W-4, T-W-7 | M-1 | S-3 |
Zamierzone efekty kształcenia - umiejętności
| Zamierzone efekty kształcenia | Odniesienie do efektów kształcenia dla kierunku studiów | Odniesienie do efektów zdefiniowanych dla obszaru kształcenia | Cel przedmiotu | Treści programowe | Metody nauczania | Sposób oceny |
|---|---|---|---|---|---|---|
| WM-WI_2-_null_U01 Can create software requirements specification | — | — | C-2, C-3, C-1 | T-L-3, T-L-4, T-L-2, T-L-1, T-P-1 | M-3, M-2 | S-1, S-2, S-3 |
| WM-WI_2-_null_U02 Can design software architecture and user interface | — | — | C-2, C-3, C-1 | T-L-4, T-L-5, T-L-6, T-P-1 | M-3, M-2 | S-1, S-2, S-3 |
Zamierzone efekty kształcenia - inne kompetencje społeczne i personalne
| Zamierzone efekty kształcenia | Odniesienie do efektów kształcenia dla kierunku studiów | Odniesienie do efektów zdefiniowanych dla obszaru kształcenia | Cel przedmiotu | Treści programowe | Metody nauczania | Sposób oceny |
|---|---|---|---|---|---|---|
| WM-WI_2-_null_K01 Ability to communicate with non-technical people | — | — | C-3, C-1 | T-L-3, T-L-4, T-L-2, T-L-1, T-L-5, T-L-6, T-P-1 | M-3, M-1, M-2 | S-1, S-2, S-3 |
Kryterium oceny - wiedza
| Efekt kształcenia | Ocena | Kryterium oceny |
|---|---|---|
| WM-WI_2-_null_W01 Explains main terms in requirements engineering and designing | 2,0 | |
| 3,0 | Student explains majority of main terms in requirements engineering and designing | |
| 3,5 | ||
| 4,0 | ||
| 4,5 | ||
| 5,0 | ||
| WM-WI_2-_null_W02 Describes process and techniques used in requirements engineering and designing | 2,0 | |
| 3,0 | Student briefly describes majority of process elements and main techniques used in requirements engineering and designing | |
| 3,5 | ||
| 4,0 | ||
| 4,5 | ||
| 5,0 |
Kryterium oceny - umiejętności
| Efekt kształcenia | Ocena | Kryterium oceny |
|---|---|---|
| WM-WI_2-_null_U01 Can create software requirements specification | 2,0 | |
| 3,0 | Student can use software tools to create software requirements specification with main elements correctly defined | |
| 3,5 | ||
| 4,0 | ||
| 4,5 | ||
| 5,0 | ||
| WM-WI_2-_null_U02 Can design software architecture and user interface | 2,0 | |
| 3,0 | Student can use software tools to design software architecture and user interface with main elements correctly defined | |
| 3,5 | ||
| 4,0 | ||
| 4,5 | ||
| 5,0 |
Kryterium oceny - inne kompetencje społeczne i personalne
| Efekt kształcenia | Ocena | Kryterium oceny |
|---|---|---|
| WM-WI_2-_null_K01 Ability to communicate with non-technical people | 2,0 | |
| 3,0 | Student can communicate with non-technical people to prepare and present requirements specification and selected elements of software design | |
| 3,5 | ||
| 4,0 | ||
| 4,5 | ||
| 5,0 |
Literatura podstawowa
- Bruegge B., Dutoit A.H., Object-Oriented Software Engineering Using UML, Patterns and Java, Prentice Hall, 2009, 3rd edition
- Larman C., Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, Prentice Hall, 2004, 3rd Edition
Literatura dodatkowa
- Freeman E., Bates B., Sierra K., Robson E., Head First Design Patterns, O'Reilly Media, 2004
- Wiegers K., Beatty J., Software Requirements, Microsoft Press, 2013, 3rd Edition