| Conditions | 11 | 
| Paths | 23 | 
| Total Lines | 42 | 
| Code Lines | 27 | 
| Lines | 0 | 
| Ratio | 0 % | 
| Tests | 29 | 
| CRAP Score | 11.3851 | 
| Changes | 1 | ||
| Bugs | 0 | Features | 0 | 
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
| 1 | <?php  | 
            ||
| 35 | $otherAccount->setSchemeName((string) $xmlOtherIdentification->SchmeNm->Cd);  | 
            ||
| 36 | }  | 
            ||
| 37 | |||
| 38 |             if (isset($xmlOtherIdentification->SchmeNm->Prtry)) { | 
            ||
| 39 | $otherAccount->setSchemeName((string) $xmlOtherIdentification->SchmeNm->Prtry);  | 
            ||
| 40 | }  | 
            ||
| 41 | }  | 
            ||
| 42 | |||
| 43 | 6 |         if (isset($xmlOtherIdentification->Issr)) { | 
            |
| 44 | 6 | $otherAccount->setIssuer((string) $xmlOtherIdentification->Issr);  | 
            |
| 45 | 6 | }  | 
            |
| 46 | |||
| 47 | 6 | return $otherAccount;  | 
            |
| 48 | }  | 
            ||
| 49 | }  | 
            ||
| 50 |