1.1.1.1 Sign up

• 1.1.1.1.1 Users shall sign up to enroll the courses on the online learning platform by specifying their username, password and an e-mail in the sign-up process.
• 1.1.1.1.2 Guest user’s username should not be taken by another account beforehand.
• 1.1.1.1.2 E-mail, password and username in the Android version can be at most 25 letters.
• 1.1.1.1.3 When guest user signs up, it automatically signs-in with the information given at sign-up step.

1.1.1.2 Username, password

• 1.1.1.2.1 A user shall select a unique username and a password containing at least 8 letters.
• 1.1.1.2.2 A user shall be able to change her password.

1.1.1.3 E-mail verification

• 1.1.1.3.1 A user shall be notified an account creation when they sign up to the system.

1.1.1.4 Sign in

• 1.1.1.4.1 A user shall enter her password correctly. If she fails to enter her password correctly six times, she shall be blocked from further retrying.
• 1.1.1.4.2 A user shall recover her password if she is blocked from further retrying, for typing wrong password six times.

1.1.1.5 Password recovery

• 1.1.1.5.1 A user shall be given a random password when they click on recover password button and type in their email address with username.

1.1.2.1 Profile Specifications

• 1.1.2.1.1 Every user shall have a profile page.
• 1.1.2.1.2 A user shall be able to upload a profile picture, specify their interests and location.
• 1.1.2.1.3 A user shall be able to follow other users and be followed back.
• 1.1.2.1.4 A user shall be able to see her followers.
• 1.1.2.1.5 A user shall be able to see her courses.

1.1.2.2 Privacy

• 1.1.2.2.1 Every user shall be able to hide her profile from the other user's accesses. If she hides herself, she shall be no longer seen by other users by any means.
• 1.1.2.2.2 Every user shall be able to partially restrict access to her profile from the other user's accesses. That is, hiding her courses, her followers, her badges etc. from other user's access.

• 1.1.3.1 Guest user shall be able to use the search feature and look for courses.
• 1.1.3.2 Guest user shall be able to see title and brief contents of a course.
• 1.1.3.3 Guest user shall sign up and create an account to enroll a course and see the full content.
• 1.1.3.4 Guest users should be able to sign-up
• 1.1.3.5 Guest users should be able to sign-in

• 1.1.4.1 A user who enrolls a course shall be considered as a student.
• 1.1.4.2 Student shall be able to see the full course material.
• 1.1.4.3 Student shall be able to monitor his/her progress in the course. Progress should indicate the percentage of the viewed content in the course.
• 1.1.4.4 Students should be able to obtain achievements by progressing in the courses.
• 1.1.4.5 Student shall be able to contribute to the course via participating polls created by lecturers.
• 1.1.4.6 Student shall be able to take notes related to the learning material.
• 1.1.4.7 Student should be able to evaluate the lecturer. Evaluation shall be in two ways: from a rating in the range of 1-5, like or dislike.

• 1.1.5.1 A user who creates a course shall be considered as a lecturer.
• 1.1.5.2 Lecturer shall be able to upload video, image, or text material to the course page.
• 1.1.5.3 Lecturer shall be able to organize the course page.
• 1.1.5.4 Lecturer shall be able to create polls for the students. Polls shall be in 3 types: anonymous mode, multiple answers and quiz mode.
• 1.1.5.5 Lecturer shall have a reputation based on the feedback they have obtained from students

• 1.1.6.1 Users shall be able to create events by providing the information on whether the meeting is online/in-person, whether there's going to be an entrance fee, amount of the entrance fee, date, time, and location.
• 1.1.6.2 Event holders shall be able to edit the related information fields (See 1.1.6.1) of their event.
• 1.1.6.3 Event holders shall be able to cancel or postpone their events.

• 1.1.7.1 Users shall type on the search bar, press enter or click on the search button in order to search for a tag, course, or profile.
• 1.1.7.2 Users shall be able to inspect the summary of the course content without enrolling in them.

• 1.2.1.1 A user shall be able to search any topic with the search box in top of the page.
• 1.2.1.2 Results of the search will be in order based on section 1.2.3 in Requirements.
• 1.2.1.3 Searching shall be based on semantic searching.
• 1.2.1.4 Courses shall be searched in search bar of search page.
• 1.2.1.5 Users shall be able to be searched.

1.2.2.1 Profile Page

• 1.2.2.1.1 Profile page shall include profile picture, username and personal information considering user's privacy settings.
• 1.2.2.1.2 System shall be able to allow users to edit their profile picture and personal information on their profile page.
• 1.2.2.1.3 There shall be a follow button on every user's profile page, which users use to follow other people.
• 1.2.2.1.4 There shall be a chang-password button on every user's profile page, which users use to change their password.

1.2.2.2 Main Page

• 1.2.2.2.1 Main page shall include most popular courses for the guest users.

1.2.2.3 My Courses Page

• 1.2.2.3.1 My courses page shall show the courses that a user is enrolled or that a user created.

1.2.2.4 Course Pages

• 1.2.2.4.1 A course page shall include the course overview if a user is not enrolled yet, or the course content fully if a user is enrolled.
• 1.2.2.4.2 A course page shall be able to be fully customizable by a teacher.
• 1.2.2.4.3 A course page shall include a note-taking part.

• 1.2.3.1 Users will see recomended courses in the homepage.
• 1.2.3.2 The recommeded courses will be decided based on their interests that they chose at the beginning, courses to which users enrolled, and what they searched.

• 1.2.4.1 Users should have a page to take notes while taking the course.
• 1.2.4.2 Users should have access to different colors and fonts while taking notes.
• 1.2.4.3 User notes should stay unchanged when user loggs off.

• 1.2.5.1 System shall support creating annotation on the screen.
• 1.2.5.2 System shall support to add text or images to the annotation.
• 1.2.5.3 System shall create hyperlink in the annotation if given text is a link.

1.2.6.1 Messaging

• 1.2.6.1.1. System should support direct messaging between the registered users.
• 1.2.6.1.2 System should mark up all messages with corresponding timestamp just right corner of the username.
• 1.2.6.1.3 System should put the username of the sender just above the message.
• 1.2.6.1.4 System should hide messages happening between two users from the others.
• 1.2.6.1.5 System should save the messages in the database for forever.
• 1.2.6.1.6 System should support sharing of resource like image.
• 1.2.6.1.7 System should support text messages for discussing ideas.
• 1.2.6.1.8 System should support asking and answering questions.
• 1.2.6.1.9 System should support sharing of notes with other users.

1.2.6.2 Forum

• 1.2.6.2.1 System must have communication channels support.
• 1.2.6.2.2 System should support leaving comment for the lecturer.
• 1.2.6.2.3 System should support leaving comment for the course.
• 1.2.6.2.4 System should support sharing of resource like image.
• 1.2.6.2.5 System should make everyone to be able to write into forum page for discussing ideas.
• 1.2.6.2.6 System should support asking and answering questions on the forum.
• 1.2.6.2.7 System should make lecturers be able to create pools in three modes: anonymous mode, multiple answers, and quiz mode.

