Chapter 1 – Why Architecting Systems?

1.1 Product and Project Systems
Before going further, we need first to introduce a distinction that will be fundamental to understand better both what is systems architecting and how to read many classical engineering issues. It indeed appears that all engineered systems are always involving...
poursuivre la lecture
1.2 The Complexity Threshold
At this stage, it is now time to explain more precisely what “systems complexity” is and how it is connected with systems architecting. An element of answer is provided by the Constructive Systems Engineering Cost Model (COSYSMO; see for instance...
poursuivre la lecture
1.3 Addressing Systems Architecting becomes Key
Due to that complexity threshold as presented in section 1.2, which is – in our understanding – the root cause of most engineering issues observed in complex systems development (we here refer to Appendix B for more details), addressing systems...
poursuivre la lecture
1.4 The Value of Systems Architecting
To complete our discussion on systems architecting, let us now focus on the value brought by this discipline, which was in particular quite well analyzed by Honour in [41]. The key point to understand is that the systems engineering approach...
poursuivre la lecture
1.5 The key Role of Systems Architects
Systems architecting would of course not exist without the right key people, i.e. systems architects, to support the architectural process! The systems architect shall indeed fundamentally be the core responsible of the systems integration issues. He/she shall thus ensure that...
poursuivre la lecture
1.6 How to Analyze a Systems Architect Profile ?
To conclude this chapter, we will briefly present the key characteristics of an (ideal) systems architect profile. Such profiles are indeed quite rare and always difficult to find as a matter of fact. Having some clues on that still poorly...
poursuivre la lecture