Responsibilities architect
architects need to be able to identify and confirm the definition of requirements, the system can break down to form the overall architecture, technology selection can correctly can develop technical specifications and promote the implementation of effective landing.
TOGAF, by definition, the big fat cloud Source erected duties repair bbs.yasewl.com architect is aware of and concerned about the fact at stake but did not become some critical details and upload interface, the architect of the role are: understanding and parsing requirements create a useful model, validation, refine and expand the model, management structure.
View from the project see:
Docking management: reporting technical solutions, progress; technical communication;
docking client PM, Project PM: assist in project planning, personnel management. Is responsible for all technical delivery guidance material;
docking business units and staff needs: Understanding and digging pain points to help sort out high-level business needs and guide demand process;
butt Development: product support, technical guidance, architecture guidance;
interconnection testing: with test plans and processes making. With a performance test or non-functional test;
docking operation and maintenance: product support, operation and maintenance support;
docking configuration & Environment: Product Support;
.......
Architectural principles
designed architecture design principle is the guiding ideology that guides us on how to organize data and functions into classes, classes on how to link together into components and programs. Reverse, the main work of architecture is the software disassembled into components, design principles to guide us on how to disassemble, disassemble the size, inter-dependent components of direction, decoupling components of methods.
Design Principles There are many, we were led architecture design principles are OCP (Open Closed Principle), at the class and level of the code are: SRP (Single Responsibility Principle), LSP (Richter substitution principle), ISP (Interface Segregation Principle) , the DIP (dependency inversion principle); at the level of the components are: REP (reuse, release the doctrine of equivalents),-CCP (common principle of closure), of CRP (co multiplexing principle), the processing component dependencies three principles: no dependence ring principle, rely on the principle of a stable, steady abstract principles.
Design principles
1, OCP (Open Closed Principle): well-designed software should be easy to expand, and to resist changes. This is the guiding principle of our architecture design, the other principles are the principles of this service.
2, SRP (Single Responsibility Principle): Any software modules, should have one and only one reason to be modified, "Modified cause" refers to a system user or owner, translate what is, any module for only one user responsible for the value of the principles that guide us how to split components.
For example, CTO and COO have statistical staff working hours, they asked the current statistical methods may be the same, we reuse the code set, then the COO said the weekend working hours statistics to be multiplied by two, modify the requirements in accordance with this Code, CTO may have to come squalling. Of course, this is a very simple example, the actual project there are a lot of code to serve more than the value of the body, which costs a great deal of Quest and modify risk. In addition, when a code has more than one owner, it will generate the code problems merge conflicts.