Skip to content
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

Added runtime scenarios to part 06 of the documentation #37

Merged
merged 1 commit into from
Feb 18, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Added runtime scenarios to part 06 of the .
UO278249 committed Feb 17, 2023
commit cb9b3866c9d76973e14eb877c6b1efdcb5a7afb6
36 changes: 17 additions & 19 deletions docs/06_runtime_view.adoc
Original file line number Diff line number Diff line change
@@ -30,28 +30,26 @@ There are many notations for describing scenarios, e.g.

****

=== <Runtime Scenario 1>
=== User registration
* _Alice enters the system for the first time and registers her personal data to create an account and start ussing the webapp.
* _The user will be able to fill a form with their data that is saved on their private POD.


* _<insert runtime diagram or textual description of the scenario>_
* _<insert description of the notable aspects of the interactions between the
building block instances depicted in this diagram.>_
=== User Login
* _Bob already registered on the system and wants to log in with their user and password to acess the webapp.
* _The user will be able to fill a form with their user and password that will be sent to the server to be authenticated and allow or deny access.

It is possible to use a sequence diagram:

[plantuml,"Sequence diagram",png]
----
actor Alice
actor Bob
database Pod as "Bob's Pod"
Alice -> Bob: Authentication Request
Bob --> Alice: Authentication Response
Alice --> Pod: Store route
Alice -> Bob: Another authentication Request
Alice <-- Bob: another authentication Response
----
=== <Runtime Scenario 2>
=== Adding a Location
* _Alice wants to add the location restaurant to the webapp and see it on the map.
* _The user will be able to select a location category and the coordinates for the location to be placed and seen on their map.

=== ...

=== <Runtime Scenario n>
=== Reviewing information about a place
* _Bob wants to select a friend's added location and see the pictures they added to it.
* _Locations made public or shared with the user will be able to be accesed by the user to review aditional information that the creator added to the place.


=== Changing privacy settings
* _Alice doesn't want their friends seeing the locations she added to the map so she acesses the settings of the webapp to disable sharing them.
* _The different settings about what information on the places and the user is accesible by their friends will be able to be changed, giving different options for each parameter.