Question 1: What does a network architect do? A network architect is called Internet architect in English.

My usual job is to be responsible for network technology architecture selection, and leading functional module design, data structure design, and external interface design; responsible for technical coordination with relevant technical cooperation teams; conducting pre-research on various forward-looking technologies And formulate suggestions within the enterprise on whether and how to introduce them; Responsible for operating data analysis, user feedback collection and function optimization of existing products; Responsible for tracking competitor dynamics, new product research and analysis; Responsible for coordinating the creativity, planning, and revision of website products , website system function planning and other work; responsible for the analysis, planning and refinement of website product columns and requirements; responsible for daily operation management after the project is launched, providing column planning and implementation status reports at different stages; responsible for optimizing the user experience of the project and improving affinity and ease of use.

My university major is computer science. Annual salary is 100,000-150,000. It is suitable for people with excellent organizational and expression skills, good communication skills, the ability to withstand work pressure, good communication, coordination and teamwork spirit, strong logical analysis skills, and the ability to quickly abstract business and analyze problems.

Question 2: What is a website architect? 1. Responsible for the overall technical design and development of the dating website;

2. Assist the project manager to ensure product quality and development;

3. Computer information management and related majors, bachelor degree or above, two years of relevant work experience;

4. Dedicated and serious, interested in developing and starting a career in the Internet industry;

5. Ability to professionally plan Internet website projects, with strong expression and copywriting skills.

Question 3: What are the responsibilities of an architect? A software architect is a technical director

First of all, a software architect is a technical director, which means that in addition to having technical skills , but also have good leadership skills. The architect's leadership skills play a very important role in the team and project quality control.

In the team, the architect is the technical manager of the project. He needs to have a rich knowledge background in order to make technical decisions. Compared with architects, project managers are responsible for managing the project's resources, time progress and costs. To use a filmmaking analogy, the project manager is the producer (who makes sure the work is done), and the architect is the director (who makes sure the work is done correctly). Because of their position in the project, architects and project managers are public figures, and within a team they are the hub of contact for everyone involved in the entire project. Architects should seek investment in building software architecture and be clear about the value that building software architecture can bring to the organization.

The architect must also organize the team around the architecture and actively invest in planning activities, because the architecture must be transformed into a sequence for completing tasks, so that what is needed at what location can be determined in a timely manner technology. One thing to note is that since the success of the architect is closely related to the overall level of the team, the architect should participate in the interview for the recruitment of new team members.

Depending on the capabilities of the architect, he can participate in the work of other teams at the same time. Architects need to make leadership decisions based on specific instances and demonstrate sufficient confidence in the decision-making process. A successful architect is people-oriented and schedules his or her team's work like a coach. This is good for the members of the group, who can get help in a timely manner. This is a huge asset to the entire team.

The architect must also focus on the delivery of practical work. He is the driving force in technology. Architects need to make decisions (often under pressure) and ensure that these decisions are communicated among team members and that they are implemented.

The architect may have a team to complete the work.

The following is an introduction to the difference between a person and a role. One person can play many roles (for example, Mary is a developer and a tester), and one role can be played by many people (for example, Mary and John are both testers). The role of architect requires a very broad range of skills, which is why the role of architect is often performed by many people at the same time. This allows technical knowledge to spread among the group, with each person bringing his or her experience to the work. Especially when a certain technology is understood by both the business department and the technical team, the technology will spread to the greatest extent. The results produced by the group need to be balanced. The term architect will be used throughout this article to refer to an individual or to an entire group of people.

[A group] is a group of people with various skills who have the same goals to accomplish and are responsible for each other. 2

If a group plays the role of architect, then there needs to be one person as the leader of these architects, who must have an overall outlook and need to mediate issues between the architect groups. Without this coordination, there is a danger that among the architect team members they may not create a cohesive architecture or that decisions may not be successfully completed.

Now a new concept has been proposed in the architect group: in order to achieve the same goals and objectives among members, the team established and published a charter for the architect group. 3

