Housekeeper verifies that laundry item is foldable. Housekeeper verifies that laundry item does not need ironing, is clean and not shrunken. This scenario describes the situation where only sorting, washing and folding are required. She irons those items that need ironing.ĭirty laundry is transported to the laundry room on Wednesday. She folds the dry laundry as she removes it from the dryer. The housekeeper sorts it, then proceeds to launder each load. It is Wednesday and there is laundry in the laundry room. If she notices that something shrank, she throws it out. If she notices that something is still dirty, she rewashes it. If she notices that something is wrinkled, she irons it and then hangs it on a hanger. She throws away any laundry item that is irrevocably shrunken, soiled or scorched. On Wednesdays, the housekeeper reports to the laundry room. She irons and hangs the items that are wrinkled. In each of these types of uses cases you will see that:Ī housekeeper does laundry on a Wednesday For our purposes we have defined them as Simple, Middleweight and Heavyweight use case for doing the laundry. Repeat the steps 2 through 7 for all other users.īelow, are examples of three use cases with increasing levels of complexity. Extract these and note them as common course use cases. Look for commonalities among the use cases.
When the basic course is described, consider alternate courses of events and add those to "extend" the use case. Describe it in terms of what the user does and what the system does in response that the user should be aware of. Each thing the use does on the site becomes a use case.įor each use case, decide on the normal course of events when that user is using the site.ĭescribe the basic course in the description for the use case. Identify who is going to be using the website.ĭefine what that user wants to do on the site. Kenworthy (1997) outlines the following steps: Write the steps in a use case in an easy-to-understand narrative. These exceptions are what happen when things go wrong at the system level. Alternative paths – these paths are a variation on the main theme.Main success scenarios – use case in which nothing goes wrong.Triggers – this is the event that causes the use case to be initiated.Preconditions – what must be true or happen before and after the use case runs.Primary Actor – stakeholder who initiates an interaction with the system to achieve a goal.Stakeholder – someone or something with vested interests in the behavior of the system under discussion (SUD).
0 kommentar(er)
