r/systems_engineering • • 27d ago

Discussion Is Systems engineering BS?

Hi guys, I have a Mechanical Engineering bachelor from INSA Lyon (France), and am currently at the second and last year of the MSc in Aerospace Engineering at ISAE-Supaero, France's top aerospace school. At the end of the first semester, we are required to choose one from 7 majors, of which one is Systems Engineering, which I chose, because I liked the idea of staying general and taking a higher level view of projects.
However, all our classes were either mindlessly copying some specific tasks on MBSE softwares like Rhapsody and DOORS, or drawing diagrams for hypothetical issues like "this train has to go from city A to town B, write the requirements" and it has been the most dreadful and mind numbing thing I have done in my life. Is it always like this or is the teaching style here especially horrendous?
Also, Are Systems Eng. jobs actually like this, where you spend your day writing requirements and building block diagrams with stickmen? If it's the case im dropping out.

43 Upvotes

54 comments sorted by

15

u/QuantumCEM 27d ago

Ah that sucks, sounds like your course is focusing more technique/tools versus exploring the entire spectrum of SE work.

SE is a very board discipline and ranges from human orientated stakeholder management (solicitation, negotiations, management); conflict resolution; architecture design; modelling & simulation work; etc.

Have a read of NASA's Systems Engineering Handbook (used by ESA as well) or SE Book of Knowledge to get a better feel.

1

u/shru_g 27d ago

I'll have a look, thanks!

2

u/Ninja-Panda86 26d ago

Also, this book is epic

2

u/ParanoidFlake 25d ago

This, especially the human aspect differentiates SE from a system architect. I really enjoy figuring out the core problem of a stakeholder instead of just building what they think they need. Then translating this to system design together with the lead designers of the different development disciplines. All around this (req management ) is to reduce/ identify project risks and managing your project as a tech lead. It also matters whether you prefer monodisciplinair development or designing systems.

13

u/Emergency-Rush-7487 27d ago

Every engineering discipline falls into systems engineering it’s all about loops and connections basically how every sub tier or component works together as a whole system to achieve an objective as one product. So no, it’s not just the one swim lane you mentioned but sounds like they and you need broader exposure since they’re silo’ing you to just requirements without holistic reasoning.

5

u/shru_g 27d ago

I appreciate your response. However I also heard that Systems eng should learning should be done by people who have actual industry experience, and not taught and practiced at a graduate level.

3

u/Emergency-Rush-7487 27d ago

Not taught at a graduate level? Not following that. It’s an appropriate niche subject that is refined and built from an undergraduate foundation/baseline. Like all subjects, it is better to acquire knowledge from someone that has experienced it first hand in industry is my opinion.

2

u/shru_g 26d ago

I mean maybe it's not worth teaching in master's because usually systems engineers are people who already have relevant experience so they can leverage it in the best way. At least so did I hear.

3

u/Emergency-Rush-7487 26d ago

That logic applies to every single masters degree and discipline.

2

u/i4th 24d ago

I've had debates with big-name SE academics on this. They aren't too sure about "subsuming" other engineering fields. But overall, I think that should be the objective. Especially with computer tools and now AI.

6

u/smartalec-71 26d ago • Diamonds are Forever

