![]() The intention is to reduce one of the risks associated with short-term memory, namely, forgetting what is not immediately visible (‘out of sight, out of mind’). ![]() Ideally, all of the steps would be visible all at once (often a page or less). The basic flow within a process or use case can usually be described in a relatively small number of steps, often fewer than twenty or thirty, possibly using something like ‘structured English’. Each planned response may be modelled using DFD notation or as a single use case using use case diagram notation. ![]() The level of detail of each response is at the level of ‘primary use cases’. This approach helps the analyst to decompose the system into ‘mentally bite-sized’ mini-systems using events that require a planned response. Single use case in a fictitious hotel using use case diagram notation. Single process in a fictitious hotel using data flow diagram notation. "Event partitioning is an easy-to-apply systems analysis technique that helps the analyst organize requirements for large systems into a collection of smaller, simpler, minimally-connected, easier-to-understand ‘mini systems’ / use cases. This file is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. This example was redesigned from the Wikipedia file: LastResortHotel BookRoom Process.png.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |