Introduction to Software Engineering
IUS Acad. year 2020/2021 Winter semester 5 credits
5 ECTS credits represent approximately 125-150 hours of study workload. Within IUS, it can be utilized as follows:
- 39 hours of lectures
- 6 hours of exercises
- 30 hours of project work
- 15 hours of continual study
- 35 hours of study for final exam
Language of instruction
Course Web Pages
Subject specific learning outcomes and competences
Generic learning outcomes and competences
Why is the course taught
Prerequisite kwnowledge and skills
- Kočí, R., Křena, B.: Úvod do softwarového inženýrství. Teaching texts, Brno University of Technology, 2010. (In Czech)
- System Modelling Based on Object-Orientation - Tutorial of UML 2.0 Language. Brno University of Technology, 2004.
- Arlow, J., Neustadt, I.: UML and the Unified Process: Practical Object-Oriented Analysis and Design, Addison-Wesley Professional; 1st edition, 2001. ISBN 0201770601.
- Křena, B., Kočí, R.: Zadání a vzorová řešení ER diagramů ze zkoušek. Assignments collection. VUT v Brně, 2016. (In Czech)
- Beck, K.: Extreme Programming Explained: Embrace Change, Addison-Wesley; 1st edition, 1999. ISBN: 0201616416.
- Page-Jones, M.: Fundamentals of Object-Oriented Design in UML, Addison-Wesley; 1st edition, 1999. ISBN: 020169946X.
- 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.(in Czech)
- 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. (in Czech)
Syllabus of lectures
- Software engineering history, basic notions, the overview of development techniques.
- Software lifetime, models of software lifetime.
- Requirement analysis, methods of requirements specification, modelling techniques (Use Case Diagram).
- Structured analysis and design, methods, modelling techniques. Data-Flow Diagram (DFD) and the Entity-Relationship Diagram (ERD).
- Object-oriented analysis and design, methods, modelling techniques. Unified Modelling Language (UML), Class Diagram and Object Diagram.
- Chosen modelling means of UML (Activity, Sequence, Communication, and Statechart Diagrams).
- Complex modelling with UML.
- Design patterns.
- Introduction to verification, validation, and testing.
- Agile methods of software development, basic principles of extreme programming and prototyping.
- Basic principles of software operation and maintenance.
- Introduction to software project management.
- Software quality, intellectual property rights, Software Engineering Code of Ethics.
Syllabus of numerical exercises
- Requirements in UML - Use case diagram, Activity diagram and State diagram (3rd and 4th weeks, 5 points)
- Data modelling - ER diagram (5th to 7th weeks, 5 points)
- Analysis and Design in UML - Class diagram, Object diagram, Sequence diagram and Communication diagram (8th and 9th weeks, 5 points)
Syllabus - others, projects and individual work of students
- Model of an information system (25 points)
The knowledge of students is evaluated within exercises, 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 his/her teacher for the alternative assignment that can compensate lost points from the exercise.
The minimal number of points which can be obtained from the final exam is 30. Otherwise, no points will be assigned to a student.
Course inclusion in study plans