Software Engineering 2 0600-IS1-3IO2
Profile of studies: general academic
Form of studies: full-time / extramural
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 lecture : 15 h
- Attendance at laboratory: 45 h
- Preparation for classes - lecture: 10 h
- Preparation for classes - laboratory: 8 h
- Literature studying: 10 h
- Preparation for exam: 8 h
- Attendance at exam: 2 h
- Attendance at office hours: 3 h
Quantitative indicators:
- Student's workload related to activities that require direct participation of a teacher: 65 h / 2 ECTS
- Student's workload related to practice-oriented activities: 45 / 2 ECTS
Type of course
Requirements
Learning outcomes
- Knows widely-used design patterns. K_W8, K_W12.
- Knows various paradigms related to software development. K_W04
- Is able to determine requirements related to an IT system. K_U22
- Is able to develop a model (fundamental UML diagrams) of an uncomplicated IT system. K_U11, K_U17
- Is able to implement an uncomplicated system based on its model and to test the implementation. K_U06, K_U15
- Is able to write design documentation and end-user documentation. K_U2
- Knows and understands principles of developing complicated software in group.
- Creatively solves problems. K_K05
Methods for assessing learning outcomes (lecture):
- written and oral test
Methods for assessing learning outcomes (laboratory):
- written and spoken report
- written and spoken test
- observation of student performance
Assessment criteria
Form of assessment: exam
Bibliography
Essential bibliography:
- E. Gamma, R. Helm, R. Johnson, J. Vlissides, Wzorce projektowe. Elemeny oprogramowania obiektowego wielokrotnego użytku, Helion, 2010
- B. Burns, "Projektowanie systemów rozproszonych. Wzorce i paradygmaty dla skalowalnych, niezawodnych usług", Helion, 2018
- M. Kleppmann, "Przetwarzanie danych w dużej skali. Niezawodność, skalowalność i łatwość konserwacji systemów", Helion, 2017
- K.P. Birman, "Guide to Reliable Distributed Systems: Building High-Assurance Applications and Cloud-Hosted Services", Springer, 2012
Supplementary readings:
- IEEE, ACM etc. standards and journals
- R.C. Martin, "Czysty kod. Podręcznik dobrego programisty", Helion, 2010
- P. Stevens, "UML inżynieria oprogramowania", Helion, 2007
- S. Wrycza, P. Marcinkowski, K. Wyrzykowski, "Język UML 2.0 w modelowaniu systemów informatycznych", Helion, 2005
- J. Cogswell, "Tworzenie użytecznego oprogramowania", MIKOM, 2005
Additional information
Additional information (registration calendar, class conductors, localization and schedules of classes), might be available in the USOSweb system: