The following is the domain checklist:

• Do you have clear strategies for transactional consistency across distributed data stores, and do these balance this need with the cost in terms of performance and complexity?
• Do you have mechanisms in place for validating migrated data and dealing appropriately with errors?
• Have you defined sufficient storage and processing capacity for archiving, and for restoring archived data?
• Has a data quality assessment been done? Have you created strategies for dealing with poor quality data?
• Is there a clear system-level concurrency model?
• Are your models at the right level of abstraction? Have you focused on the architecturally significant aspects?
• Can you simplify your concurrency design?
• Do all interested parties understand the overall concurrency strategy?
• Have you mapped all functional elements to a process (and thread if necessary)?
• Do you have a state model for at least one functional element in each process and thread? If not, are you sure the processes and threads will interact safely?
• Have you defined a suitable set of inter-process communication mechanisms to support the inter-element interactions defined in the functional view?
• Are all shared resources protected from corruption?
• Have you minimized the inter-task communication and synchronization required?
• Do you have any resource hot spots in your system? If so, have you estimated the likely throughput, and is it high enough? Do you know how you would reduce contention at these points if forced to later?
• Can the system possibly deadlock? If so, do you have a strategy for recognizing and dealing with this when it occurs?
• Will a periodic check be done on the consistency of the database and datasets?
• Is the data storage distributed?
• What are the data model, data definitions, structure, and hosting options of purchased applications (COTS)?
• What are the rules for defining and maintaining the data requirements and designs for all components of the information system?
• What shareable repository is used to capture the model content and the supporting information for data?
• What is the physical data model definition (derived from logical data models) used to design the database?
• What software development and data management tools have been selected?
• Which data owners have been identified to be responsible for common data definitions, eliminating unplanned redundancy, providing consistently reliable, timely, and accurate information, and protecting data from misuse and destruction?
• Is the data encrypted?
• Is data quality covered in the scope?
• Does architecture allow for implementation of all the key requirements?
  • Data migration
  • Data quality
  • Data validations, verifications and mapping rules
  • Data synchronization 
• Are the data quality requirements from the business user needs been addresses?
• Does the data architecture communicate an adequate vision of the system that will direct further design activities?
• Are the KPIs and KRAs for data domain adequately addressed?
• Are all interfaces between the source and target systems identified and justified?
• Has the data referential integrity and/or normalization been described?
• Are data synchronization needs addressed? Does it cater to both real-time and batch modes?
• Will the proposed data architecture satisfy all specified quality attributes and performance goals?
• Are the data model, data definitions, structure, and hosting options considered?
• Is the data quality strategy described and justified?
• Have all the data models that are part of the scope been addressed and described?
  • B2B
  • B2C 
• Are the data access requirements for standard file, message, data management, and decision support systems described?
• Have all the physical and logical data models been described?
• Are design decisions and assumptions documented explicitly and motivated?
• Are the mapping rules adequately captured and documented for the data domain?
• Have the data storage and retention considerations been addressed?
• Have the quality assurance considerations been addressed?
• Have all backup and recovery needs been addressed?
• Have migration/conversion considerations been addressed?