Build software prototype

After the R & D process is recommended to the prototype construction stage, we have a basic prototype work product. The prototype construction work has clarified our ideas and verified the technical feasibility.

The ideal prototype (after the global design phase) product features:
The layered architecture is stable.
The association between a namespace and a namespace is stable.
The association between classes and namespaces is stable.
The class-class association is unstable, prototype Program Members can adjust the strength of the association relationship as needed, for example, adjust aggregation to dependency.
The method signature of the class is unstable. The prototype programmer can adjust the method name, parameters, and return type as needed.

As a matter of fact, we know that the current prototype work products do not even have or do not have any of the above features. Therefore, we need a more comprehensive and systematic model work product to guide our coding work, such: from the model, we can explore the relationship between packages, the relationship between classes and packages, the relationship between classes and classes, and the detailed implementation of classes ....

At another level, the adjustment model must be adjusted. Code It is faster, especially when our products are very complicated. But what is the opposite? Where did we get our time? Oh, there is a method missing, an attribute needs to be added to the interface, and that parameter is not a simple type. modify it, repeat it, and repeat it. We are also happy, ^_^!

On another level, if we claim that we have very good professional habits, and when someone comes to communicate with us about similar work products, we respectfully ask them to sit down and find pen and ink and whiteboards, draw our designs, hook up our ideas, and then open our code, flip the code one page at a time, or simply don't flip it. Ask them to read it by themselves, this is what we can do. Of course, we can open our mouths and ^_^. At this time, will we be ashamed of "our own claims?

Do we have to design it like that? Do I still need to build a design model? How many sheets of paper (White Paper, black paper) and several pens (pencil and oil pen) are enough?
So, do I still need a software development process? No, we have a mouth, a brain, and enough. ^ _ ^. What do you mean by the method parameter? You said it is a string type, and it can only be empty cloud, we are all empty cloud, ^ _ ^.