Qualifications Framework level

EQF level

European Qualifications Framework (EQF) has 8 levels (1 – the lowest, 8 – the highest).

Levels reflect the complexity level of acquired knowledge, skills and competences (learning outcomes).


Go to the Glossary section
?

7

LQF level

Latvian Qualifications Framework (LQF) has 8 levels (1 – the lowest, 8 – the highest).

Levels reflect the complexity level of acquired knowledge, skills and competences (learning outcomes).

LQF covers stages of education starting from the basic education (level 1 – special basic education) to the highest education (level 8 – doctoral studies).


Go to the Glossary section
?

7

Learning outcomes

Learning outcomes are knowledge, skills and competences acquired during a certain period of learning.

In Latvia, learning outcomes are stipulated by state education standards and occupational standards (for the professional qualifications).

Learning outcomes of higher education are defined by higher education institutions.


Go to the Glossary section
?

Graduates of this study programme will:
– Acquire deep theoretical and practical knowledge in system analysis and design of the information systems, database systems and intelligent systems, as well as are able to perform already existing business system analysis, client and user interviews;
– Acquire deep theoretical and practical knowledge in programming, software systems and development environments, as well as in technologies and tools for application development;
– Be able to use different system development methods and tools for the system analysis and modelling tasks;
– Be able to develop and professionally use complex software products;
– Be able to use methodologies and tools based on object-oriented, functional or logical paradigm in the development of computer systems;
– Be able to independently define and critically analyse scientific and professional problems;
– Be able to choose the appropriate software products, tools and methods (including artificial intelligence methods) for solving problems;
– Be able to organize and manage group of software developers by applying professional standards, analyse work results and to provide risk management plan;
– Be able to improve independently their competencies.

