create activity diagram for electricity #699
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#699
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As part of the project documentation it will nice to have an activity diagram for electricity mockup
The diagram as png
what is left
I've reviewed the diagram and considered it thorughly.
This diagram comes across as some kind of hybrid between an activity and sequence diagram, not a true activity diagram.
A sequence diagram is meant to illustrate how the user and different components/processes interact with each other, whereas an activity diagram is meant to illustrate the dynamic flow of activities from one into the next, like a flowchart. An activity diagram shoulve have a single initial/start node and generally a single final/end node., unless branching leads to different outcomes.
As it reads now, the implication is that the customers request to "Get Energy data", directly triggers backend activity and ends there without ever actually returning the data to the customer (neither of which holds true, in reality).
There is also no clear indication of activity flow as no decision and/or merge nodes exist, nor are there any fork and/or join nodes(if applicable) to indicate concurrent activites/execution. This makes the diagram as a whole extremely ambigous.
Recommendation: Decide on whether an activity diagram is actually suitable here or if a sequence diagram may be more apropriate, and rework the diagram accordingly.
Here's a link that quickly explains what sets the two diagram types apart.
https://www.geeksforgeeks.org/system-design/difference-between-sequence-diagram-and-activity-diagram/
It may also be helpful to review Chapter 5: System Modeling course material(slides, book) from Software Engineering.
Thanks for the review.
You are referering to a sequence diagram that shows exact back and fourth interaction which is not in this case relevant
THe diagram is added to wiki. I close this issue.
I think there is a bit of miscommunication. I wasn't suggesting that it should back and forth interaction, but rather that it's not a clean activity diagram, and contains elements of both(IMHO), making it confusing to read. It's a diagram with an identity crisis. 😊
My comments and suggestions are based on the assumption that this was intended to be an activity diagram. The lack of nodes is a real problem, because it doesn't illustrate if activities are happening selectively or concurrently. I:E Is the customer choosing "one" of the three options, or do all of them happen concurrently?(likely not). This is something that an activity diagram should illustrate.
The multiple end nodes are also a problem, because they either are not reachable or alternatively are lacking a corresponding start node.
The multiple nodes indicates that it is the end meaning the application is only accessible by the customer lane only. I used the standards that were available in draw.io which used in software engineering :) .