• 2.1.1 The platform must comply with all rules regarding KVKK and GDPR.
• 2.1.2 User should register only accepting the privacy policy based on KVKK and GDPR.

• 2.2.1 Registering email address should be valid and unique because of using that email address to activate account, change password.
• 2.2.2 Passwords must be at least 8 characters long and includes at least one uppercase letter, one lowercase letter, one number, one special character.
• 2.2.3 The system shall encrypt passwords with SHA-256 algorithm using a randomly generated salt. Passwords hashes and the respective salt shall be stored in the database.
• 2.2.4 Users cannot be able to perform actions without priveleges not defined for them. For example users should not access to data of other users.
• 2.2.5 New access tokens should be generated for every user and api endpoints should be protected with access tokens.
• 2.2.6 All inputs should be validated in order to mitigate attacks like SQL injection.
• 2.2.7 Password fields for login and logout user interfaces shoud be hidden.

• 2.3.1 The platform should be accessed via Android application and web interface which should be responsive and support Chrome, Firefox, Safari, Edge and Opera.
• 2.3.2 The platform language should be English and support UTF-8 character encoding.

• 2.4.1 At least 1.000 registered users with their actions should be satisfied simultaneosly.
• 2.4.2 At least 15.000 guest users should be able to inspect the system.
• 2.4.3 A user should have a response in at most 1.5 seconds excluding the delay based on the machine that the user uses.
• 2.4.4 The system should back up every data related the project in every 1 hour.
• 2.4.5 Updates on the system are done at the time that usage of the system has least users. This time will be determined 2 months after the first start.

• 2.5.1 The project should satisy the rules of W3C Standards.
• 2.5.2 The semantic should be based on wikidata.org.

Member: Osman Fehmi Albayrak, Group1, Android, Online Learning Project (OLP), Personal Page

Responsibilities:

Main Contributions:

Pull Requests:

Unit Tests: I haven't implemented any unit tests. Since UI/UX depends on human interaction and endpoints are already tested by backend team, we did manual testing for possible cases.

Additional Information:

Member: Mustafa Atay, Group1, Backend (milestone 1 and 2), Frontend (milestone 3), Online Learning Project (OLP) - Budemi, Personal Page

Responsibilities:

Main Contributions:

Pull Requests:

Unit Tests:

Codes are here: #633

• I prepared unit tests for learning space
• I prepared unit tests for content
• I prepared unit tests for content list
• I prepared unit tests for content enroll

Additional Information:

Member: Harun ERKURT, Group1, Android, Online Learning Project (OLP), Personal Page

Responsibilities:

Unit Tests: I haven't implemented any unit tests.

Additional Information:

Member: Kadir Kalkan, Group1, Backend, Online Learning Project (OLP) - Budemi, Personal Page

Member:

Member: Kamil Korkut, Group 1, Front-end Team, Online Learning Project (OLP), Personal Page

Milestone 1

• I was responsible for implementing form validations for sign-in and sign-up pages.
• I was responsible for designing and implementing the forgot password page.
• I was responsible for reviewing issues.

Milestone 2

• I was responsible for implementing the dropdown menu for adding content on the learning space page, and connecting it to the add content api.
• I was responsible for implementing the join button on the learning space page, and connecting it to the enroll api.
• I was responsible for reviewing issues of the team members.

Final Milestone

• I was responsible for creating the learning space page.
• I was responsible for connecting learning space page to the learning space api.
• I was responsible for displaying learning space name on the learning space page.
• I was responsible for displaying learning space create date on the learning space page.
• I was responsible for displaying learning space tag on the learning space page.
• I was responsible for displaying learning space description on the learning space page.
• I was responsible for displaying learning space members as a list on the learning space page.
• I was responsible for adding an add resource button on the learning space page.
• I was responsible for creating the add resource page.
• I was responsible for implementing a markdown editor in the resource page.
• I was responsible for connecting add resource page to the add resource api.
• I was responsible for adding a join button on the learning space page.
• I was responsible for connecting join button to the join learning space api.
• I was responsible for adding a favorite button on the learning space page.
• I was responsible for connecting favorite button to the favorite learning space api.
• I was responsible for adding an unfavorite button on the learning space page.
• I was responsible for connecting unfavorite button to the unfavorite learning space api.
• I was responsible for implementing a logic to display the favorite button if current user is not favorited the learning space, and to display the unfavorite button if current user is favorited the learning space.
• I was responsible for reviewing my friends’ issues.

Milestone 1

• I have implemented form validations to sing-in and sign-up pages.
• I have designed and implemented the forgot password page.
• I have reviewed some issues.

Milestone 2

• I have implemented the add content dropdown menu on the learning space page.
• I have implemented the join button and its functionality.
• I have attended some of the front-end team meetings.
• I have reviewed some of the issues of the team members.

Final Milestone

• I have implemented the learning space page.
• I have implemented connecting learning space page to the learning space api.
• I have implemented displaying learning space name on the learning space page.
• I have implemented displaying learning space create date on the learning space page.
• I have implemented displaying learning space tag on the learning space page.
• I have implemented displaying learning space description on the learning space page.
• I have implemented displaying learning space members as a list on the learning space page.
• I have implemented an add resource button on the learning space page.
• I have implemented the add resource page.
• I have implemented a markdown editor in the resource page.
• I have implemented connecting add resource page to the add resource api.
• I have implemented a join button on the learning space page.
• I have implemented connecting join button to the join learning space api.
• I have implemented a favorite button on the learning space page.
• I have implemented connecting favorite button to the favorite learning space api.
• I have implemented an unfavorite button on the learning space page.
• I have implemented connecting unfavorite button to the unfavorite learning space api.
• I have implemented a logic to display the favorite button if current user is not favorited the learning space, and to display the unfavorite button if current user is favorited the learning space.
• I have reviewed my friends’ issues.

Milestone 1

• Frontend: Form Validation: #396
• Frontend: Creating Forgot Password Page: #399

Milestone 2

• Learning Space Detail Page Design #530
• Frontend - Add content and Join #563
• Frontend: Connecting the join button to the enroll api #611
• Frontend: Add Content Dropdown Popup #631

Final Milestone

• Missing tasks of milestone 2 #683
• Frontend: Add content functionality #687
• Frontend: Changing "content" to "resource" on the learning space page #723
• Frontend: Displaying Members on the Learning Space Page #724
• Frontend: Change Add Resource Functionality #725
• Frontend: Add Markdown Resource #751
• Frontend: Add Favorite and Unfavorite Functionalities #792
• Frontend: Display all LS info #831

Milestone 1

• Updating Personal Wiki Page #310
• Kamil Korkut - Individual Contribution Report #461

Milestone 2

