2015.4.7
From know: http://www.zhihu.com/question/21878150
First of all, you need to understand your project needs, that is, what your project needs to do, what functions, this needs to look at the project requirements documentation. However, some companies, this link may not have documentation, it can only do the second step, if there is no functional documentation requirements, prototype, high-fidelity always have it, this must see, at least in the heart to have a spectrum, the project in the end will be made what kind.
Then, you need to understand the functional modules of this project are divided. Project has several functional modules, the front of the developer is how to divide, looking for the front of the coder asked, this time or not to look at the code, not too urgent, it is best to get a list of their own, and then see what they have in each module contains what functions, this need to ask the front of the coder.
Next, the thing to do is how the project is organized, and at this point you can start to focus on the code. You need to understand how the hierarchy in the project is divided, how each level interacts with each other, and generally, we need to focus on the following levels:
1, network layer, that is, how the network layer of the project is organized, how to initiate network access. If you need to do more functions, it is necessary to look at their server interface documentation.
2, database layer, that is, the project database this piece, there are several tables, how to perform additions and deletions and other operations.
3. What are the entity models in the project and how the data structure is organized?
4, the project's view layer is how to combine with the network layer, the database layer, that is, how to call the network and the database in activity or fragement, how to handle the data. Simply put, that is how the data is handled, how to come, to go there.
The next step, is to start to clear their coder, which classes correspond to which modules of which functions, generally in the package or by naming differentiated, at this time, it is necessary to understand their coding specifications and naming rules, it should be through the name of the file and resources, many times, very good to clarify the code. At this point, it's best to focus on what basic base classes they have, what functions you can use directly behind them that have been written, or can be inherited directly from the base class.
After the above steps, I think, this project is almost able to get a clue, then, you can try to write or modify some functions, you can imitate others, and then try to write their own.
How to quickly join the development of an Android project