19 May, Sunday
11° C

The library of essays of Proakatemia

Guide to the Systems Engineering Body of Knowledge

Kirjoittanut: Esseepankin arkisto - tiimistä Ei tiimiä.

Esseen tyyppi: / esseepistettä.

Esseen arvioitu lukuaika on 2 minuuttia.

System engineering is a methodology to design and develop products in a step by step process. The purpose of this methodology is a concrete model of designing a process with minimal chance of failure. This book talks about multiple methods that have been used in companies to provide a solution according to customer needs. These methods have some common areas and that is Minimizing the process time, failures and costs to deliver the best solution. However using the methods yet is not one hundred percent guarantee of best solution.

This methodology is used in different fields, but in my idea the best application of such methods is in software development companies. The whole process for developing a new software is very well organized and Hierarchy of what to do next is quite clear. I recommend reading this book for people who have solid technical background, as there are loads of detail for understanding the process. However, in order to have a quick glance to the structure of one of these methodologies, you can consider a specific requirement that you will find at the beginning of your project, this requirement could be anything from your customer needs. Through the methodology, the need that you have chosen will go through the following steps and let’s name that need as parameter A:

  • Step 1: Requirement analysis
  • Step 2: System analysis and control
  • Step 3: Functional Analysis Allocation
  • Step 4: Design Synthesis


Parameter A must be clear and traceable during all the above steps, the relation of A must be clear with other elements of the system in every step as we go through all steps. Once the A is traceable in all steps then any change in A can be reflected back to all other steps. Although that may sound a time consuming at the beginning, but for a complex product there are numerous parameters that need to be taken to account. To ease this process, there are multiple software and also language programming (such as UML) are created. One of the examples of such software is SysMl, which is Briefly reviewed here for people who are interested to explore further:

SysMl is a visual modeling language that represents Semantic and notations for modeling system structure, system behavior and requirements and verification. Different type of block represents elements of a system such as sequence diagrams, state machine diagrams, requirement diagrams, activity diagrams, use case diagrams and etc. each type of diagram presents activities and flow of information in order to accomplish the design process. Nodes, flows, blocks are elements of SysMl environment that can represent each type of diagram.

From my point of view, reading of this book is not easy because the book is trying to fit different field of studies into one frame work. although you might find similarities in some fields, but they are essentially describing the world of academic with different languages and therefore modeling these languages into one is not feasible. other reason that reading this book is difficult is due to having it written by multiple authors.



  • Joonas Koivumaa

    Same as the other blog you should expand this one also. More reflection to this. This is more as a summary than reflection so doing the reflection you can expand these to show also your point of view.

Post a Comment