• Editing my part of the individual report #662
• Reviewed: #530, PR#327

Final Milestone

• Meeting with Kamil to Shape Our Roadmap #682

Milestone 1

• React authentication page PR #395

Milestone 2

• adding addcontent dropdown and join button PR #612

Final Milestone

• learning space page is added PR #684
• add content functionality is added PR #686
• resource functionality and displaying members on learning space improved PR #726
• delete .next folder and update next.config PR #833
• add description display PR #914

We have not written any unit test.

Member: Ömer Özdemir, Group 1, Android Team, Online Learning Project (OLP), Personal Page

Responsibilities:

• I was responsible for attending to the all Problem Sessions, Group Meetings, Android Meetings.
• I was responsible for introducing template design for Android app.
• I was responsible for introducing new UI for Android.
• I was responsible for improving UX for Android.
• I was responsible for determining objectives for Milestone3 for Android.
• I was responsible for distribution of the work to be done each member (Who should do Learning Space Stage1,2,3 etc.).
• I was responsible for making our design consistent with front-end.
• I was responsible for reviewing my team members' issues and pull-requests.
• I was responsible for reviewing my team member's work.
• I was responsible for hands-on testing on Android.
• I was responsible for arranging meetings with my team members in Android.
• I was responsible for detecting and fixing bugs on Android
• I was responsible for filling Android related things in Milestone 3
• I was responsible for sync of Android with back-end and front-end
• I was responsible for studying and showing Android in Milestone 3 Customer Demo
• I was responsible for everything related to Learning Space 2 (The menu page)
  • I was responsible for finding icon, text, clicking on functionality for resources in Learning Space 2.
    • I was responsible for listing all resources in Learning Space 2.
    • I was responsible for showing the owner of the resource in Learning Space 2.
    • I was responsible for showing the number of up votes of the resource in Learning Space 2.
  • I was responsible for finding icon, text, clicking on functionality for enroll in Learning Space 2.
  • I was responsible for finding icon, text, clicking on functionality for leave in Learning Space 2.
  • I was responsible for finding icon, text, clicking on functionality for members in Learning Space 2.
    • I was responsible for listing all members of Learning Space 2.
  • I was responsible for finding icon, text, clicking on functionality for add favorite in Learning Space 2.
  • I was responsible for finding icon, text, clicking on functionality for remove favorite in Learning Space 2.
  • I was responsible for finding icon, text, clicking on functionality for add resource in Learning Space 2.
    • I was responsible for design and implementation of add resource page.
  • I was responsible for changing the design when user enrolls in Learning Space 2.
  • I was responsible for changing the design when user leaves Learning Space 2.
• I was responsible for everything related to Learning Space 3 (The resource page)
  • I was reponsible for supporting markdown text in resource page.
  • I was responsible for listing the resource in Learning Space Stage 3.
  • I was responsible for design of bottom sheet layout in Learning Space 3.
  • I was responsible for implementation of bottom sheet layout in Learning Space 3.
  • I was responsible for showing the owner of content at the bottom in Learning Space 3.
  • I was responsible for showing say something at discussion part in Learning Space 3.
  • I was responsible for finding icon,text,clicking on functionality of read in Learning Space 3.
  • I was responsible for showing the number of up votes in bottom sheet layout in Learning Space 3.
  • I was responsible for finding icon, text, clicking on functionality of notes in Learning Space 3.
  • I was responsible for finding icon,text, clicking on functionality of discussion in Learning Space 3.
  • I was responsible for implementation of posting discussion in Learning Space 3.
  • I was responsible for listing all discussion in Learning Space Stage 3.
  • I was responsible for finding icon,text, clicking on functionality of edit for note in Learning Space 3.
  • I was responsible for finding icon,text, clicking on functionality of edit for resource in Learning Space 3.
  • I was responsible for finding icon,text,clicking on functionality for up vote in Learning Space 3.
  • I was responsible for finding icon,text,clicking on functionality for down vote in Learning Space 3.
• I was responsible for everything related to profile page except uploading image
  • I was responsible for introducing new UI for profile page.
  • I was responsible for showing the profile photo of the user.
  • I was responsible for showing the user id of the user.
  • I was responsible for showing the enrolled courses of the user.
  • I was responsible for the clicking on functionality of enrolled courses of the user
  • I was responsible for showing the e-mail of the user
  • I was responsible for showing about me of the user
  • I was responsible for icon,text,clicking on functionality of change password and edit profile
• I was responsible for introducing Marquee Text in home page.
• I was responsible for fixing typos in Android.
• I was responsible for everything related to sign-in page
• I was responsible for everything related to sign-up page
• I introduced model-service-view pattern into our android repository.
• I introduced retrofit library into our android repository.
• I introduced new button design into our android repository.
• I introduced new font styles into our android repository.
• I changed all fonts in Android app to new ones mentioned just above
• I was responsible for adding mock resource for the presentation
• I was responsible for creating mock learning spaces for the presentation

Main Contributions:

• I have implemented sign-up page for Android.
• I introduced retrofit library for our use from now on for api requests.
• I introduced nice front-end designs to the team for our own use from now on.
• I introduced model-service-view pattern into our android repository.
• I participated in writing the android mockup scenario for milestone 1.
• I participated into the all group meetings both Android and overall team.
• I reviewed my team member's work.
• I solved my team member's problems that they encounter in Android Studio.
• I introduced Android label to our repository.

• I have implemented Learning Space Stage 2,3, listing all learning spaces and reset password api infrastructure for Android.
• Me and Osman figured out how to send post request with header.
• I participated into the all group meetings both Android and overall team.
• I reviewed my team member's work.
• I solved my team member's problems that they encounter in Android Studio.

• Everything related to UI/UX improvement of Android app
• Everything related to Learning Space 2 (The menu page)
• Everything related to Learning Space 3 (The resource page)
• Everything related to sign-in page
• Everything related to sign-up page
• Everything related to profile page except uploading image
• Everything related to management of Android app
• Reviewing Team member's work and giving feedback.
• Reviewing Team member's work and fixing bugs their bugs.
• Studying and Presenting Android app in Customer Demos.

• Final design of sign-up page: https://github.com/bounswe/bounswe2022group1/issues/360
• Android Sign-up page - Message disappears after 2000ms: https://github.com/bounswe/bounswe2022group1/issues/388
• Android Sign-up page back-end connection: https://github.com/bounswe/bounswe2022group1/issues/384
• Sign-in and Sign-up pages for Android Application: https://github.com/bounswe/bounswe2022group1/issues/333