A good architect knows where his strengths and weaknesses are. Whether the architect role is performed by one person or a small group, they are supported by trusted advisors. They can make up for their own technical deficiencies by working collaboratively with other architects. The best architectures are usually built by a team of architects, not one person. The reason is simple, the power of a group is always much richer than the knowledge of one person.

A flaw in the concept of architect teams is that they are sometimes considered by other groups on the team to be working in an ivory tower, because their products are often smart but of no use value. This misunderstanding can be minimized from the beginning: 1) ensure that all stakeholders are actively negotiated, 2) continuously communicate the architecture and its value, and 3) have a sense of organizational strategy during execution. .....gt;gt;

Question 4: Who can tell me exactly what an architect is? Architects are generally divided into technical architects and business architects, and technical architects are divided into software architects and system architects (network architects)

Software architects generally only use what language to develop and what to use. Framework, what database to use, etc.

The system architect should use a mainframe to run the program or use multiple minicomputers or workstations to deploy the program, how much bandwidth to use, whether to use China Telecom's network or China Netcom's network, etc.

Business architects can be understood as product architecture, such as what functions need to be developed, how the functional process should be described, how functions should be related to each other, etc.

Of course, except for very large companies, ordinary companies rarely divide them so clearly. Generally, one architect dominates the world. And such architects often tend to be in the direction of software architects.

Question 5: What does a software architect mainly do? Since you are already working, I think you should know a little bit about it. Most companies also have architects.

The architect's main job is to be a system analyst, formulate the architecture, and use the framework during development, similar to the chief designer in the project.

Technical personnel who confirm and evaluate system requirements, provide development specifications, build the core architecture of system implementation, clarify technical details, and clear up major difficulties.

It requires you to transform from a programmer to an architect. You can read some architects' books. In fact, the best thing to do comes from your daily accumulation. Very thorough understanding of technology. In addition, I am very familiar with the framework. Of course, these require you to have rich project experience

Question 6: What is the main job of an architect and what knowledge is required? An architect must first have rich development experience and be a technical supervisor. Because he must know what is achievable, what are the ways to achieve it, what is the corresponding difficulty, and a series of indicators such as the adaptability of the implemented system to changes in demand. In addition, you need to have a deep understanding of design concepts such as process-oriented, object-oriented, and service-oriented, so that you can quickly detect problems in implementation and propose corresponding improvement (refactoring) plans (also commonly referred to as anti-patterns). These require long-term development practice to truly understand. It is difficult to understand it from books alone. Even if you understand it at the time, you may not be able to integrate it into practice.

In terms of technical capabilities, the most important knowledge that software architects need to master is the knowledge of component communication mechanisms, including intra-process communication (object access, function calls, data exchange, thread synchronization, etc.) and Out-of-process (including cross-computer) communication (such as RMI, D, Web Service). Today, when WEB applications are very popular, developers tend to pay more attention to communication between servers and pay less attention to communication within the process. Out-of-process cross-machine communication is the cornerstone of building distributed applications, it is a bird's-eye view in architectural design; while in-process communication is the skeleton of module implementation, it is the cornerstone of the cornerstone. If you are specifically designing an enterprise-level architecture based on .Net, the first thing you need is language-level understanding, including .NET's CLR, inheritance features, delegation and event processing, etc. Then there is the understanding of common solutions, including ASP.NET Web Service, .NET Remoting, enterprise service components, etc. In short, rich practical development experience helps avoid architects from talking on paper and brings real feasibility to code writers.

Secondly, it is also important to have sufficient industry business knowledge and business acumen. Sufficient grasp of industry business knowledge can give architects more ability to embrace changes, and can leave some room for expansion during system design to adapt to possible changes in demand. Experienced designers may have encountered this kind of thing. Wishful retention of interfaces has a very low hit rate when requirements change. In other words, the system interfaces left for scalability at the beginning of the system design failed to play a real role in the torrent of demand changes, because the changes in demand did not proceed in the expected direction, and in the end they had to accept the changes. Business redesign systems. This is because the understanding of business knowledge and judgment of the market or business have not reached a practical level that can be extended to the architecture.

