System Architect Training Summary

Posted on 2006-06-09 01:52 Xu Jianxiang

--2006 years, Zhangjiang's real estate is more than 6,000, 2010 Zhangjiang less than 2w almost no, originally only one such as home, now, such as home side is Medicine Valley ...

First, training background

From the company's long-term development, through the company's staff to carry out targeted training to enable them to continuously acquire new knowledge and related skills, improve the overall research and development capabilities, from June 3, 2006 to June 6, participated in the CAS Institute of Computing Vocational Training Center in Shanghai, the senior System architect training.

Ii. purpose and content of training

Through training, master the current common system structure design scheme, and be able to apply flexibly, master the various goals and coping strategies that affect the design of software architecture; Master a real software development process, and can specifically apply RUP's normative process to the actual system implementation.

The training is divided into four days, the first day to explain the software architecture, the next day to explain the design patterns and trade secrets, the third day to explain the RUP, the fourth day to explain the technical aspects of architecture design.

The main contents of the four-day training are:

1, the theory and practice of software architecture design;

2, design mode and system creation;

3, trade secrets;

4, RUP's component realization and management;

5. Analysis of technical problems in architecture design.

Third, the training schedule

Time	Training Content
June 3 Morning Afternoon	Basic concepts of software architecture design Design issues in the initial phase
Requirements analysis and conceptual modeling Architecture Analysis and Design
June 4 Morning Afternoon	Class design and Design patterns Further discussion of architecture design
Software Architecture and architects Trade secrets
June 5 Morning Afternoon	RUP Course Brief A substantive analysis of RUP Overview of RUP
RUP Best practices and case teaching Top-level design and RUP for ultra-large projects
June 6 Morning Afternoon	Overview design and Architecture System selection Physical and logical architecture step Java EE system
Spring and Hibernate

Iv. Experience and plan

In the four-day training course, a collection of instructor cases, in-depth study of the software architecture design, unified process and design patterns three aspects of integrated application technology.

The content of this training, time is tight, I benefited greatly. I feel very deep mainly have the following points:

1, the software architecture design is the software, hardware, network, operation, policy and other software design requirements and elements of decision-making (in the unified process, architecture research and architecture design collectively referred to as the framework analysis). Software architecture design is a system engineering, it needs to have a wide range of knowledge, from requirements analysis, architecture design to class design and even the implementation of code needs to have a thorough understanding. The key to architecture is to embrace change and design .

2, the Software Architect is responsible for the technology, is the provider of the solution, in cooperation with the project manager, make plans, determine the members, organize the team, ensure that the project is completed on schedule. The most important quality of an architect is to grasp the focus .

3, the Rational Unified process (RUP, rational unified processes), is the use case-driven, architecture-centric, iterative, incremental software development process.

RUP's software development is divided into four phases:

A, the initial stage: Identify and circumvent the major risks of the project, establish a use-case model framework, and develop milestone date phase plans;

B, Refinement stage: The analysis of problem areas, the establishment of a sound system structure, the preparation of project plans, the elimination of the highest risk elements of the project, the completion of some of the highest priority use case development;

C, the construction phase: divided into multiple iterations , gradually complete different priority use case development, core case-> High risk case-> sub-core case-> other cases;

D, delivery stage: Perform various functions, performance testing, product, deployment, complete the development of the whole system.

after each iteration, you should deliver an intermediate version that you can run .

4, the software design in the existence of repeated occurrences, can be solved in a similar way, can be identified by a pattern, and can be based on this model to create a specific solution. The design pattern is to take full advantage of the language and to take a higher view of our design, but not to design for the pattern .

5. Reasonable and normative documentation is important and necessary , such as the glossary, the use case model for functional requirements and the list of system features, technical memos (recording design motivations and principles), problem cards, etc.

Finally, Plan x month x day 14:00 ~ 18:00 in the large conference room to the R & D department in the theme of "Object-oriented software development" in-house training, the directory is as follows:
Part I: Overview of software processes
1. Software Process
Part II: Object-oriented modeling (analysis and design)
2. Conceptual modeling
3. Use case modeling
4. Interactive modeling
5. Deployment and implementation
6. Case
Part III: Design Patterns
7. What is the mode
8. Design principles
9. Gof design mode
10. Case

Xu Jianxiang
2006/06/09