Mirabito 1 - Omer Tici; Ozgur Eminogle; Bugra Aydin; Ali Gorgun: Difference between revisions

From CS486wiki
Jump to navigationJump to search
Content deleted Content added
No edit summary   (change visibility)
No edit summary   (change visibility)
 
(22 intermediate revisions by the same user not shown)
Line 1: Line 1:
''<big><big>Week 1</big></big>''
''<big><big>Week 1 02/04/2024</big></big>''
--------------------------------------------------------------------
--------------------------------------------------------------------


'''Accomplishments:'''
'''Accomplishments:'''

● Back-end side discussed about code and new back-end member Mert learned the basics of the code.
● Back-end side discussed about code and new back-end member Mert learned the basics of the code.
● Code now works on machine-readable but still needs improvements.
● Code now works on machine-readable but still needs improvements.
● Front-end side looked at the design goal and planned the structure.
● Front-end side looked at the design goal and planned the structure.
● System is integrated into computers.
● System is integrated into computers.

'''Problems:'''
'''Problems:'''
● There is an ETX character problem from the machine, back-end facing.
● There is an ETX character problem from the machine, back-end facing.
● Front-end system is going to be built from scratch.
● Front-end system is going to be built from scratch.

'''TO-DO:'''
'''TO-DO:'''
● Find a solution for the ETX character problem.
● Find a solution for the ETX character problem.
● Update inventory report to machine-readable version.
● Update inventory report to machine-readable version.
● Basic steps for the skeleton will be implemented.
● Basic steps for the skeleton will be implemented.
Login page will be designed as the beginning step.
The login page will be designed as the beginning step.

''<big><big>Week 2 02/12/2024</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● A new database will be designed and created until this week's meeting.
● The second part of the front end was created.
● The skeleton for the front end was created to have a well-organized structure.
'''Problems:'''
● Make the database match business requirements.

'''TO-DO:'''
● Update the database in the future and also update the code according to the new database.
● Starting to connect the front end with the database from the back end

''<big><big>Week 3 02/18/2024</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● Get functions created.
● New attributes from the machine added to the database.
● The Front-end version on the git side has been updated.
● Get function connection has been planned.

'''Problems:'''
● None for the back-end.

'''TO-DO:'''
● Get more attributes from the machine.
● Starting to connect the front end with the database from the back end.

''<big><big>Week 4 02/25/2024</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● Post function developed (added new commands).
● Front-end and Back-end have been connected with service.
● The third page has been improved to have a better UI for the user end.


'''Problems:'''
● Some of the commands are hard to store in the database re-design the database.

'''TO-DO:'''
● Get more attributes from the machine.
● Starting to connect the front end with the database from the back end.
● Going to continue with the next pages promising new features to the user-end.


''<big><big>Week 5 3/11/2024 - Spring Break</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● Now the function retrieves according to the latest date.
● Get all history created.
● Updated post function further now sends more commands into the database.
● The errors which are for the leaks and etc. are demonstrated at the front end.
● A number of decimal controls have been added.

'''Problems:'''
● None

'''TO-DO:'''
● Going to continue with the next pages promising new features to the user-end.
● Going to add remaining commands.

''<big><big>Week 6 3/18/2024</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● Connected and tested the new site.
● Added new section at UI showing symbols of alerts.



'''Problems:'''
● New site does not give information yet, working on it (probably going to be solved until this weeks meeting).

'''TO-DO:'''
● Going to add remaining commands.
● Going to include new sites into our UI.

''<big><big>Week 7 3/25/2024</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● The system is updated for allowing the multiple sites(UI).
● The new cite is integrated to the system so now we can see the both sites not as hardcode.
● New Site table and commands created.

'''Problems:'''
● Still site numbers are limited.

'''TO-DO:'''
● Going to add remaining commands.

''<big><big>Week 8 4/1/2024</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● Started working on the delete function.
● Design improvement for add site.

'''Problems:'''
● No problem for the front end for now.

'''TO-DO:'''
● Going to focus on other sections like authentication, settings etc.

''<big><big>Week 9 4/8/2024</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● Now back end code is working by timer.
● New commands added.
● Front-end reconstructed so the refresh function can work
● Delete function is working properly in the front end

'''Problems:'''
● No problem for the back end and front end for now.

'''TO-DO:'''
● Going to focus on other commands.

''<big><big>Week 10 4/15/2024</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● Now we are using the back-end's post function in order to acquire updating data for the user-end.
● Back-end fetching more data from the machine now.

'''Problems:'''
● No problem for the back end and front end for now.

'''TO-DO:'''
● Going to focus on other commands.


''<big><big>Week 11 4/21/2024</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● Back-end added new commands.
● Reports part added for the Front-end

