General process suggestions for Small and Medium Software Project Development

I. Writing Purpose

This document aims to explore standardized software development processes, speed up software development, improve software development quality, and reduce overall project costs.

There is a saying in the IT field: "You can do it right; you can do it fast; you can do it cheap. pick two. "What we need to do is to provide high-quality services, short project cycles, and low costs.

II. General description

From the Proposal of the user requirement specification to the delivery and use of the first complete version of the system, the project has gone through several complex or simple processes. However, regardless of the project size, the following steps are generally required:

1.Requirement Analysis.

2.Write Requirement Specification

3.Overall Design

4.Detailed Design

5.Coding implementation

6.Testing, (UAT: User acess test) trial run, online

7.Acceptance

8.Routine Maintenance

9. (the next version of circular Development)

 

 

System Analysis and requirement specification writing are particularly important in the above steps. After the requirement specification is defined, the user must sign and confirm the specification, which serves as the basis for project acceptance. This is particularly important for medium and large projects.

There are many causes for failed projects, but the following are common:

(1) In business operations, in order to hold the "list" of complicated requirements on the customer, we accept all the compromises and concessions. The project development plan and schedule are based entirely on the customer's opinions, not on the objective facts of the specific project, nor on the careful and strict evaluation of the project complexity and project workload.

(2) The demand changes in the later stage of the project cannot be completed on schedule due to the absence of detailed user requirement analysis.

 

Iii. stages of project development

In terms of the time ratio of each stage of project development, small and medium projects are generally controlled in

1: 40% Design

2: encoding 40%

3: 20% overall design/trial run

3.1 demand analysis stage

Study the customer's requirements, identify the ambiguity of the requirements, and discuss and confirm them repeatedly. Continuous validation includes the overall cognition of requirements, definition of requirements boundaries, achievable requirements under current technical conditions, and user interfaces. Through discussions within the project team, discussions with customers (direct customers, indirect customers), and other methods, the customer's real needs are constantly clarified to write the <Requirement Specification> 〉〉, sign the signature after obtaining the customer's approval. This is the first milestone in project development. This is the main basis for project acceptance.

In the system analysis phase, you can communicate with the customer through (1) Project static diagram, project static interface demo (2) system use case diagram (for example, Rose software use case diagram.

 

The tasks to be completed in this phase include:

1. Write the project Requirement Analysis Report

The purpose of this report is to provide project analysts with the necessary materials for effective and accurate communication with the customer.

2. use case diagram

Describes the interaction process between different user types of the system and other systems.

3. Create a static project interface demo

This allows you to view the user interface and usage after the project is launched and implemented at the initial stage of the project.

4. Make necessary technical advance research.

3.2 write Requirement Specification

The main purpose of writing the requirement specification is to turn the ideal requirements of customers, such as the complexity and imagination, into the requirements that can be fulfilled within a certain period of time and under certain technical conditions. Otherwise, the project will be difficult to meet the customer's ideal needs, and will always be limited by the customer's ideal needs, falling into a very passive state.

3.3 Overall Design

After completing the project requirement specification, you will enter the overall project design stage.

Documents to be completed in the overall design phase include:

1. Overall project design-Summary design manual,

2. Database Design Report

3. Overall project development schedule

In this phase, the formal development environment and test environment of the project should be established, the basic development framework of the project should be established, and the project management configuration tools (such as CVS and VSS) should be imported into the project.

After the above stages of the project are completed, it is recommended that you review the overall design and overall development preparation of the project. This phase ends after the approval of the review by the company and group expert groups. This is the second milestone of the project.

Before the next stage, the project team can submit the following materials to sccb:

1: requirement specification

2: Project general design summary

3: Project Interface Design Manual (and interface demo)

4: Project Database Design Manual, etc.

5: Overall project development schedule

3.4 detailed design

After the project completes the overall design and the development environment, you can design the project in detail.

In the project, it is recommended that the detailed design be written by senior personnel who compile the "background" program of the project. It mainly completes the main steps for each business module from the interface to the business implementation to the database connection operation and the database implementation SQL. It is recommended that you compile a module unit test program when conditions permit and perform the unit test after the module code stage is complete. ("Test-driven" development philosophy)

The purpose of the detailed design is to complete the Simulation Programming Implementation of the project module without writing code or a small amount of code.

In the detailed design phase, an accurate workload statistics can be made for a module of the Project. Therefore, a relatively accurate workload of the entire project can be counted.

3.5 coding implementation

(Omitted)

3.6 testing, trial run, and launch

(Omitted)

Iv. Remarks

Reprinted: http://www.cnblogs.com/wohexiaocai/p/3815707.html