The best way to validate the content of use cases is to ask a potential user to role-play, or work through the use case by using the written steps. This will help to confirm that each step and each input and output are correct and that the final result of the use case is the same as the result that is displayed in the event-action list.
The best way to validate the content use cases is to add notation describing all the steps and concerns and issues that may be brought upon in the system. This approach will provide guidance in the procurement of information on another use case for the same project or for a similar project, thus allowing each intuitive thinking when it comes to creating use cases for each project. I would also like to add role playing in here to assess and obtain feedback of what is right and wrong with the system. These to validating concepts could be closely related because the documenting of everything also creates a sense of “right direction” that the project is heading and what to do and not do in the future. Both of these ways assist in the correctiveness of the information that is included in the use cases
As the book states, the most powerful approach is to ask the user to role-play, or by executing the written steps in the use case. The user will make sure that the inputs can produce the outputs and final results that are displayed in the event-action list. The importance of this role-playing enables the project team to understand and outline the user-system interaction that is important in a new system.
By reviewing the the use case with its primary users we can validate the content of the use case. We can do this by confirming that each input and output are correct and that the final use case is consistent with the final results of the event- action list. By executing the steps written in the use case the user can validate that the content is correct. This is called "role playing". By following the steps as if they were directions you can reassure that the inputs will produce the output and that the final result is the definition of the use case.
The best way to validate the content of use cases is to ask a potential user to role-play, or work through the use case by using the written steps. This will help to confirm that each step and each input and output are correct and that the final result of the use case is the same as the result that is displayed in the event-action list.
ReplyDeleteThe best way to validate the content use cases is to add notation describing all the steps and concerns and issues that may be brought upon in the system. This approach will provide guidance in the procurement of information on another use case for the same project or for a similar project, thus allowing each intuitive thinking when it comes to creating use cases for each project. I would also like to add role playing in here to assess and obtain feedback of what is right and wrong with the system. These to validating concepts could be closely related because the documenting of everything also creates a sense of “right direction” that the project is heading and what to do and not do in the future. Both of these ways assist in the correctiveness of the information that is included in the use cases
ReplyDeleteAs the book states, the most powerful approach is to ask the user to role-play, or by executing the written steps in the use case. The user will make sure that the inputs can produce the outputs and final results that are displayed in the event-action list. The importance of this role-playing enables the project team to understand and outline the user-system interaction that is important in a new system.
ReplyDeleteBy reviewing the the use case with its primary users we can validate the content of the use case. We can do this by confirming that each input and output are correct and that the final use case is consistent with the final results of the event- action list. By executing the steps written in the use case the user can validate that the content is correct. This is called "role playing". By following the steps as if they were directions you can reassure that the inputs will produce the output and that the final result is the definition of the use case.
ReplyDelete