Software Engineering

General data

Course ID:	420-ES1-3IO
Erasmus code / ISCED:	11.303 The subject classification code consists of three to five digits, where the first three represent the classification of the discipline according to the Discipline code list applicable to the Socrates/Erasmus program, the fourth (usually 0) - possible further specification of discipline information, the fifth - the degree of subject determined based on the year of study for which the subject is intended. / (0613) Software and applications development and analysis The ISCED (International Standard Classification of Education) code has been designed by UNESCO.
Course title:	Software Engineering
Name in Polish:	Inżynieria oprogramowania
Organizational unit:	Institute of Computer Science
Course groups:
ECTS credit allocation (and other scores):	(not available) Basic information on ECTS credits allocation principles: the annual hourly workload of the student’s work required to achieve the expected learning outcomes for a given stage is 1500-1800h, corresponding to 60 ECTS; the student’s weekly hourly workload is 45 h; 1 ECTS point corresponds to 25-30 hours of student work needed to achieve the assumed learning outcomes; weekly student workload necessary to achieve the assumed learning outcomes allows to obtain 1.5 ECTS; work required to pass the course, which has been assigned 3 ECTS, constitutes 10% of the semester student load. view allocation of credits
Language:	Polish
Type of course:	obligatory courses
Short description:	This subject is aimed at familiarizing students with essential notions, problems, and solutions related to software engineering: - processes and models of the software life-cycle, - approaches to software development and to IT project management, - essentials of using the UML to object-oriented modeling of systems.
Full description:	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): no Number of class hours: - lecture: 30 h - laboratory: 15 h Didactic methods: lecture, presentation, discussion, laboratory classes, project, office hours. ECTS credits: 4 Details of student's workload (activity and number of hours): - Attendance at lecture : 15 x 2 = 30 h - Attendance at laboratory : 15 x 2 = 30 h - Preparation for classes: 15 h - Preparation of report: 10 h - Preparation of presentation: 5 h - Project-related work at home: 15 h - Preparation to exam: 10 h - Attendance at exam: 2 h - Attendance at office hours: 6 h Quantitative indicators: - Student's workload related to activities that require direct participation of a teacher: 66 h / 2,7 ECTS - Student's workload related to practice-oriented activities: 93 h / 4 ECTS
Bibliography:	Essential bibliography: - I. Sommerville, "Inżynieria oprogramowania", PWN, 2020 - Visual Paradigm, Guides to UML, Agile and others, 2020, https://www.visual-paradigm.com/guide/ - P. Bourque, R.E. Fairley, "Guide to the Software Engineering Body of Knowledge (SWEBOK)", Version 3.0, IEEE Computer Society, 2014, https://www.swebok.org - K.E. Wiegers, J. Beatty "Specyfikacja oprogramowania. Inżynieria wymagań", Helion, 2014 Supplementary readings: - OMG, UML 2.5.1 Specification, 2017, https://www.omg.org/spec/UML/2.5.1/PDF - 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
Learning outcomes:	- Knows processes and selected models of the software/system life-cycle. KA6_WG6, KA6_UW9 - Knows selected approaches to to system development and project management. KA6_WG6, KA6_UW9 - Knows essentials of using the UML to object-oriented modeling of systems. KA6_WG3, KA6_WG6, KA6_UW11, KA_UW12 - Is able to determine and document requirements related to an IT system. KA6_WG3, KA6_UW11 - Is able to develop a model (fundamental UML diagrams) of an uncomplicated IT system. KA6_UW9, KA6_UW11, KA6_UW12 - Notices and understands non-technical aspects and consequences of activities of an IT professional. KA6_KK1, KA6_KO1 Methods for assessing learning outcomes (lecture): - written/oral examination Methods for assessing learning outcomes (laboratory classes): - assessing written/spoken reports - observing students during classes
Assessment methods and assessment criteria:	Credit type: examination

This course is not currently offered.

Course descriptions are protected by copyright.
Copyright by University of Bialystok.