First, the code specification and coding principles
Coding rules are the rules of procedure codes to be followed, avoiding the use of difficult to understand numbers, instead of a meaningful identity, do not use the skills of highly difficult to understand the statement. Source code relationship more closely adjacent as possible.
Code style specification: The main provisions of the text, seemingly superficial, in fact, very important.
Indent: Where there is unity indent with four spaces, not to adopt 8 spaces or 2 spaces or Tab key.
Parenthesis: indicates the priority logic flash readers, it is clear that the order of operations expression.
Notes: easy to read. Annotate a module, use / ** /; annotation a variable or method using //. Comment It is necessary to modify the program as something to be constantly updated.
Branches: Each statement on a single line appears not allow more than one line of code.
Line width: defined as 100 characters.
Name: Description not mention the type or other aspects of grammar in the variable name, to avoid too much description. If the information available from the context, such information need not be written in the variable name, to avoid can not happen in the qualifier.
Underline: Scope for semantic annotation and variables separated variable name in.
Case: variable name consists of several words with case sensitivity.
Code Design Specification: General principles and aspects of the links between the design patterns and programming modules.
Function: Function Function should be clear, the most important one rule: only one thing, and to do
Second, an array of library design
No
Third, the project ER diagram
Fourth, functional flow
Registration -> Login -> Edit text or audio or photos -> Push specified time -> receive push messages
Fifth, team division
| member |
Division of work |
The proportion of work |
| Zhang handsome |
Development Framework |
25% |
| Liu Zhao strong |
Develop |
25% |
| Machen Yu |
interface design |
25% |
| Yue only group |
test |
25% |