SPSS Guide

SPSS Data View vs Variable View – Complete Explanation

Table of Contents

SPSS Data View vs Variable View

When you open IBM SPSS Statistics, two of the most important tabs you will use are Data View and Variable View. They are part of the SPSS Data Editor, but they serve very different purposes.

Data View displays the actual values collected from participants, cases, or observations. Variable View defines the structure and properties of the variables in the dataset.

In simple terms:

  • Variable View tells SPSS what each variable means.
  • Data View tells SPSS what values were recorded for each case.

Understanding this difference is essential because incorrect variable definitions can cause data-entry problems, confusing output, inappropriate statistical procedures, and inaccurate interpretations.

This guide explains SPSS Data View versus Variable View in detail, including every Variable View setting, a complete research example, common mistakes, and the correct data-entry workflow.

Quick answer: In SPSS Data View, rows normally represent cases and columns represent variables. In Variable View, rows represent variables and columns represent variable properties such as name, type, labels, missing values, and measurement level.

What Are Data View and Variable View in SPSS?

Data View and Variable View are two ways of looking at the same SPSS dataset.

In current IBM SPSS Statistics documentation, the Data Editor includes Data View, Variable View, and an additional Over View that summarizes the dataset. However, Data View and Variable View remain the two primary views used when defining and entering research data.

Data View

Data View shows the actual data values stored in the dataset.

For example, it may display:

  • A participant’s age
  • A test score
  • A gender code
  • A survey response
  • A treatment-group code
  • A measurement collected before and after an intervention

Variable View

Variable View shows information about the variables rather than the participants.

For example, it defines:

  • The variable name
  • Whether the variable is numeric or string
  • The variable label
  • The meanings of category codes
  • Missing-value codes
  • The level of measurement
  • The role assigned to the variable

IBM describes Variable View as the area where rows are variables and columns are variable attributes. These definitions are stored with the SPSS data file.

SPSS Data View vs Variable View Comparison

FeatureData ViewVariable View
Main purposeEnter, inspect, and edit actual dataDefine and edit variable properties
Each row representsOne case, participant, record, or observationOne variable
Each column representsOne variableOne variable attribute
Cells containActual recorded valuesVariable definitions and settings
Typical contentAge, income, score, group codeName, type, label, values, missing, measure
Used for data entryYesUsed to prepare variables for data entry
Shows participantsYesNo
Shows variable metadataOnly indirectlyYes
Example rowParticipant 1The variable named age
Example columnThe age variableThe Measure attribute
Best used before analysisTo check actual values and errorsTo verify coding, labels, types, and measurement levels

The Most Important Difference

The easiest way to remember the difference is:

Data View contains the data. Variable View describes the data.

Suppose a researcher collects the following information:

  • Participant ID
  • Age
  • Treatment group
  • Pre-test score
  • Post-test score

In Data View, the researcher enters each participant’s ID, age, group, and test scores.

In Variable View, the researcher defines what group means, which numbers represent the control and treatment groups, whether scores are numeric, and which measurement level should be assigned to each variable.

Understanding SPSS Data View

Data View looks similar to a spreadsheet, but its structure should be planned according to the requirements of statistical analysis.

Rows in Data View Represent Cases

Each horizontal row normally represents one case.

A case might be:

  • One survey respondent
  • One patient
  • One student
  • One company
  • One school
  • One household
  • One experimental unit
  • One observation collected at a particular time

For a standard participant-level dataset, all information for one participant should normally appear on the same row. Laerd’s data-entry guidance similarly emphasizes entering each unique case on a new row.

Columns in Data View Represent Variables

Each vertical column represents one variable or characteristic.

Examples include:

  • participant_id
  • age
  • gender
  • education
  • group
  • pre_score
  • post_score

A column should generally contain one consistent type of information.

For example, the age column should contain ages rather than a mixture of ages, names, and comments.

Cells in Data View Contain Values

A cell is the intersection of a case and a variable.

For example:

  • Row 1 may represent Participant 001.
  • The age column may represent participant age.
  • The value 24 in that cell means Participant 001 is 24 years old.

Example of Data View

Caseparticipant_idagegrouppre_scorepost_scoresatisfaction
110121162754
210224068693
310322155735
410428071702
5105251648099

