|
Posted by Michael Horowitz on August 13, 2005, 4:55 pm
If you were Registered and logged in, you could reply and use other advanced thread options
I work for an organization that does Integration, Interoperability and
Information Assurance testing on applications/systems .
I have been asked to document the decision process that goes into
determining if Information Assurance testing is applicable.
Obviously, if it's a new app/system, it gets tested. If it is a new
version of a previously tested app/system, then a review of the
changes since the last version would drive the decision. If the
changes are cosmetic, no testing is needed. If they upgrade the O/S,
we need to test.
Has anyone had any experience in this area and can lend some insight
into what things should trigger the 'test it' decision? - Mike
| 
XML site map