Thirdly, the architectural designer’s attention to people must be raised to the scope of consideration at the beginning of architectural design, including communication and judgment of personnel quality. The software process is a process of team collaboration and system building, and communication skills are the glue that holds multiple development lines together throughout the process. Everyone should have encountered something like "So that's it, I didn't know" or a developer suddenly shouted "Why is the data here no longer available?" or something like that. The purpose of communication is to avoid the confusion of multiple development lines as much as possible, so that the system construction process can be carried out in an orderly and efficient manner. In addition, attention to people is also reflected in the judgment of the quality of team members, such as which developers are more familiar with which technologies, or which developers are prone to delaying progress, etc. Only by rationally using human resources and letting the right people do the right things can the entire software process be more efficient.

Architects should always pay attention to the development of new software design and development, and constantly explore new and more effective methods, development languages, design patterns and development platforms are constantly being upgraded very quickly, and software architects need to absorb These new technologies and new knowledge are used in software system development work.

However, the exploration of new technologies should be carried out within a rational range and cannot blindly follow the trend. Solution providers always hope that you can use the latest technology they provide, and when they promote their own solutions, they often focus on their own products, which can easily give people the wrong impression. For example, databases often make people think that they can do everything, and as long as they have it, nothing else matters. But in fact this is not the case. For small applications, a lot of business logic can be put into the database in the form of scripts, but it is rare to see large applications adopting this approach. New things need to be judged from a comparative perspective, including horizontal comparison and vertical comparison, and finally some indicators such as performance, portability and upgradeability are obtained. In addition, new developers often care about new technology trends but ignore the history of technology,...gt;gt;

Question 7: What level does an architect generally come to interview for architecture? An engineer is an emerging profession in the industry. The job responsibility is to convert customer needs into standardized development plans and texts during a project development process, formulate the overall structure of the project, and guide the entire development team to complete the plan. The architect's main task is not to write specific programs, but to engage in higher-level development architecture work. He must have a good understanding of development technology and good organizational management skills. It can be said that the quality of an architect's work determines the success or failure of the entire development project. Generally speaking, system architects should have the following capabilities: 1: Have more than 8 years of industry work experience; 2: Have more than 4 years of C/S or B/S architecture product development, architecture and design experience; 3: Have more than 3 years of experience in code writing; 4: Have extensive experience in overall planning, scheme design and technical team management of large and medium-sized development projects; 5: Have a deep understanding of relevant technical standards and a good understanding of engineering standards and specifications. Grasp; 6: Have a deep understanding and proficient application of .Net/JAVA technology and the entire solution, and be proficient in WebService/J2EE architecture and design patterns, and design product frameworks on this basis; 7: Have object-oriented analysis and design , development capabilities (OOA, OOD, OOP), proficient in UML and ROSE, proficient in using tools such as Rational Rose and PowerDesigner for design and development; 8: Proficient in the development of large databases such as Oracle, Sql Server, etc.; 9: Proficient in computer systems, networks and Have a comprehensive understanding of security, application system architecture, etc., be familiar with project management theory, and have a practical foundation; 10: Have a solid foundation in application system development and project management, and have successful cases of development and implementation of large and medium-sized application systems; 11: Good team awareness and collaboration spirit, and strong internal and external communication skills.

Question 8: What is the position of a 4g network senior architect? Network system architecture takes industry needs as the core, proposes a teaching model based on practical training, and uses real enterprises under the guidance of the practical training project manager Project cases (power industry network construction projects, telecommunications network construction projects, campus network construction projects, financial network construction projects, etc.). Integrate into the actual project as a trainee employee to enhance the employment competitiveness of the trainees.

Question 9: My personal opinion on what a front-end architect does:

The architecture was the overall planning and architecture of the website’s front page, as well as the MVC design pattern and the performance optimization of JS/Css code. , improve code reusability and reduce code redundancy. It breaks away from the scope of ordinary front-end coders and pays more attention to the optimization and rationality of the code to improve the response speed of the website. It is said that authorities say that the opening speed of a website can be increased by 97% after the front-end code is optimized.