In this example:

  • Each row represents one participant.
  • Each research characteristic has its own column.
  • group = 0 represents the control group.
  • group = 1 represents the treatment group.
  • satisfaction = 99 represents a missing response.

The meanings of 0, 1, and 99 should be defined in Variable View.

Case Numbers Are Not Participant IDs

The gray row numbers displayed on the left side of Data View identify the current row positions. They are not permanent participant identifiers.

Row order can change after sorting, selecting, merging, or restructuring data. Therefore, research datasets should normally include a separate unique identification variable such as:

  • participant_id
  • student_id
  • patient_id
  • case_id

A unique ID makes it possible to identify and verify a case even if the order of the rows changes.

Values and Value Labels in Data View

Categorical variables are often stored using numeric codes.

For example:

  • 0 = Control
  • 1 = Treatment

SPSS can display either the numeric codes or their descriptive labels. The View → Value Labels option toggles between the actual values and the user-defined labels in Data View.

The underlying values remain the same.

For example, switching the display from 1 to Treatment does not convert the stored number into text. It only changes how the value is displayed.

Missing Values in Data View

SPSS distinguishes between system-missing and user-defined missing values.

System-missing value

For a numeric variable, an empty value is normally displayed as a period:

.

User-defined missing value

A researcher may use a code such as:

  • 99 = No response
  • 98 = Not applicable
  • -1 = Refused to answer

The code must also be defined as missing in Variable View. Otherwise, SPSS may treat it as a valid number and include it in calculations.

IBM documentation explains that user-missing values can be assigned descriptive labels and excluded from most calculations, while system-missing numeric values appear as periods in Data View.

Important: Never use a missing-value code that could also be a legitimate response. For an age variable, for example, 99 might be a real age. A more suitable code or system-missing value may be required.

Understanding SPSS Variable View

Variable View is the control center for the structure of an SPSS dataset.

Instead of showing participants in rows, it shows variables in rows. Each column contains a different property of those variables.

Current versions commonly display the following attributes:

  1. Name
  2. Type
  3. Width
  4. Decimals
  5. Label
  6. Values
  7. Missing
  8. Columns
  9. Align
  10. Measure
  11. Role

Complete Explanation of Variable View Columns

Variable View fieldPurposeExample
NameAssigns a short, unique variable namepre_score
TypeDetermines the variable’s data or display typeNumeric
WidthControls the defined or displayed width of the value8
DecimalsControls displayed decimal places0
LabelProvides a longer variable descriptionPre-intervention test score
ValuesAssigns labels to category codes0 = Control; 1 = Treatment
MissingIdentifies user-defined missing-value codes99
ColumnsChanges the visible Data View column width12
AlignChanges the visual alignment of valuesRight
MeasureAssigns nominal, ordinal, or scale measurementScale
RoleIdentifies the variable’s intended analytical roleInput or Target

1. Name

The Name field contains the variable’s unique identifier.

Good variable names include:

  • age
  • gender
  • education
  • pre_score
  • post_score
  • total_stress

For usability and compatibility, it is usually best to:

  • Begin the name with a letter.
  • Avoid spaces.
  • Use underscores between words.
  • Keep names clear and reasonably short.
  • Give every variable a unique name.
  • Avoid reserved SPSS keywords.

IBM allows variable names of up to 64 bytes and permits more characters than many introductory tutorials suggest. However, simple names containing letters, numbers, and underscores are generally easier to use in syntax and analysis.

Good: post_score
Poor: Post Intervention Score

The longer description belongs in the Label field, not the Name field.

2. Type

Type tells SPSS what kind of values a variable contains or how numeric values should be displayed.

Common choices include:

  • Numeric
  • Comma
  • Dot
  • Scientific notation
  • Date
  • Dollar
  • Custom currency
  • String
  • Restricted numeric

SPSS fundamentally stores variables as numeric or string. Date, time, currency, and similar options are primarily numeric values presented using specialized formats.

Numeric variables

Use Numeric for:

  • Age
  • Scores
  • Income
  • Height
  • Weight
  • Number of children
  • Numerically coded categories

String variables

Use String for text such as:

  • Names
  • Open-ended responses
  • Comments
  • Identification codes containing letters
  • City names

A string containing digits is still text. For example, the string "25" is not automatically equivalent to the numeric value 25.

3. Width

Width controls how many characters or digits are available for displaying or defining the variable’s format.

