On the BBS a few days ago, I saw someone saying that the demand document was too difficult to write. He wrote this in the post: Sometimes I think that writing demand documents is more difficult to compare system analysis.
Really?
In fact, in my opinion, many times we don't think about analyzing the document, the fundamental reason is that we have no good analysis on this issue. In fact, there are only one of the documents generated by the system analysis. Some projects may be used in system function manual or systematic analysis reports, various prototypes or some other documents, such as legacy system analysis, business process improvement, etc. Even in the name of the designed design, some use case documents or even the form of various UML maps, and in XP development may be User Storey, which is not a problem in writing, because there are existing patterns Reference. I feel that there are two possible reasons for writing documents: First, I don't know what to write, then this shows that the system analysis is not done. The second is that the skills of the organization are not enough. There is a lot of words in the belly, I don't know how to say, then this In fact, it is lacking experience in writing this document. You can improve the existing analytical document or yourself slowly practice, because it is always easy to imitate others, it is always easy to write, you have a lot of people.
But in system analysis, we must figure out that any document is to make a clear what you want, if you don't even know what you want, then you can get the better, you can get the better The bigger the effect, because you may make your audience pay more attention to your form of gorgeous rather than the empty hole. So the primary problem is that you have to figure out what you want to analyze, you have to give a reasonable solution to all kinds of questions, you have to make clear understanding of various details, set Winberge "exploration requirements "One of the words is that you have to reduce the aidity. Of course, this is also related to the software process.
The people in the system analysis have not much computer knowledge, and what they describe and what they think is likely to be different, and what they think is not necessarily the best solution. As a system analyst, we must first see the real needs from these technical content, and see what the user really needs from the appearance, to help them improve, this is the system analyst really Work should be done. Of course, the document is also very important, but I think the document itself is still relatively easy. After all, there are a lot of template mode to borrow, but exploring the demand itself is a difficult job. There is a lot of software in this world that can not satisfy customers after delivery, and a large part is because systematic analysis is not done.
