It's all written a document until the company has been writing a document. I usually don't pay attention to writing documents, occasionally writing is just a summary afterwards, and the project documentation of the Er Er. This is still a broken end.
It's quite embarrassing, just two or three documents, I wrote two days, changed twice, this is the third time, so that I don't know if it is not. There were many lessons that were gave me twice, it was worth reviewing.
On the first day, I arrived at the company, I was catching up with the company to start the database modeling, because the project group used I used PowerDesigner, so the manager made me write a document about "how to establish CDM". In fact, I am only occasionally doing the PD, I will not smell before saying from the supervisor's mouth, no way, who makes the big saying, the top of the scalp.
It is not very difficult to establish a CDM. I looked at the help document, I did an Example, and I also had some eyebrows, so I wrote a process document according to my own understanding of CDM. Just as I sent the concept data modeling (initial experience) with PowerDesigner.
The result of the documentation to the supervisor, card! The supervisor said that the domain and inheritance items are not used, delete! I want to do it if you don't use it in the document, you are not bad, of course, I didn't dare to say. Oh, delete it. So the examples were kept, this time, added, and the interpretation of the concept is added, and the relationship between the control after the CDM is generated by the CDM. Some of this deleted part but added more.
The second time I will call the document Check in to VSS, and I will call me again, ask me what role name is? (Because of my illustration, this item is filled out) I said it is a role name, can have no, the main pole, "can't have Chinese in the chart, this feature you take it from the chart, so as not to Misride other people. There is also a PDM map and other deletions that establish CDM. " At this time, I suddenly realized that the main supervisor made me write a standardized document that established CDM. Since it is a normative stuff, it is naturally accurate and clear. Oh, there is a failure ...
The lessons of the failure, reviewed, reviewed, summarizing the following:
1. Lack of CDM modeling experience, so that there is no focus when writing documents, no hindrance according to project needs.
2. Do not just start without understanding the intention of the supervisor. It is a mistake in demand analysis.
The third write document, I deleted most of the interpretative things, and more refined and accurate for the establishment of CDM, for the key, the wrong part of the wrong part. I think this time will never be cardd again ...
