Difference between revisions of "Usage Domain Analysis"
From EUDP
(Added Process text) |
|||
Line 9: | Line 9: | ||
'''Process''' | '''Process''' | ||
− | The analysis of the usage domain is about how somebody, a person or another system, interacts with the system-to-be. The two suggested activities | + | The analysis of the usage domain is about how somebody, a person or another system, interacts with the system-to-be. The two suggested activities '''Use Case Candidates''' and '''Actor Candidates''' may be parallel processes. In some cases, there are obvious use cases; but in other cases, there may not be an immediate obvious candidate. In such cases, an analysis of the possible actors may reveal use cases. The actor analysis may be performed in parallel with or after the [[Interface Analysis]], especially the interface with other systems. |
− | So jumping back and forth between several activities should not deter the developer | + | So jumping back and forth between several activities should not deter the developer from searching for all possible candidates, be it actors or use cases. |
Revision as of 12:07, 9 October 2013
Process
The analysis of the usage domain is about how somebody, a person or another system, interacts with the system-to-be. The two suggested activities Use Case Candidates and Actor Candidates may be parallel processes. In some cases, there are obvious use cases; but in other cases, there may not be an immediate obvious candidate. In such cases, an analysis of the possible actors may reveal use cases. The actor analysis may be performed in parallel with or after the Interface Analysis, especially the interface with other systems.
So jumping back and forth between several activities should not deter the developer from searching for all possible candidates, be it actors or use cases.