• Android API Infrastructure for back-end APIs: https://github.com/bounswe/bounswe2022group1/issues/623
• Learning Space Stage 3 functionality is fully implemented. : https://github.com/bounswe/bounswe2022group1/issues/622
• Learning Space Stage 2 Functionality is implemented.: https://github.com/bounswe/bounswe2022group1/issues/621
• Add Content design is implemented.: https://github.com/bounswe/bounswe2022group1/issues/619
• Add Content functionality is implemented: https://github.com/bounswe/bounswe2022group1/issues/618
• Leave Button Functionality is implemented: https://github.com/bounswe/bounswe2022group1/issues/615
• Bug fix for profile page: https://github.com/bounswe/bounswe2022group1/issues/543
• Design of third phase of learning space: https://github.com/bounswe/bounswe2022group1/issues/521
• Design of second phase of learning space: https://github.com/bounswe/bounswe2022group1/issues/520
• Reviewing Osman's Work (The navigation bar): https://github.com/bounswe/bounswe2022group1/issues/519

Week10: Android: Header Authorization Parameter
Week10: Introducing Jetpack library for Android app
Week10: New Button design and some configuration changes
Week10: Design improvement for Android
Week11: Learning Space Resource and Members new design
Week11: Learning Space Menu is created.
Week11: Redesign of profile page
Week11: Sign-in and Sign-up design changes are made
Week11: Profile page enrolled learning spaces is seen
Week11: Bug fix for sign-up and forgot-password pages
Week11: Resource page new design is introduced.
Week11: Resource (Notes,Discussion,Resource,Edit) functionality is done
Week12: Resize of creating discussing post
Week12: Resource page bottom bar becomes shorter and save functionality is added
Week12: Resource listing owner and votes is shown
Week12: Add/Remove favorite is added.
Week12: Welcome to budemi text in homepage is made sliding
Week12: UI/UX improvement on resource page.
Week12: Bug fix for profile page
Week12: Markdown is supported in resource page
Week12: Profile page image back-end connection is made
Week12: Add favorite back-end connection is made
Week12: Remove favorite back-end connection is made
Week12: User from id back-end infrastructure is made
Week12: Api connection for getting all notes in resource is made
Week12: Editting note back-end connection is made
Week12: Creating a note back-end connection is made
Week12: Content edit back-end connection is made
Week12: Implementation of upvote/downvote in resource page

Week2: Meeting with the Android team
Week2: Initialization of Android Studio
Week4: Review of Sync of Android app
Week4: Meeting with the Android team for milestone1
Week5: Meeting with the Android team
Week5: Another Meeting with the Android team
Week5: Android mockup and scenario for milestone1
Week6: Milestone 2 objectives for the Android team
Week7: Android meeting 20.11.2022
Week8: Android meeting
Week9: Android preparing for milestone2
Week9: Meeting with Back-end Team
Week9: Budemi android version for milestone 2 is completed.
Week9: Milestone2 and Milestone3 folders were missing. Pull-request.
Week10: Group Review and UI/UX Android for Milestone2.
Week10: Objectives for Android Team until Milestone3
Week11: Upvote and Unvote functionality is needed.
Week11: Edit resource functionality is needed.
Week11: Taking notes functionality is needed.
Week12: Deliverables for Milestone3
Week13: Milestone3: Group Review
Week13: Milestone 3: Scenario and Mockup for Android

Pull Requests:

• Budemi android main: https://github.com/bounswe/bounswe2022group1/pull/397
• Bug fix for user logout (user_token is set to "") : https://github.com/bounswe/bounswe2022group1/pull/452
• Milestone1 individual .md files are added : https://github.com/bounswe/bounswe2022group1/pull/451

• Api connection for GetContent, AddContent and Enroll is made - https://github.com/bounswe/bounswe2022group1/pull/584
• Learning Space Add Content is done - https://github.com/bounswe/bounswe2022group1/pull/592
• learningSpace2, topic click lands content page - https://github.com/bounswe/bounswe2022group1/pull/596
• API connection for various endpoints is done. - https://github.com/bounswe/bounswe2022group1/pull/603
• New back-end connections for android and some bug fixes - https://github.com/bounswe/bounswe2022group1/pull/605
• Discussion is fully completed. Some design changes for learning space is made - https://github.com/bounswe/bounswe2022group1/pull/610
• Some design changes for add content - https://github.com/bounswe/bounswe2022group1/pull/624
• Budemi android version for milestone 2 is completed. - https://github.com/bounswe/bounswe2022group1/pull/632
  • Reviewing Osman's change password PR - PR #568
  • Reviewing Osman's Change Password and Learning Spaces PR - PR #593
  • Reviewing Osman's Android: Members parameters passed for learning space PR- PR #597
  • Reviewing Osman's bug fix PR - PR #598
  • Reviewing Ahmet's Android dev ahmet, profile page changes PR - PR #599
  • Reviewing Osman's Forgot password page implemented PR - PR #606
  • Reviewing Osman's LS Search Implemented PR - PR #627

Milestone3 deliverables
Up vote and down vote functionality is implemented
Notes api connection is made
Note and Content api connections are made
Profile page image and more back-end connection is made
UI/UX improvement on resource page and Markdown support.
Resource and resource listing update for better UX.
Resource page new design is introduced
Profile Page enrolled courses are seen and redirected
Sign-in and Sign-up design changes
Profile page new design is introduced.
Design improvement for Android app is done.
New Button design and some config changes
Jetpack Library configuration for Android

Unit Tests: We haven't written any unit test. Since UI/UX testing is done via human computer interaction and back-end already written unit-tests for their apis, we have done it manually for all possible cases.

Additional Information:
It was my and other android team members' first time dealing with Kotlin. Since Kotlin is a compiled language not an interpreted one, it is hard to develop apps in a short amount of time. We had tough times through the development process of this project. As a good side, I am now at a nice level of developing android applications by using Kotlin though I don't prefer it. However, we failed to implement annotations functionality no matter how hard we try. This mainly because of we are not familiar with Kotlin and its tools. Another possible factor is that we started as 4 people on android team, but at the end of the day we were 2 people. Maybe, we could have managed the process better and devoted more time to implement annotations. On the other hand, we have improved our UI and UX a lot since the Milestone 2. These improvements were so satisfying for us. Besides these technical difficulties, developing a software product with other team members gave me lots of ideas about my future career. I learnt a lot about working with a team, its difficulties and advantages. To sum up, it was tough and enlightening process, and I am as thankful as I am exhausted.

Member: Ece Sarkın, Group 1, Online Learning Project (OLP), Personal Page

Member: Kadir Gökhan Sezer, Group 1, Frontend Team, Online Learning Project (OLP), Personal Page

Responsibilities:

