Mirabito - Aykut, Ayberk; Aydemir, Necati M.; Demir, Aydin: Difference between revisions
From CS486wiki
Jump to navigationJump to search
Content deleted Content added
| Line 125: | Line 125: | ||
- Normally, we had a column in the TimeSheet table called "isOngoing" and it's main purpose was to see if that individual TimeSheet is continuing or not. With that, we were able to have constraints such as not allowing our users to create another TimeSheet if they have an ongoing timesheet or not allowing them to call the API call EndSheet if the employee has no ongoing TimeSheet etc. Also, we were holding today's sheets and archived sheets in the same table which would potentially cause some delays in the system with more entries registered. As discussed in the meeting, rather than having a single TimeSheet table for every instance, we divided the current TimeSheet table into 2 different TimeSheet tables, called TimeSheetDaily and TimeSheetArchive. As their names suggest, TimeSheetDaily is for the current day's timesheet entries while TimeSheetArchive is for every other day's entries. |
- Normally, we had a column in the TimeSheet table called "isOngoing" and it's main purpose was to see if that individual TimeSheet is continuing or not. With that, we were able to have constraints such as not allowing our users to create another TimeSheet if they have an ongoing timesheet or not allowing them to call the API call EndSheet if the employee has no ongoing TimeSheet etc. Also, we were holding today's sheets and archived sheets in the same table which would potentially cause some delays in the system with more entries registered. As discussed in the meeting, rather than having a single TimeSheet table for every instance, we divided the current TimeSheet table into 2 different TimeSheet tables, called TimeSheetDaily and TimeSheetArchive. As their names suggest, TimeSheetDaily is for the current day's timesheet entries while TimeSheetArchive is for every other day's entries. |
||
- We also implemented a API call called EndDay that is designed to be called automatically when the day ends. It's functionality is deleting |
- We also implemented a API call called EndDay that is designed to be called automatically when the day ends. It's functionality is deleting left out entries inside the TimeSheetDaily for the day and adding them to the TimeSheet Archive. |
||
- We also have some Get API calls for View TimeSheets functionality. One of them is returning every single entry of an Employee in the TimeSheetArchive while the other one is giving weekly TimeSheets. Weekly TimeSheet display takes the employee ID and a number called "dist". "dist" means the requested weeks difference between this week. If a user enters 0 for the "dist", it will give this weeks entries for that employee. If the user enters 2, it will give the entries that were stored 2 weeks ago. |
|||
- A simple employee Id login interface has been created for the demo on Angular. |
|||
- Entries made without providing an Employee id were checked with an activated guard, and the entries made with a direct url without providing an Employee id were redirected to the login page. |
- A simple employee Id login interface has been created for the demo on Angular. Entries made without providing an Employee id were checked with an activated guard, and the entries made with a direct url without providing an Employee id were redirected to the login page. Employee id value is saved in session storage so that the entered id is remembered in the system as long as the tab is open. |
||
| ⚫ | |||
- Employee id value is saved in session storage so that the entered id is remembered in the system as long as the tab is open. |
|||
| ⚫ | |||
'''Problems: ''' |
'''Problems: ''' |
||
| Line 142: | Line 140: | ||
- Functions will be written for the view timesheet button and time sheets in the archive will be requested. |
- Functions will be written for the view timesheet button and time sheets in the archive will be requested. |
||
- View Timesheet button will be active. |
|||
- View Timesheet by Week functionality will be added. |
|||
- .Net identity framework will be checked. |
|||
- Will look onto "claims". |
|||
- And more depending on the meeting next week. |
|||
Revision as of 00:26, 24 October 2022
Week 1
Date: 09/25/2022
Attandence: Ayberk Can Aykut, Aydın Can Demir, Necati Mert Aydemir
Accomplishments:
- The first meeting was done with Mr.Abhineet, Mr.Eric and Professor Jones.
- Our team members set up Visual Studio 2022, .NET 6 SDK, Angular and checked some tutorials for .NET Entity Framework and Angular as requested.
- To get started with Angular, TypeScript syntax was learned and basic component hierarchy was studied.
- Since our team's overall familiarity with the Angular and our anticipation that .NET will have most of the workload for our project, we prioritized learning as much .NET as possible rather than Angular.
Problems:
- No problem occurred this week.
To-Do:
- The second meeting will be hold 09/27/2022.
- The requirements of the project and the general work plan will be clarified after the meeting.
- Studying of Entity Framework and Angular will continue.
Week 2
Date: 10/02/2022
Attandence: Ayberk Can Aykut, Aydın Can Demir, Necati Mert Aydemir
Accomplishments:
- The second meeting was done with the team, Mr.Abhineet and Professor Jones.
- As requested, we looked on to more details on .Net Entity Framework, Angular and their integration with each other.
- Our team achieved a better understanding on EF6 Code-First approach and Reactive Form component.
- Created a demo website with Angular that is connected to a web API developed in EF6.
Problems:
- No problems yet...
To-Do:
- Prepare for the demonstration in 10/04/2022.
- Studying of Entity Framework and Angular will continue.
- Rest of it will be decided after the 3rd meeting.
Week 3
Date: 10/09/2022
Attandence: Ayberk Can Aykut, Aydın Can Demir, Necati Mert Aydemir
Accomplishments:
- The bootstrap and alertifyjs modules used in the demo were replaced with angular materials upon request.
- Table and snackbar structures were used from the angular materials module downloaded with NodeJS.
- Checked the Azure environment to have some understanding on Cloud Computing and its relevance to our project.
- Prepared a Design Document regarding the requirements mentioned in our meeting this week.
Problems:
- Azure says we are not eligible for an Azure free account
To-Do:
- Look for Azure alternatives (AWS) for learning more on cloud computing
- Talk about the Design Document in the upcoming meeting to add some new key points if needed.
- Studying continues.
Week 4
Date: 10/16/2022
Attandence: Ayberk Can Aykut, Aydın Can Demir, Necati Mert Aydemir
Accomplishments:
- Tables for timesheet and employee were created in the database. We started to develop on the backend side with .Net.
- On the angular side, we developed the front end for the employee time module based on the images that Mr.Abhineet sent.
- We have uploaded client and backend applications we developed using .Net and Angular to the repository created by Abhineet on BitBucket.
- We learned about repository management using SourceTree.
- Thanks to Watson on the hub, Azure account was created by Mert (problem solved).
- The design document has been updated and visuals have been added as requested.
Problems:
- We're having trouble connecting to Azure all together.
- We are trying to connect the backend and frontend applications that we have developed, since we are trying to run the database in the cloud without any problems, we decided to code the requests on the frontend after the base URL we created in the cloud works properly.
To-Do:
- Providing trouble-free access by all team members to the database in the cloud.
- Connecting backend and frontend applications.
- Changing applications with the feedbacks we will receive in the next meeting
Week 5
Date: 10/23/2022
Attandence: Ayberk Can Aykut, Aydın Can Demir, Necati Mert Aydemir
Accomplishments:
- Normally, we had a column in the TimeSheet table called "isOngoing" and it's main purpose was to see if that individual TimeSheet is continuing or not. With that, we were able to have constraints such as not allowing our users to create another TimeSheet if they have an ongoing timesheet or not allowing them to call the API call EndSheet if the employee has no ongoing TimeSheet etc. Also, we were holding today's sheets and archived sheets in the same table which would potentially cause some delays in the system with more entries registered. As discussed in the meeting, rather than having a single TimeSheet table for every instance, we divided the current TimeSheet table into 2 different TimeSheet tables, called TimeSheetDaily and TimeSheetArchive. As their names suggest, TimeSheetDaily is for the current day's timesheet entries while TimeSheetArchive is for every other day's entries.
- We also implemented a API call called EndDay that is designed to be called automatically when the day ends. It's functionality is deleting left out entries inside the TimeSheetDaily for the day and adding them to the TimeSheet Archive.
- We also have some Get API calls for View TimeSheets functionality. One of them is returning every single entry of an Employee in the TimeSheetArchive while the other one is giving weekly TimeSheets. Weekly TimeSheet display takes the employee ID and a number called "dist". "dist" means the requested weeks difference between this week. If a user enters 0 for the "dist", it will give this weeks entries for that employee. If the user enters 2, it will give the entries that were stored 2 weeks ago.
- A simple employee Id login interface has been created for the demo on Angular. Entries made without providing an Employee id were checked with an activated guard, and the entries made with a direct url without providing an Employee id were redirected to the login page. Employee id value is saved in session storage so that the entered id is remembered in the system as long as the tab is open.
- Frontend and backend are connected. Buttons became functional. All buttons except the view time sheet in the Time module, which are clock in, clock out, go to lunch and return from lunch buttons work properly.
Problems:
- No problem this week.
To-Do:
- Functions will be written for the view timesheet button and time sheets in the archive will be requested. - View Timesheet button will be active. - View Timesheet by Week functionality will be added. - .Net identity framework will be checked. - Will look onto "claims". - And more depending on the meeting next week.
