Android Architect's path-architect's decision
Connotation + styling: Probably most people are not very understanding of this connotation and modelling, here I can give you a vivid example: believe that many people have their own cars,
We summarize the properties and functions of the car, these are the connotation, every object in nature has its own connotation (people have hands and feet, can also run), and then we
Put these connotations into a specified shape, like a template, such as the Java language if you define a class, you must specify the property and the scope (inside the curly braces)
function, the definition of this class is a shape, and then we define the car as a class in terms of the specification of a car class, then this is the connotation
embedded in the styling. Similarly, a person class can be defined according to the human connotation and the style of the class specification. It should be understandable that everyone should understand it.
Connotation +eit Modelling (base class + sub-Class)
Architect's decision:
The main source of connotation: demand knowledge, the most basic connotation comes from the knowledge of demand.
Requirements knowledge is divided into two types: 1. Knowledge of requirements--------the connotation of base class
2. Knowledge of requirements----become the connotation of sub-category
Question: What content will be put into the EIT model? (Here do not understand the EIT model, first Baidu, EIT modeling knowledge)
We are still here to illustrate, if you go to the coffee house and coffee, before you come to know the needs of knowledge (drink coffee) as the basis of the connotation of the base class, you come after the
Requirements knowledge (such as the need for coffee without sugar and other conditions) as a subclass of the connotation. So the question comes again, how to produce a coffee with sugar, this time you need
Defines an interface in which subclasses implement an interface method (for making sweetened coffee), and then when the base class invokes the function of the interface (sugar coffee is required), the subclass implements
The production of sugar-sweetened coffee method to obtain the added sugar coffee back to the base class, completed the connotation of the perfect integration of +eit modeling.
App development responsibilities: Translating requirements into code.
From Division to outsourcing model:
Strong Dragon Master E and I, the T outsourced to local bully, control E and I, outsourcing will not lose control.
Google and Apple for the strong Dragon, app development this for local bully, eit-based outsourcing model to support the strong dragon and local bully to achieve a winning business model and strategy.
Android Architect's path-architect's decision
