University of Warsaw - Central Authentication System
Strona główna

Software engineering

General data

Course ID: 1000-214bIOP
Erasmus code / ISCED: 11.302 Kod klasyfikacyjny przedmiotu składa się z trzech do pięciu cyfr, przy czym trzy pierwsze oznaczają klasyfikację dziedziny wg. Listy kodów dziedzin obowiązującej w programie Socrates/Erasmus, czwarta (dotąd na ogół 0) – ewentualne uszczegółowienie informacji o dyscyplinie, piąta – stopień zaawansowania przedmiotu ustalony na podstawie roku studiów, dla którego przedmiot jest przeznaczony. / (0612) Database and network design and administration 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: Faculty of Mathematics, Informatics, and Mechanics
Course groups: Obligatory courses for 2nd grade Computer Science
Obligatory courses for 2nd grade JSIM (3I+4M)
Obligatory courses for 3rd grade JSIM (3M+4I)
Course homepage: http://moodle.mimuw.edu.pl
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
Main fields of studies for MISMaP:

computer science

Type of course:

obligatory courses

Requirements:

Individual programming project 1000-222bIPP

Prerequisites:

Databases 1000-213bBAD
Object-oriented programming 1000-212bPO

Short description: (in Polish)

Zasady tworzenia oprogramowania w projektach programistycznych. Omówienie wybranych praktyk i narzędzi wspierających wytwarzanie oprogramowania.

Full description: (in Polish)

Projekt informatyczny.

Architektura.

Funkcjonalność.

Wzorce.

Specyfikacja.

Jakość.

Planowanie.

Zarządzanie konfiguracją.

Metodyki.

Praca w grupie.

Bibliography:

1. E.Yourdon, Death March

2. T.DeMarco, The Deadline

3. I.Sommerville, Software Engineering

4. S.McConnell, Code Complete

5. H.Takeuchi, I.Nonaka, The new product development game (article)

6. W.W.Royce, Managing development of large software systems (article)

7. M.Shaw, D.Garlan, Software Architecture

8. E.Gamma, R.Helm, R.Johnson, J.Vlissides, Design patterns

Learning outcomes:

Must have:

- Can determine development processes specific to manufactured system

- Can design (model) architecture for the system being manufactured

- Can design (model) functionality for the system being manufactured

- Can (measurably) define the quality expectations of the system being manufactured

- Can plan a software project in respect to development processes

- Can plan a software project in respect to supporting tools

- Can manage configuration, manage changes, build releases

Nice to have:

- Is able to manage small software project

- Is able to identify and select patterns (design, architectural, analytical) adequate to a given project

- Is able to identify and select methodologies (development, management) adequate to a given project

- Is able to coordinate a small programming team

This course is not currently offered.
Course descriptions are protected by copyright.
Copyright by University of Warsaw.
Krakowskie Przedmieście 26/28
00-927 Warszawa
tel: +48 22 55 20 000 https://uw.edu.pl/
contact accessibility statement USOSweb 7.0.3.0 (2024-03-22)