• I was responsible to attend all the meetings.
• I was responsible for creating the project and configuring the routine methods between pages.
• I was responsible for designing homepage page.
• I was responsible for reviewing my team member's work.
• I was responsible for distribution of the work to be done each member.
• I was responsible to help my team if they needed.
• I was responsible to follow what the rest of the team has done.
• I was responsible for writing frontend implementation of change password endpoint.
• I was responsible for writing frontend implementation of add learning space endpoint.
• I was responsible for writing frontend implementation of filter learning space endpoint.
• I was responsible for writing frontend implementation of list learning space endpoint.
• I was responsible for writing frontend implementation of sign-in endpoint.
• I was responsible for writing frontend implementation of sign-up endpoint.
• I was responsible for writing frontend implementation of profile endpoint.
• I was responsible for reviewing my team member's work.
• I was responsible for routing beetween the pages.
• I was responsible for the authentication layer.
• I was responsible for solving my team member's problems that they encounter NextJS.
• I was responsible for migration of our project from ReactJS to NextJS.
• I was responsible for writing frontend of login page.
• I was responsible for filling Frontend related things in Milestone 3
• I was responsible for detecting and fixing bugs on Frontend.
• I was responsible for distribution of the work to be done each member
• I was responsible for writing frontend of register page.
• I was responsible for sync of Frontend with back-end and mobile
• I was respobislbe for writing frontend of change password page.
• I was responsible for writing frontend of profile page.
• I was responsible for deployment of the frontend.
• I was responsible for buying the domain.
• I was responsible for configuration of the domain.
• I was responsible for everything related to Homepage.
• I was responsible for listing all learning spaces in homepage.
• I was responsible for filtering learning spaces in homepage.
• I was responsible for adding learning space in homepage.
• I was responsible for everything related to Profile.
• I was responsible for adding profile page.
• I was responsible for adding profile photo.
• I was responsible for changing profile photo.
• I was responsible for changing password.
• I was responsible for adding/editing "About Me" section.
• I was responsible for everything related to Login.
• I was responsible for authentication layer.
• I was responsible for everything related to Forgot Password page.
• I was responsible for functionality of forgot password page.
• I was responsible for everything related to Register Page.
• I was responsible for everything related to Change Password Page.
• I was responsible for creating mock for the backend.
• I have introduced nextjs framework into out team.
• I have introduced new logo design into our team.

Main Contributions:

• I have implemented home-page for Web.
• I struggled with understanding the login and sign up part. I fixed them.
• I made the api connections of the login,logout,register and sign up pages.
• I did research to show my teammates beautiful website designs.
• I compared website designs and chose the most suitable one with my group friends.
• I participated into the all group meetings both Frontend and overall team.
• I built the Reactjs project structure. I designed the folder structure. I adjusted the project accordingly.
• I also handled the token based system.
• I reviewed my team member's work.
• I helped my friends with reactjs. I helped them when they had problems.
• I introduced Frontend,Android and Backend label to our repository.
• I created the profile page. When I log in, I set it to go to the profile page with that token. With that token, I set it to logout and go to the homepage again. I set the profile page checking for the existence of the token. Ece filled out the profile part.
• I made the necessary preparations for the deployment part. I worked it from this site. I asked my friends to fulfill their responsibilities. I waited for them to do it. If they won't, I told them to tell me that I would do the deployment part accordingly. There was no answer. I wrote the Dockerfile. @Ege did the deployment part. During this process, we had these problems because of my teammates not helping us.
• I have implemented what I was responsible for.
• I have attended all group meetings and front-end team meetings.
• I reviewed my team member's work.
• I have participated in designing the flow and routing of pages during meetings.
• I have participated in designing the visual outlines of the Learning Space and Contents pages.
• I have tried to help my team members when they encounter problems.

• Know-how about Docker: https://github.com/bounswe/bounswe2022group1/issues/307
• React Learning : https://github.com/bounswe/bounswe2022group1/issues/322
• Frontend: NPM: https://github.com/bounswe/bounswe2022group1/issues/473
• Frontend: ReactJS Folder Structure: https://github.com/bounswe/bounswe2022group1/issues/373
• Frontend: Usage of Mui: https://github.com/bounswe/bounswe2022group1/issues/374
• Frontend: Sync with the Huseyyin Seyyid: https://github.com/bounswe/bounswe2022group1/issues/375
• Frontend: What is API over ReactJS?: https://github.com/bounswe/bounswe2022group1/issues/376
• Frontend: Onclick funtion over href: https://github.com/bounswe/bounswe2022group1/issues/377
• Frontend: How to run react on other parts: https://github.com/bounswe/bounswe2022group1/issues/378
• Frontend: Create temporary logo: https://github.com/bounswe/bounswe2022group1/issues/379
• Frontend: Domain of the project: https://github.com/bounswe/bounswe2022group1/issues/380
• Frontend: What is CSS?: https://github.com/bounswe/bounswe2022group1/issues/381
• Frontend: Homepage template: https://github.com/bounswe/bounswe2022group1/issues/382
• Frontend: API iplementations of sign-up and sign-in pages: https://github.com/bounswe/bounswe2022group1/issues/383
• Frontend: for the v0.2, needs : https://github.com/bounswe/bounswe2022group1/issues/387
• Frontend: Group meeting: https://github.com/bounswe/bounswe2022group1/issues/389
• Frontend: Forgot password: https://github.com/bounswe/bounswe2022group1/issues/474
• Frontend: Content of the Homepage: https://github.com/bounswe/bounswe2022group1/issues/394
• Frontend: Profile Page: https://github.com/bounswe/bounswe2022group1/issues/430
• Frontend: Token on local storage: https://github.com/bounswe/bounswe2022group1/issues/433
• Frontend: Logout page: https://github.com/bounswe/bounswe2022group1/issues/435
• Frontend: with the help of @egetaga, Dockerfile: https://github.com/bounswe/bounswe2022group1/issues/464
• Frontend: Data structure of webpage: https://github.com/bounswe/bounswe2022group1/issues/468
• Frontend: Final version: https://github.com/bounswe/bounswe2022group1/issues/472
• Work on Mui 373
• Frontend: Deployment of our project #512
• Frontend: NextJS 527
• Frontend: Auth Layer 528
• Backend: Logout Endpoint 531
• Frontend: Dockerizing and deploying an hello-world project #511
• Frontend: Homepage 579
• Frontend: Profile Page 578
• Frontend: Change password 658
• Frontend: Auth Layer of the Project 581
• Frontend: New Aws Account 576
• Frontend: Deployment 638
• Frontend: Create a Learning Space 659
• Frontend: NextJS Framework 577
• Frontend: AWS Instance - Docker #509
• Frontend: Domain of the instance #510
• Frontend: Deployment of Frontend | 583
• Frontend: README 655
• Frontend: Dockerfile638
• Frontend: Readme file fixed | 670
• Frontend: EC2 and Route53 657
• Frontend: Filter button over the learning spaces 660
• Frontend: Homepage 579
• Frontend: Cards version 727
• Frontend: Creating Learning Space 728
• Backend: Photo of a Learning Space 729
• Backend: Cors problem 730
• Frontend: Meeting with @ecesrkn 748
• Frontend: Annotations 749
• Frontend: Homepage and Resource Page are Merged 750
• Frontend: Solving @ecesrkn problems Commit
• Frontend: Home Button 822
• Frontend: New Version of the Homepage 827
• Frontend: Forgot Password 819
• Frontend: Font is changed 824
• Frontend: New Profile Page825
• Frontend: For Deployment 830
• Backend: Cors problem 730
• Frontend: Create a Learning Space Page 828
• Backend dev test bugfix 856
• Frontend-Kadir -> Frontend: Homepage, Profile 857
• Unittests: content edit, fav, unfav user from id 858
• Frontend-kadir -> Frontend 867
• Frontend: Mock Data 896
• Frontend: DockerHub 897
• Frontend: CI&CD 898
• Frontend -> Master 899
• Frontend: Profile Page 900
• Frontend: Forgot Password 902
• Frontend: Mock Data 906
• Frontend: Last Sync 940
• Frontend: Mock Data 936
• Frontend: Deployment of the final version 945

