Software product development cycle is generally composed of five phases of planning, design, implementation, stability and release, each stage is repeated mutual iteration process, which requires multi-party cooperation to find the best practical process. First Stage: Planning (Plan) Objectives: Planning Software Overall Architecture: 1. Market developers Measure market opportunities to provide market opportunities (MOD) defined user needs Provide market demand documents (MRD) identified major user cases User Scenarios 2 The project manager determines the visual provider of the product to determine the product visual file to determine the definition of check, definition projects and products' planning plan, user assistance plan 3. Product design and user researcher conceptual design, user interface graphics ( Visualize UI) 4. Development / Tester: The survey of processes, techniques, and tools that will be available 5. Service personnel assess potential user traffic assessment and maintenance of this product feasibility
The second phase: Design target: Determine how to develop departments to complete the standard 1. Market developers: Feedback to new features, complete brand strategy recommended documents 2. Project managers: Complete Functional SPECS Specifications Design Completed Surrounded Table 3. Product Design and User Researchers: User Interface Model Design 4. Personnel: Complete the Institutional Design of Development System 5. Test staff: Complete the overall test plan (refine) milestone: Plan And the completion of the design is the first milestone planning and design of software development. The formation is formed by "design" confirmation, repositioning and correction, re-estimating the decision during the design process.
The third stage: Implement main milestones, multiple small product cycles complete standards: 1. Market developers: promotion plan documents, complete market positioning and consulting strategy framework completed market promotion plan blueprint 2. Project manager: correction function specification , Management schedule, risk, correlation and relationship 3. Product design and user researchers: Frozen user interface model changes 4. Developers: Writing code and repair BUGS unit test completion writing code 5. Tester : Preparation of test function specification, complete testing tools and processes
The fourth stage: Stable Completion Standard: Release Market Test (BATA) Edition Publishing Technology Test (BATA) Continued bug Triage reaches zero bug, the test version is taken within the departmental responsibility: 1. Market developers: Complete the packaging. Promoting public relations, advertising plans, product demonstration 2. Project manager: Organize Triage Conference, eliminate program BUG 3. Developer: Repair BUGS, write new code only in the case of design changes 4. Test staff: Discover BUGS, record BUGS final Overall test 5. Service staff: installation test version
The fifth stage: Release completion standard: product release promotion, product after-sales service, technical support began operation department responsibility: 1. Market staff: Extension plan for the production of the film market 2. Project manager: The end of the finished work, prepare the next product 3. Developer: Repair BUGS 4. Test staff: Record BUGS, do the final test modification 5. Provide after-sales service, technical support development process Practice: 1. Work with the workflow and corresponding template (demand document, Design documentation, test documentation) 2. Evaluation development cycle Specifies detailed progress management 3. Risk is everywhere to ignore various dangerous signals, don't worry about failure, conceal live 4. Tool management: Tool development of middle repeatability (for example Test tool), improve development efficiency 5. Communication management: Coordination of individual departments, communicate with Email Conference 6.BUG management: BUGS encountered in the development test phase BUGS and user practical use of BUGS to collect records and process 7. Source Management: Use VSS or CSS and other source code management software management software versions to participate in the TECHED2003 meeting held last year, and finally have time to organize information. This article is based on Microsoft Software Test Engineering Li Dan. Software development after organizing
