Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-25T23:10:49Z

Sdanda: /* Design Strategy */

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* PR Request:- https://github.com/expertiza/reimplementation-back-end/pull/34
* Project Board:- https://github.com/users/surya-prakash-susarla/projects/1

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into signup_topic.rb and waitlist.rb.
* In signed_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy || Implemented || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| get_team_participants || Implemented || It is responsible to get participants in the team signed up for a given topic.
|-
| create_signed_up_team || Implemented || It is responsible for creating a SignedUpTeam instance with given topic_id and team_id if topic is available.
|}
* Add necessary schema migrations for backward compatibility.
* In signup_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || Implemented || It is used to destroy topic from the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| get_team_participants || Implemented || It is used to fetch participants of the team assigned to the topic.
|-
| count_filled_slots || Implemented || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || Implemented || It is used to return the number of slots available for the topic.
|-
| release_team || Implemented || It is used to promote 1 team from the waitlist and assign the topic.
|-
| is_assigned_to_team || Implemented || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || Implemented || It is used to retrieve all teams assigned to the topic.
|-
| is_available || Implemented || It is used to check if the given topic is available for selection by signed_up_teams
|-
| as_json || Implemented || It is responsible for serializing content of SignupTopic instance to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || Implemented || It is used to return the number of waitlisted teams for the particular topic.
|-
| promote_teams_from_waitlist || Implemented || It is used to promote first N teams from the waitlist and assigns them to the topic.
|}
* Refactor instance methods to be more succinct (ex: find_if_topic_available to available, create_sign_up_team to sign_up_team, drop_sign_up_team to drop_team)
* Rename model from “Sign Up Team” to “Signed Up Team” for better clarity.
* Remove is_waitlisted attribute in favor of better querying from the Waitlist model.
* Add tests for error conditions and exit handling.
* Add tests to validate usage of @counter_cache used to count relations.
* Create empty models (if non-existent) and add necessary model-association relations.
* Integrate and delegate waitlist handling from sign_up_topic.
* Add cascading deletes for relations to other models as appropriate.
* Add JSON serializers for REST API responses.
* Add tests using ‘shoulda-matchers’ for more exhaustive tests as appropriate.
* Integrate ‘FactoryBot’ for automatic model record generation during testing.
* Add ‘preference_priority_number’ for backward compatibility during migration.

== E/R Diagram ==
[[File:E_r_diagram.png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.
* Test Cases for signed_up_team.rb model
[[File:Signedup_team_rspec.png|900px]]
* Test Cases for waitlist.rb model
[[File:Waitlist_rspec.png|900px]]
* Test Cases for signup_topic.rb
[[File:Signup_topic_rspec.png|900px]]

File:Signedup team rspec.png

2023-04-25T22:01:20Z

Sdanda: Sdanda uploaded a new version of File:Signedup team rspec.png

File:Waitlist rspec.png

2023-04-25T21:57:29Z

Sdanda: Sdanda uploaded a new version of File:Waitlist rspec.png

File:Waitlist rspec.png

2023-04-25T21:49:25Z

Sdanda: Sdanda uploaded a new version of File:Waitlist rspec.png

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-25T21:48:05Z

Sdanda: /* Test Plan */

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* PR Request:- https://github.com/expertiza/reimplementation-back-end/pull/34
* Project Board:- https://github.com/users/surya-prakash-susarla/projects/1

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into signup_topic.rb and waitlist.rb.
* In signed_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy || Implemented || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| get_team_participants || Implemented || It is responsible to get participants in the team signed up for a given topic.
|-
| create_signed_up_team || Implemented || It is responsible for creating a SignedUpTeam instance with given topic_id and team_id if topic is available.
|}
* Add necessary schema migrations for backward compatibility.
* In signup_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || Implemented || It is used to destroy topic from the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| get_team_participants || Implemented || It is used to fetch participants of the team assigned to the topic.
|-
| count_filled_slots || Implemented || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || Implemented || It is used to return the number of slots available for the topic.
|-
| release_team || Implemented || It is used to promote 1 team from the waitlist and assign the topic.
|-
| is_assigned_to_team || Implemented || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || Implemented || It is used to retrieve all teams assigned to the topic.
|-
| as_json || Implemented || It is responsible for serializing content of SignupTopic instance to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || Implemented || It is used to return the number of waitlisted teams for the particular topic.
|-
| promote_teams_from_waitlist || Implemented || It is used to promote first N teams from the waitlist and assigns them to the topic.
|}
* Refactor instance methods to be more succinct (ex: find_if_topic_available to available, create_sign_up_team to sign_up_team, drop_sign_up_team to drop_team)
* Rename model from “Sign Up Team” to “Signed Up Team” for better clarity.
* Remove is_waitlisted attribute in favor of better querying from the Waitlist model.
* Add tests for error conditions and exit handling.
* Add tests to validate usage of @counter_cache used to count relations.
* Create empty models (if non-existent) and add necessary model-association relations.
* Integrate and delegate waitlist handling from sign_up_topic.
* Add cascading deletes for relations to other models as appropriate.
* Add JSON serializers for REST API responses.
* Add tests using ‘shoulda-matchers’ for more exhaustive tests as appropriate.
* Integrate ‘FactoryBot’ for automatic model record generation during testing.
* Add ‘preference_priority_number’ for backward compatibility during migration.

