Misunderstanding of Modeling

Misunderstanding of Modeling

Keywords:
Modeling posting time
14:56:59 Article type:
Translation to post vote
Vote
Luckygao translation Source: http://www.sdmagazine.com/documents/s=844/sdm0108k/0108k.htm


Misunderstanding of Modeling
Go out of general design mistakes and embark on a successful journey
Scott Ambler (scott.ambler@ronin-intl.com)
Original article: http://www.sdmagazine.com/documents/s=844/sdm0108k/0108k.htm
The translation of this article has not been approved by the author.
Whether you follow heavyweight methods, such as Enterprise Unified Process (EUP) or lightweight development processes, such as Extreme Programming (XP), modeling is indispensable in software development. Unfortunately, there are various errors and misunderstandings. This comes from a variety of aspects, from the study of theoretical errors, cultural deposits in the field of information technology for decades, the hype of Software Tool developers, and Object Management Group (OMG) and IEEE standards. This month, I will reveal the misunderstandings in modeling and point out the facts.
Misunderstanding 1: modeling is equivalent to writing documents.
This is probably the most destructive one, because developers can give up modeling on the pretext. Many good software developers say they don't want to waste their time on these "useless" documents. They indulge in coding and create fragile and inferior systems. In addition, even many responsible developers now think that modeling is annoying, rather than learning the corresponding modeling technology.
Fact analysis: the "model" and "document" are conceptually different-you can have a document that is not a document or a model. A design drawing is a model, either painted on the back of a napkin, written on a whiteboard, or on a Class Responsibility Collaboration (CRC) card, or a rough User Interface prototype generated based on the flowchart recorded on the newspaper and paper. Although none of these can be said to be documents, they are all valuable models.
Modeling is like planning: the value of planning lies in the planning process, rather than the planning itself. The value is embodied in modeling activities rather than the model itself. In fact, models are not a part of formal documents in your system and can be discarded after their mission is fulfilled. You will find that there are only a few models worth retaining, and they must be perfect.
Misunderstanding 2: You can consider everything from the beginning.
This is a popular term between the 1970s s and the 1980s S. Many managers are studying software development at that time. The superstition of this will lead to investing considerable time in the early stage to model everything in order to make everything right, try to "freeze" all the requirements before coding starts (see misunderstanding 4), so as to suffer from "Analytical paralysis"