Now you know his importance! Wow, take a closer look at the post from 2008. It seems that you are very concerned about cutting-edge technology. If you get it, get 2 points and leave

Question 10: What is an e-commerce architect? E-commerce architects are very important in the entire e-commerce industry. They play an important role in the business development process, and their responsibilities or concerns continue to change as the development process progresses. During the requirements phase, architects are mainly responsible for understanding and managing non-functional system requirements, such as software maintainability. stability, performance, reusability, reliability, effectiveness, testability, etc. In addition, architects must often review the requirements put forward by customers and market personnel to confirm the designs proposed by the development team; as the requirements become more and more As it becomes clearer, the architect's focus begins to shift to organizing development team members and the definition of the development process; in the software design phase, the architect is responsible for the design of the entire software architecture, key components, interfaces and development policies; in the coding phase, Architects become consultants to detailed designers and code writers, and regularly hold technical seminars, technical training courses, etc.; as the software begins to be tested, integrated, and delivered, integration and testing support will become the responsibility of the software architect. Work focus: When software maintenance begins, software architects begin to make decisions about whether new functional modules should be added to the next version of the product.

Necessary conditions

The formation of architects is trained in practice, requiring considerable technical level and years of practical experience, rather than attending several training courses and reading It only takes a few books to succeed. Obviously, in the software development process, the importance of a good software architect should not be underestimated. So how to become a good software architect?

Leadership and teamwork skills, the software architect must be a recognized technical leader who can make timely and effective decisions on technology selection at critical times.

- Have strong communication skills. At that time, this seemed to be the best thing to have in any role. Software architects need to deal with all kinds of people frequently, including customers, marketers, developers, testers, etc. Project managers, network administrators, database engineers, etc., and also serve as communicators between many roles. In terms of technical capabilities, the most important and most needed knowledge for software architects is knowledge of component communication mechanisms, such as remote procedure calls, JAVARMI, CORBA, /D, various standard communication protocols, network services, and object-oriented databases , relational databases, etc. In addition, architects should always pay attention to the development of new software design and development, and constantly explore new and more effective methods. Development languages, design patterns, and development platforms are constantly being upgraded rapidly. Software architects need to absorb these new technologies and new knowledge and use them in software system development work. Of course, industry business knowledge is also very important to software architects, which helps to design

- an architecture that meets customer needs. Excellent software architects often need to gain knowledge of industry business as soon as possible. To understand, one must learn quickly and make keen observations.

The above description is boring, but as an architect, it is endless fun in the development process of the entire software system, because this role is very challenging, sometimes it requires being versatile, and sometimes it requires Decisive, firm and merciless. In China, few software companies have independent architects. Usually a software expert wears multiple hats, including a project manager, a software architect, a software developer, and sometimes a guest tester, which is very important for software development. The cycle and product quality are unfavorable. Sometimes a person's point of view is very one-sided, and heavy work and heavy pressure will affect a person's emotions. Emotions will affect decision-making, and decision-making will affect the results, so it is worth thinking twice before acting.

Architects cannot be made through theoretical study, but it will definitely not work without learning relevant knowledge. The self-cultivation process of a general structural architect is roughly as follows.

1. Architect embryo (programmer)

The knowledge learned is language basics, design basics, communication basics, etc., which should be completed in university, including java, c, c, UML, RUP, XML, socket communication (communication protocol) - the raw materials necessary for learning to build application systems.

2. Architect Budding (Senior Programmer)

Learn about distributed systems, construction, etc. You can get in touch with them in college or in the first year of work, including distributed system principles, ejb, corba, /, webservice (graduate students can study network computers, high-performance concurrent processing, etc.)

3. Architect seedlings (designers)

Should master the above basics Based on actual project experience, thoroughly understand application design patterns, including design patterns (c version, java version), ejb...gt;gt;