== E/R Diagram ==
[[File:E_r_diagram.png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.
* Test Cases for signed_up_team.rb model
[[File:Signedup_team_rspec.png|900px]]
* Test Cases for waitlist.rb model
[[File:Waitlist_rspec.png|900px]]
* Test Cases for signup_topic.rb
[[File:Signup_topic_rspec.png|900px]]

File:Waitlist rspec.png

2023-04-25T21:42:41Z

Sdanda:

File:Signedup team rspec.png

2023-04-25T21:42:18Z

Sdanda:

File:Signup topic rspec.png

2023-04-25T21:40:51Z

Sdanda:

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-25T20:39:45Z

Sdanda: /* Design Strategy */

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* PR Request:- https://github.com/expertiza/reimplementation-back-end/pull/34
* Project Board:- https://github.com/users/surya-prakash-susarla/projects/1

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into signup_topic.rb and waitlist.rb.
* In signed_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy || Implemented || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| get_team_participants || Implemented || It is responsible to get participants in the team signed up for a given topic.
|-
| create_signed_up_team || Implemented || It is responsible for creating a SignedUpTeam instance with given topic_id and team_id if topic is available.
|}
* Add necessary schema migrations for backward compatibility.
* In signup_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || Implemented || It is used to destroy topic from the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| get_team_participants || Implemented || It is used to fetch participants of the team assigned to the topic.
|-
| count_filled_slots || Implemented || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || Implemented || It is used to return the number of slots available for the topic.
|-
| release_team || Implemented || It is used to promote 1 team from the waitlist and assign the topic.
|-
| is_assigned_to_team || Implemented || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || Implemented || It is used to retrieve all teams assigned to the topic.
|-
| as_json || Implemented || It is responsible for serializing content of SignupTopic instance to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || Implemented || It is used to return the number of waitlisted teams for the particular topic.
|-
| promote_teams_from_waitlist || Implemented || It is used to promote first N teams from the waitlist and assigns them to the topic.
|}
* Refactor instance methods to be more succinct (ex: find_if_topic_available to available, create_sign_up_team to sign_up_team, drop_sign_up_team to drop_team)
* Rename model from “Sign Up Team” to “Signed Up Team” for better clarity.
* Remove is_waitlisted attribute in favor of better querying from the Waitlist model.
* Add tests for error conditions and exit handling.
* Add tests to validate usage of @counter_cache used to count relations.
* Create empty models (if non-existent) and add necessary model-association relations.
* Integrate and delegate waitlist handling from sign_up_topic.
* Add cascading deletes for relations to other models as appropriate.
* Add JSON serializers for REST API responses.
* Add tests using ‘shoulda-matchers’ for more exhaustive tests as appropriate.
* Integrate ‘FactoryBot’ for automatic model record generation during testing.
* Add ‘preference_priority_number’ for backward compatibility during migration.

== E/R Diagram ==
[[File:E_r_diagram.png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.
* Test Cases for signup_team.rb model
[[File:Test signup team1.png|900px]]
* Test Cases for waitlist.rb model
[[File:Test wait1.png|900px]]
[[File:Test wait2.png|900px]]
[[File:Test wait3.png|900px]]
[[File:Test wait4.png|900px]]

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-25T19:56:38Z

Sdanda: /* Flow Chart */

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* PR Request:- https://github.com/expertiza/reimplementation-back-end/pull/34
* Project Board:- https://github.com/users/surya-prakash-susarla/projects/1

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into signup_topic.rb and waitlist.rb.
* In signed_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| delete_signed_up_team || Implemented || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| get_team_participants || Implemented || It is responsible to get participants in the team signed up for a given topic.
|-
| create_signed_up_team || Implemented || It is responsible for creating a SignedUpTeam instance with given topic_id and team_id if topic is available.
|}
* Add necessary schema migrations for backward compatibility.
* In signup_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || Implemented || It is used to destroy topic from the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| get_team_participants || Implemented || It is used to fetch participants of the team assigned to the topic.
|-
| count_filled_slots || Implemented || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || Implemented || It is used to return the number of slots available for the topic.
|-
| release_team || Implemented || It is used to remove team from the topic and delegate changes to waitlist.
|-
| is_assigned_to_team || Implemented || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || Implemented || It is used to retrieve all teams assigned to the topic.
|-
| as_json || Implemented || It is responsible for serializing content of SignupTopic instance to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || Implemented || It is used to return the number of waitlisted teams for the particular topic.
|-
| promote_teams_from_waitlist || Implemented || It is used to promote first N teams from the waitlist and assigns them to the topic.
|}
* Refactor instance methods to be more succinct (ex: find_if_topic_available to available, create_sign_up_team to sign_up_team, drop_sign_up_team to drop_team)
* Rename model from “Sign Up Team” to “Signed Up Team” for better clarity.
* Remove is_waitlisted attribute in favor of better querying from the Waitlist model.
* Add tests for error conditions and exit handling.
* Add tests to validate usage of @counter_cache used to count relations.
* Create empty models (if non-existent) and add necessary model-association relations.
* Integrate and delegate waitlist handling from sign_up_topic.
* Add cascading deletes for relations to other models as appropriate.
* Add JSON serializers for REST API responses.
* Add tests using ‘shoulda-matchers’ for more exhaustive tests as appropriate.
* Integrate ‘FactoryBot’ for automatic model record generation during testing.
* Add ‘preference_priority_number’ for backward compatibility during migration.

== E/R Diagram ==
[[File:E_r_diagram.png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.
* Test Cases for signup_team.rb model
[[File:Test signup team1.png|900px]]
* Test Cases for waitlist.rb model
[[File:Test wait1.png|900px]]
[[File:Test wait2.png|900px]]
[[File:Test wait3.png|900px]]
[[File:Test wait4.png|900px]]

File:E r diagram.png

2023-04-25T19:43:35Z

Sdanda:

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-25T18:51:36Z

Sdanda: /* Design Strategy */

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* PR Request:- https://github.com/expertiza/reimplementation-back-end/pull/34
* Project Board:- https://github.com/users/surya-prakash-susarla/projects/1

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into signup_topic.rb and waitlist.rb.
* In signed_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| delete_signed_up_team || Implemented || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| get_team_participants || Implemented || It is responsible to get participants in the team signed up for a given topic.
|-
| create_signed_up_team || Implemented || It is responsible for creating a SignedUpTeam instance with given topic_id and team_id if topic is available.
|}
* Add necessary schema migrations for backward compatibility.
* In signup_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || Implemented || It is used to destroy topic from the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| get_team_participants || Implemented || It is used to fetch participants of the team assigned to the topic.
|-
| count_filled_slots || Implemented || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || Implemented || It is used to return the number of slots available for the topic.
|-
| release_team || Implemented || It is used to remove team from the topic and delegate changes to waitlist.
|-
| is_assigned_to_team || Implemented || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || Implemented || It is used to retrieve all teams assigned to the topic.
|-
| as_json || Implemented || It is responsible for serializing content of SignupTopic instance to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || Implemented || It is used to return the number of waitlisted teams for the particular topic.
|-
| promote_teams_from_waitlist || Implemented || It is used to promote first N teams from the waitlist and assigns them to the topic.
|}
* Refactor instance methods to be more succinct (ex: find_if_topic_available to available, create_sign_up_team to sign_up_team, drop_sign_up_team to drop_team)
* Rename model from “Sign Up Team” to “Signed Up Team” for better clarity.
* Remove is_waitlisted attribute in favor of better querying from the Waitlist model.
* Add tests for error conditions and exit handling.
* Add tests to validate usage of @counter_cache used to count relations.
* Create empty models (if non-existent) and add necessary model-association relations.
* Integrate and delegate waitlist handling from sign_up_topic.
* Add cascading deletes for relations to other models as appropriate.
* Add JSON serializers for REST API responses.
* Add tests using ‘shoulda-matchers’ for more exhaustive tests as appropriate.
* Integrate ‘FactoryBot’ for automatic model record generation during testing.
* Add ‘preference_priority_number’ for backward compatibility during migration.

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.
* Test Cases for signup_team.rb model
[[File:Test signup team1.png|900px]]
* Test Cases for waitlist.rb model
[[File:Test wait1.png|900px]]
[[File:Test wait2.png|900px]]
[[File:Test wait3.png|900px]]
[[File:Test wait4.png|900px]]

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-25T18:46:20Z

