Software development process outline and documents generated at various stages

From: http://blog.csdn.net/flyfish1986/article/details/3870053

 

Software development process outline and documents generated at various stages

 

Yan shengsong

1Demand Research and analysis

When we build a project, the customer may verbally tell you what he wants to do, or give you some documents to tell you that this is the requirement. It is difficult to know what to do based on a few oral statements or some documents. At this time, we need to mine the requirements to get a list of functions or use case diagrams. At this time, communication is very important. By constantly communicating with customers, we can refine the use cases, and do not need to pursue complete functions or use cases. Through repeated communication, the function list is constantly improved.

The Requirement Analysis Steps are requirement acquisition, user requirement analysis, user confirmation, software requirement analysis, and Requirement Review. System design starts after review.

Formed by: approved by both partiesFunction list or use case diagram, Software Requirement SpecificationAnd so on

2System design (Object-Oriented software development process)

When you know what features need to be developed, you need to classify and classify functions according to their interrelationships, and follow the object-oriented design principles ., design classes based on these functional points, map the nouns in the case to the entity classes in the final system, and map the verbs and functions. Of course, this ing does not have a one-to-one ing relationship. During this period, we need to communicate with users to constantly improve the requirements. We need to add, delete, and modify the mappings based on actual conditions. Finally, these classes and functions form a class diagram.

The system design steps are system overall design, system architecture planning, system boundary definition, system module division, detailed class design, function design, interface implementation design, database design, reviews the design.

Document creation isInterface Design Specification, software design specification, database design specification, technical solution selection SpecificationThe software design document can use a subset of the UML diagram to describe the software from both static and dynamic perspectives. it is not required to cover all aspects. If the design does not require the participation of the database, the database design is not required.

3Implementation

Tasks should be divided according to the programming personnel level and programming efficiency. coding should be concise, efficient, readable, maintainable, scalable, and reusable according to the agreed specifications.

The implementation steps are to define coding standards and coding work standards, establish a development environment, code and execute unit tests, develop integration and deployment plan definitions, and review codes.

Document creation isUnit Test Report, code submission and unit test script

4Test

The test is based on the requirements of the software and planned according to the requirements, the software is tested in terms of functionality, security, reliability, compatibility, scalability, resource usage, ease of use, documentation, and quality.

The test procedure is to develop a test plan, review the design plan, test case design, review the design case, execute the test, and summarize the test review design report.

The document is,Project Test Plan, project test cases, project test report, Review ReportAnd so on

5Acceptance

When submitting the acceptance request, you must use the list or use case diagram approved by both parties, and the software requirement specification.

The acceptance process is to develop the acceptance plan, review the acceptance plan, implement the acceptance, deliver the signature, and provide services and maintenance.

Document creation isAcceptance plan, acceptance plan review report, acceptance reportAnd so on

 

References

1 <elaborate on software requirement analysis process extraction-Abstraction-sublimation>

Address: http://tech.it168.com/d/2008-04-02/200804022036729.shtml

2 <principles of object-oriented design patterns>

: Http://blog.csdn.net/ I _mimi/archive/2009/01/03/3689821.aspx

3 <temptation in the software design process>

Address: http://blog.csdn.net/lovetheme/archive/2008/12/27/3623218.aspx

4

Address: http://space.itpub.net/14780914/viewspace-536447

5 <define system boundaries>

Address: http://blog.csai.cn/user1/15332/archives/2006/6343.html

6 <principles that must be observed in software layering>

Address http://www.cnblogs.com/daitengfei/archive/2007/04/30/733126.html

Layer-7 architecture and hierarchical development

Address http://www.uml.org.cn/zjjs/200807013.asp