I first read people 's month is about 1 year ago. It's time to be a new project. I have time today, I have passed the classic books in this software engineering. Read "Moon Myth" with new understanding and feelings.
"Using people as a measure of a measure of a job is a danger and deceptive myth," adding people in projects to progress, will only make progress more backward. ", Has a new one for these classics understanding.
At the composition of the project, I personally prefer the number of items that have fewer number of people, which saves the time and energy taken by project communication.
In the system design, I tend to be the project system with "noble authority". I prefer to agree to agree to "the opportunity to create and invented in the specific implementation," does not decrease because of the designated external technical description, but the inverse creative activities will be enhanced because of the norms, the entire product is the same. " "The architecture designer must prepare a realization method for any characteristics described by himself, but he should not try to give a specific implementation process."
Regarding the style of the specification, the book mentioned in the book "Every instruction must repeat all the basic elements, all the words are consistent. This often makes the manual to read boring.
But precise is more important than vivid. Yes, we are more accurate rather than vivid when writing demand specifications (SRS).
