Course details

Introduction to Software Engineering

IUS Acad. year 2022/2023 Winter semester 5 credits

Current academic year

Software engineering and software crisis, history and goals of software engineering, characteristics of software products. Life cycle and stages of software development, introduction to key methodologies. Requirement analysis and specification, use case diagrams. Basic principles and modelling techniques of structured analysis and design (DFD, ERD). Basic notions of object-orientation (object, class, abstraction, encapsulation, inheritance, polymorphism). Modelling techniques of object-oriented analysis and design (class diagram, object diagram, design patterns). UML within software development (collaboration diagram, sequence diagram, activity diagram, statechart diagram, OCL). Implementation, verification and validation (black box and white box testing). Agile software development. Introduction to software maintenance. Management of software projects, quality assurance, intellectual property, software engineering code of ethics and professional practice.

5 ECTS credits represent approximately 125-150 hours of study workload. Within IUS, it can be utilized as follows:

  • 39 hours of lectures
  • 8 hours of exercises
  • 12 hours for homework assignment
  • 16 hours for team project
  • 13 hours of continual study
  • 37 hours of study for final exam


Course coordinator

Language of instruction

Czech, English


Credit+Examination (written)

Time span

  • 39 hrs lectures
  • 8 hrs exercises
  • 10 hrs projects

Assessment points

  • 60 pts final exam (written part)
  • 12 pts numeric exercises
  • 16 pts projects
  • 12 pts homework




Course Web Pages

Subject specific learning outcomes and competences

Student gets an overview in the area of complex software system development. Students acquaint especially with software development stages and with models of software life-time. Student makes sense of the methodics basis of the requirements analysis and the software system design. He/she learns to use chosen UML models.

Learning objectives

To provide an overview and basics of the complex software system building. To acquaint with the process of software systems creation. This process is analyzed as an integration of system development, software quality assurance, and software project management. To acquaint with the development stages of the software lifetime. The consideration is focused on all development stages, mainly the requirements analysis, requirements specification, and methods of software design. To learn to use basic models of UML and to get familiarity with methodics of UML-based modelling.

Why is the course taught

Software development is a complex process that often fails. Thus, the main message of this course is to warn students about problems that they as software engineers will face when creating software. Students will learn basic analysis and design techniques for software development and language UML. A special attention is given to identification of data and their relationship that is an essential task of development of any information system.

Prerequisite knowledge and skills

This course takes place in a winter term of the first year of the bachelor's study programme. Thus, we expect that students have the high school level knowledge of using computers.

Study literature

  • Kočí, R., Křena, B.: Úvod do softwarového inženýrství. Studijní opora, VUT v Brně, 2010.
  • Křena, B., Kočí, R.: Zadání a vzorová řešení ER diagramů ze zkoušek. Sbírka úloh. VUT v Brně, 2016.
  • Objektově orientované modelování systémů - učební text : učební text zaměřený na jazyk UML 2.0. VUT v Brně, 2004.
  • Arlow, J., Neustadt, I.: UML2 a unifikovaný proces vývoje aplikací. Computer Press, Brno, 2007. ISBN 978-80-251-1503-9.
  • Daoust, N. UML Requirements Modeling For Business Analysts. Technics Publications, 2012. 268 p. ‎ ISBN 978-1935504245.
  • Wiegers, K., Beatty, J. Software Requirements. Microsoft Press, 2013. 637 p. ISBN: 978-0735679658.
  • Larman, C. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development. 3rd Edition. 736 p. Pearson, 2004. ISBN: 978-0131489066.

Fundamental literature

  • Beck, K. Extrémní programování. Grada, Praha, 2002. ISBN 80-247-0300-9. 
  • Page-Jones, M. Základy objektově orientovaného návrhu v UML. Grada, Praha, 2001. ISBN 80-247-0210-X.
  • Paleta, P. Co programátory ve škole neučí aneb Softwarové inženýrství v reálné praxi. Computer press, 2004. ISBN 80-251-0073-1. 
  • Pezze, M., Young, M. Software Testing and Analysis: Process, Principles, and Techniques. John Wiley & Sons, 2007. ISBN 978-0-471-45593-6. 
  • Richta, K., Sochor, J. Softwarové inženýrství I. Vydavatelství ČVUT, Praha 1996 (dotisk 1998). ISBN 80-01-01428-2.

Syllabus of lectures

  1. Software engineering history, basic notions, the overview of development techniques.
  2. Software lifetime, models of software lifetime.
  3. Requirement analysis, methods of requirements specification, modelling techniques (Use Case Diagram).
  4. Structured analysis and design, methods, modelling techniques. Data-Flow Diagram (DFD) and the Entity-Relationship Diagram (ERD).
  5. Object-oriented analysis and design, methods, modelling techniques. Unified Modelling Language (UML), Class Diagram and Object Diagram.
  6. Chosen modelling means of UML (Activity, Sequence, Communication, and Statechart Diagrams).
  7. Complex modelling with UML.
  8. Design patterns.
  9. Introduction to verification, validation, and testing.
  10. Agile methods of software development, basic principles of extreme programming and prototyping.
  11. Basic principles of software operation and maintenance.
  12. Introduction to software project management.
  13. Software quality, intellectual property rights, Software Engineering Code of Ethics.

Syllabus of numerical exercises

  1. Requirements in UML - Use case diagram, Activity diagram and State diagram (3rd and 4th weeks, 3 points)
  2. Data modelling - ER diagram (from 5th till 7th week, 3 points)
  3. Analysis and Design in UML - Class diagram and Object diagram (from 7th till 9th week, 3 points)
  4. Analysis and Design in UML - Sequence diagram and Communication diagram (from 9th till 11th week, 3 points)

Syllabus - others, projects and individual work of students

  • Individual homework assignment - ER diagram (12 points)
  • Complex model of an information system for the team of students (16 points)


Progress assessment

Students can obtain up to 12 points from four two hours long exercises (3 points from each), 12 points for homework assignment (ER diagram), 16 points from the team project with presentation and up to 60 points from the final exam.

For receiving the credit and thus for entering the exam, students have to get at least 18 points from the exercises, homework assignment and from the project. Plagiarism and not allowed cooperation will cause that involved students are not classified and disciplinary action may be initiated.

The minimal number of points which can be obtained from the final exam is 30. Otherwise, no points will be assigned to a student.

Controlled instruction

Within this course, attendance on the lectures is not monitored. Monday lecture is given for lecture group 1BIA, Thursday lecture for group 1BIB and students from FP. Students from lecture groups 2BIA and 2BIB can choose which lecture they attend. Students can, however, attend the lecture given for the other group without any permission.

The knowledge of students is evaluated within exercises, by homework assignment, by the project and its defence and by the final exam.

Points from the exercises can be obtained only for active participation (mistakes and wrong answers are fine while neither involving into the discussion and problem-solving can result in losing points). When a student cannot attend the exercise and proves it correctly (s)he can either attend the exercise with a different group (please inform the teacher about that) or (s)he can ask for giving the points based on homework assignment (1st and 2nd exercise) or on the project (3rd and 4th exercise) .

Exam prerequisites

For receiving the credit and thus for entering the exam, students have to get at least 18 points from the exercises, homework assignment and from the project. Plagiarism and not allowed cooperation will cause that involved students are not classified and disciplinary action may be initiated.

Course inclusion in study plans

  • Programme BIT, 1st year of study, Compulsory
  • Programme BIT (in English), 1st year of study, Compulsory
  • Programme IT-BC-3, field BIT, 1st year of study, Compulsory
Back to top