static (real_ifc,mapped_ifc) does mean high,low. Although it can be used the other way around because a static translation is maintained in both directions. Just remember that real_ifc means that its the real ip (not nat'd or source) and mapped_ifc means thats its the mapped ip (nat'd address or new source).
By "Without translation" they are referring to being able to utilise the static command to not translate through a configured NAT. For example, if you have a NAT configured from the inside network to the DMZ, e.g.
global (dmz) 3 interface
global (outside) 3 interface
nat (inside) 3 0.0.0.0 0.0.0.0
Here all clients are going to the dmz and will appear to servers in the DMZ as the DMZ interface IP Address.
You could have some servers that you setup to allow more access based on the source address, if you wanted to turn NAT off for just them servers, you could configured a static like,
This will send the traffic from server 10.10.10.10 through to the DMZ and pass it out of the DMZ interface as an ip address 10.10.10.10
Without knowing what the ip range is for the DMZ and inside, i cannot really comment on your command in the config. What i will say is that it doesn't really matter which way around they go as long as the IP Addresses are correct because the static works both ways (i.e. static mapping for machine 10.10.10.5 to 172.31.32.254 is the same as 172.31.32.254 going to 10.10.10.5).
you command reads that 10.3.4.250 is the mapped (is what it maps to) and 172.16.0.3 is what its real address is before the nat process. This will work the other way around (or should)
Hope it makes sense (its been a long week with the wedding plans for next weekend so i am a little tired)