CIO work Guide read note--it architecture standard

Solutions to these issues: 1. Visualize business structures such as business rules and business processes, integrate with system architectures, and continuously maintain the state of consolidation. 2. Prevent the system from becoming complex and rigid by properly managing the system architecture.
It architecture standards can be broadly divided into the following two parts. 1. System structure standard. It determines the data processing mode and the model standard, by standardizing the introduction of middleware products, can restrict the way of application development. 2. System element Standard. It restricts the types and versions of the hardware and middleware that make up the system. By setting these standards, it is possible to maintain the consistency of the IT architecture to control and mitigate the complexity of the system.
Overall optimization EA through EA (Enterprise Architecture) is a way to visualize the organization's goals, mission, business operations, and systems that support these elements, and to make it a methodology for enterprise business and overall system view.

1. Business Architecture (BA: Policy and business systems) policy and business-related strategies, and the overall structure of the necessary business processes and information flows.
2. Data Architecture (DA: Data System) The overall structure of the information processing data necessary to implement policy and business.
3. Application Architecture (AA: Application processing System) The overall structure of the business system (application System)
4. Technology Architecture (TA: Technology System) The overall structure of the IT infrastructure represented by hardware and network.

The composition and management of Business Architecture (BA) BA refers to the enterprise business in a modeled way, its composition covers the company's overall business, including enterprise strategy, resources (resources and advantages), as well as business processes.



Standardized da Standardization of Data Architecture (DA) refers to the development of rules for how business's core datasets are presented, stored, and used in the system.
The first step: Define a unique data model for your company's industry. Step two: You need to identify how these core data is stored and configured in the system (data configuration).


Standardization of the standardized AA for Application architecture (AA) is the development of rules for "authoring" and "making methods" for applications within an enterprise's internal system.
Direct purpose: Improve the productivity and maintainability of application development, and extend the life cycle and life of the system. Indirect purpose: Reduce IT costs, improve the efficiency of your business resources by streamlining it, and improve the efficiency of your business through rapid development.




The standardization of Technical Architecture (TA) is defined by the technologies and products used to standardize the data architecture standards and application architecture standards for the upper layers, as well as how to implement them. Technology and products can be divided into three major categories of hardware, software and network, and according to the implementation of the system can be divided into performance, resistance to failure, extensibility, operability and other categories.
TA standardization, the focus is not to be confused by new technologies, new products and other propaganda, but should pay attention to "how to establish and maintain their own company system required standards", and this standard decision can not be based on technology-led to develop. The key to choosing the right technology, product, and implementation is two points: 1. Collect and organize successful cases of technology and products that have achieved stable operation results both inside and outside the company. 2. Investigate trends in IT-related technologies and products.



Ways to achieve overall optimization 1. Introduce a new architecture while radically transforming existing systems. 2. The new architecture is introduced slowly with the maintenance cycle of each system.



The overall optimization of it work activities in IT operations, including IT strategy development, the idea and plan of each system, the design of each system, the realization of each system, etc., must be implemented as the necessary work of overall optimization.
It architect's training it architect: Core people who develop it architecture standards and are responsible for their daily operations. To portray a company-wide IT architecture, it architects need not only the company's business knowledge, but also a broad range of technical knowledge, experience and business execution capabilities.
The training steps and key points of the IT architect are as follows: 1. Mining potential talents 2. Practical training of system development frontline personnel in the 3.IT Department 4. Establishment of governance organizations and mechanisms 5. Mining and nurturing next-generation IT architects


How to avoid the failure of the IT failed "computers not working" in the cause of the failures ranking: 1. Requirements are unclear, more ambiguous 2. Unrealistic functional requirements and delivery periods and budget 3. Project management and design errors, inadequate testing issues
Thus, failure is not produced in the "How to do" stage, but in the "what to Do" stage is produced. It is undoubtedly an important responsibility of the CIO to have common goals for the different stakeholders and to work together to advance the project.
The difficulty of quality and speed of the quality of the requirements should have a sense that the need not to pursue perfection, but focus on the support of the current business is the most important of those functions. In the system development, it is unrealistic to fully grasp all the users ' opinions, and it is unavoidable to assume and speculate about the function and usage that the user expects. Therefore, even if it takes a long time to define the requirements, it is not always possible to accurately determine whether the system is really beneficial to the user. Conversely, if the functional control in the minimum of the early completion of system development, through the user's response and comments on the function to improve, but more easily achieve speed and cost advantages.