• Group work distribution: https://github.com/bounswe/bounswe2022group1/issues/281
• Adding Labels: https://github.com/bounswe/bounswe2022group1/issues/321
• Checking group members: https://github.com/bounswe/bounswe2022group1/issues/282
• Reviewing GDPR Rules: https://github.com/bounswe/bounswe2022group1/issues/294
• Reviewing KVKK Rules: https://github.com/bounswe/bounswe2022group1/issues/295
• Correcting the ambiguity on the issue: https://github.com/bounswe/bounswe2022group1/issues/296
• Reviewing Contribution Plan: https://github.com/bounswe/bounswe2022group1/issues/301
• Reviewing Homepage: https://github.com/bounswe/bounswe2022group1/issues/303
• Outcomes of the meeting on 11.10.2022: https://github.com/bounswe/bounswe2022group1/issues/308
• Frontend Team Meeting: https://github.com/bounswe/bounswe2022group1/issues/318
• We need labels like Frontend,Backend, etc.:https://github.com/bounswe/bounswe2022group1/issues/321
• Group mail: https://github.com/bounswe/bounswe2022group1/issues/324
• Issue Template V2: https://github.com/bounswe/bounswe2022group1/issues/330
• Meeting with the team: https://github.com/bounswe/bounswe2022group1/issues/374
• Review of requirements: https://github.com/bounswe/bounswe2022group1/issues/470
• User requirements is reviewed. : https://github.com/bounswe/bounswe2022group1/issues/479
• Glossary and Requirements for Practice.app is reviewed.: https://github.com/bounswe/bounswe2022group1/issues/471
• An update on Requirements 1.2.2.1 Profile Specifications 637
• Frontend: Progress of my task 582
• Frontend: Extra Meeting with @ecesrkn 580
• Frontend: Report of Group Meeting 28.11.2022 559
• Frontend: Extra group meeting with @ecesrkn 661
• Backend: Cors problem 730
• Frontend: Meeting with @ecesrkn 748
• Frontend: Solving @ecesrkn problems Commit
• Frontend: For Deployment 830
• Frontend: Sync of the team 820
• Frontend: AWS Account 821
• Backend: Cors problem 730
• Frontend: Sync with the Mobile team823
• Frontend: Last Meeting 855

Pull Requests:

