The requirement document is the most important document output by the product manager in the daily work. What is the requirement document bulk sms service writing? What should be included? To clarify this problem, first of all, it is necessary to clarify who the readers of the requirements document are, and what content the readers need to obtain from the requirements document. In general terms. The following is what I understand the requirements document should look like, for everyone to discuss. The most important readers of the requirements document are the product managers themselves. Whether it is to use the requirements document to describe the realization ideas of the requirements before the requirements are realized, to design, develop, and test the requirements bulk sms service according to the requirements documents, or to review the requirements documents for review and summary after the requirements are launched.
It is based on the requirements document written by the product manager. The next readers are the designers, developers, testers, and other bulk sms service product managers responsible for the implementation of the requirements. According to my habits, the requirements document will contain the following five parts. 1. Requirements change log and version iteration record The first part is the requirements change log and version iteration records. From the proposal to the final launch of the requirements, some requirements changes or scheme adjustments must be experienced in the bulk sms service middle, so a change log is required to record these changes. The requirements changelog doesn't just write what features have been added or removed from the requirements, but more carefully.
For example, the function point A in the requirement was originally planned to be realized by solution 1, but considering the limitations of resources bulk sms service and real scenarios, it was changed to solution 2. This should also be written, although the result is still realized in the requirement. A function point, but from a process point of view, the transition from plan 1 to plan 2 is an upgrade of product managers’ thinking and a deeper consideration of resource constraints. In addition, it should also record clearly why the requirements are changed, what it looks like before and after the change, and what effects may be produced, so that the details can be found later. The version iteration record, in addition to the version iteration of the function in the requirement, should also include the iteration of the bulk sms service product manager's thinking path for this requirement. The version iteration of the functions in the requirements is familiar to everyone,