Idea of ideal team Model building and understanding of software process

An idea of ideal Team Model building:

Software design is a work that needs to be done by many people, a person is difficult or unable to complete a relatively complete software design. Therefore, the team is a must. But the team is multi-person, there can not be a person of the kind of high consistency and freedom, so how to build a more ideal team is to improve the efficiency of the premise and foundation.

The team has a variety of models, each with its pros and cons, but no matter what the pattern is, it basically follows the following principles:

1. An ideal team should have a consistent collective goal, a direction in which all members work together.

2. The Division of labor is clear, everyone must have their own tasks to be done, so as not to be dazed.

3. A clear division of labour should strengthen communication, and team members depend on each other to work together to accomplish the task. The completion of a member task affects the members responsible for the next task phase, so communication must be intensified.

Two understandings of the software flow:

The software flow is divided into the following stages:

*. Demand Analysis

1. The relevant system analyst to the user preliminary understanding of the requirements, and then use the relevant tool software to list the system to develop the large functional modules, each large function module has a small function module, for some needs more clearly related interface, in this step can be a preliminary definition of a small number of interfaces. [1]

2. The system analyst is in-depth understanding and analysis of the requirements, according to their own experience and needs to use Word or related tools to make a document system functional requirements document. This document will clearly list the large functional modules of the system, the small functional modules of the large function modules, and the related interface and interface functions. 3. The system analyst confirms the requirement to the user again.

* Overview Design

First, the developer needs to design the software system in a brief, i.e. system design. The design of the software system needs to be considered, including the basic processing flow of the system, the structure of the system, the partition of the module, the function allocation, the interface design, the operation design, the data structure design and the error handling design, which provides the basis for the detailed design of the software.

* Detailed Design

Based on the outline design, the developer needs to design the software system in detail. In detail design, describe the main algorithm, data structure, class hierarchy and call relation involved in implementing the concrete module, need to explain the design consideration of each program (each module or subroutine) in each level of software system in order to encode and test. The software needs to be fully distributed to the entire software. Detailed design should be detailed enough to be coded according to detailed design reports.

* Code

In the software coding stage, the developer according to the "Software system detailed design report" in the data structure, the algorithm analysis and the module realization and so on the design request, began the concrete programming work, respectively realizes each module function, thus realizes to the target system function, the performance, the interface, the interface and so on the request. In the standardized research and development process, the coding work in the entire project process will not exceed 1/2, usually in 1/3 of the time, the so-called sharpening wood work, the design process is done well, the coding efficiency will greatly improve, coding the different modules between the progress of coordination and collaboration is the most need to be careful, Perhaps a small module problem may affect the overall progress, so that many programmers are forced to stop waiting, this problem in many research and development process has occurred. It is important to communicate with each other and to solve the problem when coding, and for programmers, bugs are always there and you have to face it forever.

* Test

Test a well-written system. Given to the user, the user uses the following one to confirm each function. There are many kinds of software testing: According to the test executor, it can be divided into internal test and external test, according to the test scope, it can be divided into module test and whole union, according to test condition, it can be divided into normal operation condition test and abnormal condition test; All of these are well understood and no longer explained. In short, testing is also a very important step in project development, for a large software, 3 months to 1 years of external testing is normal, because there will always be unpredictable problems exist. After the completion of the test, the completion of acceptance and completion of some of the final help documents, the overall project is not complete, of course, in the future without upgrading, patching and so on, as long as not to pass affair cheat, it is necessary to keep track of the operation of the software and continue to repair the upgrade until the software is completely eliminated.

* Software Delivery

After the software test proves that the software meets the requirements, the software developer should submit to the user the product of the contract between the two parties, such as target installation program, database data dictionary, user installation Manual, user Guide, demand report, design report, test report, etc. The user installation manual should describe in detail the requirements of the installation software for the operating environment, the definition and contents of the installation software, the specific installation steps on the client, server side and middleware, and the system configuration after installation. "User Guide" should include the use of software functions of the process, operating procedures, the corresponding business introduction, special tips and precautions, etc., should also be illustrated when necessary.

* Acceptance

User acceptance.

* Maintenance

Modify the application in whole or in part according to changes in user requirements or changes in the environment.

Idea of ideal team Model building and understanding of software process