For numeric variables, Width does not normally change the precision of the underlying stored number. IBM notes that numeric values are stored internally in double precision and that the output format affects their display rather than the stored value.

For string variables, the defined width is more important because it determines how much text the variable can store.

For example:

  • A string width of 2 can store TR.
  • A string width of 20 can store Treatment Group.

Choose an adequate string width before entering or importing lengthy text.

4. Decimals

Decimals controls the number of decimal places displayed for numeric values.

Examples:

  • Age: 0 decimals
  • Test score: 0 or 2 decimals
  • Height in meters: 2 decimals
  • Percentage: 1 or 2 decimals

Changing the displayed number of decimals does not necessarily alter the underlying stored value.

For example, a stored value of 18.756 may appear as 18.76 when two decimal places are displayed.

5. Label

Label provides a longer, reader-friendly description of a variable.

Example:

  • Name: pre_score
  • Label: Participant score before the training intervention

Variable names are useful for data management and syntax. Variable labels make output tables and charts easier to understand.

A variable label describes the entire variable.

6. Values

The Values field assigns descriptive labels to individual category codes.

For example, for group:

ValueValue label
0Control group
1Treatment group

For a five-point satisfaction item:

ValueValue label
1Very dissatisfied
2Dissatisfied
3Neutral
4Satisfied
5Very satisfied

IBM supports assigning value labels through Variable View or with the VALUE LABELS command.

Value labels make data and output easier to interpret without changing the stored codes.

Variable Label vs Value Label

These two terms are frequently confused.

FeatureVariable labelValue label
DescribesThe complete variableA specific value within the variable
ExampleParticipant treatment group0 = Control
Entered inLabel fieldValues field
Applied toOne variableOne or more category codes

For group:

  • Variable label: Experimental group assigned to participant
  • Value labels: 0 = Control, 1 = Treatment

7. Missing

The Missing field defines user-missing codes.

Suppose 99 means a participant did not answer a satisfaction question.

You can:

  1. Enter 99 in Data View.
  2. Assign the value label No response.
  3. Define 99 as a missing value.

IBM allows users to define up to three individual missing values, a range, or a range plus one discrete value, depending on the variable type.

Defining the code as missing prevents SPSS from treating 99 as a genuine satisfaction score.

8. Columns

Columns changes the visible width of the variable’s column in Data View.

It affects only how much space the column occupies on screen.

It does not change:

  • The stored values
  • The variable type
  • The statistical results
  • The string’s defined storage width

Width vs Columns

WidthColumns
Relates to the variable’s format or defined value widthRelates to the visible width of the Data View column
Can matter for string storageMainly a display setting
Part of the variable definitionPart of the screen layout

This distinction is one of the most commonly overlooked parts of Variable View.

9. Align

Align determines how values appear inside Data View cells.

Options usually include:

  • Left
  • Center
  • Right

Alignment is primarily visual. It does not change the values or statistical analysis.

10. Measure

Measure specifies the variable’s level of measurement:

  • Nominal
  • Ordinal
  • Scale

Nominal

Nominal variables contain categories without an inherent order.

Examples:

  • Country
  • Department
  • Treatment group
  • Marital status
  • Blood type

Numbers used for nominal categories are codes, not quantities.

For example, assigning 1 = Control and 2 = Treatment does not mean that Treatment is twice Control.

Ordinal

Ordinal variables contain categories with a meaningful order, but the distances between categories are not necessarily equal.

Examples:

  • Satisfaction level
  • Class position
  • Education category
  • Agreement scale
  • Disease severity category

Scale

SPSS uses Scale for interval- and ratio-level numeric variables.

Examples:

  • Age
  • Height
  • Weight
  • Income
  • Test score
  • Time
  • Temperature measured on an interval scale

IBM defines nominal values as unordered categories, ordinal values as ordered categories, and scale values as having a meaningful numerical metric.

Important: The Measure setting does not transform the data. Changing a variable from Nominal to Scale does not convert category codes into meaningful quantities. It only changes the metadata SPSS uses in supported dialogs, charts, and procedures.

11. Role

Role indicates how a variable may be used in supported analytical dialogs.

Available roles can include:

  • Input
  • Target
  • Both
  • None
  • Partition
  • Split

