Brief Description

This activity amounts to $5\%($see the course syllabus$)$ of the entire course grade. So$,$ whatever you obtain as a score will be scaled to this value for final grade computation.

With this class activity, we aim to review some object$-$orientation concepts based on the knowledge you have acquired in COMP $155-$ Object$-$Oriented Programming. You will find a grading scheme at the end of this document $-$ to guide you on instructor's expectations while preparing your submission.

Problem Definitions

Implementation of Design Options: This problem is adapted from Section $2\mathrm{.}9$ of our required text $($starting on page $57).$ Assuming you are a software analyst on a project that requires extensive $($in millions$)$ rotation of points and computation of the distance between any two points and performance is key to the success of the project. However, to realize this, you are allowed to store a point either in its Polar or Cartesian coordinates formats. For example, you may choose to store a point in its Polar form but provide interfaces to convert or store it in its Cartesian form and vice$-$versa. In its Cartesian state, you will be storing the $\text{'}x\text{'}$ and $\text{'}y\text{'}$ coordinates of the point while you will be storing its distance from a reference point $(r)$ and theta $-$ an angle from the reference direction $()$ in its Polar state.

$r=\sqrt[\phantom{2}]{x^2+y^2},$

$=ta{n}^{-1}(\frac{y}{x}),$

$x=r*cos,$

$y=r*sin$

$1$

COMP $370$: Class Activity $1-$ Implementing Design Options

Equations $(1)-(4)$ show expressions for converting between attributes of Polar $($i$.$e$.,\text{'}{r}^{\text{'}}$ and $\text{'}{}^{\text{'}})$ and its counterpart $-$ Cartesian $($i$.$e$.,\text{'}{x}^{\text{'}}$ and $\text{'}y\text{'})$ coordinates. In the figure below, we provide class designs of PointCP and PointCPTest whose implementations can be downloaded from: PointCP $-$ PointCP.java and PointCPTest $-$ PointCPTest.java.

Table $1$: Alternative designs for PointCP class

$\backslash$table$[[$Design$,\backslash$table$[[$How Cartesian coor$-],[$dinates are computed$]],\backslash$table$[[$How Polar coordi$-],[$nates are computed$]]],[\backslash$table$[[$Design $2(D_2)$ : Store polar coor$-],[$dinates only $($i$.$e$.,$ create proper$-],[$ties for polar coordinates$)]],\backslash$table$[[$Computed on demand,$],[$but not stored $($with cor$-],[$responding methods$).]],\backslash$table$[[$Simply returned $($with$],[$corresponding methods$).]]],[\backslash$table$[[$Design $3(D_3)$ : Store Cartesian$],[$coordinates only$]],\backslash$table$[[$Simply returned $($with$],[$corresponding methods$).]],\backslash$table$[[$Computed on demand,$],[$but not stored $($with cor$-],[$responding methods$).]]],[\backslash$table$[[$Design $5(D_5)$ : Abstract super$-],[$class with designs $2$ and $3$ as sub$-],[$classes$.]],\backslash$table$[[$Depends on the concrete$],[$class used.$]],\backslash$table$[[$Depends on the concrete$],[$class used.$]]]]$

You are required to do the following:

Modify the original implementation of PointCP.java to reflect Design $5$ in Table $1.$ In particular, you will end up with implementations of $(D5,D_{52},D_{53}).$ You are allowed to modify implementations of methods: getDistance $(...)$ and rotatePoint $(...)$ as you deem fit to ensure consistency with other