Sdanda: /* Design Strategy */

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* PR Request:- https://github.com/expertiza/reimplementation-back-end/pull/34
* Project Board:- https://github.com/users/surya-prakash-susarla/projects/1

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| delete_team || TODO || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| serialize_display || TODO || It is responsible for serializing content to JSON format.
|}
* Add necessary schema migrations for backward compatibility.
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || Implemented || It is used to destroy topic from the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| get_team_participants || Implemented || It is used to fetch participants of the team assigned to the topic.
|-
| count_filled_slots || Implemented || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || Implemented || It is used to return the number of slots available for the topic.
|-
| release_team || Implemented || It is used to remove team from the topic and delegate changes to waitlist.
|-
| is_assigned_to_team || Implemented || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || Implemented || It is used to retrieve all teams assigned to the topic.
|-
| as_json || Implemented || It is responsible for serializing content of SignupTopic instance to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || Implemented || It is used to return the number of waitlisted teams for the particular topic.
|-
| promote_teams_from_waitlist || Implemented || It is used to promote first N teams from the waitlist and assigns them to the topic.
|}
* Refactor instance methods to be more succinct (ex: find_if_topic_available to available, create_sign_up_team to sign_up_team, drop_sign_up_team to drop_team)
* Rename model from “Sign Up Team” to “Signed Up Team” for better clarity.
* Remove is_waitlisted attribute in favor of better querying from the Waitlist model.
* Add tests for error conditions and exit handling.
* Add tests to validate usage of @counter_cache used to count relations.
* Create empty models (if non-existent) and add necessary model-association relations.
* Integrate and delegate waitlist handling from sign_up_topic.
* Add cascading deletes for relations to other models as appropriate.
* Add JSON serializers for REST API responess.
* Add tests using ‘shoulda-matchers’ for more exhaustive tests as appropriate.
* Integrate ‘FactoryBot’ for automatic model record generation during testing.
* Add ‘preferene_priority_number’ for backward compatibility during migration.

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.
* Test Cases for signup_team.rb model
[[File:Test signup team1.png|900px]]
* Test Cases for waitlist.rb model
[[File:Test wait1.png|900px]]
[[File:Test wait2.png|900px]]
[[File:Test wait3.png|900px]]
[[File:Test wait4.png|900px]]

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-17T14:51:08Z

Sdanda: /* Team */

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* PR Request:- https://github.com/expertiza/reimplementation-back-end/pull/34
* Project Board:- https://github.com/users/surya-prakash-susarla/projects/1

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| delete_team || TODO || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| serialize_display || TODO || It is responsible for serializing content to JSON format.
|}
* Add necessary schema migrations for backward compatibility.
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || TODO || It is used to destroy topic from the table.
|-
| update_topic || TODO || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| find_team_participants || TODO || It is used to retrieve participants assigned to the topic.
|-
| count_filled_slots || TODO || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || TODO || It is used to return the number of slots available for the topic.
|-
| release_topic || TODO || It is used to remove team from the topic and delegate changes to waitlist.
|-
| is_assigned_to_team || TODO || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || TODO || It is used to retrieve teams assigned to the topic.
|-
| serialize_to_json || TODO || It is responsible for serializing content to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || TODO || It is used to return the number of waitlisted teams for the particular topic.
|-
| remove_teams_from_waitlist || TODO || It is used to remove teams from the waitlist and return the removed teams.
|-
| add_teams_to_waitlist || TODO || It is used to add teams to the waitlist of the topic.
|-
| get_waitlisted_teams || TODO || It is used to retrieve the teams added to waitlist for the topic.
|}
* Refactor instance methods to be more succinct (ex: find_if_topic_available to available, create_sign_up_team to sign_up_team, drop_sign_up_team to drop_team)
* Rename model from “Sign Up Team” to “Signed Up Team” for better clarity.
* Remove is_waitlisted attribute in favor of better querying from the Waitlist model.
* Add tests for error conditions and exit handling.
* Add tests to validate usage of @counter_cache used to count relations.
* Create empty models (if non-existent) and add necessary model-association relations.
* Integrate and delegate waitlist handling from sign_up_topic.
* Add cascading deletes for relations to other models as appropriate.
* Add JSON serializers for REST API responess.
* Add tests using ‘shoulda-matchers’ for more exhaustive tests as appropriate.
* Integrate ‘FactoryBot’ for automatic model record generation during testing.
* Add ‘preferene_priority_number’ for backward compatibility during migration.

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.
* Test Cases for signup_team.rb model
[[File:Test signup team1.png|900px]]
* Test Cases for waitlist.rb model
[[File:Test wait1.png|900px]]
[[File:Test wait2.png|900px]]
[[File:Test wait3.png|900px]]
[[File:Test wait4.png|900px]]

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-14T19:15:47Z

Sdanda: /* Test Plan */

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* PR Request:- https://github.com/expertiza/reimplementation-back-end/pull/34

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| delete_team || TODO || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| serialize_display || TODO || It is responsible for serializing content to JSON format.
|}
* Add necessary schema migrations for backward compatibility.
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || TODO || It is used to destroy topic from the table.
|-
| update_topic || TODO || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| find_team_participants || TODO || It is used to retrieve participants assigned to the topic.
|-
| count_filled_slots || TODO || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || TODO || It is used to return the number of slots available for the topic.
|-
| release_topic || TODO || It is used to remove team from the topic and delegate changes to waitlist.
|-
| is_assigned_to_team || TODO || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || TODO || It is used to retrieve teams assigned to the topic.
|-
| serialize_to_json || TODO || It is responsible for serializing content to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || TODO || It is used to return the number of waitlisted teams for the particular topic.
|-
| remove_teams_from_waitlist || TODO || It is used to remove teams from the waitlist and return the removed teams.
|-
| add_teams_to_waitlist || TODO || It is used to add teams to the waitlist of the topic.
|-
| get_waitlisted_teams || TODO || It is used to retrieve the teams added to waitlist for the topic.
|}
* Refactor instance methods to be more succinct (ex: find_if_topic_available to available, create_sign_up_team to sign_up_team, drop_sign_up_team to drop_team)
* Rename model from “Sign Up Team” to “Signed Up Team” for better clarity.
* Remove is_waitlisted attribute in favor of better querying from the Waitlist model.
* Add tests for error conditions and exit handling.
* Add tests to validate usage of @counter_cache used to count relations.
* Create empty models (if non-existent) and add necessary model-association relations.
* Integrate and delegate waitlist handling from sign_up_topic.
* Add cascading deletes for relations to other models as appropriate.
* Add JSON serializers for REST API responess.
* Add tests using ‘shoulda-matchers’ for more exhaustive tests as appropriate.
* Integrate ‘FactoryBot’ for automatic model record generation during testing.
* Add ‘preferene_priority_number’ for backward compatibility during migration.

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.
* Test Cases for signup_team.rb model
[[File:Test signup team1.png|900px]]
* Test Cases for waitlist.rb model
[[File:Test wait1.png|900px]]
[[File:Test wait2.png|900px]]
[[File:Test wait3.png|900px]]
[[File:Test wait4.png|900px]]

