Andras/BoundlessFlowCampus2K
4
7
Fork 0
Code Issues 90 Pull requests 7 Projects Releases Packages Wiki Activity Actions

Clean up wiki with the following changes #1100

New issue
Closed
opened 2026-05-22 08:05:52 +00:00 by a24sakma · 11 comments
a24sakma commented 2026-05-22 08:05:52 +00:00
Collaborator
Copy link

Which models to update after the discussion

Entire system changes

1.Update system entire model with below changes
1.1 Change TempSensorMockup to services/api
1.2. MQTT shall go to DB and not to boundlessflowcampuse

2.Usecase diagram shall be updated with below changes

2.1 Logout shall happen after login and not parallel
2.2 Guest view shall also be updated with adding cards
2.3 New features that shall be included such as 
    2.3.1 Create account shall be included
    2.3.2 Forgot password shall be included

3.Sequence diagram from entire system shall be moved to service/api
4. Energy activity diagram from entire system shall be deleted.

Frontend changes

  1. delete sequence diagram from frontend
  2. remove webpage container structure from frontned

Middleware

  1. remove the class diagram and replace it with more abstract that shows the communication rather than how it is implemented. Such as connection to Db, connection to services

Mockup

  1. Clarify the first diagram that it says it is for a service
    2. change the name of methods to get[YOUR_METHOD_NAME] rather than getAllEnergy
  2. clarify the second diagram that it says it is for an api and it is an example
# Which models to update after the discussion ## Entire system changes 1.Update system entire model with below changes 1.1 Change TempSensorMockup to services/api 1.2. MQTT shall go to DB and not to boundlessflowcampuse 2.Usecase diagram shall be updated with below changes 2.1 Logout shall happen after login and not parallel 2.2 Guest view shall also be updated with adding cards 2.3 New features that shall be included such as 2.3.1 Create account shall be included 2.3.2 Forgot password shall be included 3.Sequence diagram from entire system shall be moved to service/api 4. Energy activity diagram from entire system shall be deleted. ## Frontend changes 1. delete sequence diagram from frontend 2. remove webpage container structure from frontned ## Middleware 1. remove the class diagram and replace it with more abstract that shows the communication rather than how it is implemented. Such as connection to Db, connection to services ## Mockup 1. Clarify the first diagram that it says it is for a service 2. change the name of methods to get[YOUR_METHOD_NAME] rather than getAllEnergy 2. clarify the second diagram that it says it is for an api and it is an example
b24idalu commented 2026-05-26 15:07:06 +00:00
Collaborator
Copy link

Links to all updated diagrams (minus new class diagram)

Links to all updated diagrams (minus new class diagram)
UseCase.zip
2 KiB
roombookingNewStructure.drawio.zip
2 KiB
TemperatureDiagram.zip
3.1 KiB
ContextDiagram.zip
1.4 KiB
b24idalu commented 2026-05-26 15:12:42 +00:00
Collaborator
Copy link

Pictures to use in wiki perchance

Classdiagram for middleware:
image

Pictures to use in wiki perchance Classdiagram for middleware: ![image](/attachments/bf643166-1572-4e49-a820-e0f520a7d921)
roombookingNewStructure.drawio.png
97 KiB
TemperatureDiagram.drawio.png
224 KiB
image.png
20 KiB
UseCase.drawio (1).png
75 KiB
ContextDiagram.drawio (1).png
44 KiB
roombookingNewStructure.drawio.png TemperatureDiagram.drawio.png UseCase.drawio (1).png ContextDiagram.drawio (1).png
a24sakma commented 2026-05-26 16:00:15 +00:00
Author
Collaborator
Copy link

@b24idalu you can put needs-review then someone will check when you are done

@b24idalu you can put needs-review then someone will check when you are done
👍 1
a23timgu commented 2026-05-27 09:37:37 +00:00
Collaborator
Copy link

The Temperature Diagram is still missing an interface file, and we might want to make it more horizontal rather than vertical for easer viewing. I made an updated version for my slides that we could use:

I also seem to recall the customer wanting the mockup service diagrams a bit more abstract (things like the method calls in TempService.cs being combined). Do we want to come to a consensus on how to update these?

The Temperature Diagram is still missing an interface file, and we might want to make it more horizontal rather than vertical for easer viewing. I made an updated version for my slides that we could use: I also seem to recall the customer wanting the mockup service diagrams a bit more abstract (things like the method calls in TempService.cs being combined). Do we want to come to a consensus on how to update these?
TemperatureDiagram_Wider.zip
326 KiB
TemperatureDiagram_wider.drawio.png
509 KiB
TemperatureDiagram_wider.drawio.png
b24idalu commented 2026-05-27 09:55:19 +00:00
Collaborator
Copy link

Stuff for middleware