'''Problems:'''
● No problem for the front end for now.
● Some commands are not working on New Berlin.


'''TO-DO:'''
● Going to focus on other commands and presentation.


''<big><big>Week 12 4/28/2024</big></big>''
--------------------------------------------------------------------

'''Accomplishments:'''
● Back-end added new commands.
● Structure of presentation discussed and working on presentation as a group (back-end - front-end).|
● Presentation for front-end finished

'''Problems:'''
● No problem for the front end for now.
● Some commands are not working on New Berlin.

'''TO-DO:'''
● Going to focus on other commands and presentation.

Latest revision as of 02:57, 29 April 2024

Week 1 02/04/2024


Accomplishments:

● Back-end side discussed about code and new back-end member Mert learned the basics of the code.  
●  Code now works on machine-readable but still needs improvements.
●  Front-end side looked at the design goal and planned the structure.
●  System is integrated into computers.

Problems:

● There is an ETX character problem from the machine, back-end facing.
●  Front-end system is going to be built from scratch.

TO-DO:

● Find a solution for the ETX character problem.
● Update inventory report to machine-readable version.
● Basic steps for the skeleton will be implemented. 
● The login page will be designed as the beginning step.

Week 2 02/12/2024


Accomplishments:

● A new database will be designed and created until this week's meeting.
● The second part of the front end was created.
● The skeleton for the front end was created to have a well-organized structure.

Problems:

● Make the database match business requirements.

TO-DO:

● Update the database in the future and also update the code according to the new database.
● Starting to connect the front end with the database from the back end

Week 3 02/18/2024


Accomplishments:

● Get functions created.
● New attributes from the machine added to the database.
● The Front-end version on the git side has been updated.
● Get function connection has been planned.

Problems:

● None for the back-end.

TO-DO:

● Get more attributes from the machine.
● Starting to connect the front end with the database from the back end.

Week 4 02/25/2024


Accomplishments:

● Post function developed (added new commands).
● Front-end and Back-end have been connected with service. 
● The third page has been improved to have a better UI for the user end. 


Problems:

● Some of the commands are hard to store in the database re-design the database.

TO-DO:

● Get more attributes from the machine.
● Starting to connect the front end with the database from the back end.
● Going to continue with the next pages promising new features to the user-end.


Week 5 3/11/2024 - Spring Break


Accomplishments:

● Now the function retrieves according to the latest date.
● Get all history created.
● Updated post function further now sends more commands into the database.
● The errors which are for the leaks and etc. are demonstrated at the front end.
● A number of decimal controls have been added.

Problems:

● None

TO-DO:

● Going to continue with the next pages promising new features to the user-end.
● Going to add remaining commands.

Week 6 3/18/2024


Accomplishments:

● Connected and tested the new site.
● Added new section at UI showing symbols of alerts.


Problems:

● New site does not give information yet, working on it (probably going to be solved until this weeks meeting).

TO-DO:

● Going to add remaining commands.
● Going to include new sites into our UI.

Week 7 3/25/2024


Accomplishments:

● The system is updated for allowing the multiple sites(UI).
● The new cite is integrated to the system so now we can see the both sites not as hardcode.
● New Site table and commands created.

Problems:

● Still site numbers are limited.

TO-DO:

● Going to add remaining commands.

Week 8 4/1/2024


Accomplishments:

● Started working on the delete function.
● Design improvement for add site.

Problems:

● No problem for the front end for now.

TO-DO:

● Going to focus on other sections like authentication, settings etc.

Week 9 4/8/2024


Accomplishments:

● Now back end code is working by timer.
● New commands added.
● Front-end reconstructed so the refresh function can work
● Delete function is working properly in the front end

Problems:

● No problem for the back end and front end for now.

TO-DO:

● Going to focus on other commands.

Week 10 4/15/2024


Accomplishments:

● Now we are using the back-end's post function in order to acquire updating data for the user-end. 
● Back-end fetching more data from the machine now.

Problems:

● No problem for the back end and front end for now.

TO-DO:

● Going to focus on other commands.


Week 11 4/21/2024


Accomplishments:

● Back-end added new commands.
● Reports part added for the Front-end

Problems:

● No problem for the front end for now.
● Some commands are not working on New Berlin.


TO-DO:

● Going to focus on other commands and presentation.


Week 12 4/28/2024


Accomplishments:

● Back-end added new commands.
● Structure of presentation discussed and working on presentation as a group (back-end - front-end).|
● Presentation for front-end finished

Problems:

● No problem for the front end for now.
● Some commands are not working on New Berlin.

TO-DO:

● Going to focus on other commands and presentation.