File:Test wait4.png

2023-04-14T19:04:28Z

Sdanda:

File:Test wait3.png

2023-04-14T19:04:11Z

Sdanda:

File:Test wait2.png

2023-04-14T19:03:52Z

Sdanda:

File:Test wait1.png

2023-04-14T19:03:35Z

Sdanda:

File:Test signup team1.png

2023-04-14T19:03:10Z

Sdanda:

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-13T00:06:51Z

Sdanda: /* Team */

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* PR Request:- https://github.com/expertiza/reimplementation-back-end/pull/34

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| delete_team || TODO || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| serialize_display || TODO || It is responsible for serializing content to JSON format.
|}
* Add necessary schema migrations for backward compatibility.
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || TODO || It is used to destroy topic from the table.
|-
| update_topic || TODO || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| find_team_participants || TODO || It is used to retrieve participants assigned to the topic.
|-
| count_filled_slots || TODO || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || TODO || It is used to return the number of slots available for the topic.
|-
| release_topic || TODO || It is used to remove team from the topic and delegate changes to waitlist.
|-
| is_assigned_to_team || TODO || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || TODO || It is used to retrieve teams assigned to the topic.
|-
| serialize_to_json || TODO || It is responsible for serializing content to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || TODO || It is used to return the number of waitlisted teams for the particular topic.
|-
| remove_teams_from_waitlist || TODO || It is used to remove teams from the waitlist and return the removed teams.
|-
| add_teams_to_waitlist || TODO || It is used to add teams to the waitlist of the topic.
|-
| get_waitlisted_teams || TODO || It is used to retrieve the teams added to waitlist for the topic.
|}
* Refactor instance methods to be more succinct (ex: find_if_topic_available to available, create_sign_up_team to sign_up_team, drop_sign_up_team to drop_team)
* Rename model from “Sign Up Team” to “Signed Up Team” for better clarity.
* Remove is_waitlisted attribute in favor of better querying from the Waitlist model.
* Add tests for error conditions and exit handling.
* Add tests to validate usage of @counter_cache used to count relations.
* Create empty models (if non-existent) and add necessary model-association relations.
* Integrate and delegate waitlist handling from sign_up_topic.
* Add cascading deletes for relations to other models as appropriate.
* Add JSON serializers for REST API responess.
* Add tests using ‘shoulda-matchers’ for more exhaustive tests as appropriate.
* Integrate ‘FactoryBot’ for automatic model record generation during testing.
* Add ‘preferene_priority_number’ for backward compatibility during migration.

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-12T00:55:58Z

Sdanda:

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| delete_team || TODO || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| serialize_display || TODO || It is responsible for serializing content to JSON format.
|}
* Add necessary schema migrations for backward compatibility.
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || TODO || It is used to destroy topic from the table.
|-
| update_topic || TODO || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| find_team_participants || TODO || It is used to retrieve participants assigned to the topic.
|-
| count_filled_slots || TODO || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || TODO || It is used to return the number of slots available for the topic.
|-
| release_topic || TODO || It is used to remove team from the topic and delegate changes to waitlist.
|-
| is_assigned_to_team || TODO || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || TODO || It is used to retrieve teams assigned to the topic.
|-
| serialize_to_json || TODO || It is responsible for serializing content to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || TODO || It is used to return the number of waitlisted teams for the particular topic.
|-
| remove_teams_from_waitlist || TODO || It is used to remove teams from the waitlist and return the removed teams.
|-
| add_teams_to_waitlist || TODO || It is used to add teams to the waitlist of the topic.
|-
| get_waitlisted_teams || TODO || It is used to retrieve the teams added to waitlist for the topic.
|}
* Refactor instance methods to be more succinct (ex: find_if_topic_available to available, create_sign_up_team to sign_up_team, drop_sign_up_team to drop_team)
* Rename model from “Sign Up Team” to “Signed Up Team” for better clarity.
* Remove is_waitlisted attribute in favor of better querying from the Waitlist model.
* Add tests for error conditions and exit handling.
* Add tests to validate usage of @counter_cache used to count relations.
* Create empty models (if non-existent) and add necessary model-association relations.
* Integrate and delegate waitlist handling from sign_up_topic.
* Add cascading deletes for relations to other models as appropriate.
* Add JSON serializers for REST API responess.
* Add tests using ‘shoulda-matchers’ for more exhaustive tests as appropriate.
* Integrate ‘FactoryBot’ for automatic model record generation during testing.
* Add ‘preferene_priority_number’ for backward compatibility during migration.

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.

CSC/ECE 517 Spring 2023

2023-04-12T00:54:47Z

Sdanda: /* OSS Projects */

== OSS Projects ==

[[CSC/ECE 517 Spring_2023 -E2306. Refactor user_controller.rb, user.rb and its child classes]]

[[CSC/ECE 517 Spring_2023 - E2320. Reimplement the Question hierarchy]]

[[CSC/ECE 517 Spring_2023 - E2312 + E2313. Reimplement response.rb and responses_controller.rb]]

[[CSC/ECE 517 Spring_2023 - NTNX-1. Support provisioning MongoDb via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring_2023 - E2316. Reimplement sign_up_sheet_controller.rb]]

[[CSC/ECE 517 Spring_2023 - E2315. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb]]

[[CSC/ECE 517 Spring_2023 - E2339. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb (Project 4)]]

[[CSC/ECE 517 Spring_2023 - E2323. Refactor DueDate functionality from assignment.rb]]

