Emrah Doğan - bounswe/2021SpringGroup1 GitHub Wiki

Hi everyone,
My name is Emrah. I'm a Computer Engineering student at Bogazici University. This is my personal page for CMPE 451 and CMPE 352. Here I will post what I do every week.

Contact


Time Tracking for CMPE 451

Week 2
Task Duration Type of Work
Attending to the lab and meeting with new team member Orkan and refreshing our memory about our project 2h Meeting, Research
We met with our new teammate Orkan and explained the summary of our project and what we have done so far. Then, as a team, we revised our requirements page and diagrams (sequence, etc.). We talked about our level of experience with this course and project.
Week 3
Task Duration Type of Work
Attending to the lab 2h Meeting
Reviewing the requirements page 30min Researching
Reviewing the Sequence Diagrams 30min Researching
Researching and creating detailed issues Issue 1<\a>, Issue 2<\a> 1h 30min Researching
This week, I personally reshaped the project in my mind by checking the new version of The requirements and Sequence diagram page. In this week's team meeting, we decided on team members on the Backend, Front-end mobile and Web side. We also decided which frameworks to use this week. Here I did research for frameworks and deployment options and created the necessary issues.
Week 4
Task Duration Type of Work
Attending to the lab 2h Meeting
Attending Team Meetings 1h Meeting
Reviewing new the requirements and Sequence diagram page 30min Researching
Learning Django 5h Studying
Meeting<\a> with Berke for creating Backend part of the project 3h Meeting
This week, I checked the Requirements and Sequence Diagram page for the updated version of the assistant based on feedback. Because I forgot the Django Framework, I started to learn it again. In addition, we met with Berke as a Backend team and created the project and integrated the useful functions in the practice-app we made in Cmpe 352 into our new project. We also made plans with Berke about what we should do on the backend side.
Week 5
Task Duration Type of Work
Attending to the lab 2h Meeting
Attending Team Meetings 1h Meeting
Learning Django 2h Meeting
Implementing Backend without Django Rest Framework 4h Coding
Trying to add Swagger without Rest Framework 4h Researching and Coding
Learning Django Rest Framework 2h Studying
Reimplementing Backend functions with Django Rest API 3h Coding
Learning Json-Ld and changing some functions according to them 3h Researching and Coding
Learning Activity Streams 1h Researching
Learning AWS and deployment of Backend 3h Coding
Trying to solve bugs about corse, authentication etc. 7h Coding
This week has been very busy. First of all, I continued to learn Django Framework. Afterwards, I wrote the functions allocated to me as a result of the task sharing with Berke. However, we did not use the Rest API because we left the planning of the Swagger Documentation Tool for later and we realized that this decision was not the right one. We tried to add Swagger without Rest API but Swagger interface was not rendering properly. Then I started learning Django Rest API and wrote some of my functions with Rest API. Then I learned the Json-LD structure and added some functions to the Backend. So I tried to learn what Activity Stream is. Finally, I deployed the Backend side to Amazon AWS and tried to resolve the problems that arose in integrating with the Front End sides.
Week 6
Task Duration Type of Work
Customer Meeting - Meeting
Dealing with CORS error 2h Coding
Situation assessment with Berke 1h Meeting
Debugging the existing functions 3h Coding
This week we made our Milestone presentation. We had to present it here as problematic due to CORS and authorization. Again I tried to resolve the CORS error. Then we evaluated the situation of the Backend side with Berke. I've debugged it as the existing functions also work fine and to better understand the REST framework.
Week 7
Task Duration Type of Work
Group Meeting & Backend-Frontend connection 2h Meeting-Coding
This week, we connected with frontend-web with CORS and Authentication errors resolved. We verified that many functions are working. We received feedback from Frontend for endpoints.
Week 8
Task Duration Type of Work
Attending to the lab 2h Meeting
Adding new endpoints to the Backend 6h Coding
Reconfiguring the endpoints 2h Coding
Adding changes on the existing Unit Tests 2h Coding
Adding new Unit Tests 2h Coding
This week I added a new function to the backend side. I also made various changes in some of the endpoints according to the requests of the frontend. Also, interestingly, I solved the id mismatch errors in the existing unit tests. I added unit test to the functions I just wrote.
Week 9
Task Duration Type of Work
Attending to the lab 2h Meeting
Attending to Group Meeting 1h Meeting
Doing preliminary research for advanced filtering implementation 1h Researching
Doing preliminary research for privacy features 1h Researching
Researching APIs for geocoding 1h Researching
Preparing Json-LD headings 1h Coding
Adding definitions to the Swagger documentation 1h Coding
This week has passed with more research. I did the necessary research for new features and missing ones(How should we add the missing features due to our database selection, what difficulties will we face). I prepared the JsonLD headings in a branch. I also added definitions to the endpoints for the Swagger documentation.
Week 10
Task Duration Type of Work
Customer Demo 2 3h Presentation
Contributing to the Group Report 3h Documentation
Attending the weekly meeting 2h Meeting
This week we present our 2nd Demo of the app. It was a very good presentation. Afterwards, I finished this tiring week by filling out the Group Report.
Week 11
Task Duration Type of Work
Attending the weekly meeting 2h Meeting
Backend Meeting meeting 45m Meeting
This week, we talked about the features that should definitely be in the latest version of the application. In our meeting as a backend, we determined the Advanced Search design, its current progress and what may change in the future.
Week 12
Task Duration Type of Work
Attending the weekly meeting 2h Meeting
Backend Meeting 2.5h Meeting
Group Meetings 9.5h Meeting
Adding new endpoints 8h Coding
Adding JSON-LD and Activity Streams 5h Codind and Documentation
Adding Tests 1.5h Coding
Adding Meeting notes on the wiki 1h Documentation
We talked about what features will be in the final presentation at the weekly PS meeting. We have also listed the features to be implemented in this meeting in order of importance.
We also held many group meetings this week before the final presentation. Details have been added to the Meeting Notes. This week, I made edits to the new endpoints as well as the ones that are.
In addition, I implemented the deficiencies related to Json-LD and Activity Streams. We have finished writing the backend code by writing the test functions.
I'm not talking about the details of the meetings here, as I've added the Meeting Notes to the Wiki.

