How to Develop to. Net architects step by step
Microsoft's DOTNET development is definitely a technology that is easy to get started with and difficult to improve. It is basically impossible to become a DOTNET architect without three or more years of coding accumulation. Especially in large software projects, architects are the core members of the Project. Therefore, the RUP methodology also recognizes architecture as the core, reflecting the important role of the 4 + 1 view in the entire software development process. Architects must be both proficient in technology and be familiar with the business. In addition, they must have relevant accumulation and knowledge reserves for related technologies at various stages of the software life cycle, however, it is difficult to reach this level without years of training. To become a qualified architect, you must first be a qualified or excellent programmer. coding is always the most important skill for development, in the coding process, as long as you are good at thinking and analyzing problems, you can learn a lot of related knowledge and technology. Therefore, in the development process, we must pay attention to the learning of new knowledge and new technologies, and the learning of previous experiences and achievements. Some problems that should be considered during the coding process include: 1. in the coding process, do you perform unit tests or use related tools for unit tests? If not, why can't you perform unit tests?
2. Self-encoding leakage rate and Cause Analysis of code leakage bugs
3. Whether you are conscious Code During the reconstruction process, is the idea of the relevant design model introduced?
4. Do you want to learn some advanced features of C #, such as reflection call and asynchronous processing.
5. Have you studied and compared remoting and WebService distributed technologies?
6. Do you often study open-source projects and open-source projects? Source code , Such as duwamish, petshop, nunit, Enterprise Library, and Nant.
7. Have you studied the object persistence mechanism, O/R Mapping, and other related technologies?
8. Do you pay attention to the reuse and extraction of public components and public classes during the coding process?
9. Do you often develop gadgets to improve work efficiency and consolidate learning knowledge during your daily work and study?
Design and coding are close and inseparable. waterfall models that strictly separate design and coding are generally only used in large-scale projects. The separation of coding and design in a timely manner does not mean that coding personnel do not need to think about it. coding is always a creative task, otherwise, the coding process can be completely automated without human intervention. So here we talk about design mainly refers to the systematic thinking ability of designers. Designers should analyze and think about problems at a higher level than developers. One of the most important skills of the designer is the reality-> abstract conversion. This requires the methodology, technicians need to accumulate knowledge about object analysis and design or structural analysis, and have strong database analysis and design capabilities. The key to whether a design can become a good architect lies in the depth and breadth of accumulation. Therefore, the following issues should be considered during the design process:
1. Are you competent in analyzing and designing large and medium-sized application systems? Is it just an independent function analysis and design?
2. Whether to consciously consider Component Reuse and related interface design principles during the design process. Whether the analysis mode and design mode can be applied to your own design process.
3. Have you systematically studied and Thought on XP, RUP, object-oriented, and structured methodologies.
4. Do you really understand the different guiding effects of system functional requirements and non-functional requirements on system design.
5. Will I reflect on my design functions based on future changes? Why cannot I adapt to changes?
6. Do you often develop prototypes to verify your design ideas during the design process?
7. Do you want to focus on the analysis of professional business processes while focusing on business modeling? If we pay attention to this knowledge and skills frequently during design and development, it will be a matter of time to become a qualified architect. At ordinary times, the Knowledge and Skills Used for job development are insignificant. If you do not consciously learn this knowledge, it is difficult to further improve the skills. I have participated in two Microsoft architect trainings and have the opportunity to attend the P & P workshop session at the Microsoft architecture summit in Beijing, the training instructor is the author of the smartclient architecture and design guide at the Microsoft headquarters, Edward. jezieski makes me feel the profound technical background of foreigners. Program Development persistence. Knowledge and skills that are frequently used in the DOTNET Architecture
1. RUP methodology, 4 + 1 view. Case-driven business modeling-> analysis model-> Design Model
2. Use Case mode-> Analysis Mode-> Design Mode
3. Common distributed Technologies
4. Focus on non-functional requirements such as security, exceptions, logs, and performance
5. some reference books related to the overall business of the application system (which can be downloaded from both the Microsoft website and the plug-in)
Reference books provided by Microsoft website
Enterprise Solution patterns using Microsoft. NET
. NET data accessarchitecture Guide
Application Architecture for. Net: designing applications and services
Caching architecture guide for. NET Framework applications
Designing application-managed authorization
Smart Client architecture and design guide
Other Architecture Reference Books
Software Architecture in practice
Pattern-Oriented Software Architecture
The art of software architecture
Beyond Software Architecture
Books on Models
Analysis Patterns
Design Patterns-elements of reusable object-oriented software
Applying UML and patterns
Design Patterns explained
