460-4130/01 – Development of Systems in the Automotive Industry (VSAP)
| Gurantor department | Department of Computer Science | Credits | 5 |
| Subject guarantor | Ing. Svatopluk Štolfa, Ph.D. | Subject version guarantor | Ing. Svatopluk Štolfa, Ph.D. |
| Study level | undergraduate or graduate | Requirement | Compulsory |
| Year | 1 | Semester | winter |
| | Study language | Czech |
| Year of introduction | 2019/2020 | Year of cancellation | 2023/2024 |
| Intended for the faculties | FEI | Intended for study types | Follow-up Master |
Subject aims expressed by acquired skills and competences
The goal of the subject is to provide comprehensive knowledge about the methods and approaches of the automotive electronics systems development, understand the approach of decomposition of the system solution to the subsystems and their proper integration into the system solution. Students will be able to apply the systematical approach to the system development according to the V-model, understand the importance of different development phases and use proper tools for the support of the development.
Teaching methods
Lectures
Tutorials
Summary
The subject presents to the students the knowledge about methods and approaches in the area of complex automotive electronics system development. Students will get the knowledge that is needed to proper understanding and application of the methods and approaches for the development according to the V-model with the supporting tools and methods that are used in nowadays practice.
Compulsory literature:
Markus Maurer, Hermann Winner: Automotive Systems Engineering, Springer Science & Business Media, 22. 5. 2013
Ian Faulconbridge, Michael Ryan: Introduction to Systems Engineering, Argos Press Pty Ltd (January 17, 2015)
Alexander Kossiakoff, William N. Sweet, Sam Seymour, Steven M. Biemer: Systems Engineering Principles and Practice 2nd Edition, Wiley-Interscience; 2 edition (May 24, 2011)
Recommended literature:
Leen G, Heffernan D, Expanding automotive electronic systems. IEEE Computer 35 (1):88 – 93, 2002
IEEE Recommended Practice for Architectural Description of Software-Intensive Systems. IEEE Std 1471, 2000.
Way of continuous check of knowledge in the course of semester
Rated examples in practices and written and oral examination.
E-learning
Other requirements
No additional requirements are placed on the student.
Prerequisities
Subject has no prerequisities.
Co-requisities
Subject has no co-requisities.
Subject syllabus:
Lectures
1.-3. Development process: Technological trends, development process requirements, methods and tools - traceability of customer requirements to the solutions and SW code. Traceability of system requirements to the requirements of specific SW, HW, ME and other parts.
4.-5. System development and design - decomposition to subsystems traceability of subsystems to the architecture of the system and requirements.
6.-9. HW a SW design - methods and tools, traceability of subsystems to the architecture of the system and requirements.
10.-12. Development of HW and SW solutions: e.g. automatical code development (processes and tools), automated testing.
13.-14. Quality management, project management, validation and verification.
Practices:
The goal of practices is the practical implementation of the development process on real example. Students will apply their knowledge to the development of real product from requirements to the solution.
1.-3. Customer ans system requiremets, decomposition to HW, SW, ME and other requirements.
4.-5. Methods and tools of system development (e.g. SysML), architecture description, traceability to requirements.
6.-9. Design of subsystems - traceability ti the architecture.
10.-12. Product implementation - HW a SW implementation documentation and traceability to detail design and requirements.
13.-14. Testing and quality - metrics, validation and verification.
Conditions for subject completion
Occurrence in study plans
Occurrence in special blocks
Assessment of instruction