For UML, a use case is a behavior with user interactions and observable results of value for someone. For the Use-Case community it's user goals. Use-cases mean different things to different persons. Or it may have lots of nuances and be discussed in great detail in both requirements and design documentation. Depending on the system and level of documentation, it may not be interesting enough to have any sufficient discussion in design documentation. The specific representation of any use case depends on how you are capturing or documenting your use cases. However, depending on the complexity of your system, you may opt to treat the value-adding or goal-oriented use cases differently than use cases that are only included as parts of other use cases. In most cases, the person authenticates into a system as a step in a larger process.Īs long as your use case meets the first definition, you can represent the use case on a UML Use Case diagram or in various textual/tabular templates. That is, rarely does a person log in to a system and then do nothing else. However, some definitions for a use case add the need for value or achieving an objective.Īlthough logging in (authentication) is a set of system behaviors that produces a result for an actor, it doesn't often meet the second definition of achieving an objective. At the most basic level, a use case is a set of system behaviors that products a result for one or more actors. First, you need to specifically define what a "use case" is.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |