Introduction to Software Engineering
|Language of Instruction:||Czech|
|Hour/sem||Lectures||Sem. Exercises||Lab. exercises||Comp. exercises||Other|
|Guarantor:||Křena Bohuslav, Ing., Ph.D., DITS|
|Lecturer:||Kočí Radek, Ing., Ph.D., DITS|
Křena Bohuslav, Ing., Ph.D., DITS
|Instructor:||Fiedor Jan, Ing., Ph.D., DITS|
Holík Lukáš, Mgr., Ph.D., DITS
Lengál Ondřej, Ing., Ph.D., DITS
Malík Viktor, Ing., DITS
Rogalewicz Adam, doc. Mgr., Ph.D., DITS
Šoková Veronika, Ing., DITS
Turoňová Lenka, Ing., DITS
|Faculty:||Faculty of Information Technology BUT|
|Department:||Department of Intelligent Systems FIT BUT|
| || ||To provide 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.|
| || ||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, state chart 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, intelectual property, software engineering code of ethics and professional practice.|
|Knowledge and skills required for the course:|
| || ||This course takes place in the winter term of the first year of the bachelors study programme. Thus, we expect that students have the high school level knowledge of using computers.|
|Subject specific learning outcomes and competences:|
| || ||Student gets an overview in the area of complex software system development. Students acquaints 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. Student acquaints with basics of computer publishing.|
|Generic learning outcomes and competences:|
| || ||Students learns to provide analysis and design of the software systems. Students learns to create the project documentation and the program documentation. Students will be able to read and create basic UML models.|
|Syllabus of lectures:|
- Software engineering history, basic notions, 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 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 - others, projects and individual work of students:|
- Model of an information system (25 points)
- 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, 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.
- 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.
| || ||Within this course, attadance 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 excercises can be obtained only for active participation (mistakes and wrong answers are fine while not involving into discussion and problem solving can result in loosing points).
When a student cannot attend the excercise and proves it correctly (s)he can either attend the excercise with a different group (please inform the teacher about that) or (s)he can ask his/her teacher for alternative assignement that can compensate lost points from the excercise.
The minimal number of points which can be obtained from the final exam is 28. Otherwise, no points will be assigned to a student.
| || ||Students can obtain up to 15 points from three two hours long excercises (5 points in each), 25 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 excercises and from the project. Plagiarism and not allowed cooperation will cause that involved students are not classified and disciplinary action may be initiated.|