Stuff for middleware
Middleware.zip
1.6 KiB
Middleware.drawio (1).png
40 KiB
Middleware.drawio (1).png
b24idalu commented 2026-05-27 10:02:27 +00:00
Collaborator
Copy link

Awaiting answer on Tim's question before asking for review

Awaiting answer on Tim's question before asking for review
a24sakma commented 2026-05-27 10:08:03 +00:00
Author
Collaborator
Copy link

@a23timgu wrote in #1100 (comment):

The Temperature Diagram is still missing an interface file, and we might want to make it more horizontal rather than vertical for easer viewing. I made an updated version for my slides that we could use:

I also seem to recall the customer wanting the mockup service diagrams a bit more abstract (things like the method calls in TempService.cs being combined). Do we want to come to a consensus on how to update these?

Agree

  • horizontal looks good to me too rather than verticle. I think ida can just take yours and put it because otherwise they look identical

Temperature

If you check the structure I put. I added change the name of methods to get[YOUR_METHOD_NAME] rather than getAllEnergy and Ida double checked with me and I told her that her ide that she put for room booking seems fine tome, I don't think she updated the temperature yet...

the background of room booking can be white too

@a23timgu wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/1100#issuecomment-14564: > The Temperature Diagram is still missing an interface file, and we might want to make it more horizontal rather than vertical for easer viewing. I made an updated version for my slides that we could use: > > I also seem to recall the customer wanting the mockup service diagrams a bit more abstract (things like the method calls in TempService.cs being combined). Do we want to come to a consensus on how to update these? # Agree - horizontal looks good to me too rather than verticle. I think ida can just take yours and put it because otherwise they look identical # Temperature If you check the structure I put. I added ` change the name of methods to get[YOUR_METHOD_NAME] rather than getAllEnergy` and Ida double checked with me and I told her that her ide that she put for room booking seems fine tome, I don't think she updated the temperature yet... the background of room booking can be white too
Screenshot from 2026-05-27 12-07-18.png
110 KiB
Screenshot from 2026-05-27 12-07-18.png
a23timgu commented 2026-05-27 10:34:32 +00:00
Collaborator
Copy link

@a24sakma wrote in #1100 (comment):

@a23timgu wrote in #1100 (comment):

The Temperature Diagram is still missing an interface file, and we might want to make it more horizontal rather than vertical for easer viewing. I made an updated version for my slides that we could use:
I also seem to recall the customer wanting the mockup service diagrams a bit more abstract (things like the method calls in TempService.cs being combined). Do we want to come to a consensus on how to update these?

Agree

  • horizontal looks good to me too rather than verticle. I think ida can just take yours and put it because otherwise they look identical

Temperature

If you check the structure I put. I added change the name of methods to get[YOUR_METHOD_NAME] rather than getAllEnergy and Ida double checked with me and I told her that her ide that she put for room booking seems fine tome, I don't think she updated the temperature yet...

the background of room booking can be white too

So if I'm understanding things right, we use example mockup diagrams as guide(s) for new services.
The example will have the more abstract get[YOUR_METHOD_NAME] instead of explicitly naming the method calls like we do in for example the tempService diagram.

Will we still use the existing diagrams that explicitly describe each service that were created in for example #591 for anything?

@a24sakma wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/1100#issuecomment-14584: > @a23timgu wrote in #1100 (comment): > > > The Temperature Diagram is still missing an interface file, and we might want to make it more horizontal rather than vertical for easer viewing. I made an updated version for my slides that we could use: > > I also seem to recall the customer wanting the mockup service diagrams a bit more abstract (things like the method calls in TempService.cs being combined). Do we want to come to a consensus on how to update these? > > # [](#agree)Agree > * horizontal looks good to me too rather than verticle. I think ida can just take yours and put it because otherwise they look identical > > # [](#temperature)Temperature > If you check the structure I put. I added ` change the name of methods to get[YOUR_METHOD_NAME] rather than getAllEnergy` and Ida double checked with me and I told her that her ide that she put for room booking seems fine tome, I don't think she updated the temperature yet... > > the background of room booking can be white too So if I'm understanding things right, we use **example mockup diagrams** as guide(s) for new services. The example will have the more abstract `get[YOUR_METHOD_NAME]` instead of explicitly naming the method calls like we do in for example the tempService diagram. Will we still use the existing diagrams that explicitly describe each service that were created in for example [#591](https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/591) for anything?
b24idalu commented 2026-05-27 10:37:49 +00:00
Collaborator
Copy link

Temperature & RoomBooking fix

Temperature & RoomBooking fix
TemperatureDiagram_wider.drawio.zip
102 KiB
TemperatureDiagram_wider.drawio.png
161 KiB
roombookingNewStructure.drawio (1).drawio (1).png
100 KiB
TemperatureDiagram_wider.drawio.png roombookingNewStructure.drawio (1).drawio (1).png
a24sakma commented 2026-05-27 10:40:05 +00:00
Author
Collaborator
Copy link

