Business Requirements Document (BRD)

Version V 1

Data Analysis-Plan Module (Using the XML)

Course5 Intelligence
1 Document Revisions

Version
Date Document Changes
Number
11/02/2020 V1 Version V1

2 Introduction

Analysis Plan will be built as per the XML, for this all the functionality and special instruction will be
same as the previous version of the analysis plan. In this module input file will be XML file and output
will be same.

2.1 Purpose
The purpose of this document is to discuss complete functionality of the data analysis module using
xml as the base.

2.2 Scope
Scope will be same only the input method will vary from word document to XMl.

2.3 Objective
With AI automation, using the survey input files i.e.XML and Data files, it should produce a draft
version of Analysis Plan based on type of question for each question in the survey. This will
benefit the client services team to reduce any manual intervention to design the analytics plan for
each and every question of surveys and results into saving of their efforts.
Every client has their own standards on format of tables and their requirements, which will be
maintained through client settings.

2.4 DI Flow: - flow will be same as the previous version.

 Data Analysis

Input Materials for the Data Analysis Module

A. Survey XML

It has finalized survey schema with logics and definitions. Its Optional input file as we may not be
getting survey xml for all the projects from the clients.
Our DI-OS must need to read all different SP tools xml file (ConfirmIT, Decipher, Askia and
Dimensions).
i) Variable Name and Question Text
ii) Question Responses answer (with response codes)
iii) Only Dimension data files has survey structure in it. Dimension project, DI-OS will need
to read the mdd file.
iv) For ASCII data file it should read data file and data map.
v) Width and decimal point of the variables
 B. Data File
It has respondent level data collected and data structure
Our DI-OS must need to read all different format of data files (SPSS, Excel, ASCII, Askia and
dimension data files).
i) Variable Name and Question Text
ii) Question Responses answer (with response codes)
iii) Only Dimension data files has survey structure in it
iv) For ASCII data file it should read data file and data map.
v) Data Variable to use for Table view
vi) Width and decimal point of the variables
vii) For excel data file it should read both code and label
viii) For Askia data file it should read the .qes

Working Mechanism for Analysis Plan

Step 1 - AI should identify the Question #, Question Text

Step 2 - AI should identify the Question type of Question using Questionnaire and Data structure
Step 3 - AI should validate OR match Question # of survey with Variable names of SPSS data, to pick
the answer options and its response codes of the respective questions.
Step 4 - AI should read the question logic to define the table base descriptions and logic
Step 4 – Based on Question Type and client standards, it should allocate required analysis
requirements of survey.

It should auto populate

a) Question # and Question Text
b) Question skipping condition OR Base condition
c) Nets and statistics requirements
d) Formatting requirements (if any) like ranking or sorting and
e) Client standard requirement based on client standards and Question type.

Rules for identifying the Question type: - identification will also be same as per the
previous module
Special instruction for the each question type will also be same as per the previous
module.
Analysis Plan UI- Standard Tables

UI will be same as per the developed version, difference between the modules will be as
follows.
1) Question ID: - will be generated on the basis of the question type in the XML For
system for the form name in the XML, and according the form name question id will
be generated. If form name is not available system will find the name node, and
according to the name node it will decide the question id.
2) Question type: - in the XML the question type will be generated according to get type
node.
3) Table title: - it will be generated from the tag form label.
4) Base Description: - not defined, by default it will have the all respondent, user has to
change the same manually if user wants to change.
5) Base definition: - not defined. If user define base description manually, then also
user will provide the base definition.
6) Summary: - Summary will be defined all selection of the user for the generation of
the table script.

Execution logic will remain same, only the input will change.

Data Comparison Module

Data comparison module will be same as per the previous version, as we are comparing the
data file, not the xml. We will decide in the net has for the comparison of the ML.