What does a system engineer do?

A Systems Engineer designs and manages complex systems over their entire life cycle. They analyze user needs, design systems, coordinate system development tasks, and ensure the efficient integration of all components and subsystems. This role involves understanding both the technical aspects of systems and the needs of the users and stakeholders.

A customer has a need to achieve an outcome. The outcome is predicated upon creating capabilities, all of which break down into lots of functions which need to work both in themselves and integrally with other functions. This drives the need to put systems in place which will give you the integrated functionality which creates the capabilities which achieve the outcome. Or in English, the outcome they need has to work in certain ways ,which means making stuff which will work in achieving the outcome.

Managing interaction with people and their nature to enhance collaboration and their interest for contributing to the project. After all, people that build together the actual product matter the most. The most important job of the System Engineer can be likened to a glue binding together the entire technical implementation of the system, ensuring that the needs, concepts, defined solution, and the workings of all people are all consistent and pushing the project in the same right direction.

My view of what a SE specifically does (given they may also do some specialty engineering) 1) facilitate Systens thinking with all teams - to help rents elicitation, concept develop, root cause of problem investigation 2) model emerging understanding of both problem and solution in MBSE 3) manage define requirements, evidence (from analysis), definition (derived needs) and verification data, and the solution (so full configuration mgt) 4)support decision making (with criteria from reqts, and data) 5) engineering mgt - integrating with planning via a SEMP - defining appropriate activities to get appropriate maturity at each stage

Few of the responsibilities of system engineers 1. Analyze the customer requirements, discuss, and negotiate the needs of the customer. 2. Analyze the product requirements for a better fit with the customer's needs, find the gaps in the needs. Create new system requirements for the gaps identified in the product. 3. Check if the subsystem requirements are properly derived from the system requirements or not. 4. Coordinate with the validation team, mainly system validation and integration validation, to ensure committed customer requirements are satisfied. 5. Need to verify the bilateral traceability between customer requirements and system requirements, system to subsystem requirements, and requirements to the validation report.

Systems engineers possess the ability to adapt their expertise to various projects and employ diverse methodologies. However, their core function lies in comprehending, articulating, and facilitating seamless interaction between system components within specific environments. Ultimately, their success hinges on a combination of talent, technical knowledge, and effective communication, ensuring the smooth operation of complex systems.

System Engineering tasks begin with analysis and decomposition of customer needs and operational concepts into requirements. The SE captures these requirements in a requirement management tool along with rationale, constraints, stakeholders, and any other support documentation to provide pedigree during technical reviews. The next step is tracing these requirements to lower-level requirements (system to subsystem) along with structures, interfaces, and behaviors in support of the aforementioned reviews. This traceability along with parametric analysis ensures the design will meet the customer needs and provides the basis for implementation and validation culminating in the fielding, sustainment, and eventual retirement of the system.

The main Systems Engineers skill is Integration (in the broad sense) - the ability that combines Systems Thinking, ability to collaborate and understand diverse disciplines, to connect disconnected elements, and many other components.

O engenheiro de sistemas deve ser capaz de definir todo o processo de ciclo de vida do produto, para isso ele deve contar com algumas habilidades que o suportará em suas decisões, essas habilidades são compostas de boa visão holística do negócio, bom conhecimento técnico, e excelente relacionamento interpessoal.

In system engineering, proficiency lies in systems thinking to comprehend intricate interdependencies, adeptly managing requirements to capture, analyze, and prioritize needs. Utilizing tools such as SysML for system modeling is crucial, alongside rigorous risk management to identify and mitigate potential issues. Proficiency also includes ensuring seamless integration and testing of subsystems, effective communication to facilitate interdisciplinary collaboration, adept problem-solving to resolve technical challenges, and comprehensive lifecycle management from inception through retirement phases.

The skills necessary will be to learn the MBSE approach and to learn the languages such as Systems Modeling Language (SysML) to support the overall architecture and a framework to support the overall project (e.g. DoDAF).

In addition to the other contributors....I believe the System Engineer has to have the right combination of: - technical skills for the task - managerial skills - soft skills (people skills, communication, etc.) - will and desire to see the "forest from the trees" and drive a path through it, without an immediate reward - the right combination of realism/optimism to realize: - the wrong path - its own limitation and where deep expertise is needed

Modern Model Based Systems Engineering uses tools to capture models, usually SysML or UML, and keep them at the center of the systems engineering process. Tools like Cameo are important to facilitating the process, keeping models and providing integration points for designs.

Jira, Excel, and Python are - in my opinion - essential tools for a systems engineer, serving as reliable allies in your professional journey. Keeping your work organised, clear, and concise is achievable through Jira's capabilities. Excel proves invaluable for visualising, analysing, and transforming data in specific ways. Additionally, when it comes to more advanced scripting and ensuring the accurate provision of numbers and information to subsystems, as well as vice versa, Python stands out as a crucial asset in your toolkit.