Lead programming engineer

  • Knowledge

    Professional knowledge
    1. Principles of resource planning.
    2. Critical thinking.
    3. Lifecycle of information technology projects and systems.
    4. Team management methods.
    5. Principles and methods for selecting information.
    6. Methods for processing and analysing information.
    7. Methods for managing technical resources.
    8. Nature of accounting, principles, regulatory enactments, char of accounts.
    9. Time planning techniques.
    10. Principles of resource planning.
    11. Work assessment methodology.
    12. Risk management.
    13. Fundamentals of project management.
    14. Time planning strategies.
    15. Methods for assessing the quality of systems and processes.
    16. Software development processes.
    17. Operating principles and technical parameters of software.
    18. Computer applications and information technologies.
    19. Methods for searching and processing information.
    20. Project management.
    21. Project management in an international environment.
    22. Strategic management.
    23. Principles, methods, and tools of project management.
    24. Principles and norms of professional ethics.
    25. Time planning principles.
    26. Project governance processes.
    27. Modern trends in project management.
    28. Software documentation standard.
    29. Software architecture.
    30. Data structures.
    31. Methods for algorithm notation and development.
    32. Types and methods for algorithm notation.
    33. Software architecture.
    34. Data structures.
    35. Requirements analysis in the system development process.
    36. Methods for algorithm notation and development.
    37. Types and methods for algorithm notation.
    38. Software engineering.
    39. Entity-relationship models.
    40. Unified Modelling Language (UML) diagrams.
    41. Communication tools, channels, and development trends.
    42. Intercultural communication and communication differences.
    43. Guidelines for requirements specification.
    44. Requirements analysis in the system development process.
    45. Knowledge acquisition methods.
    46. Software development technologies.
    47. Software development methods.
    48. Comparison and assessment methods.
    49. Software development tools.
    50. Software development lifecycle.
    51. Programming methods.
    52. Software quality standards.
    53. Programming languages and technologies.
    54. Use of version control systems.
    55. Mathematical foundations of computer science.
    56. Database technologies.
    57. Development of software documentation.
    58. Management of software code configuration.
    59. Software code debugging and testing tools.
    60. Testing process methodology.
    61. Software quality standards.
    62. Software code debugging methods.
    63. Testing automation methods.
    64. Testing tools.
    65. Software testing methods.
    66. Software testing standards.
    67. Operating principles and technical parameters of software.
    68. Computer applications and information technologies.
    69. Testing process methodology.
    70. Software quality standards.
    71. Software code debugging methods.
    72. Testing automation methods.
    73. Testing tools and version control systems.
    74. Software testing methods.
    75. Software testing standards.
    76. Standards for management of software development projects.
    77. Software development documentation standards.
    78. Software development methods.
    79. Standards for management of software development projects.
    80. Software development verification and validation standards.
    81. Software auditing standards.
    82. Standards for management of software development projects.
    83. Standards for software development project documentation.
    84. Software development standards.
    85. Standards for management of software development projects.
    86. Software development verification and validation standards.
    87. Standards for management of software development projects.
    General knowledge
    1. Classification of regulatory enactments.
    2. Databases and information resources related to regulatory enactments and standards.
    3. Scope and requirements of Latvian, EU, and international regulatory enactments and standards applicable to the performance of work tasks.
    4. Potential injuries and illnesses related to the use of sector-specific technologies, systems, and equipment.
    5. Regulatory enactments concerning occupational safety and the necessary training and instruction of personnel.
    6. Principles and equipment for organising an ergonomic workplace.
    7. Technologies for the use of renewable energy resources.
    8. Methods and techniques for reducing emissions and greenhouse gas outputs.
    9. Environmentally friendly technologies for work organisation and performance.
    10. Grammar and language functions.
    11. Language styles and types of verbal interaction.
    12. Diversity of language and communication in different contexts.
    13. Sector-specific vocabulary and professional terminology.
    14. Public speaking.
    15. Concept of cultural diversity.
    16. Verbal and non-verbal communication in a multicultural environment.
    17. Use of professional terminology in English.
    18. Intercultural communication principles in a multicultural environment.
    19. Intercultural interaction.
    20. Proficiency in the use of ICT systems.
    21. Information and device security technologies and evaluation characteristics, personal data protection requirements.
    22. Classification, operating principles, components, technologies, protocols, and standards of information and communication technologies and data transmission networks.
    23. Principles of developing and formatting business documentation and presentations.
    24. Types, forms, and operational characteristics of entrepreneurship.
    25. Regulations regarding employment relationships.
    26. Types of remuneration and fundamental principles of its formation, characteristics depending on the company’s field of activity and the specifics of task execution.
    27. Structure, work organisation principles, and levels of personnel responsibility in software development companies.
    28. Distribution of duties and functions of a programming engineer and subordinated specialists.
    29. Social and political structure of society.
    30. Human rights and legal norms of civil law.
    31. Business communication, the social and information exchange environment of different generations.
    32. Fundamental principles of conflict resolution and stress management methods.
    33. Stages of research and innovation, research methodologies, scientific paradigms.
    34. Self-assessment principles and mechanisms.
    35. Professional development and growth.

  • Skills

    Professional skills and attitudes
    1. To ensure team leadership.
    2. To identify the nature of the problem to be resolved.
    3. To assess the scope of the problem.
    4. To select the set of resources necessary to resolve problems.
    5. To assess the selected information and restrictions.
    6. To plan the resources available for the task, adapting and selecting tools managed by the company.
    7. To plan the project, optimally using resources.
    8. To assess human resources and form a project work group.
    9. To plan human resources, project execution time and schedule.
    10. To ensure the compliance with the development process schedule and quality requirements.
    11. To plan and ensure risk management in accordance with the requirements of regulatory enactments and applicable standards, project goals, and needs.
    12. To manage/monitor the stages of project development.
    13. To assess financial risks and develop a plan for their mitigation within the scope of own professional activity (responsibility).
    14. To conduct systematic search and research of information, based on the technical parameters of software.
    15. To perform comparative analysis of software.
    16. To select the most suitable project management tools, methodologies, and iterative approaches for project management.
    17. To select, apply, and combine the most suitable methodology for project implementation.
    18. To plan the team’s work time rationally.
    19. To observe the norms of professional ethics and code of conduct.
    20. To follow the principles of effective communication.
    21. To analyse software documentation.
    22. To be familiar with the stages of software algorithm development.
    23. To ensure software development in accordance with the selected algorithm and established coding guidelines.
    24. To verify the conformity of software algorithm with user needs and test software operation scenarios.
    25. To be familiar with methods and techniques for algorithm notation and visualisation.
    26. To be familiar with methods for algorithm design and construction.
    27. To design algorithms and data structures according to the needs and available resources.
    28. To be familiar with the stages of system design.
    29. To be familiar with methods for visualising complex process descriptions.
    30. To be familiar with the Unified Modelling Language (UML).
    31. To possess knowledge of system analysis, delivery, and execution.
    32. To plan, manage, and disseminate work-related information (communication management).
    33. To respond and provide feedback to the communication target audience.
    34. To formulate a work task for continuous and automated software deployment.
    35. To ensure the acquisition of knowledge from the client and user for the development of requirements.
    36. To be familiar with methods for using software development tools.
    37. To verify the compliance of the software development tool with project requirements.
    38. To write source code according to the selected algorithm and established code development guidelines.
    39. To read and analyse the existing software unit source code.
    40. To verify the conformity of source code with user needs and test software units.
    41. To select the most efficient software development method according to the task description.
    42. To manage the conformity of the work environment with the technological process and rectify non-conformities.
    43. To refine and structure the design in algorithmic units.
    44. To process data (in relation to databases).
    45. To use a version control system for items.
    46. To write software code in accordance with coding guidelines.
    47. To assess the content and scope of testing work.
    48. To prepare the necessary and sufficient criteria definition for verifying the operation of a software unit.
    49. To prepare software unit test documentation.
    50. To analyse errors and deficiencies discovered during the software unit testing process.
    51. To prepare examples of software unit test data sets and corresponding expected results for software testing.
    52. To conduct systematic search and research of information, based on the technical parameters of software.
    53. To perform comparative analysis of software.
    54. To manage software versions.
    55. To process the possibilities of integrating the client request into existing systems.
    56. To plan and manage software deployment stages.
    57. To ensure client support and user training.
    58. To plan and manage software development stages.
    59. To prepare reports on the stages of software development.
    60. To identify software development risks and propose solutions.
    61. To plan the work of the software development team and monitor deadlines.
    62. To plan and perform quality audits of the software development process, standards, and codes.
    63. To plan the work of the software development team and organise internal knowledge sharing.
    64. To plan the software documentation development process.
    65. To plan the software deployment process.
    66. To implement the software deployment plan.

    General skills and attitudes
    1. To understand the requirements of sector-specific standards and regulatory requirements.
    2. To select appropriate regulatory enactments and standards for completing a work task.
    3. To comply with and use the necessary regulatory enactments for completing a work task.
    4. To comply with and use field-specific standards when completing a work task.
    5. To comply with regulatory occupational safety requirements when completing tasks.
    6. To evaluate the impact of work environment risk factors on human health and safety.
    7. To analyse and use environmentally friendly technologies.
    8. To evaluate the environmental impact of the project and select the most efficient solution for completing a task when designing system operations.
    9. To communicate and express own opinion in the official language both verbally and in writing while performing professional work duties.
    10. To use professional IT terminology in the official language.
    11. To follow business communication principles in the official language.
    12. To use English for verbal and written communication in various professional situations and settings.
    13. To follow intercultural communication principles in a multicultural environment.
    14. To comply with information technology security and personal data protection requirements.
    15. To use information resources, systems, databases, and software to retrieve and process information.
    16. To use information technologies, tools, and specialised software to perform sector-specific duties.
    17. To understand the operational principles and functions of software development companies and their structural units depending on the field of activity and specifics of the company.
    18. To respect the rights and obligations of the employer and employee.
    19. To comply with internal rules and professional and general ethical principles of the organisation.
    20. To work in a team, communicate with subordinated employees, resolve operational conflicts, and find compromise solutions.
    21. To understand client needs and interest, following the principles of best practices and building a foundation for long-term cooperation.
    22. To communicate efficiently in a multicultural environment, cooperating with specialists at different levels and communicating with individuals involved in IT processes.
    23. To improve own social and civic skills depending on the specifics of information technologies and professional duties in the field of professional activity.
    24. To critically evaluate the relevance of own professional experience, skills, and knowledge to the performance of professional duties.
    25. To improve own professional competences in response to the emergence of new technologies and changes in professional duties and sector-specific regulatory requirements.

  • Competences/ autonomy

    Professional competences
    1. Ability to assess the resources necessary for project development.
    2. Ability to evaluate the adequacy of existing resources for project implementation and the scope of the task.
    3. Ability to plan the project implementation time and the necessary technical support for the team.
    4. Ability to identify issues during the task execution.
    5. Ability to respond promptly to changes in the task execution schedule.
    6. Ability to understand the scope of required competences.
    7. Ability to manage a team and resolve conflict situations.
    8. Ability to define the task execution time.
    9. Ability to evaluate the conformity of completed work with the assigned tasks.
    10. Ability to assess the technical information of the assigned work.
    11. Ability to develop a calendar plan.
    12. Ability to evaluate the scope of the task.
    13. Ability to ensure the selection of resources for the development process in line with the requirements of the applied technologies and quality documentation.
    14. Ability to coordinate the development of the risk management plan and monitor its implementation.
    15. Ability to identify budget planning methods.
    16. Ability to plan software development activities and understand the principles of cost formation for their implementation.
    17. Ability to define and analyse the functionality, structure, and operation of software, including the processes, development tools, and technologies used in the software.
    18. Ability to obtain, select, and analyse information on existing IT solutions and technologies.
    19. Ability to conduct research on market supply and demand.
    20. Ability to formulate and substantiate the minimum resource requirements for a system during execution.
    21. Ability to perform software assessment.
    22. Ability to substantiate and document own opinion.
    23. Ability design by reading and understand the specifications of software requirements.
    24. Ability to comply with the existing standards applicable to the project.
    25. Ability to design by analysing various technical solutions and selecting the most appropriate one.
    26. Ability to design by creating a conceptual data model and a physical model.
    27. Ability to design by creating an implementation model (class and/or function hierarchy).
    28. Ability to design by constructing and describing algorithms.
    29. Ability to design by preparing the software design description document.
    30. Ability to apply and combine project management methodologies, tools, and iterative approaches.
    31. Ability to responsibly complete tasks individually or in a team, meeting the established work performance deadlines and quality requirements.
    32. Ability to read and analyse algorithm descriptions and pseudocode.
    33. Ability to transform the source code of an algorithm in the programming language specified for the task.
    34. Ability to simulate software operation scenarios.
    35. Ability to document software algorithms and operation scenarios, using pseudocode and visual algorithm notation.
    36. Ability to select the most appropriate algorithm according to the project needs and available resources.
    37. Ability to develop an algorithm, using design and construction methods appropriate for the task.
    38. Ability to select the appropriate algorithm for completing specific tasks according to the project needs and the amount of available resources.
    39. Ability to develop a system model, using the Unified Modelling Language.
    40. Ability to read and analyse visualised process descriptions.
    41. Ability to develop system design stages while collaborating in a team.
    42. Ability to obtain client requirements.
    43. Ability to document client requirements to plan tasks.
    44. Ability to formulate a work task for continuous and automated software deployment.
    45. Ability to ensure the compliance with requirements.
    46. Ability to assess the tools and technologies necessary for code development.
    47. Ability to propose alternative solutions for task execution.
    48. Ability to manage and configure the development environment.
    49. Ability to develop program code, reading and understanding software design descriptions.
    50. Ability to analyse input and output data.
    51. Ability to comply with design and software development guidelines.
    52. Ability to construct and implement algorithms.
    53. Ability to read and analyse program source code.
    54. Ability to optimise software, analysing its execution time.
    55. Ability to document the code.
    56. Ability to debug the developed software code.
    57. Ability to define and manage code requirements.
    58. Ability to develop unit tests in accordance with guidelines.
    59. Ability to perform testing, analysing input and output data.
    60. Ability to perform testing, constructing algorithms.
    61. Ability to perform testing, analysing the program execution time.
    62. Ability to test software by conducting change impact analysis.
    63. Ability to test software by conducting continuous and automated deployment.
    64. Ability to analyse the functionality, structure, and operation of software, including the processes, development tools, and technologies used in the software.
    65. Ability to obtain, select, and analyse information independently.
    66. Ability to conduct research on market supply and demand.
    67. Ability to maintain software, reading and understanding the documentation and code of the maintained system.
    68. Ability to maintain software, processing change requests and issue reports.
    69. Ability to maintain software by conducting change impact analysis.
    70. Ability to maintain software by making changes to the software.
    71. Ability to maintain software, managing the configuration of maintained software.
    72. Ability to read code and assess compliance with functional requirements.
    73. Ability to assess the applied software development standards in the project.
    74. Ability to document and communicate non-conformities.
    75. Ability to draw up software development reports in accordance with client requirements.
    76. Ability to manage team work according to the scheduled deliverables under the project.
    77. Ability to identify and communicate code delivery risks to the project manager.
    78. Ability to assess code quality and compliance with the standards set by the client or sector.
    79. Ability to document and communicate non-conformities.
    80. Ability to manage team planning according to established goals of the project.
    81. Ability to identify and communicate code delivery continuity risks to the project manager.
    82. Ability to explain documentation requirements to programmers.
    83. Ability to deliver software documentation according to the standards established by the client.
    84. Ability to plan the timely development of software documentation.
    85. Ability to identify and document risks associated with software delivery.
    86. Ability to propose software delivery rollback scenarios and risks.
    87. Ability to deliver software deployment documentation and support the deployment.
    88. Ability to document and communicate the software delivery plan.
    89. Ability to implement the cutover plan.
    General competences
    1. Ability to understand and comply with the requirements of sector-specific regulatory enactments and standards and select the appropriate regulatory enactments and standards to compete the specific work task.
    2. Ability to responsibly ensure and organise the task execution by complying with occupational safety requirements and using safe work techniques and work organisation principles.
    3. Ability to ensure, organise, and monitor the compliance with environmental protection requirements depending on specialised demands.
    4. Ability to assess the environmental impact of a project.
    5. Ability to express and interpret concepts, ideas, facts, and opinions both verbally and in writing in the official language, understanding and using professional terminology and concepts.
    6. Ability to engage in construction discussion and express reasoned opinions, while providing information in a correct, comprehensible, and linguistically appropriate manner.
    7. Ability to communicate in English, using professional terminology.
    8. Ability to read, understand, and translate professional, specialised, and technical literature.
    9. Ability to efficiently communicate in a multicultural environment, following the principles of intercultural communication.
    10. Ability to comply with information technology security requirements and occupational safety requirements when performing professional duties.
    11. Ability to use information resources, systems, databases, specialised software, and other information and communication technologies when performing sector-specific duties.
    12. Ability to understand the specific operating principles, structure, and functions of various fields and comply with regulations regarding employment relationships and principles of professional ethics when performing duties.
    13. Ability to use social and civic skills in business and professional communication in the work setting and civil situations.
    14. Ability plan, make decisions, and assume responsibility for own professional development, including the forms and directions of developing professional skills and knowledge.