[[CSC/ECE 517 Spring 2023 - E2317: Reimplement participant.rb]]

[[CSC/ECE 517 Spring 2023 - E2314. Reimplement the response map hierarchy]]

[[CSC/ECE 517 Spring 2023- NTNX-4. Extend NDB operator provision postregresql aws]]

[[CSC/ECE 517 Spring 2023 - E2321. Reimplement QuestionnairesController and QuestionsController]]

[[CSC/ECE 517 Spring 2023 - E2305. Grading audit trail]]

[[CSC/ECE 517 Spring 2023 - E2329. Grading audit trail(Project 4)]]

[[CSC/ECE 517 Spring 2023 - E2309. Refactor Node model and its subclasses]]

[[CSC/ECE 517 Spring 2023 - NTNX-2. Support provisioning mySQL databases via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring 2023 - E2300. Refactor E1858. Github metrics integration]]

[[CSC/ECE 517 Sping 2023 - E2322: Refactor Questionnaire View to display Bookmark Rating]]

[[CSC/ECE 517 Spring 2023 - NTNX-3. Refactor models to keep profiles (software, compute, network, etc) as optional and use default if not specified]]

[[CSC/ECE_517_Spring_2023_-_E2301._Refactor_review_maping_helper]]

[[CSC/ECE_517_Spring_2023_-_E2330._Reimplementation_Invitation_Controller]]

[[CSC/ECE_517_Spring_2023_-_E2337._Reimplement_node_hierarchy]]

[[CSC/ECE_517_Spring_2023_-E2339._Reimplement signed_up_teams_controller and sign_up_topics_controller.rb]]

[[CSC/ECE_517_Spring_2023_-_E2320._Reimplement the Question Hierarchy]]

[[CSC/ECE_517_Spring_2023 - E2341. UI for Participants.rb]]

[[CSC/ECE_517_Spring_2023_-_E2336._Reimplement_response.rb]]

[[CSC/ECE_517_Spring_2023_-_E2345._Reimplement_QuestionnairesController_and_QuestionsController]]

CSC/ECE 517 Spring 2023 - E2340. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-06T19:27:48Z

Sdanda: /* Design Strategy */

CSC/ECE 517 Spring 2023 - E2340. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-05T22:10:16Z

Sdanda:

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| delete_team || TODO || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| serialize_display || TODO || It is responsible for serializing content to JSON format.
|}
* Add necessary schema migrations for backward compatibility.
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || TODO || It is used to destroy topic from the table.
|-
| update_topic || TODO || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| find_team_participants || TODO || It is used to retrieve participants assigned to the topic.
|-
| count_filled_slots || TODO || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || TODO || It is used to return the number of slots available for the topic.
|-
| release_topic || TODO || It is used to remove team from the topic and delegate changes to waitlist.
|-
| is_assigned_to_team || TODO || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || TODO || It is used to retrieve teams assigned to the topic.
|-
| serialize_to_json || TODO || It is responsible for serializing content to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || TODO || It is used to return the number of waitlisted teams for the particular topic.
|-
| remove_teams_from_waitlist || TODO || It is used to remove teams from the waitlist and return the removed teams.
|-
| add_teams_to_waitlist || TODO || It is used to add teams to the waitlist of the topic.
|-
| get_waitlisted_teams || TODO || It is used to retrieve the teams added to waitlist for the topic.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.

CSC/ECE 517 Spring 2023 - E2340. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-05T21:57:51Z

Sdanda: Created page with "== Team == * Mentor - Krishna Saurabh Vankadaru * Sai Venkata Varun Danda * Saketh Vangala * Surya Prakash Susarla * Pull Request - https://github.com/expertiza/reimplementat..."

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* Pull Request - https://github.com/expertiza/reimplementation-back-end/pull/19
* Project Board - https://github.com/users/SakethVangala11/projects/1/views/1

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* Thorough RSpec tests are required for the reimplemented models.
* Change all references of sign_up_teams to signed_up_teams.
* Fix all code review comments.
* There is no designated waitlist model to handle scenarios regarding waitlisting, upgrading and handling multiple registrations.
* Some methods have readability concerns that needs to be refactored.
* There are ambiguous class and instance methods that can be optimized for better reusability.
* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| delete_team || TODO || It is responsible for deleting the team from the table and delegating any changes in topic.
|-
| serialize_display || TODO || It is responsible for serializing content to JSON format.
|}
* Add necessary schema migrations for backward compatibility.
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| destroy_topic || TODO || It is used to destroy topic from the table.
|-
| update_topic || TODO || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| find_team_participants || TODO || It is used to retrieve participants assigned to the topic.
|-
| count_filled_slots || TODO || It is used to return the number of slots filled for the topic.
|-
| count_available_slots || TODO || It is used to return the number of slots available for the topic.
|-
| release_topic || TODO || It is used to remove team from the topic and delegate changes to waitlist.
|-
| is_assigned_to_team || TODO || It is used to validate if the topic is assigned to the team
|-
| get_assigned_teams || TODO || It is used to retrieve teams assigned to the topic.
|-
| serialize_to_json || TODO || It is responsible for serializing content to JSON format.
|}

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| count_waitlisted_teams || TODO || It is used to return the number of waitlisted teams for the particular topic.
|-
| remove_teams_from_waitlist || TODO || It is used to remove teams from the waitlist and return the removed teams.
|-
| add_teams_to_waitlist || TODO || It is used to add teams to the waitlist of the topic.
|-
| get_waitlisted_teams || TODO || It is used to retrieve the teams added to waitlist for the topic.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

* Upgrade RSpec test cases for sign_up_team.rb to validate delete_team and get_participants.
* Upgrade and add RSpec test cases for sign_up_topic.rb to find participants, handle slot availability and assignment status.
* Create RSpec test cases for waitlist.rb to validate adding teams to waitlist, remove teams from waitlist and query status of team's waitlist.
* Add general RSpec test cases for error handling and validate JSON serialization.

CSC/ECE 517 Spring 2023

2023-04-05T21:57:38Z

Sdanda: /* OSS Projects */

== OSS Projects ==
[[CSC/ECE 517 Spring_2023 -E2306. Refactor user_controller.rb, user.rb and its child classes]]

[[CSC/ECE 517 Spring_2023 - E2320. Reimplement the Question hierarchy]]

[[CSC/ECE 517 Spring_2023 - E2312 + E2313. Reimplement response.rb and responses_controller.rb]]

[[CSC/ECE 517 Spring_2023 - NTNX-1. Support provisioning MongoDb via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring_2023 - E2316. Reimplement sign_up_sheet_controller.rb]]

[[CSC/ECE 517 Spring_2023 - E2315. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb]]

