The Product Manager's Desk Reference by Haines Steven

Author:Haines, Steven...
Language: eng
Format: epub
Published: 2013-06-12T21:47:33.851000+00:00

Organizing Documents

In order to clarify and justify the requirements, Product Management and Product Development need to collaborate and negotiate. Product Management needs to be able to explain the requirements, while Development needs to be able to interpret and understand them, so it can respond accordingly. Many products are treated as a system, structured from a variety of product elements, so there should be a document hierarchy that organizes the requirements according to the product's overall design. In a system, there may be a list of requirements for software as well as for the physical hardware (as described earlier); there could also be a series of documents focusing on performance, maintainability, and security.

I cannot provide you with an explicit set of guidelines that tell you how many types of documents should be used, because the documentation is dependent on the type of product and its degree of complexity. The critical takeaway is this: requirements should be organized so that you can easily isolate specific requirements that may need to be considered separately. For example, if you plan to evaluate subassemblies as they are completed, it would be highly inconvenient to have requirements for those subassemblies scattered through many sections of several documents.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.