View method and dimension method, thinking about Software Architecture

Is this method reasonable to describe the architecture through a set of views? This view is equivalent to the horizontal plane of a thing. It seems unreasonable to list the architecture by cross-cutting in different directions, because the horizontal plane is more and more as the complexity of the system increases. Similar class diagram + activity diagram + sequence diagram + state diagram + component diagram + deployment diagram, or other such view classification methods, such as SUP4 + 1 view, are limited to several existing horizontal planes, is it enough?

 

The crosstab chart is good, but as long as all the crosstab charts can be listed, the design is comprehensive enough. Otherwise, many challenges and changes will be made continuously in the development stage, all the challenges and changes in the coding phase, if not due to changes in requirements, are caused by poor design considerations. If you follow these common cross-section, it is still inevitable that you make some adjustments in the encoding phase, which means that your design is incomplete and that the horizontal section is not listed.

 

Software, such as objects, has different dimensions. Objects have three dimensions, more software dimensions, and the most basic dimensions include availability, reliability, robustness, reusability, and scalability. Considering the software architecture based on these dimensions, for example, looking at an object from the outside, we can see it as a peak on the ridge side, and the distance and distance vary) the view method is focused on the internal structure and implementation of the architecture, while the dimension rule is to examine the software as a whole. If the former is a tactical angle, then the dimension method angle is a strategic angle.

 

The combination of the two perspectives can effectively capture all aspects of the software architecture. Architecture is not only a matter of thinking, but also a process of thinking. Although there are applicable models, the adjustment process still needs to be based on actual needs. The combination of dimensions and crosstab views helps us understand the software architecture and the methods and nature of the software architecture.