Time Tracking for CMPE 352

Week 1
Task Duration Type of Work
Weekly Meeting 1h 15min Meeting
Creating my Personal Wiki Page 1h Documentation
Creating Communication Plan 1h Meeting and Documentation
Liked Repository Research 30min Research and Documentation
Looking at the some part of suggested video 30min Research

I met my friends in my group and created my personal page. What is wiki, how to use them, I learned. I made a favorite repo search and added it to the favorite repo page with its explanation.
Liked Repository Research and adding to Pillow :
The part which impress me is that this library provides extensive file format support, an efficient internal representation, and fairly powerful image processing capabilities to Python interpreter.

Week 2
Task Duration Type of Work
Weekly Meeting 40min Meeting
Updating System Requirements 4h Research and Documentation
The main importance of this week was to choose the project we were going to implement and to consider the requests of the candidate projects. After our project was determined, I determined the project requirements and added the necessary items.
Created tabs
1.2.1, 1.2.1.1, 1.2.1.2, 1.2.1.3, 1.2.1.4, 1.2.1.5, 1.2.1.6, 1.2.1.7, 1.2.1.7.1, 1.2.1.7.2, 1.2.1.7.3, 1.2.1.7.4
1.2.2, 1.2.2.1, 1.2.2.2, 1.2.2.3, 1.2.2.4, 1.2.2.5, 1.2.2.6
1.2.3.4
1.2.4, 1.2.4.1, 1.2.4.1.1, 1.2.4.1.2, 1.2.4.1.3, 1.2.4.1.4, 1.2.4.1.5, 1.2.4.1.6, 1.2.4.1.7
1.2.5, 1.2.5.1, 1.2.5.2, 1.2.5.3, 1.2.5.4, 1.2.5.5
Week 3
Task Duration Type of Work
Analyzing and updating the System Requirements 1h Research and Documentation
Customer Meeting (PS) 2h Meeting
There are not many assignments this week. The only thing that matters these weeks is Customer meeting Ps. It is a good introduction to what customer expect from us.
Week 4
Task Duration Type of Work
Customer Meeting 2h Meeting
Weekly Meeting 1h Meeting
Grouping Scenario 2 of Acceptance Criteria for
Mockup Asssignment with Bilal Tekin
1h Research and Documentation
Grouping Scenario 3 of Acceptance Criteria for
Mockup Asssignment with Bilal Tekin
1h Research and Documentation
Investigate and think about System Requirements 1h 30min Research
Thinking Questions for Questions Page 30min Research
Before our first meeting with our customer, we decide which questions we should ask him. On friday, we make a meet up with our customer(teaching assistant) and talked about the project. It's was very benifical and removed some uncertainties in the project description. Moreover, this week we create mockup of our system. While doing these, we realized that we need to add new system requirements. I do this adding operations with Bilal.
Week 5 - 6
Task Duration Type of Work
Weekly Meeting 1h Meeting
Research on UML design 1h 30min Research
Designing Use Cases Diagram 3h Assignment
Customer Meeting (PS) 1h 30min Meeting
Redesign my personal efforts page 2h Documentation
In our weekly meeting, we decided to learn more about UML, use cases, class diagrams and sequence diagrams. We split the assignment among the group members. I worked mostly worked on use cases with Cem, Hakan and Muhammet.
In this week's PS, we analyze the current process with diagrams and how we can improve it. It was very informative.
I also redesigned my personal page. I made it look more detailed and better
Week 7
Task Duration Type of Work
Weekly Meeting 1h Meeting
Reviewed almost all of the work done until Week 7 1h Research
Working on the Gantt chart with teammates 2h 30min Assignment
Reviewed the milestone report and gave feedback to my team 30min Assignment
Filled out my personal column in the RAM 1h 30min Documentation
In weekly meeting, we determined what and how to do it. We have compiled all the work we have done so far in the milestone project. We filled in the personally reserved column in the RAM matrix.
We also created a Gantt chart using ProjectLibre with all of our teammates.
Week 8
Task Duration Type of Work
Spring Break - -
This week was the spring break week, so we took a week off from work as a team.
Week 9
Task Duration Type of Work
Weekly Meeting 2h Meeting
Identifying what needs to be learned 1h Research
Learning Effective Github Usage 4h Research
This week I outlined what we will learn for our new assignment. This assignment is quite large compared to other assignments. Therefore, determining what to learn is very important.
There is a lot to learn in PS as well.
Week 10
Task Duration Type of Work
Weekly Meeting 4h Meeting
Learning Django, Docker and EC2 12h Research
Customer Meeting 1h Meeting
Researching Third Party APIs 1h Research
Implementing News API 4h Assignment
Implementing Other Parts in the project 4h Assignment
Filling Documents 4h Assignment, Documentation
This week very busy. I've spent a lot of time on practice-app this week. It took a lot of time to learn new things and put them into practice. I also learned what it is like to work with teammates at the same time. Deploying the application is a very different event that everyone should learn. The homework was indeed very, very long.
⚠️ **GitHub.com Fallback** ⚠️