Lessons_learned_RefikaKalyoncu

1.1 What went well

• We didn't have any connection problems between our teammates which sped up the process
• We had a good looking frontend design not just html but which includes java script code and .css.
• The problems were solved quicker than we expect
• We followed the plan, we didnt fell behind except some minor works

1.2 What went wrong

• I didnt start the report at the beginning but at the end so it was so hard to remember and put together everything I done in only two days.
• Burakcan was much more experienced about frontend from most of our teammates, so to match his front design we had to make so much effort which was time consuming a lot
• The folder names and the structure changed a few times which created unmatched files during pushing and pull requests.
• We merge most of the code in the end so merging this much of code synchronously also created a difficulty.

1.3 Actions to improve the process

• Individual reports should be written earlier
• The lead person in frontend should consider others' knowledge
• Planing file structure and names at the beginning will help a lot as well.

1.4 What I've learned in this class

• What is git
• How to prepare the requirements of a project
• Analysing existing softwares according to our puposes
• What is a use case diagram, how it will be prepared.
• What is a class diagram, how it will be prepared.
• What is a sequence diagram, how it will be prepared.
• Preparing scenarios for a software
• How to decide as a group in any kind of situation
• Documenting myself and my effort
• Dockerizing and deploying an application
• How to build a frontend
• What is get and post requests
• What is an API
• How to use github
• How to merge using vscode
• How to run an application in local