Split Method We find this pattern in Amazon API evolution.
It does not mean that one method split into several methods,
but that one method was replaced by two different methods
in different conditions. In Amazon API, the functionality of a
method named 'PutInboundShipment' is to create or update
an item about shipment in the database. If the item already
exists, its record is updated; otherwise is created. In the new
version, if the user wants to create an item, they should use
the method named 'CreateInboundShipment', otherwise they
should use 'UpdateInboundShipment' for updating the record
of that item.