[[CSC/ECE 517 Spring_2023 - E2340. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb (Project 4)]]

[[CSC/ECE 517 Spring_2023 - E2323. Refactor DueDate functionality from assignment.rb]]

[[CSC/ECE 517 Spring 2023 - E2317: Reimplement participant.rb]]

[[CSC/ECE 517 Spring 2023 - E2314. Reimplement the response map hierarchy]]

[[CSC/ECE 517 Spring 2023- NTNX-4. Extend NDB operator provision postregresql aws]]

[[CSC/ECE 517 Spring 2023 - E2321. Reimplement QuestionnairesController and QuestionsController]]

[[CSC/ECE 517 Spring 2023 - E2305. Grading audit trail]]

[[CSC/ECE 517 Spring 2023 - E2309. Refactor Node model and its subclasses]]

[[CSC/ECE 517 Spring 2023 - NTNX-2. Support provisioning mySQL databases via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring 2023 - E2300. Refactor E1858. Github metrics integration]]

[[CSC/ECE 517 Sping 2023 - E2322: Refactor Questionnaire View to display Bookmark Rating]]

[[CSC/ECE 517 Spring 2023 - NTNX-3. Refactor models to keep profiles (software, compute, network, etc) as optional and use default if not specified]]

[[CSC/ECE_517_Spring_2023_-_E2301._Refactor_review_maping_helper]]

[[CSC/ECE_517_Spring_2023_-_E2337._Reimplement_node_hierarchy]]

[[CSC/ECE_517_Spring_2023_-_E2320._Reimplement the Question Hierarchy]]

CSC/ECE 517 Spring 2023

2023-04-05T21:55:36Z

Sdanda: /* OSS Projects */

== OSS Projects ==
[[CSC/ECE 517 Spring_2023 -E2306. Refactor user_controller.rb, user.rb and its child classes]]

[[CSC/ECE 517 Spring_2023 - E2320. Reimplement the Question hierarchy]]

[[CSC/ECE 517 Spring_2023 - E2312 + E2313. Reimplement response.rb and responses_controller.rb]]

[[CSC/ECE 517 Spring_2023 - NTNX-1. Support provisioning MongoDb via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring_2023 - E2316. Reimplement sign_up_sheet_controller.rb]]

[[CSC/ECE 517 Spring_2023 - E2315. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb]]

[[CSC/ECE 517 Spring_2023 - E2339. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb (Project 4)]]

[[CSC/ECE 517 Spring_2023 - E2323. Refactor DueDate functionality from assignment.rb]]

[[CSC/ECE 517 Spring 2023 - E2317: Reimplement participant.rb]]

[[CSC/ECE 517 Spring 2023 - E2314. Reimplement the response map hierarchy]]

[[CSC/ECE 517 Spring 2023- NTNX-4. Extend NDB operator provision postregresql aws]]

[[CSC/ECE 517 Spring 2023 - E2321. Reimplement QuestionnairesController and QuestionsController]]

[[CSC/ECE 517 Spring 2023 - E2305. Grading audit trail]]

[[CSC/ECE 517 Spring 2023 - E2309. Refactor Node model and its subclasses]]

[[CSC/ECE 517 Spring 2023 - NTNX-2. Support provisioning mySQL databases via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring 2023 - E2300. Refactor E1858. Github metrics integration]]

[[CSC/ECE 517 Sping 2023 - E2322: Refactor Questionnaire View to display Bookmark Rating]]

[[CSC/ECE 517 Spring 2023 - NTNX-3. Refactor models to keep profiles (software, compute, network, etc) as optional and use default if not specified]]

[[CSC/ECE_517_Spring_2023_-_E2301._Refactor_review_maping_helper]]

[[CSC/ECE_517_Spring_2023_-_E2337._Reimplement_node_hierarchy]]

[[CSC/ECE_517_Spring_2023_-_E2320._Reimplement the Question Hierarchy]]

CSC/ECE 517 Spring 2023

2023-04-05T21:55:04Z

Sdanda: /* OSS Projects */

== OSS Projects ==
[[CSC/ECE 517 Spring_2023 -E2306. Refactor user_controller.rb, user.rb and its child classes]]

[[CSC/ECE 517 Spring_2023 - E2320. Reimplement the Question hierarchy]]

[[CSC/ECE 517 Spring_2023 - E2312 + E2313. Reimplement response.rb and responses_controller.rb]]

[[CSC/ECE 517 Spring_2023 - NTNX-1. Support provisioning MongoDb via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring_2023 - E2316. Reimplement sign_up_sheet_controller.rb]]

[[CSC/ECE 517 Spring_2023 - E2315. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb]]

[[CSC/ECE 517 Spring_2023 - E2340. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb (Project 4)]]

[[CSC/ECE 517 Spring_2023 - E2323. Refactor DueDate functionality from assignment.rb]]

[[CSC/ECE 517 Spring 2023 - E2317: Reimplement participant.rb]]

[[CSC/ECE 517 Spring 2023 - E2314. Reimplement the response map hierarchy]]

[[CSC/ECE 517 Spring 2023- NTNX-4. Extend NDB operator provision postregresql aws]]

[[CSC/ECE 517 Spring 2023 - E2321. Reimplement QuestionnairesController and QuestionsController]]

[[CSC/ECE 517 Spring 2023 - E2305. Grading audit trail]]

[[CSC/ECE 517 Spring 2023 - E2309. Refactor Node model and its subclasses]]

[[CSC/ECE 517 Spring 2023 - NTNX-2. Support provisioning mySQL databases via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring 2023 - E2300. Refactor E1858. Github metrics integration]]

[[CSC/ECE 517 Sping 2023 - E2322: Refactor Questionnaire View to display Bookmark Rating]]

[[CSC/ECE 517 Spring 2023 - NTNX-3. Refactor models to keep profiles (software, compute, network, etc) as optional and use default if not specified]]

[[CSC/ECE_517_Spring_2023_-_E2301._Refactor_review_maping_helper]]

[[CSC/ECE_517_Spring_2023_-_E2337._Reimplement_node_hierarchy]]

[[CSC/ECE_517_Spring_2023_-_E2320._Reimplement the Question Hierarchy]]

CSC/ECE 517 Spring 2023 - E2339. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb (Project 4)

2023-04-05T21:44:24Z

Sdanda: created design doc for Prog 4

CSC/ECE 517 Spring 2023

2023-04-05T20:44:23Z

Sdanda: /* OSS Projects */

== OSS Projects ==
[[CSC/ECE 517 Spring_2023 -E2306. Refactor user_controller.rb, user.rb and its child classes]]

