search

nus-cs2103-AY2425S1 / pe-dev-response

0 stars 0 forks source link

Multiple Instances of the applicaiton opened on the same platform is not updated #628

Open nus-se-script opened 1 day ago

nus-se-script commented 1 day ago

ISSUE

In EventfulNUS, when multiple instances of the application are open, changes made in one window do not reflect in the other. This can lead to data inconsistency, particularly for users who manage a high volume of event data across multiple faculties, roles, or participants[which is mentioned in the UG and DG]. A user might open multiple instances of EventfulNUS, intending to work on different aspects of the event data in parallel (e.g., managing participants in one window while scheduling events in another). However, any changes made in one instance, such as adding a new participant or updating event details, remain isolated to that specific window. The manager for this should be very busy also, most people working/ study have multiple tabs like 100 tabs open, not to mention about people working to handle the IFG, a cross-faculty University level game This could lead the user to mistakenly assume that their updates were applied globally across all instances.

Further, there was mentioning in the UG that the data is saved automatically, which could be confusing to users.

image.png

Demostration
video:https://raw.githubusercontent.com/nus-cs2103-AY2425S1/pe/master/files/ae9079c3-7d51-4fac-a962-7bd253a2e010.mp4

Reason for severity

This issue impacts the reliability of the application, particularly in event management scenarios where accuracy and synchronization are essential, such as coordinating participants, updating event details, or assigning roles. For busy event organisers, managing a large volume of data across faculties or roles, the risk of data discrepancies becomes particularly significant.

[original: nus-cs2103-AY2425S1/pe-interim#888] [original labels: type.FeatureFlaw severity.High]

leowolf275 commented 17 hours ago

Team's Response

Hello, thank you for the bug report! While we know that users may want to use multiple instances of the app and edit the lists in parallel, we see this feature as "Out Of Scope" for the current version of our project. For now, we believe it's suitable for our users to stick to one application instance at a time.

In addition, we also believe that this violates some of the project constraints. For example, we are not allowed to use a DBMS (Constraint-No-DBMS) (Database Management System like MySQL) to store data. However, to have data changes flow consistently among multiple instances of the app, one would require a DBMS. The need of a backend also violates the Constraint-No-Remote-Server.

Duplicate status (if any):

--