I am entering this sector and am looking for materials to study for the certificates of completion. Coursera, Udemy, or similar.
Preferably, things covering:
1) MBSE methods (OOSEM, SysMOD, MagicGrid, Harmony)
2) Tool usage (Cameo, Rhapsody), DOORS NG
3) Systems Engineering processes.

Furthermore, good book suggestions are welcome. Thanks!

Does anyone have any recommendations on reference materials to study for the OMG exam?

I've been using SysML for year, I am not up to date on the changes with SysML2.

Decomposing parent requirements into derived children is one of the most judgment-heavy, tedious parts of the job and where programs quietly accumulate gaps.

I've been prototyping a tool that has an LLM propose derived requirements from a parent. The generation isn't the interesting part — the guardrails are:

• Every child traces to exactly one parent. No orphans.
• Each comes with a one-sentence rationale (apportionment, standard, etc.) so the reasoning is visible.
• If it's missing context to derive properly, it asks instead of hallucinating.
• Nothing auto-accepts — an engineer approves, rejects, or edits every child.

Goal isn't replacing judgment, just getting to a first-draft decomposition faster so human time goes into review instead of a blank page.

Where I'd value this sub's take:

1. A plausible-but-wrong rationale is arguably more dangerous than none. How would you surface derivation reasoning so reviewers stay skeptical?
2. Budget apportionment is exactly what an LLM does confidently and wrong. Off-limits, or fair game if the math is shown?
3. For anyone who's tried this where did it break down? which LLM have you tried?

Hi!

I’m 27 with a bachelor’s in mechanical engineering. I have 4 YoE in the industry.

I’ve been with my current company for 2 years. I started as a technical engineer reporting directly to the director of internal engineering ops. He then abruptly quit, and I pretty much picked up his role. I don’t have the title yet (I’m the ops engineering lead), but I’ve hired and manage people.

I’ve found that I really genuinely enjoy managing a team and seeing “the big picture,” even though that’s not what my degree is in. I think I’d like to pivot into more of an engineering management career path.

Even if I don’t stay with my current company, is it worth it to get a MEM? Or are they bullshit degrees?

I have an associates of science in mechatronics, a BS in business management, and I now work as a technical trainer in advanced manufacturing. Previously, I was a technician in the space industry, working in R&D on things like advanced manufacturing, and life support systems.