Examples:

  • An independent variable may be assigned Input.
  • A dependent variable may be assigned Target.
  • A train/test indicator may be assigned Partition.

IBM notes that all variables are assigned Input by default. Role assignments affect only dialogs that support them and do not change command syntax.

For most beginner analyses, leaving Role at its default setting is acceptable.

Complete Worked Research Example

Suppose a researcher wants to examine whether a training program improves test scores.

The researcher records:

  • Participant ID
  • Age
  • Experimental group
  • Pre-test score
  • Post-test score
  • Satisfaction with training

Step 1: Define Variables in Variable View

NameTypeDecimalsLabelValuesMissingMeasureRole
participant_idNumeric0Unique participant identification numberNoneNoneNominalNone
ageNumeric0Participant age in yearsNoneNoneScaleInput
groupNumeric0Experimental group0 = Control; 1 = TreatmentNoneNominalInput
pre_scoreNumeric0Test score before interventionNone99ScaleInput
post_scoreNumeric0Test score after interventionNone99ScaleTarget
satisfactionNumeric0Satisfaction with training1–5 response labels; 99 = No response99OrdinalTarget

Step 2: Enter Observations in Data View

participant_idagegrouppre_scorepost_scoresatisfaction
10121162754
10224068693
10322155735
10428071702
105251648099

The last satisfaction value is entered as 99, but Variable View tells SPSS to treat it as missing rather than as an extremely high satisfaction score.

Step 3: Display Value Labels

After enabling Value Labels, the group column may display:

Stored valueDisplayed label
0Control
1Treatment

The stored data remain numeric.

Correct SPSS Data-Entry Workflow

A reliable workflow is:

1. Prepare a codebook

Before opening SPSS, list:

  • Variable names
  • Full variable descriptions
  • Data types
  • Category codes
  • Missing-value codes
  • Measurement levels

2. Open Variable View

Create one row for each variable.

Define at least:

  • Name
  • Type
  • Label
  • Values, where applicable
  • Missing values
  • Measure

3. Open Data View

Enter or import the actual observations.

Use:

  • One row per case
  • One column per variable
  • One cell per recorded value

4. Check value labels

Toggle Value Labels to confirm that category codes have the intended meanings.

5. Validate categorical variables

Run:

Analyze → Descriptive Statistics → Frequencies

Look for:

  • Invalid category codes
  • Unexpected values
  • Missing-value errors
  • Empty categories
  • Typographical mistakes

6. Validate scale variables

Use descriptive statistics to check:

  • Minimum
  • Maximum
  • Mean
  • Standard deviation
  • Number of valid and missing cases

An age of 250, for example, probably indicates a data-entry error.

7. Save the SPSS file

Save the dataset in .sav format so that variable labels, value labels, missing-value definitions, formats, and measurement levels are preserved.

Data View vs Variable View for Common Tasks

TaskCorrect view
Enter a participant’s ageData View
Change a variable’s nameVariable View
Enter survey responsesData View
Define 1 = Male and 2 = FemaleVariable View
Inspect an individual participantData View
Set a variable as nominalVariable View
Add a complete variable labelVariable View
Correct an incorrectly entered scoreData View
Define 99 as missingVariable View
Change the number of displayed decimalsVariable View
View category labels instead of codesData View
Change a numeric variable to stringVariable View

Common Mistakes in Data View

Mistake 1: Placing multiple participants in one row

For a participant-level dataset, each participant should normally have a separate row.

Mistake 2: Splitting one participant across several rows unintentionally

This creates duplicate cases unless the research design deliberately uses long-format data.

Mistake 3: Treating row numbers as IDs

Row numbers may change. Create a dedicated identification variable.

Mistake 4: Mixing text and numbers in one variable

A column containing 25, Thirty, and Unknown cannot be analyzed consistently as a numeric age variable.

Mistake 5: Entering category labels inconsistently

Entries such as Male, male, M, and 1 may be treated as different values.

A consistent numeric coding system with value labels usually reduces these problems.

Mistake 6: Using Excel-style formulas in cells

Data View is spreadsheet-like, but it is not designed to store formulas in individual cells in the same way as Excel.

Use:

  • Transform → Compute Variable
  • Transform → Recode
  • SPSS syntax

Mistake 7: Entering a missing code without defining it

A code such as 99 will be treated as a real value unless it is declared missing.

Common Mistakes in Variable View

