The following is the domain checklist:

• Have standards for development been used (for instance, standard scheme techniques, standards for structured programming, standards for database approach, recognizable nomenclature, and standards for the use of user interfaces)?
• Have applied national and international standards been used, for instance to exchange of data via networks (OSI, TCP/IP, XML), of applications in the IBM-environment (SAA) or of a standard programming language which can be compiled on a wide variety of hardware?
• Are the routine actions built into the interface consistent?
• Have check processes (watchdogs) been applied?
• Is the operator able to supply status information?
• Is the data processing split up into sub-transactions?
• Have the input, processing and output been implemented separately?
• Have possible machine dependencies been implemented in separate modules?
• Has the essential functionality been stored in separate modules?
• Have I/O operations been classified in separate modules in order to separate the retrieval of data from the processing of data?
• Have the programs been structured, and are they easy to understand?
• Is open, consistent, and up-to-date technical documentation available?
• Have the programs been parameterized?
• Will technical actions within the interface be used?
• Are the subsystems distributed?
• Will data processing be done dually?
• Have the algorithms been optimized?
• Are tools provided to enable customisation and development of business services? Can services be cloned? Can the tools be used by business staff to set up services?
• What proprietary technology (hardware and software) is needed for this system?
• What change control software is used to manage system version control?
• What is the change control process? Please describe this both from a business and technical perspective.
• What change control notes does the customer receive?
• What system build tools are used to create the system?
• How is the system packaged and distributed?
• How many copies of the system are needed at any one time? How is change control managed across these copies?
• Have you planned how your software architecture will be validated throughout its development?
• Have you identified suitable validation techniques for use at each stage of the lifecycle? Do you know when you will use each?
• Is it possible to restart an application after a system breakdown?
• Is it possible to restart an application after an application breakdown?