The following is the domain checklist:

• Are the essential functions of the information system shielded in a separate subsystem?
• Are well-trained substitutes on stand-by within the production organization?
• Are well-trained substitutes on stand-by within the user organization?
• Have provisionsbeen made so that, in case of serious disturbances or disasters, the information services may continue as much as possible?
• Is a plan for disasters available?
• Is the user organization's level of dependency on the information system stated (critical, sensitive, non-sensitive)?
• Has the maximal tolerable time of breakdown been stated?
• Has it been determined what constitutes a disaster?
• Is a co-ordinator assigned in case a disaster occurs, and are the authorities and responsibilities determined for such situations?
• Have the emergency procedures and the alternative procedures for a possible transition period been described? (Amongst other aspects, attention needs to be paid to procedures handling unfinished transactions at the point of breakdown.)
• Does the plan for disasters include possible alternative hardware?
• Is, as part of the plan for disasters, a plan for an alternative location available?
• Have the organizational aspects been described, including the procedures for an alternative location?
• Has it been established which functionary is authorized to decide to make use of alternative computers?
• Has a similar production environment been reserved, for instance, in an alternative computer centre, including accompanying procedures for alternative use?
• Does the (external) executive organization responsible for the implementation of the alternative use have an up-to-date plan for alternative use?
• Is the plan for disasters known within the relevant organization departments? Will the plan for alternative use be tested periodically, but at least once a year?
• Will the findings of the test of the alternative computer use lead to amendments in the plan for alternative use?
• Will a test of the plan for alternative use take place after a major change in the system architecture?
• Have manual procedures been prepared in order to substitute (parts of) the automated information services?
• What level of reliability and accessibility is predicted for the system?
• How fault tolerant is the system and what are the fault handling strategies and procedures?
• Is the architecture well organized and have you provided a system overview, background information, constraints, and a clear organizational structure for all downstream designs?
• Have you identified approved performance targets, at a high level at least, with key stakeholders?
• Have you considered targets for both response time and throughput?
• Do your targets distinguish between observed performance (that is, synchronous tasks) and actual (that is, taking asynchronous activity into account)?
• Have you assessed your performance targets for reasonableness?
• Have you appropriately set expectations among your stakeholders of what is feasible in your architecture?
• Have you defined all performance targets within the context of a particular load on the system?
• Checklist for Architecture Definition
• Have you identified the major potential performance problems in your architecture?
• Have you performed enough testing and analysis to understand the likely performance characteristics of your system?
• Do you know what workload your system can process? Have you prioritized the different classes of work?
• Do you know how far your proposed architecture can be scaled without major changes?
• Have you identified the performance-related assumptions you have made (and validated them if needed)?
• Have you reviewed your architecture for common performance pitfalls?