Interviews with industry software team (by mail, microblogging, letter, read blog, etc.), ask about their software development process.
Read blog by the way, I know that the software development process is as follows:
1, the first project plan, initially planned to be a milestone in nature. You can press the waterfall model settings, the main point milestone for the needs assessment, design review, after the unit test code development and integration testing, deployment of on-line is a very important milestone, the average user would expect when the system can be used to enter the trial operation period (also referred to as user can test phase
2, requirements development phase: how to write demand is critical, make software to call a grilled one thousand one hundred thirty-three Wu Si-qi forty-four. How to learn to demand development can go to the next classic "requirements engineering" is the translation of the book, is not very thick, but need to do better able to understand why this need to exercise their own practical experience. If there are project members can do together we need at this stage for business to understand, analyze, how to carry out research and written expression, business flow chart describing the document editing capabilities as well as have a lot of requirements. Generally divided into "user requirements specification" and "requirements specifications", small projects can write a "needs analysis", "user requirements specification" is described by the language of the user, allowing users and the development team agreed to the demand of understand, "requirements specifications", is the analysis of user needs, the formation of the system to have a function, the user can provide truly interoperable document, which is an important baseline late in the design and code development. In addition, as what it needs to come up with user UI and user communication is also an important means of access needs, although this belongs to the category of design
3, the system design stage: overall system architecture, combined with users of the system environment, the development of language and running on your network hardware requirements, determine development tools, application system architecture design relationships, through the analysis of user requirements phase of classification, description of each subsystem and the user module or a global view of the FIG, and relationships with other systems. That is, the border issue to figure out the system. In addition to high-level summary of the design in architecture design, also we need to design a network topology diagram, and deployment diagram. Summary There is a more important design subsystems, modules reasonable division. Name of the module will largely be the main menu of the user, how to get a clearer subsystems and modules with the user's point of view is very important.
4, code development and unit testing phase: This phase general need to improve the waterfall model, similar to the down-generation development, a reasonable division of the module, the code development master plan of the testing phase is divided into multiple time periods, each time period includes code development, unit testing and integration testing, this stage also need to track demand for change control, change if there is demand, then put requirements documents, design documents are re keep up. Benefits down is to keep the process on behalf of the development of the code development stage pull, there is no timely self-examination, careless to commit time, not the user wants, there may not be what you want.
5, the project manager important responsibility is to control the schedule, early detection of risk, and can come up with good prevention measures and solutions. Reasonable arrangements for the development team tasks, task scheduling and timely convergence, you will feel very artistic sense, to their own experience of this. In addition, attention to the situation of each project team staff to maintain high combat effectiveness, to discover and encourage the team to move forward together toward a goal.
6, testing, testing is a very important aspect of the project, how to test, how accurate the test, how to effectively test, how the test coverage, time, manpower, experience Den aspects, there will be constraints. Advanced testers can analyze each test point system, we need to be involved in the design stage, early to know how to test, to write test cases.
7, paperwork, documentation in project development also occupies an important position, unless you think the code is the only project outcomes, then you throw away the document it, everything in your mind, a team of staff go, part of the project it away. In fact, code development also requires documentation, is the result of the code, the code is the result of comments, module development files also important results, because the programmer logic in the development time is kind of how useful role for the future look into the problem. Unless your level of system design methods to the class, the code logic are also designed well, then the programmer CODEING go.
8, QA is the quality assurance process of the project, some companies it QA and testing into one position called the QA & testing personnel, or called QA staff. QA is the supervision of the whole process of the project, independent of the project. Supervision of project managers submit the results in each project milestones, warehousing form the baseline.