• Changes according to the new term #302
• addition of newcomers #305
• I created the frontend-v0.2 branch. The whole project is based on that brach. All of the team worked on that.
• 0.1.0-alpha #475: https://github.com/bounswe/bounswe2022group1/pull/475
• The merged version of frontend-kadir and frontend-content 636
• Docker file updated 654
• Create frontend_project_plan.md 465
• Frontend content 588
• Commands of the nextjs is added 656
• Instructions of frontend is added to Readmen 667
• (Review) empty url fields are replaced with non-empty string 852
• (Review) Home Page Favorite Learning Spaces ( https://github.com/bounswe/bounswe2022group1/pull/848)
• (Review) Instructions of Frontend App Dependencies Updated 889
• (Review) Backend dev test bugfix 856
• Frontend-Kadir -> Frontend: Homepage, Profile 857
• (Review) Unittests: content edit, fav, unfav user from id 858
• Frontend-kadir -> Frontend 866
• Frontend-Kadir -> Frontend: Homepage, Profile 867
• Frontend-kadir -> Frontend 867
• (Rewview) Currently, a user can see all notes, but a user can only see his/her own note. I fixed this bug 869
• Frontend -> Master 899

Unit Tests: Since frontend testing is done via human computer interaction, I haven't coded any unit test.

Additional Information: I actually noted what I have done in this link. This link can also be used to track my work.

Member: Ege Onur Tağa, Group1, Backend, Online Learning Project (OLP) - Budemi, Personal Page

Responsibilities for Milestone 3:

• I was responsible for bug fixing in the profile page (when user enrolled and then disenrolled, our backend still showed her as enrolled).
• I was responsible for implementing a functionality to favorite and unfavorite learning spaces (app/favorite and app/unfavorite).
• I was responsible for bug fixing the favorites functionality (a user could favorite the same learning space multiple times).
• I was responsible for implementing annotation support in the backend (separate project running on a different endpoint).
• On top of that, I was responsible for creating a project and deploying it into AWS EC2 for annotation support.
• I was responsible for fixing the bug in the patch method of profile page.
• I was responsible for meeting with my team members to discuss the customer milestone 3.
• I was responsible for reviewing my team member's pull requests and issues.
• I was responsible for implementing editing content.
• I was responsible for bug fixing the unit tests (discussion and leave learning space failed due to the changing data model.).
• I was responsible for writing unit tests for all my endpoints in the customer milestone 3 (I have written the unit tests for milestone 1 and 2 already, and wrote the ones for content edit, fav, unfav user from id, and tests for get, post, patch, delete for annotation).
• I was responsible for integrating our final backend software to master.
• I was responsible for preparing API endpoint docs for the endpoints I have written.

Main Contributions for Milestone 3: The backend team at Budemi (consisting of me and Kadir Kalkan) worked really well together and were super organized. We were able to create a bunch of endpoints that made things easier for the frontend and mobile teams, and it was all because we had such a strong team dynamic. We all helped each other out and learned from each other throughout the project. My specific responsibilities included implementing and bugfixing the codebase, annotations, and deployment. I've listed my contributions below for you to check out.

• I bug fixed the profile page (when user enrolled and then disenrolled, our backend still showed her as enrolled).
• I implemented a functionality to favorite and unfavorite learning spaces (app/favorite and app/unfavorite).
• I implemented annotation support in the backend (separate project running on a different endpoint).
• I fixed the bug in the patch method of profile page.
• I met with my team members to discuss the customer milestone 3.
• I reviewed my team member's pull requests and issues.
• I implemented functionality to editing content.
• I reviewed my team member's pull requests and issues.
• I bug fixed the unit tests (discussion and leave learning space failed due to the changing data model.).
• I did an introductory speech in the customer milestone.
• I wrote unit tests for all my endpoints in the customer milestone 2 (I had written the unit tests for milestone 1 and 2 already, and and wrote the ones for content edit, fav, unfav user from id, and tests for get, post, patch, delete for annotation).
• I prepared API endpoints for the endpoints I have written.
• I was responsible for integrating our final backend software to master.
• I wrote the executive summary, software package and standards sections in the milestone 3 group review.

• Backend - Bug Fix in the Profile Page
• Backend - Favorites bug
• Backend - Implementing annotations API
• Backend - Creating a project and deploying it into AWS EC2 instance for the annotations
• Backend - Bugfix in the profile page

• Meeting for the final customer presentations
• Milestone 3: Writing Executive Summary
• Milestone 3: Writing Standards Section
• Milestone 3: Writing Software Package Section

Pull Requests for Milestone 3:

• Implemented user_id to user retrieve functionality
• Backend dev favorite learning spaces
• Implemented editing content
• I implemented annotations support on the backend.
• Bugfixed the multiple favorites problem
• Fixed the bug in the patch methd of profileApiView
• Backend dev test bugfix
• Unittests: content edit, fav, unfav user from id
• Tests for get, post, patch, delete for annotation
• Backend-Final Customer Milestone update

Unit Tests for Milestone 3:

From first milestone until the second milestone:

• I have prepared unit tests for content.
• I have prepared unit tests for edit content.
• I have prepared unit tests for favoriting a learning space.
• I have prepared unit tests for unfavoriting a learning space.
• I have prepared unit tests for user from id.
• I have prepared unit tests for Annotation API including get, post, patch, delete for annotation.
• You may check their codes in this PR and for the Annotation: PR.

As part of my development process, I made sure to write unit tests for all of the code that I created. This was an important step to ensure that the code was working properly and met the desired specifications. By writing these unit tests, I was able to catch any errors or issues before the code was deployed, leading to a smoother and more efficient development process.

Additional Information for Milestone 3: I assisted the frontend and android teams by providing online support to help them utilize our APIs. Despite having comprehensive documentation, there were times when they required further explanation and clarification on certain points. To ensure that they were able to use our APIs effectively, I made myself available to answer their questions and provide guidance as needed.

Responsibilities for Milestone 2:

• I was responsible for implementing the discussion related endpoints (/app/discussion/ and /app/discussion-list/).
• I was responsible for implementing listing endpoint (app/learning-space-list/).
• I was responsible for implementing searching related endpoints (app/learning-space-search/ and app/learning-space-tag-search/).
• On top of that, I was responsible for creating data models for these endpoints in Django.
• I was responsible for adding tagging specification to learning spaces.
• I was responsible for dockerizing the backend application.
• I was responsible for deploying the backend application into AWS EC2 instance.
• I was responsible for reviewing my team member's pull requests and issues.
• I was responsible for preparing slides for the customer milestone 2.
• I was responsible for doing an introductory speech in the customer milestone.
• I was responsible for writing unit tests for all my endpoints in the customer milestone 2 (I have written the unit tests for milestone 1 already).
• I was responsible for fixing bugs in the backend software.
• I was responsible for reviewing my team member's work in their pull requests and issues.
• I was responsible for preparing API endpoints for the endpoints I have written.

Main Contributions for Milestone 2: As a backend team of Budemi, we were very organized and had a strong team mentality. I see that we provided many (17) endpoints that facilitate the jobs of frontend and mobile and it is only possible because of our strong team mentality. During the all parts of the project, we learned from each other. As a team member, apart from implementing my parts, which are summarized here, we also reached and learned from each other. I was responsible for implementing the codebase and also deployment. I summarized my contributions below for your review.

• I implemented the discussion related endpoints (/app/discussion/ and /app/discussion-list/).
• I implemented listing endpoint (app/learning-space-list/).
• I implemented searching related endpoints (app/learning-space-search/ and app/learning-space-tag-search/).
• I created data models for these endpoints in Django.
• I added tagging specification to learning spaces.
• I dockerized the backend application.
• I deployed the backend application into AWS EC2 instance.
• I reviewed my team member's pull requests and issues.
• I prepared slides for the customer milestone 2.
• I did an introductory speech in the customer milestone.
• I wrote unit tests for all my endpoints in the customer milestone 2 (I have written the unit tests for milestone 1 already).
• I reviewed my team member's contributions in their pull requests and issues.
• I prepared API endpoints for the endpoints I have written.
• I explained the use of our endpoints to Android team and also reviewed their implementation.
• I wrote the executive summary and standards sections in the milestone 2 group review.

• Backend - Implementing the Discussion API
• Backend - Implementing Searching and Listing for Learning Spaces
• Backend- bugfix and adding tag functionality
• Backend - Implementing Tag Search API
• Backend - Writing an API doc for my APIs
• Backend - Deployment into AWS

• Meeting with Android Team
• Milestone 2: Writing Executive Summary
• Milestone 2: Writing Standards Section

Pull Requests for Milestone 2:

• Backend dev discussion
• Revert "Backend dev discussion"
• Backend dev discussion forum
• Implemented an APIs searching and listing all Learning Spaces
• Implemented tagging, fixed bug,improved LSpace API
• Implemented tag search functionality
• I have prepared tests for discussion and search
• Backend Second Milestone Codebase

Unit Tests for Milestone 2:

• I have prepared unit tests for discussion.
• I have prepared unit tests for discussion list.
• I have prepared unit tests for learning space list.
• I have prepared unit tests for search with parameter.
• I have prepared unit tests for search with tag.
• You may check their codes in this PR

In the end, I have written unit tests for all the code I have developed.

Additional Information for Milestone 2: I have carried out online support to both the frontend and android teams in using our APIs. We have fully documented, yet they sometimes still needed further explanation.

Responsibilities for Milestone 1: I was responsible for the dockerization and deployment for the OLP. Moreover, I have implemented login, logout, change-password functionalities, together with writing test cases for register, login and logout. Also, I was responsible for editing glossary and requirement pages. Additonally, I was responsible for presentation slides and also preparing the scenarios for the customer meeting.

Main Contributions for Milestone 1: I have implemented login, logout and change password functionalities. Moreover, I dockerized the backend project and deployed into AWS EC2 instance. Additionally I prepared a presentation and a scenario for the customer meeting. Another important thing I did is to edit the glossary and requirements for the project. Moreover, I reviewed and edited the semantic searching page.

• Dockerization and Deployment into AWS EC2: https://github.com/bounswe/bounswe2022group1/issues/342
• Implementing login, logout and change-password functionalities: https://github.com/bounswe/bounswe2022group1/issues/368
• Implementing unit tests for register, login and logout: https://github.com/bounswe/bounswe2022group1/issues/369
• Learning Django: https://github.com/bounswe/bounswe2022group1/issues/320

• Checking and updating Glossary and Requirements: https://github.com/bounswe/bounswe2022group1/issues/297
• Reviewing Semantic Search Page: https://github.com/bounswe/bounswe2022group1/issues/298
• Preparing a presentation and scenarios for Milestone 1 Customer Meeting: https://github.com/bounswe/bounswe2022group1/issues/405
• Editing authentication related requirements slightly: https://github.com/bounswe/bounswe2022group1/issues/437

Pull Requests for Milestone 1:

• Backend-dev Login, logout and change password functionalities: https://github.com/bounswe/bounswe2022group1/pull/364
• Added test cases for login, logout and register: https://github.com/bounswe/bounswe2022group1/pull/367
• Adding the latest Docker files for AWS EC2 deployment: https://github.com/bounswe/bounswe2022group1/pull/426
• Merging Backend-Development into master https://github.com/bounswe/bounswe2022group1/pull/431
• Adding communicator in parentheses next to me: https://github.com/bounswe/bounswe2022group1/pull/300

Unit Tests for Milestone 1:

• I have prepared unit tests for register
• I have prepared unit tests for login
• I have prepared unit tests for logout
• You may check their codes in this PR

Additional Information for Milestone 1: I have carried out online support to both the frontend and android teams in using our APIs. We have fully documented, yet they sometimes still needed further explanation.

Member: Ahmet Cemil YAZICI, Group 1, Android Team, Online Learning Project(Budemi), Personal Page

Responsibilities for Milestone 1: I have dealt with Scenario & Mockups creating the Scenario and Mockup slides with my teammate Ömer Özdemir, Harun Erkurt. I have also designed the homepage of the app, I have designed the main page, changed the visibility of the buttons according to user token which is responsible for checking if the user is logged or guest. I also took part in the reviewing process for some of my teammates’ pull requests and issues.

Responsibilities for Milestone 2:

• I was responsible for work distribution decisions for Android team.
• I took on the main page design and implementation.
• I was responsible for profile page design and implementation.
• I have also designed the see profile page design and endpoint connection.
• I was responsible for edit profile page design and endpoint connection.
• I was resposible for Mockup & Scenarios for this term.
• I have changed the requirements according to changes on the project as we go on with the project.
• I have reviewed and changed necessary UML sequence diagrams.
• I was responsible for documenting the changes on requirements for milestone 2.
• I was responsible for setting the APK icon on android team.

Responsibilities for Milestone 3:

• I was responsible for work distribution decisions for Android team.
• I took on the main page design and implementation.
• I was responsible for profile page design and implementation.
• I have also designed the see profile page design and endpoint connection.
• I was responsible for edit profile page design and endpoint connection.
• I was resposible for Mockup & Scenarios for this term.
• I have changed the requirements according to changes on the project as we go on with the project.
• I have reviewed and changed necessary UML sequence diagrams.
• I was responsible for documenting the changes on requirements for milestone 3.
• I was responsible for changing the APK icon on android team.
• I was responsible for adding navigation bar to change password page.
• I was responsible for adding navigation bar to profile page.
• I was responsible for adding new resources for presentation (20 of them).
• I was in charge of code reviews for this milestone, approving pull requests etc...
• I did background, text colouring for some pages.

Main Contributions for Milestone 1: I have implemented the xml and activity file of main page, found example png files on google and put on drawables. Used images for example main page and image buttons. I have also checked if user is logged or not and set visibility accordingly. I have reviewed and merged several files, made several pull requests for my own changes. I also bugfixed my friends code, solved the unexpected errors.

Main Contributions for Milestone 2: I took on being a part of Android team on the first meeting, I have played an active role on duty assignments throughout the project. I have started with the main page implementation and design, i have put on the necessary buttons and images. I have then worked on profile page which we access through main page. I have implemented and designed see profile page and edit profile change. I then worked on endpoint and database connection for these pages. I set the APK icon on Android APP. In the end i took notes on the milestone presentation for further improvements. I have wrote the requirement changes progress for this milestone 2.

Main Contributions for Milestone 3: I have played an active role on duty assignments throughout the project. I have started with the main page implementation and design, i have changed or improved the necessary buttons or images. I have then worked on profile page and fixed some bugs which we access through main page. I have implemented new features and designed see profile page and edit profile change. I then worked on endpoint and database connection for these pages. I set the new APK icon on Android APP. I have wrote the requirement changes progress for this milestone 3 group report.

• Collaborative Work on Android Studio
• Initial Homepage Commits
• View Binding Decision
• Buttons for Homepage
• Visibility Change on Guest

• Sequence Diagram Revisions
• Android Team Meeting
• Modifying Requirements
• Creating Individual Report Template for Milestone 1
• Scenario & Mockups

• profile page creation, functionality - Android #553
• Adding profile creation page for new users. #575
• Create - Edit Profile Page - Android #594
• Android Team - Milestone 2 Coding Part Finished #600
• Profile Page - Image POST API / Android #604
• APK Icon Set - Android #630

• Customer Meeting Evaluation - Android Team #503
• Android Team Meeting #515
• Updating requirements to match current project plan - Android #585
• Profile Page Endpoints Change Proposal - Android #573
• Milestone 2 Tag #586
• Work Distribution - Android #587
• Requirement changes progress #647

• Implementation and Editing Action Bar #707
• App Icon Changed - Android #877
• Added navigation bar to Change Password - Android #892
• Added navigation bar to Create Profile #893
• Bugfix - Android #918

• Navigation Bar on All Pages - Android #769
• Changing Budemi APK icon - Android #796
• Need to Add Navigation to Other Pages - Android #891
• Mock Data and Rehearsal for Milestone 3 - Android #920
• Adding resources for learning space Python #931

Pull Requests for Milestone 1:

• First Pull for Homepage
• Buttons added on Homepage
• Finalized Budemi Android Team
• Creating a Fresh Branch for Working Code
• Deleting Android from Master Because of an Error

Pull Requests for Milestone 2:

• profile Changes - Android #545
• Android dev ahmet, profile page changes #599

Pull Requests for Milestone 3:

• Android main #884
• navigation bar added to change password #888
• navigation bar added to create profile #894
• deleted android w/ omer #911
• Android main #886

Unit Tests for Milestone 1:

• We have no unit tests implemented on android team due to backend team already implementing them for api's and android team used human interactions to test possible edges.

Unit Tests for Milestone 2:

• We have no unit tests implemented on android team due to backend team already implementing them for api's and android team used human interactions to test possible edges.

Unit Tests for Milestone 3:

• We have no unit tests implemented on android team due to backend team already implementing them for api's and android team used human interactions to test possible edges.

Additional Information for Milestone 1: I have assumed several roles on top of my own to implement and bugfix several pages of my friends. Also helped to improve the designs, and codes. Checked other developer teams apps to get ideas and use on our project.

Additional Information for Milestone 2: I have took on additional responsibilities throughout the project for work distribution and 1v1's with professor. Peer learning with my group mates.

Additional Information for Milestone 3: I have took on additional responsibilities throughout the project for work distribution and 1v1's with professor. Peer learning with my group mates.