Design Profile (Master): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 1: | Line 1: | ||
{{Button Back BCM TE}}{{Button Back CM TE}}{{Template:Planning Methodology TE}} | {{Button Back BCM TE}}{{Button Back CM TE}}{{Template:Planning Methodology TE}} | ||
= <span style="color:#0000FF">'''Design Profile (Master) Template'''= | = <span style="color:#0000FF">'''Design Profile (Master) Template'''= | ||
This template is a checklist for developing test design profiles to help the | This template is a checklist for developing test design profiles to help the Organisation BCM Coordinator ensure that all aspects of the test have been considered before a test. | ||
== '''Definition''' == | == '''Definition''' == | ||
Line 7: | Line 7: | ||
* Objective | * Objective | ||
* [[Type of Tests| Type of Test]] | * [[Type of Tests| Type of Test]] | ||
* Scope and Scale | * Scope and Scale | ||
** Active | |||
** Passive | |||
** Degree of involvement | |||
* Components to be tested | * Components to be tested | ||
** Plans | ** Plans | ||
Line 23: | Line 26: | ||
* Time of Test/Schedule | * Time of Test/Schedule | ||
* Duration | * Duration | ||
* Frequency | * Frequency | ||
** Mandatory | |||
** Desirable | |||
* Notice Requirement/Warning | * Notice Requirement/Warning | ||
* Briefing of Participants | * Briefing of Participants |
Revision as of 14:56, 2 June 2025



Design Profile (Master) Template
This template is a checklist for developing test design profiles to help the Organisation BCM Coordinator ensure that all aspects of the test have been considered before a test.
Definition

- Objective
- Type of Test
- Scope and Scale
- Active
- Passive
- Degree of involvement
- Components to be tested
- Plans
- People
- Place
- Resources
- Success Criteria
- Essential Pre-Conditions
- Participants
- Internal
- External
Scheduling
- Time of Test/Schedule
- Duration
- Frequency
- Mandatory
- Desirable
- Notice Requirement/Warning
- Briefing of Participants
- Scenario
- Write Test Plan
- Budget for Test
Execution/ Monitoring
- Controllers
Document
- Documentation (capable of audit) -Track events and degree of success
Review/ Measure
- Post-Mortem Meeting
Report/ Output
- Post-Test Actions (documented) –link to maintenance/reporting
Maintenance/ Follow-Up
- Make amendments to plan as required