Qualification acquisition requirements

Previous education
Higher education qualification of LQF level 6 (bachelor, professional bachelor or professional higher education qualification) in the same or compatible branch of science or professional field of higher education, as well as a certain professional experience laid down by higher education institution
Ways to acquire 
Qualifications can be acquired in the framework of education programs or in the evaluation and recognition of non-formal knowledge, skills and competences acquired (in vocational education LKI Levels 2-4).
?
Formal (through education programmes)
ECTS credit points 
Snice 11.10.2022 60 credit points correspond to the study results acquired in full-time studies in one academic year in accordance with the European Credit Transfer and Accumulation System (ECTS).Since 11.10.2022

Till 11.10.2022 1 Latvian credit point corresponds to 1,5 ECTS credit point.
?
120
Duration of study 
Duration of qualification in full-time studies
?
2 years

Qualification document

Awarding body

Higher education institution:

Collapse

Qualifications Framework level

EQF level

European Qualifications Framework (EQF) has 8 levels (1 – the lowest, 8 – the highest).

Levels reflect the complexity level of acquired knowledge, skills and competences (learning outcomes).


Go to the Glossary section
?

7

LQF level

Latvian Qualifications Framework (LQF) has 8 levels (1 – the lowest, 8 – the highest).

Levels reflect the complexity level of acquired knowledge, skills and competences (learning outcomes).

