Software Requirements Best Practices read the note one

12th Chapterthe first chapter of "Software Requirements Best Practices" describes the "demand status analysis", the author in the beginning of the article by enumerating Standish Group organizations summarized some of the data is very clear and persuasive expression of software requirements for the success of the software plays a very important role, specific data such as:

Among the software success factors are 15.9% user participation, 13% clear demand description, 8.2% realistic customers expect these weights up to nearly 50%, it is clear that the demand analysis in the software engineering industry is very important and must do and to do well.

The authors cite a lot of real-world examples (perhaps only in the workplace to understand it), these examples are real real or is happening, the author of one by one points out the drawbacks; for example, write a software specification requirements statement, our requirements are to whom to see, who will see that part? These two problems are real, indeed, the hard-pressed programmer to slow down to write a thick stack of documents, respectfully Qizaotanhei to the manager, but the manager will look at it seriously? Yes, he certainly won't! First of all, the manager has his own main responsibility not to waste too much time in this regard; second, a specification needs a manual less than tens of thousands of words, contains a lot of content, the manager does not know what to look at; again, the programmer's requirements specification is too many professional terminology, and the manager is not necessarily know the technical person, This brings a lot of unnecessary trouble in understanding. Therefore, in writing the document, the author proposed the method: The requirements specification should be organized by the Business Wizard tree structure.

In addition to this aspect of the problem the author also cited "Low user participation" "User demand is too unrealistic" "Software Requirements change frequently" "Internal personnel communication distortion" and other major issues. As a novice without understanding the software requirements, of course, is not thinking about this much, think that the play of software is in writing (it seems really ridiculous), now really appreciate the importance of demand and goals. In fact, in the need and exchange of the key is to deal with people, demand analysts and customers efficient communication between the Code writer and the project manager of the tacit cooperation, and the company's various departments of seamless collaboration is the key to success. As for technology, these can be bought with money.

Software Requirements Best Practices read the note one