Mistake 1: Confusing Type with Measure

Type describes how values are stored or formatted.

Measure describes the level of measurement.

For example:

  • gender can have Numeric type.
  • Its Measure can be Nominal.

Mistake 2: Confusing Width with Columns

Width relates to the variable format or string capacity. Columns controls how wide the variable looks in Data View.

Mistake 3: Using labels as variable names

A name such as Participant satisfaction after completing the training program is unnecessarily difficult to manage.

Use:

  • Name: satisfaction
  • Label: Participant satisfaction after completing the training program

Mistake 4: Forgetting to click Add when defining value labels

In the Values dialog, enter the value and label and then click Add before moving to the next category.

Mistake 5: Assigning Scale to every numeric variable

A numeric code is not automatically a scale variable.

Examples:

  • 1 = Urban, 2 = Rural is nominal.
  • 1 = Low, 2 = Medium, 3 = High is ordinal.
  • Actual age in years is scale.

Mistake 6: Using text categories when numeric coding is more reliable

String variables are valid, but numeric codes with value labels are often easier to manage for categorical analysis, especially for ordered categories. IBM specifically warns that alphabetical order may not represent the correct order for ordinal string categories.

Mistake 7: Changing a variable type without checking existing data

Changing types after data entry or import can cause invalid values, truncation, or missing data. Always create a backup before making major structural changes.

When Should You Use Variable View First?

Use Variable View first when:

  • Creating a new dataset manually
  • Entering questionnaire responses
  • Creating categorical variables
  • Defining missing-value codes
  • Preparing a dataset for another researcher
  • Building a reusable data-entry template
  • Setting up a dissertation or thesis dataset

Although SPSS allows users to begin entering values directly, defining the variables first generally produces a cleaner and more reliable dataset.

When Should You Use Data View First?

You may inspect Data View first when:

  • Opening an existing .sav file
  • Importing data from Excel or CSV
  • Checking whether values imported correctly
  • Looking for coding errors
  • Reviewing a particular case
  • Correcting observations
  • Comparing raw values with statistical output

After importing data, always review Variable View because imported files may not contain complete labels, missing-value definitions, or correct measurement levels.

Can Variables Be Created Directly in Data View?

Yes. Entering data in a new column can cause SPSS to create a variable automatically.

However, the automatically assigned settings may not be appropriate. You should still check Variable View and correct:

  • Name
  • Type
  • Decimals
  • Label
  • Value labels
  • Missing values
  • Measure

For carefully designed research data, defining variables before entering cases is safer.

Switching Between Data View and Variable View

You can switch views by clicking the tabs at the bottom of the Data Editor.

IBM also documents the following keyboard shortcut:

  • Windows/Linux: Ctrl + T
  • Mac: Command + T

In Variable View, the spacebar can open dialogs for Type, Value Labels, and Missing Values when the relevant cell is selected.

Can Changing Variable View Alter Data View?

Yes, depending on the setting changed.

Changes that affect interpretation or display

  • Renaming a variable changes its column heading.
  • Adding value labels changes how coded categories can be displayed.
  • Changing decimals alters the displayed precision.
  • Changing Columns alters the visible column width.
  • Changing Measure affects metadata used by some procedures.
  • Defining missing values affects how specified codes are treated in analyses.

Changes that may affect compatibility or values

  • Changing Numeric to String
  • Changing String to Numeric
  • Reducing string width
  • Applying an inappropriate date format

Create a backup before changing the type or defined width of an existing variable.

Wide and Long Data Formats

The “one participant per row” rule applies to many standard datasets, but not every research design uses the same structure.

Wide format

One participant occupies one row, while repeated measurements occupy separate columns.

idscore_prescore_post
15572
26075

Long format

One participant can occupy multiple rows, with another variable identifying time or condition.

idtimescore
1Pre55
1Post72
2Pre60
2Post75

The correct structure depends on the statistical procedure, research design, and data-management requirements.

Therefore, “one participant per row” is a strong beginner rule for ordinary cross-sectional data, but repeated-measures and multilevel datasets may require long format.

Data View and Variable View Are Connected

The two views are not separate datasets.

They are two representations of the same file:

  • Data View displays the values.
  • Variable View displays the data dictionary or metadata.
  • A variable created in Variable View appears as a column in Data View.
  • A variable created in Data View appears as a row in Variable View.
  • Changing a variable name in Variable View changes its heading in Data View.
  • Defining value labels in Variable View changes how codes can be displayed in Data View and output.