@a23timgu wrote in #1100 (comment):

@a24sakma wrote in #1100 (comment):

@a23timgu wrote in #1100 (comment):

The Temperature Diagram is still missing an interface file, and we might want to make it more horizontal rather than vertical for easer viewing. I made an updated version for my slides that we could use:
I also seem to recall the customer wanting the mockup service diagrams a bit more abstract (things like the method calls in TempService.cs being combined). Do we want to come to a consensus on how to update these?

Agree

  • horizontal looks good to me too rather than verticle. I think ida can just take yours and put it because otherwise they look identical

Temperature

If you check the structure I put. I added change the name of methods to get[YOUR_METHOD_NAME] rather than getAllEnergy and Ida double checked with me and I told her that her ide that she put for room booking seems fine tome, I don't think she updated the temperature yet...
the background of room booking can be white too

So if I'm understanding things right, we use example mockup diagrams as guide(s) for new services. The example will have the more abstract get[YOUR_METHOD_NAME] instead of explicitly naming the method calls like we do in for example the tempService diagram.

Will we still use the existing diagrams that explicitly describe each service that were created in for example #591 for anything?

I think we are on good foot with having one example from service which is tempservice and one example from api which is room booking. It is good enough as those services have same structure which temp service represents and and room booking represents how api looks like

@a23timgu wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/1100#issuecomment-14593: > @a24sakma wrote in #1100 (comment): > > > @a23timgu wrote in #1100 (comment): > > > The Temperature Diagram is still missing an interface file, and we might want to make it more horizontal rather than vertical for easer viewing. I made an updated version for my slides that we could use: > > > I also seem to recall the customer wanting the mockup service diagrams a bit more abstract (things like the method calls in TempService.cs being combined). Do we want to come to a consensus on how to update these? > > > > > > # [](#agree-agree)Agree > > > > * horizontal looks good to me too rather than verticle. I think ida can just take yours and put it because otherwise they look identical > > > > # [](#temperature-temperature)Temperature > > If you check the structure I put. I added ` change the name of methods to get[YOUR_METHOD_NAME] rather than getAllEnergy` and Ida double checked with me and I told her that her ide that she put for room booking seems fine tome, I don't think she updated the temperature yet... > > the background of room booking can be white too > > So if I'm understanding things right, we use **example mockup diagrams** as guide(s) for new services. The example will have the more abstract `get[YOUR_METHOD_NAME]` instead of explicitly naming the method calls like we do in for example the tempService diagram. > > Will we still use the existing diagrams that explicitly describe each service that were created in for example [#591](https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/591) for anything? I think we are on good foot with having one example from service which is tempservice and one example from api which is room booking. It is good enough as those services have same structure which temp service represents and and room booking represents how api looks like
👍 1
a24sakma commented 2026-05-28 07:20:09 +00:00
Author
Collaborator
Copy link

@b24idalu Great job all the points are completed!
The is completed. I close this issue

@b24idalu Great job all the points are completed! The is completed. I close this issue
a24sakma 2026-05-28 07:20:09 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
#1236-edit-mode-txt
#1229-generic-themed-buttons
Add-an-option-to-set-no-image-to-image-view-1227
#1242-prog-bar-colors-fix
#1239-Remove-Vertical-Scroll
Image-view-error-1230
Make-the-card-title-and-header-of-card-uniform-1233
both_teams_week_8
team_2_week_7
team_1_week_7
temp_branch_week_7
team_2_week_6
team_1_week_6
team_2_week_5
team_1_week_5
temp_branch_week_5
team_2_week_4
team_1_week_4
week_4_temp_branch
temp-branch-week-3
team_2_week_3
team_1_week_3
team_2_week_2
team_1_week_2
temp-week-2-merge-branch
team_2_week_1
team_1_week_1
No results found.
Labels
Clear labels   
_CRITICAL_

Only use this label for critical tasks that are project-scope,and must be addressed ASAP.

  
API

   
app

   
backEnd

   
Blocked, waiting for further changes

   
bug

Something is not working

  
cleanup

Issues to cleanup the codebase (restructure folders, remove deprecated or smelly code)

  
close

Issue to close

  
design

   
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
feature request

   
frontEnd

   
help wanted

Need some help

  
invalid

Something is wrong

  
low priority

   
needs input

Issue needs input from product owner or customer

  
needs review

issue is in need of review

  
project documentation

   
question

More information is needed

  
research

   
reviewed

This Issue has been reviewed

  
script

   
security

use this for security-related issues

  
SQL

  
style

   
testing

   
topLevel

Reserved for top-level, project-wide issues.

  
wontfix

This won't be fixed

No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
b24idalu
a24sakma
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#1100
No description provided.