Personal experience talk about software construction

Activities in the project development process: defining issues, requirements analysis, planning and construction, software architecture, detailed design, coding and commissioning, unit testing, integration testing, integration, system testing, and assurance maintenance.

Originally in the book to see these times, indeed confused, but recently in charge of the development of the project really deep experience ah.

Demand is really important, in the beginning of the work must be determined before, otherwise often modified, not only do a lot of wasted time, but also increased the cost of development delays. Therefore, the first task of a development project is to produce a fully qualified requirements document.

How is the plan built? Of course, do the project can not be said to take one step, we must calculate the workload in advance, reasonable allocation of time and work. For example, what is the function or module of the project, how much time each part takes to complete, what can be done at the same time, what needs to be prioritized, and so on, and how the project architecture should be designed, how the database should be designed, and how the members ' tasks should be properly distributed. Another point, many times the development experience tells me, do not be too perfect, at the beginning of the time do not consider anything, but should first complete a simple function of the test version, first to be able to use, and then add the function above, otherwise it will backfire.

Software architecture is also important, otherwise maintenance can be difficult. As for detailed design and coding debugging, it is necessary to clear division of labor, the control of time, and good communication work.

Unit testing increases the cost of development (higher learning costs, more design techniques, code work for unit tests, etc.), but it not only improves code quality, reduces bugs when we write code, but also enables developers to think about the process of working code implementation content and logic, improve feedback speed, and reduce duplication of effort , improve development efficiency, and make code easier to maintain.

As for the next steps there is not much to say here, but also to focus on "build." Many programmers do not follow the above steps in their own development projects, and in their eyes, these activities are likely to be classified as "programming". So is it really important to build software?

The answer is inevitable. Software development is not done, it is important to improve the quality of the software and the productivity of the developer. I have a friend whose ability is very strong, but he is not suitable for development. He belongs to the kind of complete rather than thinking of the programmer, he completed a project or some modules of the work is very fast, but, the quality is not good, the real use of the time will find a lot of drawbacks, such as the most deadly problem ———— crashes, memory leaks, this is undoubtedly a software fatal.

An ideal software project requires careful analysis of requirements and architectural design before it can be built.

An ideal software project after the completion of the construction, but also through a comprehensive, professional system testing.

In reality, many less perfect software projects, often skip the requirements and design, and later, because there is not too much time to fix the error, the testing process has been thrown aside. However, the build cannot be without! Don't you?

Personal experience talk about software construction