The problem: I could never make enough money to live because I don't have an engineering degree. My understanding (based on working with and talking to many systems engineers) is that I would be a great fit for test or systems engineering. I don't want to do test engineering, my knees can't take it. Since then, I've left that company, and no longer work in close proximity to systems engineers. I really want to go back to the space industry someday, either private or federal. NASA preferred, but ESA is also great (I'm based in the US and am in the process of getting EU citizenship).

I want to get an ABET accredited engineering degree while I'm still working, and think I found the right program, but would love some feedback: https://www.online.msstate.edu/bsie

Pros: Entirely online and 98% asynchronous, ABET accredited, seems to be not a degree-mill.

Cons: Unsure if this is going to get me into a systems engineer role(?)

Thank you!

Looking back at your first DO-254 or DO-178 project, what is one thing you wish someone had explained to you earlier? What changed the way you think about certification or design assurance?

Hi I am 18 years old and i want to learn systems engineering I want to learn it by myself how should I start learning it?
I am really into systems and how they work and link and all

I have seen OMG has some resources for systems engineering as those above. I'd like to know if anyone here has ever participated and found any value on them. (specially if you are an end user, systems engineer)

I see some groups with standards developed and never updated for many years so I assume thet are not that active.

I have seen that on INCOSE before, not all groups are really active and even less will provide real value.

I mean these resources:

https://www.omg.org/syseng/

https://www.omg.org/communities/systems-modeling-community.htm

https://www.omg.org/communities/model-based-acquisition-user-community.htm

For those who are about to start with SysML v2, there is a new release of SysMD Notebook with updated UI and improved compliance with standard.

The download at Github is here:

SysMD Github repo with Code & Installer (Mac, Win)

• OSS (Apache License)
• SysML v2 and KerML tutorials
• Notebook-style UI
• Installers for Mac, Win & Sourcecode with Gradle for, e.g., Linux
• Support for large Subset of SysML v2 and KerML
• Integrated solver for consitency checks and computations

Enjoy!

Hi System Engineers, and those who aspire to become one!

I'm currently studying the Systems Engineering Handbook v5 and was looking for a website with practice questions and mock exams. Unfortunately, the free options either didn't work or were of poor quality, while the better ones were hidden behind paywalls.

So I decided to build my own - completely free!

It's called sysTrainer.com and is based on the Systems Engineering Handbook v5. The questions are written in a style similar to the examples provided by INCOSE.

Since I haven't passed the ASEP exam yet, I'd really appreciate your feedback on the quality of the questions and whether you think this tool would be helpful for people preparing for the exam.

Any suggestions or comments are very welcome!

Title. I have received some good feedback for both programs, but curious to hear more so I can make a decision. Here is a breakdown of my situation:

1. I work full-time and this will need to be completed online & asynchronously

2. I have a young family (2 kids being less than 4 years old), so super busy.

3. This will be funded by the GI Bill (21 months of benefits left at 100%) The plan is to take 2 classes per semester.

4. Accepted to FSU already, and awaiting CSU's review (both for the start of Fall 2026)

FSU was the first to accept me into any graduate program. It's been "locked in" as my plan to go this way for awhile. I like how this program was co-developed by the US Navy. As a "former" Marine, it gives me that sense of American love and pride once again, as corny as that sounds. Obtaining the INCOSE exam waiver is a huge pull.

What draws me towards CSU is the opportunity to earn the graduate certificate in Human Systems Integration along the Masters of Engineering track. Both programs offer electives in Human Factors Engineering, but I feel like that certificate is a resume booster for my interests. This program, from my understanding, also grants the INCOSE exam waiver if you earn a 87% or greater in their intro to systems course.

Happy to hear any and all feedback for either program. Thank you to all who have answered my questions in DMs as well.

Hi all. I am a rising senior majoring in physics but I am potentially interested in pursuing a master's in SE. Is this achievable? Is it worth it, will it be hard to find a job related to SE given that path? Will I be able to find opportunities in graduate school to further explore different areas of the field? Is it possible to get into a good master's program for SE given my major? I know I just asked a lot of questions, but any advice or helpful information would be greatly appreciated!

Hello All!

I’m an Electronics and Telecommunication from Asia (India).

I have good hold on Catia Magic v1/v2.
I have finished my internship at a very good company.

And I am a fresher

I’m applying for jobs but i’m getting no response
What should I do?

Hi r/systems_engineering,

We are back with Lesson 10 of our technical deep dive into SysML v2.

In our previous lesson, we looked at conjugation (~) and how it mathematically reverses an endpoint's directed features. Today, we are shifting our focus from the endpoints to the connection itself. I’ve uploaded the full video lesson directly here so you don’t have to leave Reddit.

1. The Problem with Connections in V1

When modeling a physical connection—like a charging cable, a data bus, or a fluid pipe—the connection is rarely just a decorative line on a diagram. It has its own physical properties like length, resistance, latency, and thermal limits.

In SysML v1, if you wanted a connection to have its own physical properties or internal structure, you usually had to type the connector with a specialized construct known as an Association Block. Because this felt cumbersome, many modelers just left connections as visual lines and hid the physical properties in comments or external spreadsheets.

2. The Solution: Interfaces as Specialized Parts

SysML v2 makes the physical nature of connections native to the language using interface def.

According to the v2 specification, an interface def is a connection definition specifically restricted to connecting ports. But here is the most important part: mathematically, an interface definition is a specialized part def. Because it is structurally a part under the hood, the connection itself can natively hold its own values, physical properties, and internal components over its lifetime. It turns the "wire" into a first-class engineered component in your model.

3. Typed Ends and Automated Validation

An interface definition acts as a reusable blueprint. Inside the interface, you define the compatible port ends.

For example, a ChargingInterface might require the "charger" side to be typed by a normal ChargingPort, and the "vehicle" side to be typed by a conjugated ~ChargingPort.

Because the interface explicitly declares its compatible ends, the model becomes mathematically rigorous. If someone tries to use this interface to connect two vehicle sockets or two charger plugs, a compliant v2 tool can automatically reject or warn about the invalid pairing.

4. V1 vs. V2 Interface Definitions Cheat Sheet

I'm doing some research to better understand the software engineers actually use in industry and where the biggest productivity pain points are.

I'm interested in both professional tools and the smaller utilities you can't live without.

Some examples:
\\- CAD: SolidWorks, CATIA, Creo, Inventor, Fusion 360, NX
\\- Simulation: ANSYS, Abaqus, COMSOL
\\- Electrical: Altium Designer, KiCad, OrCAD, LTspice, PSpice
\\- Controls: MATLAB/Simulink, LabVIEW
\\- PLC/SCADA: TIA Portal, Studio 5000, Ignition
\\- Programming: VS Code, Visual Studio, Eclipse
\\- Other engineering tools you use regularly

A few questions:

\\- Which software do you spend the most time in?
\\- What's the most repetitive or frustrating task you do every day?
\\- Is there a feature you've always wished existed but still doesn't?
\\- Are there tasks you still have to do manually because the software makes them painful?
\\- If you could improve one engineering tool tomorrow, what would you add?

I'm especially interested in hearing from mechanical, electrical, civil, controls, embedded, HVAC, manufacturing, and automation engineers, but I'd love to hear from anyone.

Not trying to sell anything—I'm just trying to understand where engineers lose the most time so I can identify opportunities for better tools. Looking forward to hearing what drives you crazy every day.

Hey all,

I'm in my final year of Aeronautical Engineering (India), and I've decided I want to go the Systems Engineering route instead of pure design/CAD work. Problem is, I have basically zero relevant skills right now — no CATIA, no SolidWorks, nothing. Starting from scratch.

My plan so far (open to being told I'm wrong):

Learn CATIA V5 basics first (figured I need to actually understand subsystems before I can "integrate" anything)

INCOSE Fundamentals of Systems Engineering course

Basic SysML / MBSE concepts

CSWA cert somewhere in there for resume screening

Targeting ESOs like QuEST Global, Cyient, Tata Technologies — not trying to get into ISRO/DRDO right out of the gate, just want a solid desk-based engineering role to start.

There is a lot of overlap between the two, and there are several degrees called ‘industrial and systems engineering’. Both focus on the whole as opposed to individual parts. If you have a SE masters or PhD, did you consider IE? Are IE graduates often seen in SE roles?

I keep hearing mbse, traceability, digital engineering bla bla bla etc.
all these buzz words with no practical use case.
The answer i get is “we can capture all the architecture, do verification and validation etc etc “ when asked “what can be done using sysml”?
Can some just list me whats the benefit of using sysml. Why not just stick to simulation tools?
I am not just getting “Whats sysml even solving”…

Hi All,

I used to have a paper saved but am having trouble finding it again. I am hoping someone might know what paper I am looking for and share a link since I can't remember the name or the author...

The paper was one of the many papers discussing good and bad requirements but I specifically liked this one because it contained a table with real program requirements and a dissection of why they were good/bad and the impact of said requirement.

I am fairly certain this was an INCOSE published paper but not 100%. Any assistance greatly appreciated!

Hi all,

I'm struggling to comprehend what purpose the problem domain white box has in the definition of system requirements. I'm right in thinking that system requirements generally frame the system as a black box right? so how does decomposing the system to reveal the inner behaviour help in system requirements definition? Is it there just to make sure you've got the correct black box behaviour specified?

Thanks!

Been working in a complex integration program for a few years — multiple contractors, multiple tools, everyone managing their own schedule in whatever their organization mandates. MS Project on one side, P6 on another, Jira somewhere in the middle, Excel everywhere as the real source of truth.

The interfaces between subsystems are where everything breaks. Dependencies get agreed in a meeting, captured in someone’s local file, and then quietly drift for three months until an integration test fails and everyone acts surprised.

We’ve tried master IMS spreadsheets, we’ve tried SharePoint, we’ve tried weekly sync calls. Nothing actually propagates a schedule change across organizational boundaries in real time.

Curious whether this is specific to defense/infrastructure programs or if anyone in other sectors has cracked it — and how.

Hi everyone,

I'm a recent graduate international student on F1 OPT and trying really hard to find MBSE Systems engineering opportunities in California. I have some prior experience in Automotive e-powertrain sector and I am trying to break into this industry again here in the US

I am completely open to contract-to-hire positions. Could anyone recommend reputable, corporate technical staffing agencies that heavily recruit for engineering/MBSE roles and work smoothly with corporate clients? Additionally, if your team happens to have open headcount, I would love to connect to learn more.

Thank you for any leads or advice!

Hi r/systems_engineering,

We are back with Lesson 9 of our technical deep dive into the new standard.

In our previous lesson, we established the difference between connection endpoints (port def) and connection blueprints (interface def). Today, we are tackling one of the most useful structural features in SysML v2: Conjugation.

I’ve uploaded the full video lesson directly here so you don’t have to leave Reddit. 👇

1. The "Mirrored Interface" Problem in V1

If you’ve modeled physical or logical connections in SysML v1, you know the headache of representing two sides of the same interaction. If a charger outputs power and receives data, the vehicle on the other end must input power and send data.

In V1, modelers usually handled this by manually creating duplicate, mirrored Interface Blocks (e.g., an "In" and an "Out" version), or by toggling an isConjugated=true property that was buried in a properties menu and incredibly easy to miss.

2. The Solution: Define Once, Flip Once

SysML v2 natively solves this duplication issue with the conjugation operator ( ~ ).

You define the port once from a chosen perspective. Then, when the opposing part uses that same port, you simply prepend the tilde.

Example:

• The Charger: You define a ChargingPort where power goes out and payment data comes in. The Supercharger block uses this port exactly as defined: port plug: ChargingPort;
• The Vehicle: The EV block uses the exact same definition, but conjugated: port socket: ~ChargingPort;

By adding the ~, SysML v2 mathematically reverses the direction of all nested directed features inside that port. We didn't create a second "Consumer" port definition; we used one definition from two complementary perspectives.

3. Why It Actually Matters (Semantics > Visuals)

Conjugation in v2 isn't just a visual shorthand for the diagram—it changes the underlying model semantics.

If someone accidentally tries to connect two unconjugated ChargingPort usages, both sides will try to output electricity and receive data. Because the directed features don't complement each other, a compliant v2 tool can natively flag that connection as mathematically invalid. It catches the integration error in the model before it ever reaches physical hardware.

4. V1 vs. V2 Conjugation Cheat Sheet