Reading notes – corporate downsizing

Get your FREE Diabetes Recipes eBook!

Spent the morning today, went to the bookstore reading a book on enterprise architecture books: “corporate downsizing” (3 stars), this book is suitable for architects and CIO to read, mainly discusses how to streamline the corporate structure, the reason is simple, but it is hard. The book is divided into two parts: the first part of the problem by showing some of the visual complexity of the problems brought about, and then analyzed from a mathematical point of view; the second part, discussed the process of solving complex problems – simple iterative partitions (SIP) , the following major contents of the book to share with you.

Enterprise Architecture
Enterprise IT architecture goal is to maximize the business value of investments, it is a high-level corporate vision, focus and organization between IT architecture and business architecture. IT systems can not meet the business needs if it would be a big waste, but no corresponding IT business process support is hard to improve efficiency. “Enterprise Architecture As Strategy” said the authors of the book a truly effective use of enterprise architecture, business less than 5%, while the enterprise architecture is so important, so the more necessary attention to enterprise architecture.

Most enterprise architects are some of the methodology more or less experience, but in this area can have very wide field of vision of the architect is one of the few, so the author describes in the book about the most popular Zachman, TOGAF, and FEA, he more specifically, that these methodological framework, there is no good guide to what is good architecture and what is bad architecture, but also how to do architecture (Note: TOGAF9 now contains some guidance and content framework for guidance on how to structure .) He believes that good architecture should be a simple structure that is lean, in the second section also presents a simple iterative partitions (SIP) method.

Complexity: C = PD
Book through a number of positive and negative, such as coins, dice and other visual examples, the mathematical model explain the principles of complexity:

C = PD (c-complexity; P-every decision point in the circuit number; D-determined number of points)

Dice has 6 faces of a dice can produce 6 different combinations, 2 of 36 species, 3 is 216 (63) species, 12 are 2,176,782,336 kinds, so the system supports more functions, each function of the large ones more much more complex system, may increase exponentially, so people do not think demand has only increased the amount of 20% of the features, but the system complexity may be increased exponentially. The book also mentioned the concept to increase the barrel, in fact, the concept of partition, the cluttered object is divided into different zones according to the logic to reduce complexity, such as 12 die in two barrels, the complexity is 2X66 = 93000, and 612 = 2176782336 complexity is not an order of magnitude compared.

The complexity of business processes and decision points that determine the number and the number of points on the path leads. Software complexity and the number of variables and those variables related to the number of states. Whether business or software systems, their complexity can be modeled through the dice system. In this model, the number of dice, the number of faces of each dice, these dice is that if there is split into several baskets.

Subset of self-government: ABC

ABC is the basic unit of enterprise architecture, which is an autonomous business capabilities, is a business unit, between these units are autonomous, and in a defined way to interact.

A (Autonomous): autonomy, does not depend on the function of other ABC also work
B (Business): business, there are defined business purposes
C (Capability): ability, the ability to create a visible effect of the external world
ABC model simplification of the entire business model:

Model for simplifying the income, the results from the segmentation process
Model in dealing with the issue only concerned with what ABC did, not how to do
The five rules partition
Simplifying the complexity of the three main methods: partition (split), iterative (Executive sub-district) and simplified (removed sub-district, subtract).

Must be the correct partition: partition a subset of autonomy ABC
Partition to be the right definition: function must be assigned to the equivalence relation based on the ABC collaboration
The appropriate number of sub-partition (3-8)
Elements in every sub-partition must be set on the number and importance of roughly
The interaction between sub-district must be minimized and clearly defined, ABC should have partnerships
Simple iterative partitions (SIP)
We already know that ABC is the basic unit of enterprise architecture, how do we find the ABC it? SIP is a find such a process.

Assessment
Prepared
Segmentation: from the perspective of corporate executives began to split
Simplification: the need for business functions? Whether the combination can be taken? Can outsource non-core functions?
Prioritized: Value Map Analysis

Iteration: TOGAF and other methods can be used
Interoperability
The book comes to some of the methods of interoperability:

Use of the process, method calls
Use a shared database
Use of shared data access layer
The interaction with SOA
Software Castle Model

Software Castle Model
A no part of the package system into Web services, but to an outside entity called the Guard to achieve Web services, Guard A representative of the outside world to interoperate with the system. Guard outside and use SOA to operate.

I drew a diagram ppt: A, B is a subset of the two ABC autonomy

Technology Division:

Rule 1: Autonomy
Rule 2: clear boundaries
Rule 3: Functional partitioning
Rule 4: the definition of dependent
Rule 5: Asynchronous
Rule 6: Data Partitioning
Rule 7: No Cross-Service
Rule 8: Single-point security
Rule 9: Inside Trust
Rule 10: Keep it simple
These rules are somewhat similar to the rules of SOA, It sounds simple, but doing it can be difficult!