A course is the basic teaching unit, it's design as a medium for a student to acquire comprehensive knowledge and skills indispensable in the given field. A course guarantor is responsible for the factual content of the course.
For each course, there is a department responsible for the course organisation. A person responsible for timetabling for a given department sets a time schedule of teaching and for each class, s/he assigns an instructor and/or an examiner.
Expected time consumption of the course is expressed by a course attribute extent of teaching. For example, extent = 2 +2 indicates two teaching hours of lectures and two teaching hours of seminar (lab) per week.
At the end of each semester, the course instructor has to evaluate the extent to which a student has acquired the expected knowledge and skills. The type of this evaluation is indicated by the attribute completion. So, a course can be completed by just an assessment ('pouze zápočet'), by a graded assessment ('klasifikovaný zápočet'), or by just an examination ('pouze zkouška') or by an assessment and examination ('zápočet a zkouška') .
The difficulty of a given course is evaluated by the amount of ECTS credits.
The course is in session (cf. teaching is going on) during a semester. Each course is offered either in the winter ('zimní') or summer ('letní') semester of an academic year. Exceptionally, a course might be offered in both semesters.
The subject matter of a course is described in various texts.
MI-NSS.16 Normalized Software Systems Extent of teaching: 2P Instructor: Completion: ZK Department: 18102 Credits: 5 Semester: L Annotation:
Students will learn the foundations of Normalized Systems theory, which studies the evolvability of modular structures based on concepts from engineering such as stability from systems theory and entropy from thermodynamics. Initially, the theory was developed at the level of software architectures, where the concept of stability was translated into the definition of so-called combinatorial effects. These effects occur when the impact of a change to the software architecture is dependent on the change itself, as well as on the size of the system. The latter is highly undesirable, as it will cause even a simple change to incur an ever-increasing impact as the size of the system grows over time. As such, combinatorial effects can be considered as a main cause of Lehman?s Law of Increasing Complexity (see, e.g., http://en.wikipedia.org/wiki/Lehman's_laws_of_software_evolution). Additionally, the concept of entropy was used in the study of which micro-states in a modular structure correspond with a given macro-state. This is related mainly to issues such as testing in software architectures. Normalized Systems theory consists first of a set of principles which indicate where violations of stability and entropy-related issues occur in any given software architecture. These principles indicate that very fine-grained modular structures are required in order to control them. In the second part of the theoretical framework, it is shown how software architectures can be constructed based on a set of 5 design patterns called elements. These elements provide the core functionality of information systems in terms of storing data, executing actions, workflows, connectors and triggers, while controlling for violations of the stability and entropy-related principles, allowing them to realize new levels of evolvability in software architectures. Recently, Normalized Systems theory was also applied to the modular structures in business processes and enterprise architectures, with the goal of constructing a foundational theory for Enterprise Engineering.
Lecture syllabus:
Course will be realized in a block (concentrated) form in the first or second week of May. The main lecturer will be prof. Jan Verelst from University of Antwerp, co-author of the book Normalized Systems (see study materials) LecturesExercises
1. Engineering basics a. Stability in systems theory b. Entropy in statistical thermodynamics 2. Normalized Systems Theory a. NS principles b. NS principles c. NS elements d. NS elements 3. NS Tools a. NS expanders b. Prime Radiant 4. Enterprise Engineering: applying NS theory to enterprises a. Generalizing NS theory b. Generalizing NS theory c. NS Business Processes d. NS Enterprise Architectures 5. Conclusion a. Reflection: applying concepts from engineering to software and enterprises
1. Exercises-Normalized Systems theory a. Identification of Combinatorial Effects b. Identification of Combinatorial Effects c. GUI customizations d. Security customizations 2. Exercises-Enterprise Engineering a. Normalizing a BPMN-business process b. Creation of an elementary element at the enterprise level Seminar syllabus:
Literature:
Mannaert Herwig, Verelst Jan. Normalized systems: re-creating information technology based on laws for software evolvability, isbn 978-90-77160-00-8-S.l., Koppa(2009).Requirements:
Basic knowledge of basics of software engineering and programming languages.
Informace o předmětu a výukové materiály naleznete na https://moodle-vyuka.cvut.cz/course/view.php?id=2731 The course is also part of the following Study plans:
Study Plan Study Branch/Specialization Role Recommended semester MI-WSI-WI.2016 Web and Software Engineering V 2 MI-SP-SP.2016 System Programming V 2 MI-SP-TI.2016 System Programming V 2 MI-PSS.2016 Computer Systems and Networks V 2 MI-NPVS.2016 Design and Programming of Embedded Systems V 2 NI-TI.2018 Computer Science V 2 MI-ZI.2016 Knowledge Engineering V 2 MI-ZI.2018 Knowledge Engineering V 2 MI-WSI-ISM.2016 Web and Software Engineering V 2 MI-PB.2016 Computer Security V 2 MI-WSI-SI.2016 Web and Software Engineering PZ 2 MI-SPOL.2016 Unspecified Branch/Specialisation of Study VO 2
Page updated 19. 4. 2024, semester: L/2020-1, L/2021-2, Z/2023-4, Z/2024-5, Z/2019-20, Z/2022-3, L/2019-20, L/2022-3, Z/2020-1, Z/2021-2, L/2023-4, Send comments to the content presented here to Administrator of study plans Design and implementation: J. Novák, I. Halaška