your post reeks of fear, you're afraid your l33t sysadmin skills are not going to be needed if your company starts using a modern software process. sad.

no, he said you have the ability to WRITE DATA to one particular context (schema). you can't escalate permissions or affect the database server configuration itself. yeah, you could overwrite data for that one app, but it couldn't scale beyond that. Y'all are thinking of single system concerns this is a system-of-systems. The goal is to ensure that even if one system is SOMEHOW compromised, that access does not spread to other systems.

the number of angry BOFH sysadmins worried about losing their jobs instead of learning something new is HIGH on this thread

the amount of sheer ignorance in this comment thread is ASTOUNDING

The point of these tools, is to simply verify the consistency of a design, not to execute or examine existing source code. The steps involved are:
1) Come up with software design
2) Implement software design in one of these tools (model it in Z, or as a state machine using fsp/ltsa)
3) Use said tool to verify the consistency of the design.

Now, this activity, of course, takes a lot of time, and is unlikely to ever be of any use to your average J2EE/Ajax/Enterprise application. Areas where they CAN be of use are in things such as life-critical systems. For instance medical devices, or air plane control systems. Using something like FSP/LTSA you can model, check, and verify that your design does not every allow the system to enter into an invalid state. Now, remember, this says nothing about the final code, there is a separate issue of the code not matching the design, but it is possible to verify that the design does not ever lead to invalid states.