|
|
|
| High Level |
- Estimated time line of auditing process.
- Outline of system/application audit methods to be performed.
- Audit checks to be carried out.
- Cost
- Functionality
- Quality
- Reliability
- Security
- Suitability
- Documented audit results
- Tools to be utilized during auditing
- Costing of audit process
- Sign off requirements
- Outline of system/application intended usage, the pros and cons measured, documented, problems identified and solutions considered
- Audit Report
- Audit Scope
- Tasks
- Goals
- Findings
- Summary
- Results
| | Low Level |
- Specifications of System/Application for Auditing.
| Number of interfaces in application with details of. i.e. name, usage, |
Number of dialog boxes with details of usage. |
| Buttons and Controls used in application. |
Any crucial properties/added properties utilized within application. |
| Menu items used within the application |
Non Standard controls used. |
All of the above details are available from application specs.
While it is not essential, actual code for the application would provide
all these details, but typically from the application specifications.
- Typical usage documents from developers/users. This should detail
how the user interacts with the application. Al of the test cases will be basedon these.
- Databases in use with application. Drill down on reports/error logs
generated.
- Critical timings of the applications. Should the application perform
under time restrains?
- Typical test data. An example being inputs for forms.
Again these should be available from the application specification.
- Reporting requirements with expected details. An idea of how often and
to whom.
- Sign off at low level.
| |
