Cmme Process Document

 

Over the past one and a half years, I participated in an important project and helped me participate in two projects and some time slice design and development tasks.

Let's look at it again.

These personal accumulation is no longer simply a technical topic, but more is the overall personal quality, teamwork, and collaborative work. In the process of collaboration with colleagues, we consciously improve our ability to communicate, communicate, and describe various aspects. In this process, we can understand the significance of software engineering and standardization, and truly understand the meaning of software engineering and standardization.CmmeSoftware management theme value. The value of our technology is to serve our customers. Technology is only one of the key points in the entire software project. A good technical system is the basis for supporting good software products, but the technology will not, it cannot be the whole of the software.

2010 years of participation cmme there were a lot of supplementary documents, now let's look back at cmme if we do things based on this set of rules, the results will be very good and cannot be guaranteed, but at least the results will not be very bad.

I have been reading two books recently,<UMLAnd Mode Applications>,<Agile Software Development>The two most impressive phrases are iteration and responsibility. The method of small steps and fast running is combined with a pragmaticCmmeWhat will happen to the process?

 

 

Structure

 

 

Document Writing

 

 

 

Cmme/others