-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Case Diagram for both Registered and Unregistered User #29
Comments
Its good. We can add more ideas later on. |
There should be an option to purchase and checkout for the registered users. |
sure @jp1433 |
User on one side should be our system which is communicating with the user. Registered and unregistered user should be on one side |
Even i think system should be included in diagram |
Navjot is correct. A user role can be a non-human user. Instead of
calling your system "System", a friendlier name might make writing stories
less of a chore (e.g., Apple calls their voice system "Siri").
Best Regards,
Hao C. Lac, Ph.D. (Computational Science)
…On Tue, Feb 21, 2017 at 7:21 PM, Navjot Kaur ***@***.***> wrote:
Even i think system should be included in diagram
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADr-JvS67B0AJNBcx0gvG_JhljMGk9LWks5re39wgaJpZM4MFt6M>
.
|
GameVault can be one name for our system |
I would avoid names that convey inanimateness since it would be no
different from "System".
Best Regards,
Hao C. Lac, Ph.D. (Computational Science)
…On Tue, Feb 21, 2017 at 7:57 PM, Avjot Kaur ***@***.***> wrote:
GameVault can be one name for our system
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADr-Jr8MPWtvenhDwHoxO0WwDM5CAi-0ks5re4f8gaJpZM4MFt6M>
.
|
Is "Gamers" ok? |
We'll use keyword "System" for the use cases. |
I have created this Use Case Diagram for User. Please review it and tell me if you have any more ideas to add to this use case.
The text was updated successfully, but these errors were encountered: