This is subtle piece of good
Java style.
For really maintainable code,
you should always create an object using the most specific class you can find, but refer to it as the least specific. This allows you to change the SimpleDateFormat constructor to any other DateFormat class (say a custom DateFormat which is not based on SimpleDateFormat)with no changes to any other code.
The type of each variable in your system should be decided solely on the operations you require of it. In this case we only require operations provided by the base DateFormat class, so the variable "doesn't need to know" which child class was used to create it.
In this case the code is very short, so the benefits are small (if you changed to a new type of DateFormat in your version, you would need to change the name SimpleDateFormat twice, rather than just once for mine), but as software gets larger this approach becomes very important in ensuring maximum flexibility and reuse, with minimum maintenance overhead.