Great video. Nice and clean review of topics. Requirements section could benefit from introducing Design Thinking to arrive at desired outcomes consumers of the product (solution) . The first challenge is mapping those desired outcomes to features (FFs & NFFs). The next challenge is mapping the features to services, realized through processes and functions (function points) If we assemble this into a modeling environment we can run simulations to analyze lineage, completeness, and identify gaps. This is valuable for discussions with stakeholders and providers who fund and build (or assemble) the solution so they understand the impacts of scope change.
Thanks for the feedback Jeffrey, and the expansion. Scope definition is always a big issue, and being able to model changes for impacts definitely would be handy!
Very nice video! I will be doing a master in data science and there are quite a few of system engineering courses. This video really helped me understand what it is, especially with the keyboard example since I am a semi mechanical keyboard enthusiast =)
Enjoyed the presentation. Sometimes it's just easier to just write your thoughts down on a piece of paper rather than tons and tons of PowerPoint slides.
Thank you, old-school blackboard/whiteboard style teaching is a method I enjoy doing in the office in-person when I can, but these days you have to adapt and evolve :)
I didnt understand something, i am not a systems engineer i am just looking for something that i wonder. Are the systems engineer building the product or just making any product compatible with related systems or just building require product for making things more compatible and controllable
Its not that straight forward. A systems engineer is kind of like a consultant who works with design engineers, production engineers, development engineers, hardware engineers, software engineers etc. As part of the chain of events, the systems engineer ensures that all of the considerations are covered, from what the 'system' needs to include, and as you say, the important compatibility with relevant systems and so on, so forth. They themselves are like the spiderweb and glue of the design, testing, and implementation of a 'product' or 'system'.
INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and activities NASA Systems Engineering Handbook System Engineering Fundamentals - Defence Systems Management College (DSMC Press) System Engineering Analysis, Design, and Development: Concepts, Principles, and Practices: Charles S. Wasson 2015 should get you going.
If you were really interested though, there are a lot of things out there that you could look at to learn more about Systems Engineering. I think from a basics point of view, no-one is too dumb for it!
![Basic Introduction of Systems Engineering (V-method) [Part 1 of 2]](/img/logo.svg){kind=logo}
