Meeting 27.09.21

Meeting Minutes 27/09/21

Meeting agenda: Finish UML.

Discussing whether we should get rid of the login functionality. -Removing the rating system.

-Assumption: are multiple users using the same app, does the database require access from data from multiple users or is it used for just storing data?

-Do we have a global popularity count?

Is randomly generated data important?

Do we have to be able to update the database based on user input?

Choices for panel: -favourites (how many people favorited the object) -ratings (discontinued) -number of views

Do we store data for just one user or access/store data for multiple users?

Conclusion: -throw away stock rating -Takahiro’s approach-using favourites and updating to the database without login functionality -Alan’s approach-using view instead of favourites or only using data for one user.

Final decision-using views and updating the database without login functionality Option to change nickname -Still keep add to portfolio (without user)-specify when and how much you brought

Do we want to differentiate what you brought and what you are interested in?

Requirements for functionality: high level use case diagram

Abstraction of data handler class -> to avoid smells -> stockhandler

User can: -View panel (MainActivity) -Select categories (MainActivity) -Select stock from category list (ListActivity) -Side menu bar access -Access to search screen

Must be able to check for duplicate stocks in portfolio.

They can: -view a stock -search for a stock -favourite a stock -add a stock to portfilio

UML design :

Change SearchFunction relation. Based on Interface Segregation principle. (Lecture slide 3, page 30).

Before :

After