Android architect's path-architect's decision-making and android Architecture

Android architect's path-architect's decision-making and android Architecture
Android architect's path-architect's decision-making


Connotation + shape: Most people may not understand this connotation and shape very well. Here I can give you a vivid example: I believe many people have their own cars,
We summarize the attributes and functions of cars. These are meanings. Every object in nature has its own meaning (people have hands and feet, and can also run). Then we
Put these Connotations into a specified shape, similar to a template. For example, if the java language defines a class, attributes and
Function. The definition specification of this class is a shape. Then, we define the automobile class according to the class specification, so this is the connotation.
Embedded in the shape. Similarly, a person class can be defined based on the Human Connotation and the class specification. In this case, you can understand it.
Connotation + EIT modeling (base class + subclass)
Architect decision-making:
The main source of connotation: Demand knowledge, the most basic connotation comes from and demand knowledge.
There are two types of requirement knowledge: 1. Requirement knowledge --> the connotation of becoming a base class
2. Demand knowledge --> the connotation of becoming a subclass

Q: What are the meanings in the EIT model? (I do not understand the EIT modeling here. First, I would like to know the EIT modeling knowledge under Baidu)
Let's give an example here. If you go to the coffee house and coffee, you will know the requirement knowledge (drinking coffee) before you come as the basis class connotation.
Requirement knowledge (for example, coffee requires no sugar or other conditions) as the meaning of sub-classes. The problem arises again. How can we produce coffee with sugar?
Defines an interface. The subclass implements the interface method (used to make coffee with sugar). Then, when the base class calls the interface function (requires coffee with sugar ),
The sugar coffee production method obtained from the sugar coffee returned to the base class, completed the perfect integration of connotation + EIT styling.

App development responsibilities: Convert requests into code.
From division of labor to outsourcing mode:
Strong dragon master E and I, outsourcing T to the ground snake, control E and I, outsourcing will not be out of control.
Google and apple are strong dragons, and app development is the geographic snake. The EIT-based outsourcing model supports strong dragons and geographic snakes to achieve a win-win business model and strategy.