One of the most valuable tools I've been exposed to and had the opportunity to implement is DSM. Design structure matrix. I've used it for several design exploration activities. In essence, it was used to create functional allocation analysis. Mapping functions to components in order to enable traceability and set up baseline for DFMEA and system interface analysis.

A engenharia de sistemas necessita de ferramentas para gerenciar as informaçoes do produto durante todas as fases do projeto, listei aqui algumas ferramentas e não nomes de software comerciais. Essas ferramentas auxiliam na identificação de falhas, definição de escopo, modelagem, etc.: - Context Diagram - Functional Failure Mode and Effects Analysis - Function Means Analysis - Functional Modelling - Holistic Requirements Model - Matrix Diagram - N2 Analysis - Need Means Analysis - Pugh Matrix - Quality Function Deployment - Stakeholder Map - Systemic Textual Analysis - The Analytic Hierarchy Process - Viewpoint Analysis

Los ing. de sistemas utilizan diversas herramientas, incluyendo software de modelado y simulación (como MATLAB o Simulink) para diseñar y analizar sistemas. Herramientas de desarrollo de software (IDEs como Eclipse o Visual Studio) son esenciales para programación. Utilizan sistemas de control de versiones (Git, SVN) para gestión de código y documentación. Herramientas de gestión de proyectos (Jira, Trello) ayudan en la planificación y seguimiento. Para la integración y despliegue continuo, emplean Jenkins o Docker. Utilizan plataformas de virtualización (VMware, VirtualBox) para pruebas y desarrollo, y herramientas de análisis de seguridad (Wireshark, Nessus) para evaluar vulnerabilidades. también usar bases de datos (SQL, NoSQL).

Whatever their boss tells them to do. That is why developing a complete SEbok based on the activity performed by a SE is an impossible task

Subject-matter engineering deals with bringing the laws of physics into useful designs and products. Systems Engineering deals with the laws of human nature and relations in large groups - and helps the team realize a product IN SPITE of our human nature. Electrical engineers know the laws of electricity and magnetism; systems engineers know the laws of human behavior, combined with their technical knowledge, to ensure projects do not "crash and burn" on the technical side.

Systems Engineering is a trans-disciplinary approach So, a systems engineer 1) works across traditional , reductionist solos, ensuring a common understanding of problem and solution 2) applies a systems process to assist development of solution ‘that works’ -requirements driven but very iterative - requirements to solution, and between solution layers 3) applies, with whole team, Systems thinking as a framework for curiousity 4) models and manages (traceability and rationale) requirements and solution architecture (both logical and physical) 5) integrated with PM to ensure right activities performed in right order to give ‘confidence to proceed’ Overall - seeks to optimise the whole not the parts

La ingeniería de sistemas difiere de otras ingenierías en su enfoque en integrar componentes de software, hardware y procesos para funcionar como un todo, priorizando la visión global sobre detalles específicos. Se centra en la gestión de proyectos, análisis de requisitos y optimización de procesos. A diferencia de disciplinas como la mecánica, eléctrica o civil, que se enfocan en áreas concretas y técnicas específicas, la ingeniería de sistemas requiere habilidades multidisciplinarias y gestión de la complejidad de sistemas integrados, siendo clave en entornos donde la interacción entre tecnología, personas y procesos es crítica.

Systems engineers manage interfaces. Their role is to help navigate teams to converge into a fully integrated solution. They realize every interface is a discontinuity in the system and as such they strive to minimize that stress raiser in the system.

In my experience, a system engineer in the semiconductor industry designs and integrates complex semiconductor systems, considering factors like performance, power consumption, area, thermal and cost. They collaborate with hardware and software teams to ensure seamless integration and functionality across all system components. System engineers conduct thorough testing, optimize performance, and troubleshoot issues to ensure that semiconductor systems meet specifications and quality standards. Additionally, they document system requirements, design specifications, and test results to maintain clear communication and support ongoing development efforts.

Curiosity and EQ! These are 2 traits that you rarely see in textbooks as skills required for systems engineers. Typically, experts are appointed as systems engineers, but this is not necessarily the best approach for all situations. I once had a manager who would tell me often that I had a "keen" understanding of tractors and somehow, I made things work. Not sure if it was a complement or not. However, I reflected on this several times and it came down to being humble in acknowledging I did not have all answers and having the ability to talk to experts, ask the right questions and bring teams together with a framework of building a great joint solution.

Systems engineering at Product Level, is about seeing the "big picture" AND considering the right priorities while working with a diverse team. In my opinion is one the most satisfying and fulfilling tech careers. But...it takes years of "walking" your career through various individual technology ingredients, subsystems, industries and applications, leadership roles, that model you into being a systems engineer.

I have 3 golden rules. 1. Don't put the same information in more than one place. As a systems engineer I spend too much time matching databases. I dream of the perfect project where I never match databases again. 2. Don't make rules you can't police. I have often read a 30 page process of rules to make something happen to find the process didn't make anything happen. I dream of a project where the processes are so simple they can be explained on a single page and are verified by those who use it not those who created it. 3. Don't make decisions before you have to. This makes people angry. Always ask "when do I need to make this decision?"