The following is a personal obscenity:
When we took over to a new project, the usual development process is:
Needs analysis -> System -> Encoding -> Test
The requirements analysis phase:
We need to repeatedly communicate with customers, figure out what he really needs is, most people usually just practice sound transmission machine, simply put the customer's request relayed to others
In the requirements analysis stage, we should first investigate where industrial customers, a clear understanding of the customer's industry business logic, in order to understand the customer really wants is what the premise, but after a clear understanding of customer needs, combined with their own technical experience appropriate to the customer to discuss a more perfect solution, and can be extracted from the needs of customers really want
System design phase:
The importance of system design is that you can not add designs to cover a small house, but you can not go on without the premise of the design cover skyscraper, which is why many projects do not do it very often the cause of system design, (I to cover only the house, to live on the line). But if you need to run a long-term project continues, and needs constant maintenance in sight, not a clear system design certainly does not work, it will eventually fall in a burst of high winds. How to design a system?
After the first step to understand customer needs, the customer needs a detailed written on paper,
1: Start looking for nouns. This is the first step called domain modeling
2: On the basis of the field of modeling, began to create an object, the object is modeled in one model, which is the property of the object model nouns, verbs and we look for in the requirements specification, and then classified into different verb model, which is the method (usually this step is more difficult, it is difficult to distinguish which model the behavior of which belong to)
3: Each object will be connected via a variety of design principles and design patterns together (there is no express right now not to use the design principles and design patterns) you can not use the design principles, but certainly better use of design principles, not using the design principles of the consequences someday you might fall into a pit
coding:
Coding system design through the design phase, (which is not a lot of reason code code is self-deprecating agricultural farmers?), This step is really not much gold, similar to the translation, crying. . .
test:
Responsibility test is very important, he was the last one off before the product launch. . .
In the face of the waterfall flow needs, how to deal with?
Waterfall demand that every hour every day there are new demands came at the same time there is no connection between these demands, give an example:
1: to add a Wings Iron Man
2: add a tail to Iron Man
3: Iron Man needs to be red wings
4: Iron Man can fire-breathing. . .
After all, the needs of customers, regardless of what is required to meet the customer does not care about adding a feature on a sophisticated system of how difficult it is to develop things, (just do not understand how it empathy?) Clearly If you take a normal process: requirements analysis - system design - coding - testing, it is certainly not completed within the specified time, so this time most of the practice is to ignore the system design stage (more waste of time), and then use their project the familiar experience to add a field in a short time, this situation if you are a veteran can be normal, if it is possible to get a novice that is a disaster. So deal with solutions waterfall is not development, but in the absence of system design aspects.
System design aspects when considering new requirements under the premise of the entire system architecture. There must be between the needs analysis and code development a link, this link is to sort out the complicated requirements to be expected planned project specifications, requirements analysis is in accordance with the rate per hour coming in, and to design systems to be developed a document given week, even two weeks in order to solve the contradiction between stability waterfall demand frequent and software development. Premise system design is responsible for the design must be very familiar with the project code structure and business logic, or designed also difficult to use.