Project walkthrough

Project CodeReview

Prior to the development projects in the CodeView artificial walkthrough, there is an automated walk-ways, are commonly used OLCInt, which is automatically included some of the rules, you can combine automated xcode walkthroughs. Some of the larger projects, the walk will be combined with scenario analysis logic, etc., or some specifications can not enter rules, which generally use artificial time walkthrough

Common Walkthrough:

• Walkthrough

1. Some if nested if necessary, whether to repeat;
2. If there is excess unused variables constant, annotations, dead code, a large section of code comments and the like;
3. Attribute type is wrong, for example with weak agents, memory leaks, for example, circular references, the closure is not employed __weak the like;
4. Some code optimization, such as whether the variable can be reduced, with the value of the system itself (e.g. cell data source is determined inside, can inexpath Analyzing, will not have to separate out the cell judgment);
5. Some data out of range determination processing, for example, the data source cell determines the best way to sit down, whether the value of the current taken in the current data source method;
6. At some point (e.g. auction request only once every 3 seconds to request the auction period) logical / on demand must be optimized;
7. Some storage location of the code, such as resource files (images, html, etc.) into its own Resourcefolder, write code into the respective modules in children (such as a network request put children in XXXX module, router modules jump XXXX children string into a child module, the module portion XXXX bid drawn into the child, etc.);
8. There is no contamination of the code, strong coupling;

• UI Walkthrough

FIG prototype codes match, pixel, whether the expected color;