A use case shows a set of activities that are performed to produce some result. An event-action case shows some event, the action it will take, and the requirements needed for that event. A use case should be prepared for every item on the event-action list because it will describe all of the possible actions. The use cases for each item will ensure that there is no misunderstanding of what the actions will be with each event. It will take more time to prepare all of these use cases but there will not be any confusion about the event, actions, and requirements.
Use cases show how certain events are triggered which leads the system to respond in one way or another. Depending on the size of the process there could be a lot of activities or just a few, but it is important to list each one no matter how insignificant it may appear at first. It may seem like a small step to the person creating the case, but to the uswer it may be important. The use case should be prepared for each one of the events listed so nothing goes wrong and the user knows exactly what actions will take place.
Yes because the advantages of having a use case is because of potential reusability of another use case. Authentication and validation credentials may be necessary for certain businesses that handle or deal with hazardous materials. The only thing that a use case should not need to be created is a use case each time a same task is needed. The previous one can be used again and if additions are needed there will be a need to create another use case.
Use cases are an effective way for analysts to break down a complex project into smaller more palatable pieces. For very simple and small projects use cases are often not necessary, however projects which go into alot of detail can be more efficiently analyzed through the application of use cases. When using use cases they are most valuable when used to describe each individual event, this is because they examine exactly what triggers each event, what its inputs and outputs are and all of the steps within each event. Long story short, yes these need to be used for each event within a complex project.
Use cases should be prepared for every action the system has going on. The reason behind this is because use cases goes through the actions the system should provided for the user and shows what the user should do in order to perform these actions. So not only do use cases help prevent actions from not working but also helps users understand the process in order to use the system.
A use case shows a set of activities that are performed to produce some result. An event-action case shows some event, the action it will take, and the requirements needed for that event. A use case should be prepared for every item on the event-action list because it will describe all of the possible actions. The use cases for each item will ensure that there is no misunderstanding of what the actions will be with each event. It will take more time to prepare all of these use cases but there will not be any confusion about the event, actions, and requirements.
ReplyDeleteUse cases show how certain events are triggered which leads the system to respond in one way or another. Depending on the size of the process there could be a lot of activities or just a few, but it is important to list each one no matter how insignificant it may appear at first. It may seem like a small step to the person creating the case, but to the uswer it may be important. The use case should be prepared for each one of the events listed so nothing goes wrong and the user knows exactly what actions will take place.
ReplyDeleteYes because the advantages of having a use case is because of potential reusability of another use case. Authentication and validation credentials may be necessary for certain businesses that handle or deal with hazardous materials. The only thing that a use case should not need to be created is a use case each time a same task is needed. The previous one can be used again and if additions are needed there will be a need to create another use case.
ReplyDeleteUse cases are an effective way for analysts to break down a complex project into smaller more palatable pieces. For very simple and small projects use cases are often not necessary, however projects which go into alot of detail can be more efficiently analyzed through the application of use cases. When using use cases they are most valuable when used to describe each individual event, this is because they examine exactly what triggers each event, what its inputs and outputs are and all of the steps within each event.
ReplyDeleteLong story short, yes these need to be used for each event within a complex project.
Use cases should be prepared for every action the system has going on. The reason behind this is because use cases goes through the actions the system should provided for the user and shows what the user should do in order to perform these actions. So not only do use cases help prevent actions from not working but also helps users understand the process in order to use the system.
ReplyDelete