The essense of the software atchitecture

最新推荐文章于 2024-04-27 10:50:03 发布

hbffff

最新推荐文章于 2024-04-27 10:50:03 发布

阅读量856

点赞数

分类专栏： Thinking in Architecture 文章标签： interface semantic module less system table

本文链接：https://blog.csdn.net/hbffff/article/details/4382130

版权

Thinking in Architecture 专栏收录该内容

1 篇文章 0 订阅

订阅专栏

The architect seems a hot job in software industry. About the role or responsibility,there are a lot of definition. For me, I’d like to make things as simple as possible. So my definition is not complicated. I think the main responsibility of an architect is to sketch the high level perspective of the whole system. In other words, the architect has the ability to divide the whole system into available modules, and make sure the individual module takes a clear, and, in best case, orthometric responsibility. Further, after the division, there is a simple interaction among modules,then modules can be combined as needed.In a word, an architect master the technology of dividing and combining. To be strict, it is not only a technology, but an art design. The architect is originally from the architecture industry, where an architect is called an artist often. What is the difference between art and engineering? Engineering means repeatable, reusable and the flow is strict. Art, however, is creative ,filled with personality and the flow is optionally.

The software design is very similar to architecture design. It has to follow some engineering principles, such as open& close, inverse dependency. Meanwhile, it is also branded by the style of an architect. Each architect has his own taste, more or less, different with others.

My style is simple+extensible. I always keep the interface simple and properly extensible.

The responsibility of an module is supposed to be clean and simple, so on interface, it is supposed to present the same style. The simple also means the semantic of the interface is firm and, consequently, the interface is testable. That is the key of the interface design of an module. Make it testable!!! No matter how you change the implementation, keep the interface and the make it testable as it did.

Extensible is hard to master. We have to balance between poor-design and over-design. The

extensible contains the experience of an atchitect. In most cases, it is experience dependent. My suggestion is keep the proper extensible, and avoid the over-extensible. Let’s welcome the changes when they come. Do not expect the first design can accommodate all the new changes. Which is impossible for ever.

Ok, keep in mind ,keep it simple and properly extensible.

hbffff

关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
The essense of the software atchitecture

Normal 0 7.8 pt 0 2 false false false MicrosoftInternetExplorer4 <!-- /* Font
复制链接

扫一扫