(Meaning no one dark, do not like do not spray, pure entertainment)
background:
In the actual development, a problem commonly encountered: changing needs.
This is inevitable, there are many reasons, roughly summarize:
Scene ①: Because people's thinking is always subject to variation, product performance to the client or manager or even testing or other development. Analogy: a set of UI design, development did so, and above the results the next day that the UI does not look good, change! But the service (background Interface) do not need to change, but, front to change.
Scene ②: because different people's understanding of things, a reaction to the development, that is, front and back and even UI even product manager and even customers such as understanding of the needs of different. Analogy: Customers want a tiger, Product Manager UI or feel like a cat, so let UI drew a cat; that is a background animals can eat and drink Lazard, then wrote animals; and the front end is to use UI interface and to draw animals like cats, do a tiger out. But not the same as the tiger and cat calls, even in animals did not cry design attributes, then it will have several consequences: change background, foreground change, according to UI do not, or do not call it. As for what kind of final result depends on the company culture and communication process of the team.
The most common is the top two reasons, of course, there are many others, such as technical bottlenecks, version update and functional, consider not comprehensive product design, the time factor, or even external factors and so on.
phenomenon:
He said above so many reasons to change the demand analysis, now say the phenomenon is a demand for change, and change is a bug aspects.
Take the demand for a start if the design is not good, such as design does not leave room for expansion and modification, after a finished version, if you want to expand, it will take a lot of energy, and very prone to a lot of bug. Take the work of the phenomenon, now there is a need to bridge the shelves in a river, people can reach there from the side of the river.
The idea designer (XXX) is: find a wood, river width multiplied by the person's shoulder (back-end interface design), ride in the river, get (want to do simple). Then find the two right distal positions, with a background of wood, resting on the upper side.
Well, this time needs done, people can walk on top of the wood. A complete version.
With a period of time, when the customer wants to be two-way traffic, so this time it was not enough width planks, so that background, if it continues to use wood, nor is it can not achieve the target, for example, two people come together to face, so they go sideways, then walk normally. As a result, the front end going to change, add a condition, when the two coincide, walking sideways, more than two, wait.
After a period of time, the user may want the cars in the past, then the board even more to die at this time, so the board should widen the thickening, or even consider the construction of the bridge in the true sense. But the construction of the bridge significantly more complicated than a piece of wood, all began to change. Back to the raw material, UI design to the drawings, the front began to bypass. (I do not know the real bridge-building, here by pure imagination) we must first consider the good, what are the elements, for example, to the deck to the pier, to railings and so on. The raw material has not come when the front began to put on airs, to setting up the various needs of all, imagine the background will give you the piers, bridges, stone, railings and so on. However, until interfaces written, raw materials arrived, only to find raw materials (Interface) only cement. The reason is, the front end can be made with cement piers, railings and the like. then. . . Finally made an end, cement was found difficult to use, often hang, specifications and chaotic, often with bubbles (return null), you need to make up their own front-end (check) with other materials (Interface), so it is often the case, a module , page whenever you need to find more than a dozen interfaces, and a variety of front-end data processing (dynamic deck with wood there, dynamic fill the pit with wood there).
During use of the bridge, if there are problems, since the raw material (interface) cement only, it is to go and change the structure of the front end, not only by changing the structure of the rear end to change to change the ratio of cement (interface parameters), then shining new front-end ratio of cement to re-patching.
This example may be a bit exaggerated, but the fact is true. And then hands it to the test, you need to measure the bridge. For example, the quiz can not be over-aircraft artillery, tanks, aircraft carriers quiz can not be on the (exaggerated, ha ha). For example, try to take the edge will not be overturned. While doing a lot of front-end railing (compatible with a variety of conditions scenes), and once overturned it, for example, the middle of the railing big gap, then a small toy car overturned. At a time when the background is not directly related to it, because that is a provider of cement. Thus the front end of the railing to encrypt. Aircraft artillery tanks, aircraft carriers horsepower foot, cement, breaking overturned, at most, is the background to something more solid concrete and reinforced to the front railing. He walked lost, plus front-end to the signpost, walked get lost (parameter acquisition less), front-end to make a compass (check with other interfaces), and even wanted to airport. . . . . .
There's even a scene: The background to the N route, for example, people leave the road, cars go way, way aircraft artillery tanks go. Then the front end to judge whether a person or car or something to take a different road. Although the goal is the same, across the river. But then, and indeed completely different design. Design on a bridge (one page), while N path, but some of the bridge piers, railings, etc. (parameters) are not, according to drawings do it - no material, so a lot of places do not, in the end ugly death. Shining interface to do it, to get rid of a lot of parameters, the last page or ugly death. The number of background should not focus on various parameters, and should not be a bunch of no significance to interface it?
And you want to avoid this phenomenon, in fact, is not said than done: give the background of several materials (rich interface parameters to improve some more, at every turn is not null, can not give in to that kind would never), the design of comprehensive consideration some (I do not just want to change)
……
Ah, too many feelings, do the next summary.
to sum up:
Having said that, I want to say is that, very often, not only of how simple and how to do it, but from the beginning of the design considerations more fully. These and personal experience has a direct relationship, which is why the development of a more adequate experience to do something out of the general graduates than do something useful;
The second is, in terms of cooperation, we can not only of how simple how to own, regardless of people's life and death. This one is communication, on the one hand is the people's work habits, on the one hand and corporate team culture. For example, some people have been accustomed to the old salted fish, how to communicate did not use, do not change even with the leaders said. This is bad.