Programming is a point, and software engineering is a surface

WriteProgramIs a point,Software EngineeringIt is a face, and I spent three years on this point, and seldom think about the software life cycle andSoftware Engineering. It seems that you only know it after practice.

Below isSoftwareSurvivalCycleStage 1

I:Software EngineeringProblem definition stage

Process:

1. Market personnel begin to negotiate with the customer.

2: create a temporary project team at a temporary meeting of market personnel.

3: Go to the customer's location for a survey to determine the requirements and scope of the project.

4: After completing the survey, write the Requirement Specification (written by developers) based on the accumulated data ).

5: The developer writes the Software Requirement Specification and submits it to the marketing department or product manager for approval.

6: After the approved demand statement is approved, the market personnel should confirm the request statement with their own solutions (written by the Marketing Department) to the customer. The confirmation is complete.

7. After the requirement statement and solution are determinedCodeEstimation, evaluation phase.

Result output: Output the Survey Report (Problem definition), Specification (Requirement Analysis), Solution (Feasibility Analysis Report.

II:Software EngineeringProject plan and project initiation phase

Process:

8: the project leader distributes a code estimation table, which allows developers to evaluate the code (multiple evaluations), determine the business bottom line, select the best assessment, and determine the arrangement of developers through the evaluation.

9: the project leader sends a project status report, asking its developers to prepare for the project (build the framework through the requirement specification, set up the project environment, design the database (review required), and

Project Interface Design). The project leader prepares the project and prepares the project plan.

10: if it takes a long time to establish a project, ask the developer to continue the preparatory work or write the project investigation report, Project Feasibility Analysis Report, project proposal, project review report, and submit

The Project Manager approves the project and promotes project initiation.

11: after the project is approved, determine the developer. The project manager asks the quality department manager to set up the configuration database and send the configuration table to the relevant manager and developer.

Documents that have passed the review are placed in the location of the configuration library to determine the phase baseline.

result output : Output code evaluation form (resource and cost), database design document, project investigation report, Project Feasibility Analysis Report, project proposal, Project Review Report, configuration library form, and technical framework.