SPSS Data View vs Excel

Although Data View resembles Excel, there are important differences.

SPSS Data ViewExcel worksheet
Columns are expected to represent variablesColumns can contain almost any arrangement
Cells normally contain data valuesCells may contain values or formulas
Variable properties are stored separatelyFormatting and structure are more flexible
Designed for statistical proceduresDesigned for general spreadsheet work
Measurement levels can be assignedNo equivalent built-in statistical metadata
User-missing values can be definedMissing values depend on spreadsheet conventions

SPSS requires a more structured dataset because statistical procedures depend on consistent variable definitions.

Best Practices

  1. Create a codebook before data entry.
  2. Include a unique case-identification variable.
  3. Use clear, concise variable names.
  4. Add descriptive variable labels.
  5. Apply value labels consistently.
  6. Define all special missing-value codes.
  7. Select measurement levels carefully.
  8. Keep each column limited to one variable.
  9. Keep coding consistent across all cases.
  10. Run frequencies and descriptive statistics before analysis.
  11. Save an untouched copy of the original data.
  12. Avoid overwriting original variables during recoding or computation.

Suggested Visual Guide

A useful visual workflow for this article is:

Questionnaire or data source

Create a codebook

Define variables in Variable View

Enter or import observations in Data View

Check values, labels, and missing data

Run statistical analysis

Frequently Asked Questions

What is the difference between Data View and Variable View in SPSS?

Data View contains the actual values for cases and variables. Variable View contains the definitions and properties of those variables.

What does each row represent in SPSS Data View?

Each row normally represents one case, such as a participant, patient, student, organization, or observation.

What does each column represent in Data View?

Each column represents one variable, such as age, gender, treatment group, income, or test score.

What does each row represent in Variable View?

Each row represents one variable in the dataset.

What does each column represent in Variable View?

Each column represents an attribute, such as Name, Type, Width, Label, Values, Missing, Measure, or Role.

Should I use Variable View before Data View?

For a new manually entered dataset, it is generally best to define the variables in Variable View before entering observations in Data View.

Why does SPSS show dots in Data View?

A period in a numeric cell normally represents a system-missing value. It means that no valid numeric value is stored for that case and variable.

Why are numbers displayed as words in Data View?

Value Labels may be enabled. SPSS is displaying descriptive category labels instead of the underlying numeric codes.

Does changing a value label change the data?

No. Changing 1 = Male to 1 = Man, for example, changes the descriptive label but not the stored value 1.

Is gender numeric or string in SPSS?

It can be stored as either. A common method is to store gender as a numeric variable with value labels and assign Nominal as the measurement level.

Is an ID variable nominal or scale?

An identification number is normally nominal because its numbers identify cases rather than measure quantities.

Can I analyze string variables in SPSS?

Some procedures accept string categorical variables, but many statistical calculations require numeric variables. Numeric category codes with value labels are often more convenient.

What is the Role column used for?

Role tells supported dialogs whether a variable is intended as an input, target, partition, or another analytical role. It does not change the actual data or command syntax.

What happens when I change Measure from Nominal to Scale?

The data values do not change. The variable’s metadata changes, which can affect how it appears or is handled in some dialogs, charts, and procedures.

Are Data View and Variable View separate files?

No. They are different views of the same active SPSS dataset.

Conclusion

Data View and Variable View work together to organize an SPSS dataset.

Data View is where the actual observations are entered and inspected. Variable View is where the variables are named, described, formatted, coded, and classified.

Remember the basic structure:

  • In Data View, rows are cases and columns are variables.
  • In Variable View, rows are variables and columns are variable attributes.

A reliable SPSS workflow begins by planning the dataset, defining variables carefully in Variable View, entering or importing observations into Data View, and checking both views before running statistical analyses.

Correctly using these two views creates cleaner data, reduces coding errors, improves output readability, and provides a stronger foundation for valid statistical analysis.

About the author

Muhammad Hassan

Muhammad Hassan writes about research design, academic methods and data-analysis concepts for ResearchMethod.net. His work focuses on presenting methodological topics in clear language for students and early-career researchers. Articles are developed from recognized methodological literature and official software documentation.