{"id":25945,"date":"2021-01-04T10:11:04","date_gmt":"2021-01-04T09:11:04","guid":{"rendered":"https:\/\/cesam.community\/2021\/01\/04\/chapter-8-conclusion\/"},"modified":"2023-01-23T10:29:52","modified_gmt":"2023-01-23T09:29:52","slug":"chapter-8-conclusion","status":"publish","type":"post","link":"https:\/\/cesam.community\/fr\/2021\/01\/04\/chapter-8-conclusion\/","title":{"rendered":"Chapter 8 \u2013 Conclusion"},"content":{"rendered":"

8.1 A first Journey in Systems Architecting<\/h2>

This pocket guide intends to offer to the reader a first journey through systems architecting and we hope that it was appreciated. We thus explored the following topics as provided in Table 11.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Chapters<\/strong><\/td>\nTopics covered<\/strong><\/td>\n<\/tr>\n
Chapter 0<\/a><\/td>\nSystems Fundamentals<\/a><\/td>\n<\/tr>\n
Chapter 1<\/a><\/td>\nSystems Architecting Motivations<\/a><\/td>\n<\/tr>\n
Chapter 2<\/a><\/td>\nCESAM Framework Overview<\/a><\/td>\n<\/tr>\n
Chapter 3<\/a><\/td>\nEnvironment Architecture<\/a><\/td>\n<\/tr>\n
Chapter 4<\/a><\/td>\nOperational Architecture<\/a><\/td>\n<\/tr>\n
Chapter 5<\/a><\/td>\nFunctional Architecture<\/a><\/td>\n<\/tr>\n
Chapter 6<\/a><\/td>\nConstructional Architecture<\/a><\/td>\n<\/tr>\n
Chapter 7<\/a><\/td>\nTrade-offs Techniques<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>

Table 11 \u2013 Systems architecting topics covered within the pocket guide<\/span><\/strong><\/p>\n<\/div>

However one shall notice that our pocket guide does of course not cover the full domain of systems architecting. We only focus on the fundamentals that every systems architect \u2013 even junior \u2013 shall know. Thus we put the stress on system modelling, since one just cannot do any systems architecting activity in practice without models. Models do indeed form the language of systems architecting: they can be used to analyze a problem, to describe a system, to elaborate a common vision, to communicate on a solution … The internal coherence of a system model \u2013 that leads to permanent crossed checking between the various diagrams we introduced \u2013 is also a very powerful tool for the systems architect in order to be confident in the robustness of an architecture.<\/p>\n<\/div>

8.2 The other Key Systems Architecting Topics<\/h2>

We did not discussed in this pocket guide, that was just intended to be an introduction to this huge domain1<\/a><\/sup> Systems architecting is a continent to explore, to rephrase an expression due to Marcel Paul Sch\u00fctzenberger, one of the seminal fathers of modern computer science (personal communication). <\/span>, of many other systems architecting topics \u2013 summarized in Table 12 below, that could be addressed by all people who wants to specialize in systems architecting. Among them, we may cite a first group of three important topics \u2013 even if usually not the ones to learn on a first step \u2013 that should also be part of the common knowledge of any senior systems architect, that is to say:<\/p>\n