Software Engineering 1 510-IS1-2IO1-23
Profile of studies: general academic
Form of studies: full-time
Course type: obligatory
Field and discipline of science: exact and natural sciences, computer science
Year of studies/semester: 2 / 4
Preliminary requirements (so-called sequential system of classes and examinations): ---
Number of class hours:
- lecture: 30 h
Didactic methods: lecture, presentation, discussion, office hours.
ECTS credits: 2
Details of student's workload (activity and number of hours):
- Attendance at classes:
- - lecture : 30 h
- Literature studying: 10 h
- Preparation for exam: 7 h
- Attendance at exam: 2 h
- Attendance at office hours: 1 h
Quantitative indicators:
- Student's workload related to activities that require direct participation of a teacher: 33 h / 1.3 ECTS
- Student's workload related to activities that do not require direct participation of a teacher: 17 h / 0.7 ECTS
Type of course
Mode
(in Polish) zdalnie
Course coordinators
Learning outcomes
- Knows processes and selected models of the software/system life-cycle. KP6_WG12, KP6_WG5
- Knows selected approaches to to system development and project management. KP6_WG12, KP6_UW15, KP6_UW17
- Knows essentials of using the UML to object-oriented modeling of systems. KP6_WG4, KP6_WG8, KP6_UW15
- Understands the necessity for continuously improving his/her skills. KP6_UU1
- Notices and understands non-technical aspects and consequences of activities of an IT professional. KP6_KO1
Assessment criteria
Credit type: graded
Rules of AI usage v.25.09.29
Students can use AI systems only to the extent permitted by law acts adopted by the University and Faculty, to automatize mechanic actions that require nether creative nor critical thinking, and that do not require understanding processes and technologies.
Students are prohibited from using AI to do tasks that aim to develop students' creativity, skills and knowledge, that should be solved without automatization in order to ensure the learning outcomes.
Questions and doubts about AI usage should be communicated to the teacher.
Bibliography
Essential bibliography:
- I. Sommerville, "Inżynieria oprogramowania", PWN, 2020
- P. Bourque, R.E. Fairley, "Guide to the Software Engineering Body of Knowledge (SWEBOK Guide)", Version 3.0, IEEE Computer Society, 2014, available on-line [https://www.computer.org/education/bodies-of-knowledge/software-engineering]
- J. Werewka, "Wybrane zagadnienia zarządzania projektami w przedsiębiorstwach Informatycznych", Wyd. AGH, 2013, available on-line [https://www.researchgate.net/profile/Jan-Werewka]
- S. Wrycza, P. Marcinkowski, K. Wyrzykowski, "Język UML 2.0 w modelowaniu systemów informatycznych", Helion, 2005
Supplementary readings:
- K.E. Wiegers, J. Beatty "Specyfikacja oprogramowania. Inżynieria wymagań", Helion, 2014
- OMG, "Unified Modeling Language (UML), Version 2.5.1", 2017, available on-line [https://www.omg.org/spec/UML]
- H. Kniberg, M. Skarin, "Kanban and Scrum: Making the Most of Both", InfoQ, 2009, available on-line [https://www.infoq.com/minibooks/kanban-scrum-minibook/]
- R.C. Martin, "Czysty kod. Podręcznik dobrego programisty", Helion, 2010
Additional information
Additional information (registration calendar, class conductors, localization and schedules of classes), might be available in the USOSweb system: