The description of the instance does not provide the developer to provide details of the features they want to develop. If you stop demand development during the user's demand phase, you will find that the developer must ask many questions to make up for their gap. To reduce this uncertainty, you need to describe each of the usage examples into a detailed functional requirement (A R L O W1 9 9). Each instance can lead to multiple functional requirements, which will enable the executor to perform related tasks; and multiple usage instances may require the same functional requirements. For example, if there are five usage examples that need to be verified for user identity, you don't have to write 5 different blocks. You can use a variety of ways to write a functional requirements documentation that is associated with an instance. What way to use depends on whether you want the development group to design, construct and test from the use of instance documents, software requirements scale, or both. These methods are not perfect, so choosing those software demand methods that are best for you to write documents and management projects. Avoid generating information redundancy in different places, because redundancy will make demand management more difficult. 1. Methods that use only use examples Although you may still need to use a separate software demand specification to record the needs of specific usage instances, however, a possible method is to include functional requirements in each of the usage instances. Among them. You must cross the functional requirements that are repeated in multiple usage instances. One way is to be set forth by the "including" previously discussed, some public functions (such as user authentication) are split into a separate, reusable usage example in this relationship. 2. Another method of combining the use of examples and S R s is another method to limit the use of examples to the abstract user requirements, and select the functional requirements obtained from the usage example in software requirements specification. In this approach, you will need to create trackability between using the instance and related functional requirements. The best way is to store all instances and functional requirements into the database or business requirements management tool, which will allow you to define these trackability linkages (see Chapter 1 9). 3. Methods of using software requirements Specifications Third methods are to organize software requirements specifications by using examples, and include examples of instances and functional requirements. With this method, you don't need to independently write detailed use of the instance document; however, you need to determine the functional requirements of redundancy, or only state it for each functional requirement, and whether it is repeated in other instances regardless of whether the demand is repeated. Refer to its original description.
