1031 - Selected chapters in software engineering
| Course specification | ||||
|---|---|---|---|---|
| Type of study | Master academic studies | |||
| Study programme | ||||
| Course title | Selected chapters in software engineering | |||
| Acronym | Status | Semester | Number of classes | ECTS |
| 1031 | mandatory | 1 | 2L + 2E | 6.0 |
| Lecturers | ||||
| Lecturer | ||||
| Lecturer/Associate (practicals) | ||||
| Prerequisite | Form of prerequisites | |||
| Learning objectives | ||||
| Mastering modern methods, techniques and tools for rapid development of complex software systems and comparative analysis of advantages and disadvantages compared to classical approaches.. software development. Application of agile and adaptive approaches to model-driven software development. | ||||
| Learning outcomes | ||||
| Upon successful completion of the course, the student will be able to apply an adaptive and agile methodological approach in the software development process. They specify, design and implement complex software products based on modeling, define standards of software product architecture, data warehouse architecture and formulate bases for automatic code generation of complex software products. | ||||
| Content | ||||
| First unit mandatory content: Approaches to rapid software development. Methods and techniques of rapid software development. Tools for rapid software development. Code generators. Overview of methodological approaches to software development (relation between agile and traditional methods). Prototype software development. Software development based on models (Model Driven Architecture). Standardization of functional and visual characteristics of typical software systems and creation of bases for automatic code generation. Second unit (variable content): In each generation, students, by majority decision, choose two additional areas from the Software Engineering Body of Knowledge (SWEBOK) that are not covered in the first unit. | ||||
| Teaching Methods | ||||
| Interactive (active) lectures supported by slide projections. The use of modeling tools and development environments is left up to individual teams. | ||||
| Evaluation and grading | ||||
| The exam is taken through the creation and defense of a team project and the final part of the exam, which includes a skill test (tasks) and a knowledge test (theory). | ||||