"Efficient product documentation is an integral part of the process of creating a great product in the development process Writing a product document can force everyone to think rationally, communicate frequently and clear responsibilities and responsibilities from the very beginning of the project - all of these Will result in better software quality, lower schedule risk, and less time consuming product documentation including the following:
As shown in Figure 1, users and application scenarios
By clarifying the user groups, user roles, user rights, and so on, combing and building user application scenarios according to business scenarios helps to make demand analysis more accurate and make product functions more comprehensive and closer to user needs.
2, the system / product goals
Clear product user needs, by the needs of the priority and value classification, and decide what kind of product design, and use this product to achieve what kind of goal.
3, the introduction of functional modules
Design and planning of products need to have the function modules, function points, and generally there will be the main function of the page to support this function module.
4, functional requirements detailed specifications
- From the top down, describe the composition of the product and all the ibutes of the page
- From the user's standpoint, consider the interaction of feature pages
- System Products business logic and rules of the sort "
Signup today to claim your Discount. Get Started before it's too late!
