1, divided into incremental integration testing and non-testing assembly incremental assembly test
1) Non-incremental assembly test (non-integration testing by formula): the module is in the test unit in accordance with the overall structural view of a disposable integrated together, and be connected to the whole test procedure.
General method to prepare a black box test set and tested. Program error prone, not easy to integrate achievements. Auxiliary module unit tests using the more suitable for small-scale development system.
2) increasing the test assembly (integration testing by formula): Based on the test unit, with top-down or bottom-up layer by layer test installation, the installation know the final test is completed.
May also be used to top-down bottom-up integration testing combined integration testing, unit testing and integration testing with the combination.
The error decomposition, easy to find errors and the test is successful, the system is suitable for large-scale development.
2, the project manager can get a better performing organization support for the project to the project's strategic planning needs of the organization, contact
3, the concept of software product line that is to meet specific market or customer needs, product mix has publicly management features
4, the field is covered CMMISoftware Product Development and Services
CMMI (Capability Maturity Model Integration For Software , Software Capability Maturity Model Integration) is (both methods belong to the test-driven development mode based on CMM (Capability Maturity Model For Software, Software Capability Maturity Model) is developed from the )
CMMI by the US software Engineering Institute of Carnegie Mellon University (software Engineering Institute, SEI) expert software process improvement and software development management aspects of organizations around the world took four years and developed, and promote the implementation of a worldwide kinds of software capability maturity evaluation criteria, mainly used to improve the software development process to guide and evaluate software development capability.
5, on the TDD (Test-Driven Development)
- Test-driven development style is an agile development methodology
- TDD demand for developers to learn test-related knowledge
- May be used to develop and test driver program binding pair
- Test-driven development is suitable for use CMM / CMMI method
6, most people occupied the coding phase
7, design patterns:
- The builder pattern: representing the construct with the separation, using a plurality of simple objects step by step to construct a complex object is a complex object
- Observer pattern: many relationship between objects, when an object is modified, it is automatically notified dependent objects
- Strategy pattern: each of encapsulated algorithm, the algorithm can be replaced with each other so that each such client algorithm itself and the algorithm used to independently separated from each other
- Proxy Mode: provides a proxy for other objects to control access to this object
8, prototyping highest requirements for the development of software design and development staff
9, in development, generics simplify programming and improve the efficiency of development, generic classes are reference types, generic type safety and reduce the number of classes can enhance conversion
