- changed version to alpha04
Isolate some cluster code from larger classes
Issue #328
new
USE CASE: WHAT DO YOU WANT TO DO?
Read, understand, and work on cluster code.
STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)
N/A
CURRENT BEHAVIOR
Some cluster classes became very large and have too many responsibilities.
EXPECTED BEHAVIOR
Cluster code is nicely arranged by separating responsibilities, lowering cohesion, and encapsulating code.
DEVELOPERS ONLY SECTION
SUGGESTED CHANGE (Pseudocode optional)
Isolate most of the inner classes and reduce dependencies/ communication. Separate responsibilities.
FILES AFFECTED (where the changes will be implemented) - developers only
ClusterController, ClusterProcessor
LEVEL OF EFFORT - developers only
medium
COMMENTS
Comments (6)
-
-
- edited description
-
- changed milestone to Coding Convention Adherence
-
- changed component to Coding Convention Adherence
-
- removed milestone
Removing milestone: Coding Convention Adherence (automated comment)
-
- changed version to beta2
- Log in to comment