Since method parameters shouldn't be updated, it makes sense that that's both communicated and enforced with the use of ``++final++``. 


This rule raises an issue for methods with non-``++final++`` parameters.


== Noncompliant Code Example

----
public void doSomething (String a, int b) {  // Noncompliant
  // ...
}
----


== Compliant Solution

----
public void doSomething (final String a, final int b) {  // Noncompliant
  // ...
}
----


