Architect
"The ideal architect should be both a literary person and a digital home. He should also know history, passionate about philosophical research, proficiency in music, knowing medicine knowledge, and has law to learn, and understanding astronomy and astronomy."
--- Vitruwei (ancient Roman architect), 25 years ago
"The ideal architect should be a person of letters, a mathematician, familiar with historical studies, a diligent student of philosophy, acquainted with music, not ignorant of medicine, learned in the responses of jurisconsults, familiar with astronomy and astronomical calculations." - Vitruvius, Circa 25 BC
The architect must have more art, mature practice, strong insight, and rich experience. In this way, he can quickly understand the issue in the absence of complete information and make a prudent judgment based on experience. More precisely, the architect designer (or member of the archive team) must have the following skills:
The software architect must be well-rounded, posses maturity, vision, and a depth of experience that allows for grasping issues quickly and making educated, critical judgment in the absence of complete information. More specifically, the software architect, or members of the architecture Team, Must Combine these Skills:
Experience: including both experience in the field of problem (by thorough understanding), including experience in software engineering. For a framework, these qualities requirements can be borne by team members, but at least one architect can grasp the global global.
Experience in both the problem domain, through a thorough understanding of the requirements, and the software engineering domain. If there is a team, these qualities can be spread across the team members, but at least one software architect must provide the global vision for the PROJECT.
Leaders can be able to promote the technical progress of each team, and can make a key decision under pressure and then implement it. To improve efficiency, architect designers and project managers must work closely. The architect designer is mainly responsible for solving technical problems, and the project manager is mainly responsible for solving administrative management issues. The architect must have the right to make a decision on technical issues.
Leadership in order to drive the technical effort across the various teams, and to make critical decisions under pressure and make those decisions stick. To be effective, the software architect and the project manager must work closely together, with the software architect leading the technical issues And The Project Manager Leading The Administrative Issues. The Software Architect Must Have The Authority To Make Technical Decisions. Communication: The trust of others can be able to convince, incentive and guidance. The architect cannot lead the leadership, but must win other people in the project. In order to improve efficiency, architects must win project team, project manager, customer, user group, and respect for the management team.
Communication to earn trust, to persuade, to motivate, and to mentor. The software architect can not lead by decree, only by the consent of the rest of the project. In order to be effective, the software architect must earn the respect of the project TEAM, The Project Manager, The Customer, And The User Community, AS Well As The Management Team.
Take the goal, actively take the initiative, and pursue results. The architect designer is the technology motivation to promote the development of the project, not an empty home. In his career, successful architect designers have always made a compromise in the absence of being invasive and withstand pressure. The framework designer can only be successful in the project in the project.
Goal-orientation and Pro-activity with a relentless focus on results. The software architect is the technical driving force behind the project, not a visionary or dreamer. The career of a successful software architect is a long series of sub-optimal decisions made in Under Those WHO CAN FOCUS ON DOING What Needs to Be Done Will Be Successful In this Environment of the project.
The architect designer is responsible for leading and coordinating technical activities and artifacts throughout the project. The frame designer should establish an overall structure of each architecture: the detailed organizational structure of the view, the packet of the element, and the interface between these major packets. Therefore, compared with other characters, the structural designer's appearance is in breadth, not depth.
The software architect role is responsible for the software architecture, which includes the key technical decisions that constrain the overall design and implementation for the project.The software architect has overall responsibility for driving the major technical decisions, expressed as the software architecture. This typically includes Identifying and documenting the architecturally significant assects of the system, incruding requirements, design, importation, and deployment "views" of the system.
The architect is also responsible for providing rationale for these decisions, balancing the concerns of the various stakeholders, driving down technical risks, and ensuring that decisions are effectively communicated, validated, and adhered to.
