(in Polish) Software Engineering 2 510-IS1-3IO2-23-ENG
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: 3 / 5
Preliminary requirements (so-called sequential system of classes and examinations): Software engineering 1
Number of class hours:
- lecture: 15 h
- laboratory classes: 45 h
Didactic methods: lecture, presentation, discussion, laboratory, project.
ECTS credits: 4
Details of student's workload (activity and number of hours):
- Attendance at classes:
- - lecture : 15 h
- - laboratory: 45 h
- Preparation for classes:
- - laboratory: 5 h
- Literature studying: 10 h
- Student's own works on computer programs, projects, reports, presentations, homeworks: 10 h
- Preparation for exam: 8 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: 67 h / 2.7 ECTS
- Student's workload related to activities that do not require direct participation of a teacher: 33 h / 1.3 ECTS
Type of course
Mode
(in Polish) w sali
Course coordinators
Learning outcomes
- Knows widely-used design patterns. KP6_WG8, KP6_WG12, KP6_UW15
- Knows various paradigms related to software development. KP6_WG4, KP6_WG5, KP6_WG8
- Is able to determine requirements related to an IT system. KP6_KO1, KP6_UU1
- Is able to develop a model (fundamental UML diagrams) of an uncomplicated IT system. KP6_UW6, KP6_UW11, KP6_UW15, KP6_UK3
- Is able to implement an uncomplicated system based on its model and to test the implementation. KP6_UW8, KP6_UW7, KP6_UW15, KP6_UW17
- Is able to write design documentation and end-user documentation. KP6_UK2, KP6_UK3
- Knows and uses principles of developing complicated software in group. KP6_UO2, KP6_UO1
Assessment criteria
Credit type: examination
Students cannot be examined before passing the laboratory/exercises.
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.
Additional information
Additional information (registration calendar, class conductors, localization and schedules of classes), might be available in the USOSweb system: