About Exam

Exam number/code: 225-030
Exam name: Certified Document Imaging Architech
Exam no. of questions: 85 Questions
Duration: 90 minutes for Native English speakers, 120 minutes for Non-native English speakers
Passing score: 700 on a scale of 100 - 900
Question types: Multiple choice questions (MCQ's), Multiple choice single answer, Multiple choice multiple answer, Drag and drop & Simulations (optional)

CompTIA’s CDIA+ certification is an internationally recognized credential acknowledging competency and professionalism in the document imaging / document management industry. CDIA+ candidates possess critical knowledge of all major areas and technologies used to plan, design and specify an imaging system. To achieve CDIA+ certification, the examinee must take and pass the exam within the specified time (90 minutes). The skills and knowledge measured by this examination are derived from an industry-wide and worldwide job task analysis, which was validated through a survey. The results of the survey are used in weighting the domains and ensuring that the weighting is representative of the relative importance of that content to the job requirements of a document imaging professional with twelve to eighteen months on-thejob experience.

• Gather Business Requirements 25%
  
• Analyze Business Process 22%
  
• Recommend Solution 16%
  
• Design Solution 24%
  
• Plan for the Implementation 13%
  

Exam Objectives

• Gather Business Requirements
• Define the problem and determine the goal of the solution
• Determine the internal groups that will work with the solution and assess their skill levels
• Determine the external groups that will work with the solution
• Determine where will people access the system, in which locations, using what type of connections
• Determine the regional and organizational compliance, legal, and standardization requirements (e.g., document retention rules and laws)
• Determine the security needs (e.g., access, document security)
• Determine the project timeline
• Identify integration requirements (e.g., with legacy systems)
  
• Determine the capacity requirements for server processing and storage (e.g., peak processing)
• Document quantities of documents (both electronic and paper if applicable)
• Determine the long-term storage capacity requirements
• Define query requirements (e.g., number per day, number of query users)
• Analyze the input requirements (resolution, image size, volume, scanner performance) to select the appropriate input devices and interfaces based on the characteristics of the source documents (e.g., color, weight, finish)
• Calculate the amount of image and indexing data (database or file system) to be stored based on the document life cycle requirements
• Determine the needed capacity, response times, and throughput rates
• Collect all detailed information required for solution design (e.g., technological environment, infrastructure, types of operating systems, databases)
• Determine growth needs and plan for scalability
• Determine the required service levels for maintenance
• Identify the company's vision and mission, goals, characteristics of the business (e.g., business vision, current and future business challenges, business standards, IT infrastructure)
• Determine and confirm capacity, quantities and types of data to validate the storage requirements and growth estimates
• Determine the need for back file or data conversion/migration is required
• Create specific requirements document
• Document the current records storage management requirements and how the new solution addresses these
• Determine workflow rules (e.g., flow diagrams)
• Develop an acceptance criteria for the imaging solution
• Determine user modifications to image ( e.g. annotations, user stamps, electronic signing, highlighting)
• Determine manual workflow (e.g., ad hoc or non-rules based)
• Determine manual integration needs.
• Determine output requirements (fax, email, printing)
• Determine documents preparation requirements, user interactions, (e.g., sorting requirements, batch sizes, document separators)
• Determine paper handling and disposal process
• Recommend alternatives for document preparation
• Define specific retrieval needs and system requirements to support retrieval
• Document all the information collected during requirements-gathering phase, obtaining user’s acceptance sign-off and validation towards them
• Analyze Business Process
• Gather the business requirements and expectations (e.g., ROI, work improvements, customer service, access to data) by interviewing the project owner and key persons to determine which processes will benefit from DMS/DIS and by reviewing the company's documents (e.g., Web, company brochures, RFP)
• Scope the di