Great video. They are 15 years I am teaching my colleagues about System Engineering, but such a simple and clear explanation I never managed to reach! My respect
This is the possibly the best video on basic systems engineering ive ever seen. very simple and straight to the point explanation on V model. very good work.
Almost didn't watch this video when I saw MATLAB because I thought it was going to be about mechanical design alone. But i was wrong - It is the best and most properly explained video of Systems Engineering I've seen so far. Was glad brian used a software app example. Hoping more universities offer Systems Engineering at the Masters's (MSc) level. I will jump at it immediately. This teaches and prepares you to be a good Tech entrepreneur that isn't scared of tough tough problems.
Brian, when u started releasing videos 11yrs ago, I just started uni in elec eng. Your control system videos were a life saver, literally gold dust. We watched the whole series. Now fast forward, wanting to learn more, I came across these and literally gasped. Brian my friend, you deserve an award.
Hey guys, thanks for the messages. I did not get the job haha. After the phone interview I had a 4h interview with a panel of people where I presented about my projects for 1h, then I went for 5 1o1 interview for 30min each. I did well in all the interviews except the last one (the bar raiser) where I was asked many technical questions about cryogenic fluids. On my resume I said I was concentrating my masters degree in Fluids, so I think that is why those fluid system questions came up. Sad part is that I just started my concentration haha.
Sir, your material distilled the necessary knowledge to approach the subject in a few videos in a much more effective ways than hours of Powerpoints & PDFs I combed through before. Chapeau! Thanks
I've endured several systems engineering courses. They all dive into tedious detail straight out. This is a great overview and the slide at around 3:40 is a spot on top level summary. Thanks!
Great video. I've been a professional systems engineer for just over 2 years now, and still feel like I'm on a massive steep uphill learning curve, even with all the requirements engineering courses and INCOSE publications I've read I still find it a struggle. it's not for the faint-hearted. Just one thing I think was missing, or not drawn out in your video, was the boundary of the project, which you have to define as early as possible, to stop your system goalposts from moving. Anyhoo, I look forward to watching your other videos.
Well in systems engineering the learning curve never flattens out the way it does for a design specialist. Every change in regulations, every relevant change in technology(where relevant is up to you), and most changes in how things are done will pass your table at some point. And you got to have the courage to make or break stakeholder's expectations. Brian might have excluded the project boundary because it depends on the industry. At high stakes and risk you got to be very tight. To the point where aviation or nuclear plants do not allow any tech to be integrated that wasn't well-established when the project started. At medium stakes, you can be a little bit more flexible. Like with cars or smartphones where you get "facelifts" or "Gen.X". And at very low stakes, like "big tech/software" it's more important to adapt your goalposts to the current demand of the end customer than it is to keep a release date or scope. But yes having your goalposts moving too much basically means you are not doing your job right.
Great explanation. Thank you. just a consideration: solving problems, optimising a system, reaching a goal, responding to a customer's wants and trying to satisfy it, and innovation requires a slightly different approach. Another crucial element is whether the system already exists or whether it has still to be created.
I'm a college student fascinated with the design of complex systems. This was a fantastic video, thank you very much for taking the time to design and make it (wondering if you used a systems design approach when making the video haha)!
This is Brilliant! Happy to see my man Brian giving these kinds of talks! I'm expecting to see introductions on system programming languages like sysML and similar diagram based modeling tools, and how those tools interact and work for the whole system.
Hello Brian, you made excellent tutorial!! I've been in automotive industry since 2015 and your description well fits the reality. Really looking forward to seeing more lectures from you. Thank you!!
Sounds a lot like Product Management. Please look into what Product Management is and what it offers. Exactly the gathering and coordination of resources described in this video.
Lesson 1 completed Systems Engineering is a process that we can use to develop a model that is too complex to conceptualize, design and build. As a monolithic, single, indivisible, interconnected, whole but distinct entity. • What is the definition of a monolith? - A block. - A system made up of units. - A sphere. • What is the definition of single in the context? - Independent. - Different. - Unique. • What is an indivisible system? - Separable. - Indespensable unit. -Unbreakable. • Then how can it be interconnected? - It has a grid line. - It is aligned. - it is interdependent. • So how is it distinct from other models? - It is different. - It unique. - It is bold. • What is an entity? - A monolith - Single -indivisible - whole - and distinct structure.
Systems Engineering is a process that we can use to develop a MODEL that is too complex to conceptualize, design and build. As a monolithic, single, indivisible, interconnected, whole but distinct entity. • What is a model? - A thing used as an example to follow or imitate. - An applicable condition used to achieve an end. - The derivative of a set plan or objective. • What is complex? - Difficult. - Intertwined. - Impossible. • What is design? - To impress -"A plan or specification for the construction of an object or system or for the implementation of an activity or process or the result of that plan or specification in the form of prototype, product or process."- google - To bring an idea to life. What does build mean? - To do something in addition to that achieved. - To add upon previous wins. - To transform a given process. ….............................................................
I love Systems Engineering. It is the missing language all engineers need to learn. Thinking in terms of systems with multiple interdependent components where each component/module can again be considered as a system of interdependent modules.
Pretty well presented. I didn't agree with everything, but pretty good overall. Just to note that very complex projects are doomed to fail without a systems engineering approach, these are mainly space projects, defence, medical equipment, and aerospace. Also the cost of the SE function changes with complexity, from a few percent of the design cost, to 10-20% of total project cost.
I've spent alot of my career in application-level software projects throughout medical, fintech and other industries and I strongly believe the Systems Engineering approach is hugely beneficial there as well. People who do it right are often doing Systems Engineering without even knowing they are. Those that don't usually fail.
Also system engineering is covered by the standards ISO 15288 for systems and ISO 12207 for software. For simpler systems, ISO 29110 a free publically available standard can be used.
Great video. I would make one comment is that integration and verification begin during the development phase to identify integration requirements and aggregates and the verification criteria needed for the system elements and sub systems. See ISO 24748-6 Integration Engineering and IEEE 1012 Verification and Validation
After watching this video I'd say I'm slightly more confused as I thought a systems engineer was responsible for designing IT systems for a corporation but the way its described here makes it seem more like a general engineering job. Also would like to ask if this job title gets misused a lot and mislabeled. I was recently reached out to for a systems engineer job and the way it was described to me gave me the impression the position is more like a systems administrator job dealing with servers and whatnot.
WHAT IS SYSTEMS ENGINEERING AND SYSTEMS THINKING? Systems Engineering is a process that we can use to develop something that is too complex to conceptualize, design, and build as a monolithic, single, indivisible, interconnected, whole but distinct entity. Explanation What is a process? • A process is an elongated time frame of work or a cycle of activity aimed at achieving a set of objectives or according to google search " a series of actions or steps undertaken to a particular end." What does it mean to develop? • To create or to build or to accomplish a task. ................................................................
Question: can a person with a major in systems engineering be hired at projects in different fields? Like jumping around between working at a medical company and an automotive company
Any idea what software he is using to create his presentation? I like his presentation style and clarity, love to try and adapt some of his techniques.
Sorry, just seeing this! I screen capture photoshop while I draw everything out. I then speed that video up and do a voiceover. I've detailed my process here a little more. Hope this helps! engineeringmedia.com/my-setup
Hi Brian, thank you for this video. i do have a question though. would you say a systems engineer basically looks out for potential problems in a system?
You could probably say that. But they also help to prevent problems in a system. I think the key is that, say, an electrical engineer can design a circuit board, understand what all the parts do and how they work together, design it in a way that meets requirements, ensure that it meets requirements through tests or something else, and always be on the lookout for problems in the board. Same for a mechanical engineer or anything else. A systems engineer does exactly this but at the system level. When a system because complex enough it requires a person or group of people to treat it like its own problem (like a circuit board or mechanical part). Someone needs to understand what all of the parts do and how they work together, design it in a way that meets system-level requirements and ensure it meets those, and always be on the lookout for problems. It's an engineer ... but at the system level. Did that answer your question?
Quality engineer is a somewhat broad term. In my experience as one that works on medical devices, ultimately we are focused on effective ways to test the requirements that systems engineers define. Good quality engineers will recognize the "spirit" of a requirement, and create test methods that verify the system/subsystem meets a requirement while minimalizing the chance of false-pass. That process includes a lot of risk management, creating uncertainty budgets for the measuring equipment you use, performing G R&R's. We also help other engineering disciplines test their work (did X change fix the problem?).
Hi, I had completed my UG degree in the course Robotics and Automation, and I am going to pursue my masters this fall (coming August) in the course MS in Robotics and Autonomous systems and the specialization is Systems engineering. Hope I had chosen this course correctly. Pls be free to share your opinion
@@josephanthony1655 I would advise you to do so, since algebra, geometry, and precalculus provides the foundations to understand the new concepts you see in Calculus (Examples: Algebra has Logarithms and Cartesian Planes, Geometry has Volumes of Revolution, PreCalc provides domains and ranges for trig functions and trig rules).
in practice, not 'exist' systems engineering. = software producer = T.I = sistem analist not "system engineer". in practice, system engineering is software engineering, Techology information. Please, make a REAL SYSTEM Engineering. System = ALL not only 'softwares' of fking informatic area
@@geekovishlord4778 I watched the entire video. He spent more than half the video explaining how it's not a middle man position without giving any quantifying data
@@ykr786 Many studies have shown how systems engineering is a key factor in reducing the costs of development of systems engineering and how it is necessary especially when developing critical systems. Using the term "middle man" implies that systems engineering introduces more costs to the project development (like a middle man in sales for example that can be reason of a high cost of the end product that is sold). There is a certain cost to using system engineering in projects but the return of investment is well worth the cost and seeing the systems developed today, in different domains are more and more complex, systems engineering is becoming a necessity to develop such systems. You can easily find studies quantifying the benefits of using systems engineering
@@geekovishlord4778 you are right that I am implying that systems engineers are just a burden on cost. That's because the things they do can easily be achieved by quality engineers, product engineers or even by a technical engineer with the right IT tools
As he stated it everyone is a system engineer for small projects, it is the big projects that are complicated that need a dedicated group of people to get that job done instead of taking time from the other specific groups
Great video. They are 15 years I am teaching my colleagues about System Engineering, but such a simple and clear explanation I never managed to reach! My respect
same!!
rightly said!!!!, do you aware of the software tool he is using to make the model time stamp 6:20 in the video???
@@ervikrantsharma You mean System Composer? It is an add on of Matlab Simulink.
@@carlotuzi5027 i am new to matlab will explore
This is the possibly the best video on basic systems engineering ive ever seen. very simple and straight to the point explanation on V model. very good work.
a new series by Brian, that made my day
Almost didn't watch this video when I saw MATLAB because I thought it was going to be about mechanical design alone. But i was wrong - It is the best and most properly explained video of Systems Engineering I've seen so far.
Was glad brian used a software app example.
Hoping more universities offer Systems Engineering at the Masters's (MSc) level. I will jump at it immediately.
This teaches and prepares you to be a good Tech entrepreneur that isn't scared of tough tough problems.
I can not agree less on this bro
@@ebobomaxwell2577 and that’s fine.
But with any reasonable argument you have to back it up with facts.
Brian pops up in so many places, I practically owe him my career at this point
Brian, when u started releasing videos 11yrs ago, I just started uni in elec eng. Your control system videos were a life saver, literally gold dust. We watched the whole series. Now fast forward, wanting to learn more, I came across these and literally gasped. Brian my friend, you deserve an award.
🥰 I really appreciate that! I can't believe it's been 11 years though
If I get a systems engineering position at BlueOrigin I have to thank him, technical phone interview tomorrow!
Good luck mate
Good luck! I hope you get that position!
How did it go??
How did it go mate
Hey guys, thanks for the messages. I did not get the job haha.
After the phone interview I had a 4h interview with a panel of people where I presented about my projects for 1h, then I went for 5 1o1 interview for 30min each.
I did well in all the interviews except the last one (the bar raiser) where I was asked many technical questions about cryogenic fluids.
On my resume I said I was concentrating my masters degree in Fluids, so I think that is why those fluid system questions came up. Sad part is that I just started my concentration haha.
Sir, your material distilled the necessary knowledge to approach the subject in a few videos in a much more effective ways than hours of Powerpoints & PDFs I combed through before. Chapeau! Thanks
Thanks for the kind comment :)
I've endured several systems engineering courses. They all dive into tedious detail straight out. This is a great overview and the slide at around 3:40 is a spot on top level summary. Thanks!
Great video. I've been a professional systems engineer for just over 2 years now, and still feel like I'm on a massive steep uphill learning curve, even with all the requirements engineering courses and INCOSE publications I've read I still find it a struggle. it's not for the faint-hearted. Just one thing I think was missing, or not drawn out in your video, was the boundary of the project, which you have to define as early as possible, to stop your system goalposts from moving. Anyhoo, I look forward to watching your other videos.
Did you get any of the INCOSE certs? I have one.
Well in systems engineering the learning curve never flattens out the way it does for a design specialist. Every change in regulations, every relevant change in technology(where relevant is up to you), and most changes in how things are done will pass your table at some point. And you got to have the courage to make or break stakeholder's expectations.
Brian might have excluded the project boundary because it depends on the industry. At high stakes and risk you got to be very tight. To the point where aviation or nuclear plants do not allow any tech to be integrated that wasn't well-established when the project started. At medium stakes, you can be a little bit more flexible. Like with cars or smartphones where you get "facelifts" or "Gen.X". And at very low stakes, like "big tech/software" it's more important to adapt your goalposts to the current demand of the end customer than it is to keep a release date or scope.
But yes having your goalposts moving too much basically means you are not doing your job right.
Great explanation. Thank you.
just a consideration: solving problems, optimising a system, reaching a goal, responding to a customer's wants and trying to satisfy it, and innovation requires a slightly different approach. Another crucial element is whether the system already exists or whether it has still to be created.
I'm a college student fascinated with the design of complex systems. This was a fantastic video, thank you very much for taking the time to design and make it (wondering if you used a systems design approach when making the video haha)!
This is the best video on the complete description of Systems Engineering
🥰
@@BrianBDouglas Hey man, i just subbed to your channel. Great content on control systems.
Thank you Brian. Convaying knowledge in a simple way is a hard work and I'm sure it takes considerable amount of time and effort! Appreciate it mate!
Excellent video. I appreciate the simplicity with which you explained the essence of systems engineering.
This is Brilliant! Happy to see my man Brian giving these kinds of talks! I'm expecting to see introductions on system programming languages like sysML and similar diagram based modeling tools, and how those tools interact and work for the whole system.
I would be happy to add that as well. There are some pretty nice and cheap Udemy courses if its urgent for you. :)
telling your team to NOT jump right in to design is the hardest part....,
Or telling the stakeholder
Best Video about SE! I have to hold a presentation about this soon and this is so much better and joyful than the given source!!
Thank you Brian! your controls series was amazing excited for this new one
Thanks!
Hello Brian, you made excellent tutorial!! I've been in automotive industry since 2015 and your description well fits the reality. Really looking forward to seeing more lectures from you. Thank you!!
Can robotics engg can make UGVs
Lucky to have you as a teacher❤️
This series is absolute gold! Thank you for creating it. :)
I will say one thing: I wanna be like this guy. God damn it, he's so smart 🙌🏼
amazing series for systems engineering 101! what do i do without you?
He taught me so much，even English！
Wow! Amaying and simplified video. A great way to explain the approaches and concepts. Thanks a lot Brian
Oh! A new serie by Brian :D
I'm excited to get this one shared. Thanks for the comment!
Sounds a lot like Product Management. Please look into what Product Management is and what it offers. Exactly the gathering and coordination of resources described in this video.
Check out the International Council on Systems Engineering. I have one of their certifications.
Tanks. Nice and informative, easy to follow and understand, present for the ear.
Lesson 1 completed
Systems Engineering is a process that we can use to develop a model that is too complex to conceptualize, design and build. As a monolithic, single, indivisible, interconnected, whole but distinct entity.
• What is the definition of a monolith?
- A block.
- A system made up of units.
- A sphere.
• What is the definition of single in the context?
- Independent.
- Different.
- Unique.
• What is an indivisible system?
- Separable.
- Indespensable unit.
-Unbreakable.
• Then how can it be interconnected?
- It has a grid line.
- It is aligned.
- it is interdependent.
• So how is it distinct from other models?
- It is different.
- It unique.
- It is bold.
• What is an entity?
- A monolith
- Single
-indivisible
- whole
- and distinct structure.
This is amazing. Do you have any plans on making a series on tools like Autosar, Dspace?
Now, I am clear about what I want to approach.
So glad to hear! Can you tell us more? What was your takeaway?
This is an incredible video about SE, very clear and objective, thanks for this great job!
Glad it was helpful!
Amazing and nicely presented role of system engineer! I can personalize it!
*Systems engineer. A big difference. Other than that you are right.
Such a great explanation!! Thank you so much
Beautifully concise
Systems Engineering is a process that we can use to develop a MODEL that is too complex to conceptualize, design and build. As a monolithic, single, indivisible, interconnected, whole but distinct entity.
• What is a model?
- A thing used as an example to follow or imitate.
- An applicable condition used to achieve an end.
- The derivative of a set plan or objective.
• What is complex?
- Difficult.
- Intertwined.
- Impossible.
• What is design?
- To impress
-"A plan or specification for the construction of an object or system or for the implementation of an activity or process or the result of that plan or specification in the form of prototype, product or process."- google
- To bring an idea to life.
What does build mean?
- To do something in addition to that achieved.
- To add upon previous wins.
- To transform a given process.
….............................................................
I love Systems Engineering. It is the missing language all engineers need to learn. Thinking in terms of systems with multiple interdependent components where each component/module can again be considered as a system of interdependent modules.
Check out the International Council on Systems Engineering. I have one of their certifications.
@@FirstPeterr Thanks. It's more of interest than profession for me. But no doubt, it helps professionally as well.
Awesome video Brian as usual.
Loving these videos so far. Thanks Brian
Thanks Brian!!
Pretty well presented. I didn't agree with everything, but pretty good overall. Just to note that very complex projects are doomed to fail without a systems engineering approach, these are mainly space projects, defence, medical equipment, and aerospace. Also the cost of the SE function changes with complexity, from a few percent of the design cost, to 10-20% of total project cost.
I've spent alot of my career in application-level software projects throughout medical, fintech and other industries and I strongly believe the Systems Engineering approach is hugely beneficial there as well. People who do it right are often doing Systems Engineering without even knowing they are. Those that don't usually fail.
Also system engineering is covered by the standards ISO 15288 for systems and ISO 12207 for software. For simpler systems, ISO 29110 a free publically available standard can be used.
Nice. I was thinking of pointing that out.
Do you think that a systems engineering degree is worth it and in-demand?
Do you need a system engineer in the development of a SoC? Or it's all EE.
Logical architecture are also called functional architecture, is that so ?
I'm new to systems engineering. Question: is it the same as business analysis? Differences?
Very well explained ,impressive
Thanks!
Can someone explain what a system is? He talks about using/designing systems but what is it?
This is SO nice
Thank you :)
Great video. I would make one comment is that integration and verification begin during the development phase to identify integration requirements and aggregates and the verification criteria needed for the system elements and sub systems. See ISO 24748-6 Integration Engineering and IEEE 1012 Verification and Validation
What a fantastic video!
thanks Brian for this great content
I wish I could present like this guy
Nice and detailed explanation! But isn't the thing you mentioned as "systems engineering" called PLM (product lifecycle management)?
From my understanding, PLM is the process or system that is needed after product is released. EcCR ECO happened in this stage
After watching this video I'd say I'm slightly more confused as I thought a systems engineer was responsible for designing IT systems for a corporation but the way its described here makes it seem more like a general engineering job. Also would like to ask if this job title gets misused a lot and mislabeled. I was recently reached out to for a systems engineer job and the way it was described to me gave me the impression the position is more like a systems administrator job dealing with servers and whatnot.
Great vid , easy to understand
WHAT IS SYSTEMS ENGINEERING AND SYSTEMS THINKING?
Systems Engineering is a process that we can use to develop something that is too complex to conceptualize, design, and build as a monolithic, single, indivisible, interconnected, whole but distinct entity.
Explanation
What is a process?
• A process is an elongated time frame of work or a cycle of activity aimed at achieving a set of objectives or according to google search " a series of actions or steps undertaken to a particular end."
What does it mean to develop?
• To create or to build or to accomplish a task.
................................................................
At the beginning, what do you mean by a single monolithic entity? Nice video, thanks! 👍
Question: can a person with a major in systems engineering be hired at projects in different fields? Like jumping around between working at a medical company and an automotive company
Is production engineering same as system engineering?
"Yes'nt" haha, depends of your specialization and experiences but "yes" in certain way.
Hello everyone kindly help me understand is systems engineering same as computer systems engineering? I'll appreciate
Any idea what software he is using to create his presentation? I like his presentation style and clarity, love to try and adapt some of his techniques.
Sorry, just seeing this! I screen capture photoshop while I draw everything out. I then speed that video up and do a voiceover. I've detailed my process here a little more. Hope this helps! engineeringmedia.com/my-setup
Hi Brian, thank you for this video. i do have a question though. would you say a systems engineer basically looks out for potential problems in a system?
You could probably say that. But they also help to prevent problems in a system. I think the key is that, say, an electrical engineer can design a circuit board, understand what all the parts do and how they work together, design it in a way that meets requirements, ensure that it meets requirements through tests or something else, and always be on the lookout for problems in the board. Same for a mechanical engineer or anything else. A systems engineer does exactly this but at the system level. When a system because complex enough it requires a person or group of people to treat it like its own problem (like a circuit board or mechanical part). Someone needs to understand what all of the parts do and how they work together, design it in a way that meets system-level requirements and ensure it meets those, and always be on the lookout for problems. It's an engineer ... but at the system level. Did that answer your question?
Excellent ..thank you.
U have tried to Simplify the Specific Subject within perfect boundary and its application to real world applications. Thanks for sharing.
Very good as usual. Thank you
What's the difference between quality and systems engineer ?
Quality engineer is a somewhat broad term. In my experience as one that works on medical devices, ultimately we are focused on effective ways to test the requirements that systems engineers define. Good quality engineers will recognize the "spirit" of a requirement, and create test methods that verify the system/subsystem meets a requirement while minimalizing the chance of false-pass. That process includes a lot of risk management, creating uncertainty budgets for the measuring equipment you use, performing G R&R's. We also help other engineering disciplines test their work (did X change fix the problem?).
What was this blackboard software was this video made with???
Nice cours, very interesting to hold up! Further, try to show the amazing engeening's apps, to be monetised.
Oops! The amazing effect of engineering's apps.
People needs utilities, i noted that with my own experience.
Great video
very well explained, thumb up!
Great Video. Are there a similar video on Systems integration and test engineering?
Excellent!
Great video!!
Came here because of Miss Kobayashi who works at systems engineering :O
Lol same
Stakeholders main requirement nowadays : ' The product has to fail within 6 months after the warranty expires '
Informative
I hope you choose e-VTOL aircraft as an example in the next video :D
Oof, please don't be disappointed by the example (it's not e-VTOL ... far from it actually) :)
@@BrianBDouglas no problem. It would still be great learning experience:)
Hi, I had completed my UG degree in the course Robotics and Automation, and I am going to pursue my masters this fall (coming August) in the course MS in Robotics and Autonomous systems and the specialization is Systems engineering. Hope I had chosen this course correctly. Pls be free to share your opinion
How much math is used what kind of math is used for system engineering.
Dont forget Emmergent Properties of System.
Can you please suggest me any certification on automotive system engineering and architecture.
Good stuff
Novel
What app are you using?
I've written up my process and the hardware and software that I use here: engineeringmedia.com/my-setup
The needs of the many outweigh the needs of the one
- Spock.
I’m about to make something great.
❤
Sa Bilkentli
as
as
What Math is needed ?
@@GajinWilk Thank You 👍
@@GajinWilk I forgot to ask. Do I have to learn algebra or anything other math before calculus ?
@@josephanthony1655 I would advise you to do so, since algebra, geometry, and precalculus provides the foundations to understand the new concepts you see in Calculus (Examples: Algebra has Logarithms and Cartesian Planes, Geometry has Volumes of Revolution, PreCalc provides domains and ranges for trig functions and trig rules).
@@screwyou3890 I've started on Algebra. Not sure where to go next.
Aoa surah 116 Ko purhna ki ejszat da de
Project HR and glorified babysitter, got it.
What makes you say that?
in practice, not 'exist' systems engineering. = software producer = T.I = sistem analist not "system engineer". in practice, system engineering is software engineering, Techology information. Please, make a REAL SYSTEM Engineering. System = ALL not only 'softwares' of fking informatic area
Systems engineer is basically a glorified middle man... As if the industry wasn't already filled with middle man
I suggest you rewatch the video. Your statement couldn't be farther from the truth.
@@geekovishlord4778 I watched the entire video. He spent more than half the video explaining how it's not a middle man position without giving any quantifying data
@@ykr786 Many studies have shown how systems engineering is a key factor in reducing the costs of development of systems engineering and how it is necessary especially when developing critical systems. Using the term "middle man" implies that systems engineering introduces more costs to the project development (like a middle man in sales for example that can be reason of a high cost of the end product that is sold).
There is a certain cost to using system engineering in projects but the return of investment is well worth the cost and seeing the systems developed today, in different domains are more and more complex, systems engineering is becoming a necessity to develop such systems. You can easily find studies quantifying the benefits of using systems engineering
@@geekovishlord4778 you are right that I am implying that systems engineers are just a burden on cost. That's because the things they do can easily be achieved by quality engineers, product engineers or even by a technical engineer with the right IT tools
As he stated it everyone is a system engineer for small projects, it is the big projects that are complicated that need a dedicated group of people to get that job done instead of taking time from the other specific groups
Thank you...well done