Software development process
Interbank trick works slag slag! Storm cry. . . .
Millet (intelligent hardware unit) on one side, two sides Let me explain in detail about the software development process
definition
Software development process :
- wiki: software development process (software development process) is a software development life cycle (software development life cycle), the various stages of realization of the demand for software-defined analysis, design, implementation, testing, delivery and maintenance. Software development process is a step should follow the development and building systems, software development road map
Common process model:
Agile development - Waterfall
requirements->design->implementation->verification->maintenance
Process
Requirements Analysis -> Outline Design -> detailed design -> coding -> Programs Test -> Software Delivery -> Customer acceptance -> Code Maintenance -> reconstruction project
1. Demand Analysis
Established demand, on demand can create a functional description
Probably clear flow of events: the logic model, the classification system function modules, package diagram
The operator specifies the various functional modules implemented
Simple demo (demo): critical role in the tender
2. Summary of design
Process-oriented mainframe - flow of events, attention to detail
object-oriented main frame - the object of the process
What needs module, which interfaces
3. Detailed Design
1. According to the abstract object class, the class diagram is formed
2. class distribution of responsibilities, the main member functions. Details, function behavior
3. By timing diagram validation class member functions can be realized and the flow of events
4. design class member variables, member variables from the pre-conditions, postcondition, method temporary variable.
5. analysis and design class member function's return value, parameters, function names, visit control attributes (public private protected)
6. Process Design member functions: process (FIG activity / state FIG), abnormal
Active state diagram
7. Other details: constructor, destructor, copy constructor, operator overloading
8. Abstract incorporated by inheritance and polymorphism. optimization. Reduce the coupling between modules.
9. Apply design patterns. Not to use design patterns and design patterns. It could easily backfire.
The final formation of a detailed design document
Interface controller, call
Detailed description of the functionality, interface type, function, conditions, process design, key algorithms, the key repository
4. Write code
Be written in accordance with the code design documents
Writing code is the basic test to verify
1. The basic test, to test the function of each class and the main function definition
2. Test Unit, module level
3. Integration testing, the modules are completed, do integration testing
5. Verify test
Black box testing
White-box testing
Functional testing, performance testing, stress testing, robustness testing, stability testing
6. Product Release
Installation Guide, User Guide
7. Customer acceptance
8. Maintenance Code
Software and change according to different functions
9. remodeling project
There are new technologies emerge, the software does not change the function of demand, with new technology to re-implement the original functionality while