[[CSC/ECE 517 Spring_2023 - E2320. Reimplement the Question hierarchy]]

[[CSC/ECE 517 Spring_2023 - E2312 + E2313. Reimplement response.rb and responses_controller.rb]]

[[CSC/ECE 517 Spring_2023 - NTNX-1. Support provisioning MongoDb via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring_2023 - E2316. Reimplement sign_up_sheet_controller.rb]]

[[CSC/ECE 517 Spring_2023 - E2315. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb]]

[[CSC/ECE 517 Spring_2023 - E2339. Reimplement signed_up_team.rb, sign_up_topic.rb, sign_up_sheet.rb (Project 4)]]

[[CSC/ECE 517 Spring_2023 - E2323. Refactor DueDate functionality from assignment.rb]]

[[CSC/ECE 517 Spring 2023 - E2317: Reimplement participant.rb]]

[[CSC/ECE 517 Spring 2023 - E2314. Reimplement the response map hierarchy]]

[[CSC/ECE 517 Spring 2023- NTNX-4. Extend NDB operator provision postregresql aws]]

[[CSC/ECE 517 Spring 2023 - E2321. Reimplement QuestionnairesController and QuestionsController]]

[[CSC/ECE 517 Spring 2023 - E2305. Grading audit trail]]

[[CSC/ECE 517 Spring 2023 - E2309. Refactor Node model and its subclasses]]

[[CSC/ECE 517 Spring 2023 - NTNX-2. Support provisioning mySQL databases via NDB Kubernetes Operator]]

[[CSC/ECE 517 Spring 2023 - E2300. Refactor E1858. Github metrics integration]]

[[CSC/ECE 517 Sping 2023 - E2322: Refactor Questionnaire View to display Bookmark Rating]]

[[CSC/ECE 517 Spring 2023 - NTNX-3. Refactor models to keep profiles (software, compute, network, etc) as optional and use default if not specified]]

[[CSC/ECE_517_Spring_2023_-_E2301._Refactor_review_maping_helper]]

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-27T22:20:48Z

Sdanda: /* Team */

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* Pull Request - https://github.com/expertiza/reimplementation-back-end/pull/19
* Project Board - https://github.com/users/SakethVangala11/projects/1/views/1

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}

[[File:signupteam-1.jpeg]]
[[File:signupteam-2.jpeg]]

* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}

[[File:signuptopic-1.jpeg]]
[[File:signuptopic-2.jpeg]]

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly. We have attached the unit test assessment video as shown here https://vimeo.com/810685088

[[File:unit_test-1.jpeg]]
[[File:unit_test-2.jpeg]]
[[File:unit_test-3.jpeg]]
[[File:unit_test-4.jpeg]]

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-23T21:49:06Z

Sdanda: /* Project Description */

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* Pull Request - https://github.com/expertiza/reimplementation-back-end/pull/19

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to reimplement the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}

[[File:signupteam-1.jpeg]]
[[File:signupteam-2.jpeg]]

* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}

[[File:signuptopic-1.jpeg]]
[[File:signuptopic-2.jpeg]]

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly. We have attached the unit test assessment video as shown here https://vimeo.com/810685088

[[File:unit_test-1.jpeg]]
[[File:unit_test-2.jpeg]]
[[File:unit_test-3.jpeg]]
[[File:unit_test-4.jpeg]]

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-23T21:48:16Z

Sdanda: /* Project Description */

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* Pull Request - https://github.com/expertiza/reimplementation-back-end/pull/19

== Project Description ==

The objective of the project is to reimplement the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to refactor the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}

[[File:signupteam-1.jpeg]]
[[File:signupteam-2.jpeg]]

* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}

[[File:signuptopic-1.jpeg]]
[[File:signuptopic-2.jpeg]]

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly. We have attached the unit test assessment video as shown here https://vimeo.com/810685088

[[File:unit_test-1.jpeg]]
[[File:unit_test-2.jpeg]]
[[File:unit_test-3.jpeg]]
[[File:unit_test-4.jpeg]]

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-22T21:34:57Z

Sdanda: /* Test Plan */

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* Pull Request - https://github.com/expertiza/reimplementation-back-end/pull/19

== Project Description ==

The objective of the project is to refactor the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to refactor the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}

[[File:signupteam-1.jpeg]]
[[File:signupteam-2.jpeg]]

* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}

[[File:signuptopic-1.jpeg]]
[[File:signuptopic-2.jpeg]]

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly. We have attached the unit test assessment video as shown here https://vimeo.com/810685088

[[File:unit_test-1.jpeg]]
[[File:unit_test-2.jpeg]]
[[File:unit_test-3.jpeg]]
[[File:unit_test-4.jpeg]]

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-22T21:34:31Z

Sdanda: /* Team */

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* Pull Request - https://github.com/expertiza/reimplementation-back-end/pull/19

== Project Description ==

The objective of the project is to refactor the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to refactor the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}

[[File:signupteam-1.jpeg]]
[[File:signupteam-2.jpeg]]

* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}

[[File:signuptopic-1.jpeg]]
[[File:signuptopic-2.jpeg]]

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly. We have attached the unit test assessment video as shown [https://vimeo.com/810685088 here]

[[File:unit_test-1.jpeg]]
[[File:unit_test-2.jpeg]]
[[File:unit_test-3.jpeg]]
[[File:unit_test-4.jpeg]]

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-22T21:34:01Z

Sdanda: /* Team */

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla
* PR Link - https://github.com/expertiza/reimplementation-back-end/pull/19

== Project Description ==

The objective of the project is to refactor the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to refactor the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}

[[File:signupteam-1.jpeg]]
[[File:signupteam-2.jpeg]]

* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}

[[File:signuptopic-1.jpeg]]
[[File:signuptopic-2.jpeg]]

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly. We have attached the unit test assessment video as shown [https://vimeo.com/810685088 here]

[[File:unit_test-1.jpeg]]
[[File:unit_test-2.jpeg]]
[[File:unit_test-3.jpeg]]
[[File:unit_test-4.jpeg]]

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-22T21:22:36Z

Sdanda: /* Design Strategy */

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla

== Project Description ==

The objective of the project is to refactor the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to refactor the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}

[[File:signupteam-1.jpeg]]
[[File:signupteam-2.jpeg]]

* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}

[[File:signuptopic-1.jpeg]]
[[File:signuptopic-2.jpeg]]

* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly. We have attached the unit test assessment video as shown [https://vimeo.com/810685088 here]

[[File:unit_test-1.jpeg]]
[[File:unit_test-2.jpeg]]
[[File:unit_test-3.jpeg]]
[[File:unit_test-4.jpeg]]

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.

File:Signuptopic-2.jpeg

2023-03-22T21:20:41Z

Sdanda:

File:Signuptopic-1.jpeg

2023-03-22T21:20:27Z

Sdanda:

File:Signupteam-2.jpeg

2023-03-22T21:20:10Z

Sdanda:

File:Signupteam-1.jpeg

2023-03-22T21:19:55Z

Sdanda:

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-22T21:17:11Z

Sdanda: /* Test Plan */

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla

== Project Description ==

The objective of the project is to refactor the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to refactor the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}
* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly. We have attached the unit test assessment video as shown [https://vimeo.com/810685088 here]

[[File:unit_test-1.jpeg]]
[[File:unit_test-2.jpeg]]
[[File:unit_test-3.jpeg]]
[[File:unit_test-4.jpeg]]

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.

File:Unit test-4.jpeg

2023-03-22T21:15:13Z

Sdanda:

File:Unit test-3.jpeg

2023-03-22T21:14:58Z

Sdanda:

File:Unit test-2.jpeg

2023-03-22T21:14:36Z

Sdanda:

File:Unit test-1.jpeg

2023-03-22T21:14:19Z

Sdanda:

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-22T21:04:18Z

Sdanda: /* Test Plan */

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla

== Project Description ==

The objective of the project is to refactor the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to refactor the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}
* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly. We have attached the unit test assessment video as shown [https://vimeo.com/810685088 here]

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-22T20:53:09Z

Sdanda: added team members

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Team ==

* Mentor - Krishna Saurabh Vankadaru
* Sai Venkata Varun Danda
* Saketh Vangala
* Surya Prakash Susarla

== Project Description ==

The objective of the project is to refactor the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to refactor the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}
* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly.

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.

CSC/ECE 517 Spring 2023 - E2315. Reimplement signed up team.rb, sign up topic.rb, sign up sheet.rb

2023-03-22T14:51:48Z

Sdanda: /* Future Plan */

== Background ==

Expertiza is an open source software written using Ruby on Rails which functions as a learning management software system. It has many different functions and abilities including the ability to create assignments, quizzes, assignment groups and topics, and also a complete mechanism for providing peer reviews and feedback for other groups and other teammates. It includes functionality to assign a project topic for each team. If it is not available, then it waitlists the team in case if the topic is available. The sign_up_team.rb, sign_up_topic.rb and sign_up_sheet.rb are the model classes in this project to provide this functionality.

== Project Description ==

The objective of the project is to refactor the following Ruby on Rails model classes in the existing project:- SignUpTeam, SignUpTopic and SignUpSheet. SignUpTeam model class represents a signed-up team for a particular sign-up topic in a specific assignment. SignUpTopic model class represents a topic that can be signed up for in a course assignment. SignUpSheet class stores the logic for creating a signed_up_team for a topic for a particular assignment. This class is being used as a module having all class methods.

The task is to refactor the existing code present in these model files and implement them in a new repository. Since the project is implemented from scratch, there are various aspects of the project that have to be implemented and therefore unit test cases are implemented to test the implementation.

== Issue Description ==

* The SignedUpTeam class has methods that handle multiple responsibilities, including finding participants and teams, releasing topics, and removing signed up teams. This violates the single responsibility principle and makes the class harder to understand and maintain.
* Some of the queries in the class use complex SQL statements and multiple joins, which can make them hard to read and understand. These complex SQL queries in the code could be simplified and made more readable by using ActiveRecord's query interface instead.
* The same code is repeated in multiple methods, such as the code to find signed up teams for a given topic. This violates the Don't Repeat Yourself (DRY) principle and can make the code harder to maintain.

== Design Strategy ==

* To tackle the mentioned problem, three model class files namely sign_up_team.rb, sign_up_topic.rb and waitlist.rb are implemented.
* sign_up_sheet.rb is removed because the class methods can be refactored into sign_up_topic.rb and waitlist.rb.
* In sign_up_team.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_sign_up_team || Implemented || It is responsible for creating a new sign up team in the table.
|-
| delete_sign_up_team || Implemented || It is responsible for deleting a sign up team from the table.
|-
| find_team_participants || Implemented || It is used to get participants in the team signed up for the given topic.
|-
| update_sign_up_team || TODO || It is responsible for adding/removing a team member from the sign up team and updating the changes in the table.
|-
| release_topics || TODO || It is used to update the waitlist and release topics.
|}
* In sign_up_topic.rb, the following functionality are being implemented:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| create_topic || Implemented || It is used to create a new topic in the table.
|-
| update_topic || Implemented || It is used to modify the attributes like description, max_choosers or category in the table.
|-
| delete_topic || Implemented || It is used to remove the sign up topic from the table.
|-
| format_for_display || Implemented || It is used to return the formatted topic name.
|-
| find_if_topic_available? || Implemented || It is used to fetch available topic for further selection. A topic is considered available if the total number of teams assigned to the topic are less than the maximum choosers allowed.
|-
| update_waitlisted_users || TODO || It is used to send update to all waitlisted users regarding waitlist changes.
|}
* In waitlist.rb, the following functionality are yet to be implemented in next phase:-
*;
{| class="wikitable" style="margin-left:40px"
|-
! Method Name !! Status !! Description
|-
| add_team_to_waitlist || TODO || It is used to add a sign up team to the topic’s waitlist.
|-
| assign_topic_to_team || TODO || It is used to assign the topic to a team in the waitlist.
|-
| remove_team_waitlist || TODO || It is used to remove a sign up team from the topic’s waitlist.
|-
| destroy_waitlist || TODO || It is used to remove all the sign up teams from the topic’s waitlist.
|}

== Flow Chart ==
[[File:Oss_proj3.drawio_(1).png]]

== Test Plan ==

We have implemented test cases using RSpec for different validation checks for both sign_up_team.rb and sign_up_topic.rb. The other test cases include 'create' tests that validate whether the utility methods can create the records in the table as expected. Moreover, 'update' test cases are included to validate whether the modifications are updated in the table. Finally, we perform 'destroy' tests to validate whether the record is deleted from the table. We also added unit tests that validate other instance methods, such as format_for_display, in both SignUpTeam and SignUpTopic model classes. We created helper stubs for the new methods yet to be implemented to perform the testing process smoothly.

== Future Plan ==

The future scope of this project is to implement waitlist.rb model class that handles the functions related to adding/removing sign up teams to the waitlist for each topic. There are other instance methods in both sign_up_team.rb and sign_up_topic.rb that requires implementation. But, since they are dependent on other model classes, we have added them to our TODO list to implement them in the future.