Users should concentrate on the steps that are followed when everything flows smoothly, generally with use cases, the user should make sure that the steps are listed in the order in which they are performed. Users also may want to write down the steps with instruction and outline the process with detail. This will keep things more organized in use cases and help the user deal with large numbers of use cases.
One way to handle a large number of use cases situation is to try and condense all information and create a more focused use case. Such a creation would have to have the use case be broken down in to parts that pertain to each other. This will identify that the postconditions will precede the preconditions of the next created use case. Division of the major task of the use case will prevent a broad focus and confusion amongst its users and even analysts.
The other way to handle this type of situation of grouping the use cases in to packages. These packages will be grouped in relation of the use cases topic. In marketing a new product, for example, a business could create a use case on the different approaches.
Users need to concentrate on making their steps consis and to the point. Make sure that you do not have more then nine steps in a USE case, otherwise it could cause differentiation in the size of your steps. You could also use packages. The point of a package is to eventually be grouped in relation to the use cases topics. You can create different techniques to help promote this use case with these ideas.
Users should concentrate on the steps that are followed when everything flows smoothly, generally with use cases, the user should make sure that the steps are listed in the order in which they are performed. Users also may want to write down the steps with instruction and outline the process with detail. This will keep things more organized in use cases and help the user deal with large numbers of use cases.
ReplyDeleteOne way to handle a large number of use cases situation is to try and condense all information and create a more focused use case. Such a creation would have to have the use case be broken down in to parts that pertain to each other. This will identify that the postconditions will precede the preconditions of the next created use case. Division of the major task of the use case will prevent a broad focus and confusion amongst its users and even analysts.
ReplyDeleteThe other way to handle this type of situation of grouping the use cases in to packages. These packages will be grouped in relation of the use cases topic. In marketing a new product, for example, a business could create a use case on the different approaches.
Users need to concentrate on making their steps consis and to the point. Make sure that you do not have more then nine steps in a USE case, otherwise it could cause differentiation in the size of your steps. You could also use packages. The point of a package is to eventually be grouped in relation to the use cases topics. You can create different techniques to help promote this use case with these ideas.
ReplyDelete