[Systems Engineering] #1. INTRODUCTION – Navigating Systems Engineering


I’m Danappa, a systems engineer in the automotive electronics industry in Korea, with six years of experience as a Systems Engineer.

Recently, compliance with international standards such as Functional Safety (ISO26262), A-SPICE, and Cyber Security (ISO/SAE21434) is increasingly emphasized in this industry. These changes have significantly highlighted the importance of systems engineering.

However, the application of systems engineering is still in its early stages. There are not many colleagues who fully understand systems engineering, and even fewer people show interest in it.

Despite this, many companies are feeling the need to strengthen their systems engineering capabilities and are expanding their investments in recruitment and training.

Against this backdrop, I aim to provide useful information to those looking to build a career as a systems engineer in the automotive electronics industry. Through this process, I also hope to enhance my own skills.

This images represent navigating systems engineering in the automotive industry. Images include a vehicle design studio, engineers at work, computer screens showing software and hardware design, and advanced engineering tools. generated by DALL-E

Originally a hardware engineer, I worked in that role for eight years before a chance opportunity led me to start working in systems engineering.

At my company, systems engineering was just being introduced, so there was no one to pass down the knowledge to me. I had to teach myself, learning about systems engineering through the internet, YouTube, online and offline courses.

What I realized through this process is that systems engineering is broad and somewhat abstract, making it difficult to approach easily. In contrast, the development of hardware or software in the electronics field is intuitive with tangible outputs (e.g., circuit diagrams, code), and there are clear criteria for assessing the quality of the results.

There are also many useful guides for this. However, the system design documents, the output of systems engineering, are not intuitive, and the evaluation criteria are vague. It was hard to find appropriate materials on the internet, especially those tailored to the automotive electronics industry.

Additionally, there are hardly any blogs or online communities in Korea that deal with systems engineering in the electronics field, which I found disappointing.

For these reasons, although I am not a systems engineering expert, I challenge Navigating Systems Engineering, and would like to share the knowledge and experience I have gained in performing my work.

For Navigating systems Engineering I plan to cover in my blog are as follows (subject to continuous addition or change):

No.TopicBrief Explanation
1Overview of Systems EngineeringSystems engineering is a field of engineering that designs, integrates, and manages complex systems. This field focuses on optimizing the performance and functionality of the overall system by efficiently combining elements from various disciplines. This blog explains the basic knowledge and importance of systems engineering.
2Introduction to SysML (System Modeling Language)SysML (System Modeling Language) is a generalized graphical modeling language for modeling complex systems. SysML is useful for integrating multiple perspectives and facilitating communication in systems engineering projects. In this blog, we will convey the basics of System SysML and its importance in systems engineering.
3How to Use Sparx Enterprise ArchitectWe will guide you on how to use sparx Enterprise Architect and how to do SysML modeling using Enterprise Architect.
4Functional Safety (ISO26262) Knowledge for Systems EngineersISO 26262 is an international standard for functional safety in the automotive sector, providing guidance for managing risks that may arise during the development of a vehicle’s electronic and electrical systems. This standard includes risk assessment, risk mitigation, and system verification procedures to ensure the safe design and operation of vehicles. This blog explains the ISO26262 basic principles that systems engineers need to know.
5Cyber Security (ISO/SAE21434) KnowledgeISO/SAE 21434 is an international standard for managing cybersecurity risks in the automotive industry. This standard defines cybersecurity requirements across the entire life cycle of a vehicle and provides a framework for managing cybersecurity during the design and development of a vehicle’s electronic systems. This blog explains the Cyber Security knowledge that systems engineers in the automotive electronics industry need to know.
6Understanding A-SPICEA-SPICE (Automotive Software Process Improvement and Capability dEtermination) is an international standard for evaluating and improving the quality and performance of automotive software development and related processes. This standard aims to improve the software development capabilities of the automotive industry by providing a process model and evaluation methodology that covers the entire software development process. This blog provides A-SPICE knowledge that systems engineers in the automotive electronics industry need to know. This explains.
7Understanding AutosarAUTOSAR (AUTomotive Open System Architecture) is a standardized open software architecture for automotive electronic systems. This standard provides a scalable, interoperable, and modular approach for developing electronic systems in vehicles. In this blog, we will convey the basic concepts that systems engineers need to know about autosar and knowledge that is useful in practice.
8MBSE FrameworkMBSE, or Model-Based Systems Engineering, is a modern approach to managing the complexity and increasing efficiency of systems development. There are several frameworks that integrate this methodology, each designed for a specific industry or project type to systematize and standardize the systems engineering process. The MBSE framework enables more effective development by clearly defining complex system requirements and supporting the design and verification process through models.
9Requirement EngineeringA Requirements engineering is the process of identifying, documenting, and verifying user needs and constraints in the early stages of development of a system or software. This field aims to define required functionality and performance, and manage these requirements to ensure they are met. This blog explains the basic knowledge that systems engineers in the automotive electronics industry need to know when developing system requirements.
10Information on SysML CertificationSysML Certification is a program that assesses and certifies knowledge and skills in Systems Modeling Language (SysML). This certification helps demonstrate that individuals have the ability to model complex systems using SysML. This blog provides a brief explanation of SysML Certification, application process, and know-how.
11Life as a System Engineer in the Korean Electronics IndustryLife as a systems engineer in the Korean automotive electronics industry involves the challenging role of designing, analyzing, and integrating complex systems in a rapidly changing technological environment. In this blog, I would like to share what I experience while working as a systems engineer in this field.
12Useful Resources for Studying System EngineeringSystems engineering is difficult to learn because the content is vast and abstract. To help with this, I would like to share the books, websites, and other resources I refer to while posting on this blog.

As I conclude this introductory post, Navigating Systems Engineering, I want to emphasize that I am not an expert in this field, so there may be errors or inadequacies in my writing.

I kindly ask for your understanding and active feedback. If you have opinions or additional explanations, please feel free to leave a comment, and I will update the content accordingly.

I hope my articles will be helpful to those who are working as systems engineers in the automotive electronics industry or planning to join in the future.

Lastly, Thank you for reading this Post, Navigating Systems Engeering.

For the first post on this blog, we will explore the question, “What is a ‘System’?” which is our primary subject of discussion.

Much of the general knowledge of Systems Engineering that begins with this Navigating Systems Engineering post was compiled from studying the Guide to the Systems Engineering Body of Knowledge (SEBoK) provided by Incose. If you want more detailed information, you can read SEBoK directly by going to the Ari link.


[Systems Engineering] #2. Definition of System

[Systems Engineering] #3. Understanding Systems Thinking

[Systems Engineering] #4. Useful knowledge of systems thinking

[Systems Engineering] #5. Understanding Systems engineering

[Systems Engineering] #6. Who is Systems Engineer

[Systems Engineering] #7. Understanding MBSE (Model Based Systems Engineering)

[Systems Engineering] #8. Additional practical knowledge about MBSE

[Systems Engineering] #9. What is Good System Model?

[Systems Engineering] #10. Understanding SysML (System Modeling Language)

Leave a Comment