Budapest University of Technology and Economics, Faculty of Electrical Engineering and Informatics

Dr. Zoltán Micskei, associate professor, MIT

Before taking the course, the students should be able to

- (K2) explain the basic mechanism of imperative programming languages,

- (K3) develop a non-trivial program based on a high-level specification,

- (K3) solve modeling problems using simple modeling languages (e.g. final state machines). 

The objective of the course is to introduce the students to the design, development, and maintenance of large-scale software systems. The course presents the techniques and methods to produce the software as a product. In addition to the presentation of the technical aspects, people and project management techniques and methods are also introduced.

Students satisfying the course requirements will be able to understand and manage the problems related to the development of large-scale software systems and they will be able to participate in such development processes. The knowledge acquired in this course will be the background for the Software Laboratory course.

Software modeling and UML
2. Modeling software: Why model? What can we model? The Unified Modeling Language (UML) modeling language family. Modeling structure: class diagram, modeling instances, package diagram, component diagram.
3. UML behavioral modeling I.: use case, activity diagram, sequence diagram.
4. UML behavioral modeling II.: state machine diagram, connecting different viewpoints.

Software development processes
5. Steps and artefacts of the software lifecycle. Popular lifecycle models (waterfall, V-model, incremental)
6. Classic and agile software development. Agile and Lean practices. Examples: Scrum, XP.
7. Fundamentals of version control. Centralized and decentralized version control. Typical workflows and patterns (GitHub Flow, Mainline...).

Software development practices
8. Requirement management: Importance of requirements. Eliciting, analyzing, prioritizing requirements. Types of requirements. Traceability. Handling changes in requirements.
9. Design and architecture: Fundamental concepts (abstraction, modularization). Elements of software architecture. Design patterns. Documenting designs.
10. Managing source code: properties of good source code. Coding guidelines and standards. Code review. Using static analysis tools.
11. Testing I.: concepts and goals of testing. Testing process. Testing levels. Risk-based testing.
12. Testing II.: test design techniques (specification and structure-based techniques).

Project and people management
13. Managing software projects. Estimation, project planning and tracking. Agile project management practices and tools.
14. Measurement and analysis in software development. Process definitions and metrics.

Laboratory exercises:

1. Using a UML modelling tool with basic diagrams
2. Practicing UML-based object-oriented design
3. Version control systesm (git), basic workflows (GitHub Flow)
4. Build systems. Continuous integration.
5. Checking code style. Code review. Using static analysis tools
6. Test design and implementation. Measuring code coverage.

• Slides and materials on the course website
• Ian Sommerville: Software Engineering, 10th edition, Pearson, 2015
• Martin Fowler: UML Distilled, Addison-Wesley, 2003
• Robert C. Martin: Clean Code: A Handbook of Agile Software Craftsmanship, Pearson, 2008
• Dorothy Graham et al.: Foundations of Software Testing, Cengage, 2019
• Titus Winters et al.: Software Engineering at Google, O'Reilly, 2020

Dr. Balla Katalin, associate professor, IIT

Dr. Goldschmidt Balázs, associate professor, IIT

Dr. Micskei Zoltán, associate professor, MIT