iam going to design a system that has a login facility. After login the logged user can do several things so is it needs to include login usecase by that several usecases.
相关问题
- System sequence diagram - Can system request input
- Does Visual Studio 2010 Professional support UML m
- Can a [GoF]-ConcreteSubject override the notify me
- How to represent enumeration classes with methods
- How to specify “one at a time” in UML?
相关文章
- Code Iris plugin on Android Studio
- Designing a sequence diagram for an auction system
- Game engine design choice [closed]
- state transition with different guard condition
- Resources for learning how to better read code
- What is a use-case? How to identify a use-case? [c
- Relationships in a UML class diagram
- How do you convert a document in UML 1.3 - XMI 1.1
In most cases, it will only clutter up your diagrams. Login is neither complex nor does it give you much added value as a use case. In your textual document that includes the use cases with description, include as a prerequisite a list of features that require a successful login. Easier to track and to test.