LQF covers stages of education starting from the basic education (level 1 – special basic education) to the highest education (level 8 – doctoral studies).


Go to the Glossary section
?

7

LQF PQ level:

Kas ir LKI?2

Theoretical and practical training corresponding to the LQF levels, characterized by the learning outcomes that can be achieved at the relevant level, which gives the opportunity to perform work corresponding to a certain level of complexity and responsibility.
?

7

Qualification field, stage and type

Thematic field (ISCED 2013)
International Standard Classification of Education (ISCED) developed by UNESCO.
?

Information and Communication Technologies (ICTs) (061)

Detailed field: (ISCED 2013)

Database and network design and administration (0612)

Education
Stages of Latvian education system included in the LQF:
- basic education
- secondary education
- higher education
?

Higher education

Qualification type
ITypes of Latvian education:
-General education
-Professional education
-Academic education
?

Vocational

Full or partial

Full qualification

Sector Qualifications Structure: Electronic and optical equipment manufacturing, information and communication technology sector

Kvalifikācijas tips:
Base qualification:
Connected to: Professional Bachelor Degree in Computer Systems, Programming Engineer (RTU) , (BA) , Professional Bachelor's Degree in Computer Systems, Software Engineer (BAT) , (ISMA) , Professional Bachelor in Information Technologies, Programming Engineer (LiepU) , Professional Bachelor's Degree in Information Technology, Software engineer (RTA) , Professional bachelor's degree, Programming engineer (ViA) , Professional Bachelor’s Degree in Information Technologies, Programming engineer (DU) , Professional Bachelor Degree in Information Technologies, Programming Engineer (LBTU) , Professional Bachelor’s Degree in Information Technologies, Programming engineer (RTU) , (RTU) , Professional Bachelor Degree in Computer Systems, Programming Engineer (RTU) , Professional Bachelor Degree in Computer Systems, Qualification of Programming Engineer (BA) , (BAT) , Professional Bachelor Degree in Computer Systems, Programming Engineer (RTU) , Professional bachelor degree in computing science, Programming Engineer (EKA) , Professional bachelor degree in computing science, Programming Engineer (EKA) , Professional bachelor degree in information technology, Software Engineer (LiepU) , Professional Bachelor's Degree in Information Technologies, Programming Engineer (ViA) , Professional Bachelor’s Degree in Information Technologies, Software Engineer (DU) , Professional Bachelor in Information Technologies, Programming Engineer (LBTU) , (RTU) , Professional Master Degree in Computer Control and Computer Networksand, Engineer in Programming (RTU) , Professional Master Degree in Information Technology, Engineer in Programming (LiepU) , Professional Master's degree in Computer Systems, Systems Analyst (ISMA) , Professional Master Degree in Computer Systems, Systems Analyst (RTU) , Professional Master’s Degree in Computer Sciences, System Analyst (RTA) , DIPLOMA OF VOCATIONAL SECONDARY EDUCATION with professional qualification: Information Systems Security Specialist

Link to the descriptions of the Sector Qualifications Structure levels

Other information

National Education Information System

Active qualification

Period for issuing qualification: 2023-2029

Last changes: 27.06.2025

Posted: 01.02.2024