Introduction to Software Engineering
FIT-IUSAcad. year: 2020/2021
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
- 30 hours of project work
- 13 hours of continual study
- 35 hours of study for final exam
Learning outcomes of the course unit
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.
Students learn to provide analysis and design of the software systems. Students will be able to read and create basic UML models.
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.
Recommended optional programme components
Recommended or required reading
Kočí, R., Křena, B.: Úvod do softwarového inženýrství. Studijní opora, Vysoké učení technické v Brně, 2010. (CS)
Kočí, R., Křena, B.: Úvod do softwarového inženýrství. Teaching texts, Brno University of Technology, 2010. (In Czech)
Objektově orientované modelování systémů - učební text : učební text zaměřený na jazyk UML 2.0. Vysoké učení technické v Brně, 2004. (CS)
System Modelling Based on Object-Orientation - Tutorial of UML 2.0 Language. Brno University of Technology, 2004.
Arlow, J., Neustadt, I.: UML2 a unifikovaný proces vývoje aplikací. Computer Press, Brno, 2007. ISBN 978-80-251-1503-9. (CS)
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)
Křena, B., Kočí, R.: Zadání a vzorová řešení ER diagramů ze zkoušek. Sbírka úloh. VUT v Brně, 2016. (CS)
Beck, K.: Extrémní programování. Grada, Praha, 2002. ISBN 80-247-0300-9. (CS)
Beck, K.: Extreme Programming Explained: Embrace Change, Addison-Wesley; 1st edition, 1999. ISBN: 0201616416.
Page-Jones, M.: Základy objektově orientovaného návrhu v UML. Grada, 2001. ISBN 80-247-0210-X. (CS)
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)
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. (CS)
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. (CS)
Richta, K., Sochor, J.: Softwarové inženýrství I. Vydavatelství ČVUT, Praha 1996 (dotisk 1998). ISBN: 80-01-01428-2. (in Czech)
Planned learning activities and teaching methods
Assesment methods and criteria linked to learning outcomes
Students can obtain up to 16 points from four two hours long exercises (4 points from each), 24 points from the project 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 and from the project. Plagiarism and not allowed cooperation will cause that involved students are not classified and disciplinary action may be initiated.
Language of instruction
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.
Specification of controlled education, way of implementation and compensation for absences
Within this course, attendance on the lectures is not monitored. Monday lecture is given for lecture group 1BIA, Friday lecture for group 1BIB. Students from lecture groups 2BIA and 2BIB can choose which lecture they attend. Students from 1BIA and 1BIB lecture groups can attend the lecture given for the other group without any permission.
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 avoiding 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.
Type of course unit
39 hours, optionally
Teacher / Lecturer
- 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.
8 hours, compulsory
Teacher / Lecturer
- Requirements in UML - Use case diagram, Activity diagram and State diagram (3rd and 4th weeks, 4 points)
- Data modelling - ER diagram (5th and 6th weeks, 4 points)
- Analysis and Design in UML - Class diagram and Object diagram (7th and 8th weeks, 4 points)
- Analysis and Design in UML - Sequence
diagram and Communication diagram (9th and 10th weeks, 4 points)
7 hours, compulsory
Teacher / Lecturer
- Model of an information system (24 points)
eLearning: currently opened course