Throughout this entire process, we need to consider interconnectivity. Now with our security functionality and the philosophy and the design principles we discussed up 'til now, there comes the requirement for sensitive management of information and the information that allows us to control the system environment. This means we have to have ways of examining the session and the management tools that will safeguard from improper construction or invasion, and that will include all the application elements that are aligned, and that the flow control itself is correctly imposed to ensure data in motion is protected in all reasonable spots while we avoid things like unnecessary complexity.

Each program will need to be sure to handle exceptions and errors in the proper way, because by trapping and checking these and identifying the various failure modes that can produce them, we're going to define that each is properly handled and resolved without undo system impact or exposures. This is also an opportunity for us to improve psychological acceptability for the user. And again, encourage them not to try to find shortcuts.

Configuration is without question of one of the most important processes we'll have, both in design and in operation. Now in the design phases, we apply these to control design elements and changes being made so that we maintain fidelity with the plan in whatever configuration it currently is in. In the operation of course, this will ensure continued alignment with the intended mission and operational control. And as we use these processes that the produced application or system continues to serve the intended business need that prompted its creation in the first place.