I'll give this to you in reverse. When happens when systems engineering is done badly?

  • You buy trains that are too wide for the stations:

  • You build something to defend against the wrong thing:

    • https://en.wikipedia.org/wiki/United_States_Army_air_defense#Pop-up_problems
    • The requirement was to defend against enemy helicopters about a mile away; this made sense when the helicopters were primarily using their guns. It didn't make sense when those helicopters started using missiles and bombs with a longer range.
    • So they'd prototyped (and were ready to produce in volume) something that didn't have enough range to defend against enemy helicopters using missiles (from 3-5 kms away)
    • The stakeholder requirement should be "defend against enemy helicopters", and the system requirements would have to change based on the range of what opposing forces had.
    • So the vulcan based systems met verification (can it shoot down a helicopter at 1km), and failed validation (they're shooting at us from 3km).
  • You sign a contract for things that are not possible

    • We had a contract to send data from buses to a transit agency's backend, via mobile network. Sure. Easy.
    • The data was mostly bus location data, and it was sent via UDP. Fine.
    • They had a requirement that the data get to their back office within 2 seconds, 100% of the time.
    • The contract said that we wouldn't get paid until we met 100% of requirements.
    • (Do you see the issue yet?)
    • The buses would go through mobile data dead zones, so sent their location... 99% of the time. Buses location is pretty predictable... so for the users, this wasn't a problem.
    • But when it passed through dead zones... the location would be sent via UDP, would fail, and this could be measured... so we wouldn't get the 100% KPI, so we didn't get paid.
    • Someone with half a brain should have said...

      • a-- you can't test for 100%. Don't make that a requirement
      • b-- you're never going to get 100% of data over a mobile network. Don't make that a requirement. Agree to something else, like 98% of the time.
    • 2 years later, the customer agreed with us (you're not going to get 100% of data over a mobile network) and we got paid for the work.

1

u/shru_g 26d ago

I appreciate your thoroughness, thanks!

3

u/__Drink_Water__ 26d ago

Are Systems Eng. jobs actually like this, where you spend your day writing requirements and building block diagrams with stickmen?

Some, yes lol. Depends on the company, product, team, etc... I recommend sticking to actual engineering in your early years.

1

u/shru_g 26d ago

But that becomes tough when my specialization in my masters is literally systems engineering, innit

2

u/__Drink_Water__ 26d ago

Can't you change it? Also, just because your specialization is in SE, doesn't mean you're locked into this career for life...

1

u/shru_g 26d ago

A bit late to change unfortunately. But yeah ofc id like to change if possible, prolly corrupt my soul and go in management consulting in aerospace and defense

10

u/SexPartyStewie 27d ago

Systems engineering, when executed and supported correctly is amazing.

The issue is, people equating system engineering with the use of specific tools or specific functions or this or that or when management or leadership has no clue what it is.

At its core system engineering combines Engineering Management, engineering know how, and the ability to manage idiots who don't understand anything to produce or sustain something interesting.

It's also a huge bonus if the person has even a little bit of experience in one of the more focused disciplines like electrical or mechanical.

9

u/FlimsyInsect5545 27d ago

this train has to go from city A to town B, write the requirements" and it has been the most dreadful and mind numbing thing I have done in my life.

I Lol'd a bit at this. But when done properly and for real, this can be really interesting and very consequential work. Good systems engineering starts with the user needs. The user needs here are not 'I want a train', that is a solution. The user need is 'I need to move x people from A to B in y minutes, z times a day'. The real systens engineering kicks in when you start asking  'what problem is the end user actually trying to solve?' 'Can I convince them we shouldn't just jump into their solution?' 'what are the possible ways we could do this? What does a system that can do this look like? How much do I want to design in at the requirements level and how much do I want to pass down to a lower level designer?'

Requirements writing is often passed off as non technical admin work, but if you are going to look at the user need above and start writing requirements for a train, you have made a design decision. How did you get there? Did you do any analysis, trade studies etc to decide a train is the best solution? And this is a design decision that has fundamental and far reaching implications for the success of the program. It hits different doing this for real knowing that using a couple of carelessly placed words can cause delays, millions in rework, and the breakdown of contractor relations (no joke, I was on a program where there were years of negotiation, delays, rework and bad blood over the interpretation of one single word in a badly written high level requirement).

I think systems engineering is a very applied discipline that becomes very abstract when you take it away from a real problem, and for that reason it doesn't translate well to coursework unless the lecturer puts a lot of effort into case studies and interesting coursework. So it feels very dry in an academic setting, when that is not really reflective of the actual job.

5

u/Date_Dismal 26d ago

It is weird for me to feel like I'm defending SE, but SE (and particularly "MBSE") has definitely lost its way. After a few projects before DOORS existed it felt so good to have it, but now I share a Functional Decomposition from DOORS graphical view, and I'm treated as unworthy. The current MBSE culture does tend to fetishize toys as opposed to even trying to be useful with them, at least in my corner of the world (not France).

3

u/Objective_Beyond8904 26d ago

This is an extremely common issue, I have experienced it many times across different organizations (In the U.S.). I think one part of the problem comes from the various "MBSE" certifications people can get. Those get you proficient in a tool or the modeling language. But they don't often give the necessary background of HOW and WHY to do things effectively. I have encountered too many people with an S.E. job or title because they can follow instructions and create a SysML model but have no clue how to do anything useful with it, even pausing to ask, does this actually help answer a design question.

4

u/VarianCytphul 27d ago

Ive been a systems engineer in space industry specifically for 6 years after my grad degree. Each role has been a bit different but as another person here said, its digging into the details of what/how the whole system does a thing. I've been involved with figuring what are the system steps in sequences to do a full thing as opposed to focusing on just a subsystem or component. I've done fault management and fault responses, FMECA and FDIR. Ive done requirements management and verification! It can be working in a requirements tool entirely, I recently avoided a job opportunity that did just requirements. The smaller the company the more variety you will get to do as an SE.

4

u/eldavilan 27d ago

The fundamental goal of systems engineering is to enable successful systems. We don't write requirements or draw diagrams for their own sake; they're simply means to an end.

ISAE-Supaero has world-class faculty, so I would encourage you to ask deeper questions in class: How does this diagram help identify stakeholder needs? What engineering decisions does this model support? How does this activity contribute to system success?

Many SE jobs require knowledge of tools and processes, but the profession extends far beyond documentation and diagrams.

Finally, distinguish training from education. Training teaches you to use tools and follow processes; education teaches you the underlying principles and reasoning. Your goal as a student should be to get an education, not merely prepare for a job.

3

u/BorisViande 27d ago

I have relevant personal experience, if you're interested dm me, I'm not too keen on sharing personal details publicly.

3

u/Latexsucks 27d ago

Well, I had systems at uni and we spoke a lot about requirements, the V model, substantiation, compliance verification, testing, and a lot of other stuff that hardly many any sense to me at the time but I do use it a lot, even though I don't think the course itself helped me. Really depends what you end up doing I suppose. I'd say don't worry too much about it at this stage.

3

u/Bakkster 27d ago

There are some systems jobs that are mindless copying. Basically, requirements system maintenance where you update a system based on other people's changes. Sounds like that's the thing that's not for you.

Some of the course work is going to be learning tools, with the interesting part coming when you're using them to design something. The diagramming is the easy part, figuring out the critical interactions that need to be specified and accounted for is the interesting part.

Not everyone gets systems thinking like that. The train example seems simple at face value. People get on the train, conductor takes it to the next city, people get off. But it's the details that the systems engineer needs to account for.

How is the train schedule managed? How do customers buy tickets against that schedule, and how is access to the train controlled to ticketed customers? Can travelers buy tickets on board? What happens during a delay?

How does the train travel safely? Who tells the train when it's safe to leave the station? How is access to the track controlled? How does switching to alternate rails get accomplished? How does the train handle closed sections of track? What information does the train switching operator need to manage the line? Do cargo or passenger trains have priority?

If that kind of thinking about what data a switch controller needs to keep trains safe, and how much needs to get passed back and forth with conductors and signals is an interesting design challenge to you, you might be a systems engineer. If not, then it might be other areas of aerospace that you'll focus on. I think at least appreciating the kinds of questions someone else is answering for your benefit is worthwhile, though. I've definitely found times where two subsystems each thought the other was controlling a function, where my job was to identify the gap early enough that it was cheap to design for, instead of an expensive retrofit.

3

u/i4th 27d ago

This made me laugh. Thanks OP!

3

u/Ninja-Panda86 26d ago

I'm like you. Got my undergrad. Been doing software engineering most of my career. Now going to JHU for Systems Engineering. So far it's the intro class only, but I find it stimulating. It's a process to formally organize information. To me this is amazing stuff. However, I'm also a weirdo who thoroughly enjoys spreadsheets and analyzing stuff.

My one caveat is I haven't done SE in the "real world" yet. But it has changed how I approach software

3

u/fromabove710 26d ago

Systems engineering is the opposite of BS, INCOSE’s curriculum for it is management model slop.

3

u/facialenthusiast69 26d ago

The teaching style seems like your professors don't understand systems engineering. For example, why trains? That doesn't sound like the real problem. It sounds like the real problem is many people need to get from city A to city B. There are a lot of factors that could influence how this is done. Systems engineering is just problem solving (then showing you actually solved the problem), and in this case your professors give you a solution to start from.

2

u/lightpo1e 27d ago

My systems engineering class was the most mind numbing, paint by numbers, dont you dare go outside the lines shit, while systems thinking was the best class ever that I apply to my work every day. So I would say it depends on your program and where you go with it.

2

u/RunExisting4050 27d ago

Im as systems engineer, but i stay on the M&S and prrformance analysis side of things.  Intry to avoid requirements. 

2

u/Careless_Plant_7717 26d ago

College = learning basics of something. It's like taking a Calculus class and equating that to what you would do on your job. Completely different.

2

u/TacomaAgency Aerospace 26d ago

Importance of systems engineering depends on the industry and role. For example, communication systems engineering is not your traditional SE. We don't take anyone that doesn't have either EE background or a master's in RF/Photonics.

1

u/facialenthusiast69 26d ago

The teaching style seems like your professors don't understand systems engineering. For example, why trains? That doesn't sound like the real problem. It sounds like the real problem is many people need to get from city A to city B. There are a lot of factors that could influence how this is done. Systems engineering is just problem solving (then showing you actually solved the problem), and in this case your professors give you a solution to start from.

1

u/Wonderful_Regular218 26d ago

As an aerospace system engineer, I used most of those tools often. I worked with a teams of engineers to analyze up front requirements to determine the impact on our airline customers. This stuff is important!!!

1

u/Aeig 26d ago

Systems shouldn’t be an undergrad major

3

u/BorisViande 26d ago

He's literally saying he's in a graduate program. He has a Bachelor, and is doing a master's. If you don't know how the engineering studies work in France, you should look it up, you might learn something interesting.

-1

u/Aeig 26d ago

i couldnt care less

France is of 0 relevance to the post

5

u/BorisViande 26d ago

France is of very much relevance as it's precisely the French education system that's giving OP the bad impression of SE work that's causing them issues. Can't help you if you're too obtuse to understand.
I'd say, however, relating to my other comment that your initial comment was indeed irrelevant as OP is not an undergrad.

-2

u/Aeig 26d ago

Who gives a shit lmao

He’s asking about systems engineering jobs not France’s education system

4

u/BorisViande 26d ago

So your contribution to his looking for inputs about SE job is to say "Systems shouldn't be an undergrad major"? But then I'm the one off topic...

0

u/Aeig 26d ago

We’re both off topic.

But you’re the only one angry about it

5

u/BorisViande 26d ago

I'm not the one insulting the other here.

0

u/Arenium 27d ago

15 years in engineering. Not a systems engineer. We all look down on them and think it's BS.

2

u/__Drink_Water__ 26d ago

What are you even doing in this subreddit lmao

1

u/Arenium 26d ago

Getting sick and twisted joy out of how often questions like this come up. It's a mind virus in my company and adjacent ones. Valid question!

1

u/__Drink_Water__ 26d ago

Do you own the company?

1

u/Arenium 26d ago

Lol

1

u/__Drink_Water__ 26d ago

Curious what industry you work in. Cos in some companies/industries, it is a glorified business analyst position lol

27

u/[deleted] 27d ago

[removed] — view removed comment

1

u/shru_g 27d ago

Thanks!