Snippets of programming experience other than "black box test Management"

In addition to doing a good job of "black box test Management", individuals find the following more worthwhile to work on, after all, "before and after"!

1, architecture and algorithm feasibility test analysis: Mainly including performance, concurrency and other aspects

2, Codereview: Very simple, but many people did not do so, in fact, this is more likely than "black box test" to detect boundary problems, process correctness problems. Worth popularizing!

3, test drivers and unit testing, many people in order to achieve those who do not understand the requirements of programming management, often less than these seemingly not easy to make progress steps. (to a large extent, change the design thinking)

It's easy to avoid mistakes when you know where things can go wrong.

4, UML and use cases: especially UI modeling, individuals feel the most indispensable, UML and use cases should at least be able to cover the core content.

Specific how to do, according to each person, each unit or even each project to do specific optimization, here to provide ideas.

5, the intention of the structure (function modules of the relationship < use cases >, Distributed Computing node relationship < that is, layered >, class hierarchy <uml diagram >, upgraded file, database schema, database table Paradigm <er diagram >, Concurrent access and multithreading and so on): bad structure, code up the difficulty, problems and many difficult to solve! In personal experience, it can be divided into six stages.

A user needs to collect, interview and confirm-->
B Architecture and feasibility analysis and documentation of-->
C develop test deployment and maintenance detail Plan-->
D1 unit encoding, Test <-->D2 deployment Test-->
E1 development environment Integration and testing-->
E2 Real Environment Simulation test-->
E3 Deployment Preview--> (original system backup)-->
F deployment

1 Major "outputs" in each phase (regardless of input)
A: Requirements specification, UI modeling, use cases and UML diagrams and the first draft of system use Help files, System risk reports that may exist
B: System architecture Diagram (logical and physical), core algorithm code and test report, second party and third party component risk Analysis report
C: Detailed instructions for each module of the system, database architecture and testing, development of each function, coderivew and test Plan, deployment plan (equivalent to daily build), integrated test plan, system upgrade consideration and solution. Note that you can solve the possible problems of the database before the code as much as possible!
D: Code, bug management, executable files, development environment, test environment
E: Installable packages, end-user documentation, and related documents before modification to be consistent with the current system
F: Possible problem plan, installation and continuous optimization according to the actual situation, into the maintenance phase

2 time allocation: A:b:c:d:e:f=10:10:20:50:5:5,a stage time this refers to when the project starts, the time before the start is counted.

The real code time may be 50%