[UserStory] encapsulation issue in ILFrame.java

[cgamble2]

User Story

Essential components

• Title describes the story
• Stakeholder type is identified
• Outcome is described
• Rationale is explicit
• Acceptance criteria are verifiable and from the perspective of the stakeholder

Story

As a maintainer
I want ILFrame.java to have proper encapsulation
so that the internal implementation does not affect the external API

Supporting Info

This design change may require refactoring or modifications to the internal design of other classes.

Acceptance Criteria

Any instance variables of ILFrame.java that need to be accessed or modified by other classes are private and have accessor methods.

Dependencies

Depends On

issue #32

[jody]

We do not need a stringent requirement for getter and setter methods for instance variables. We would only required them where there's explicit needs for that information to be accessed or modified from outside the class.

Because is not a refactoring of the ILFrame class (it changes the interface of the class), it would be useful to maintainers to explicitly mention that internal designs of other classes may need to be modified as a result of this issue's design change.

[jody]

The supporting info looks good!

It appears that there are no Acceptance Criteria, which means there's no way to determine whether or not a PR actually satisfies this User story.

[cgamble2]

Thank you. I updated the Acceptance Criteria for each encapsulation issue.

[jody]

Completed triage.