Refactor OrbitFinder

[thkruz]

User Story

• As a developer of the Keep Track project,
• I want to refactor the OrbitFinder class to reduce its complexity and improve logical flow,
• So that the codebase becomes more maintainable, and methods within the class are more encapsulated and less inter-dependent.

Acceptance Criteria

• Given the current state of the OrbitFinder class with high complexity and interdependent methods,
• When I refactor the class,
• Then the class should exhibit lower complexity, have a more logical flow, and its methods should be more encapsulated and less inter-dependent.

Tasks

• Analyze the current OrbitFinder class to identify areas of high complexity and inter-dependency.
• Design a refactoring plan that outlines the steps to reduce complexity and improve logical flow.
• Refactor methods to be private where appropriate, ensuring encapsulation and reducing unnecessary exposure of class internals.
• Implement changes to reduce the inter-dependency of methods within the class.
• Conduct code reviews and testing to ensure the refactored class maintains its functionality and adheres to project standards.

Commentary

The refactoring of the OrbitFinder class is crucial for the long-term maintainability of the Keep Track codebase. This task should focus on improving code readability and reducing the complexity without altering the external behavior of the class. Collaboration and continuous integration practices should be followed to ensure a smooth transition and effective refactoring process.