Professional knowledge
1. Fundamental principles of teamwork.
2. Software development lifecycle models.
3. Project management methods for work planning.
4. Company’s standards and procedures.
5. Methods and tools for assessing the resource capacity.
6. Risk management – risk identification.
7. Planning of project resources.
8. Company’s documentation.
9. Knowledge acquisition methods (e.g., interviews, brainstorming, focus groups).
10. Modelling of organisational structure.
11. Process modelling – for stakeholder engagement.
12. Cooperation and communication methods and tools.
13. Planning methods and tools.
14. Role and responsibility assignment matrix (RACI matrix).
15. Software development lifecycle models.
16. Methods for researching and analysing the organisational structure.
17. Methods and tools for requirements and change management.
18. Decision-making methods.
19. Organisational policies.
20. Information management methods.
21. Methods for representing structured information.
22. Process modelling – for information management.
23. Tools for requirements and change management.
24. Work performance assessment methods.
25. Process analysis methods.
26. Risk management – risk impact analysis.
27. Cause-and-effect analysis.
28. Fundamental principles of teamwork.
29. Fundamental principles of planning.
30. Fundamental principles of risk management.
31. Lifecycle of IT solutions.
32. Methods and tools for requirements and change management.
33. Requirements engineering methods.
34. Role of knowledge, information, and data in business systems and their management.
35. Theoretical foundations of the operation of business, IT, and physical systems.
36. Risk analysis and management.
37. Methods and tools for analysing problems and objectives.
38. Methods and tools for analysing organisational structures.
39. Methods and tools for analysing company’s capabilities and processes.
40. Methods and tools for representing company’s models and architecture.
41. Methods and tools for value analysis.
42. Methods for analysing the strategic interaction of business environment elements.
43. Solution assessment methods and tools.
44. General architecture of IT solutions.
45. Installation, use, and configuration of existing IT solutions.
46. Structure of software and corresponding operating systems.
47. Methods and tools for modelling IT solutions.
48. General structure and architecture of IT solutions.
49. Support documentation, methods, and tools for the development of IT solutions.
50. Development of IT solution documentation.
51. Methods, notations, and tools for describing and modelling IT solutions.
52. Methods and technical means for improving solutions.
53. Business domain of IT solution application.
54. Functionality and structure of IT solutions.
55. Methods for defining and describing IT solutions.
56. Procedures, standards, methods, and tools for the development, formatting, and codification quality of documents.
57. Requirements engineering methods.
58. Methods and tools for the visualisation of information flows and processes.
59. Decision modelling methods and tools.
60. Fundamental principles of planning.
61. Fundamental principles of risk management.
62. Stakeholder analysis techniques.
63. Methods for identifying the goals and scope of a project.
64. Requirements elicitation techniques and their selection criteria.
65. Methods for identifying goals and scope.
66. Fundamental principles of resource management.
67. Methods for encouraging people’s engagement.
68. Requirements elicitation techniques and their selection criteria.
69. Systems thinking approach.
70. Principles of verbal and non-verbal communication.
71. Methods and tools for knowledge retrieval.
72. Methods for encouraging people’s engagement.
73. Active listening techniques.
74. Conflict resolution methods.
75. Sector-specific documentation standards.
76. Standards for documenting the context of requirements elicitation.
77. Information documentation methods.
78. Information visualisation methods.
79. Support tools and methods for compiling elicitation session results.
80. Critical thinking approach.
81. Conversation management methods.
82. Conflict resolution methods.
83. Methods for promoting and supporting requirements approval.
84. Principles of verbal and non-verbal communication.
85. Methods and tools for communication elicitation results.
86. Fundamental principles of teamwork.
87. Methods and tools for facilitating the cooperation process.
88. Intercultural communication principles in a multicultural environment.
89. Approaches and methods for requirements analysis.
90. Best practices and principles of the documentation of requirements.
91. Methods and tools for requirements and system modelling.
92. Solution architecture.
93. Visual prototyping methods and tools.
94. Methods and tools for analysing user experience.
95. Circulation of documents within the company and project.
96. Techniques and tools for secure data storage.
97. Use of scientific methods in data analysis.
98. Solution architecture.
99. Requirements quality criteria.
100. Solution assessment criteria.
101. Fundamental principles of requirements traceability.
102. Requirements traceability methods.
103. Organisation’s business principles.
104. Supplier assessment methods.
105. Knowledge acquisition methods (e.g., interviews, brainstorming, focus groups).
106. Market research and analysis methods.
107. Organisational structure and culture.
108. Cost calculation methods.
109. Risk analysis.
110. Methods for assessing alternatives.
111. Business analysis methods.
112. SWOT analysis.
113. Focus groups.
114. Qualitative and quantitative solution assessment methods.
115. Market research methods.
116. Decision analysis methods.
117. User case/scenario analysis.
118. Risk analysis – risk identification.
119. Methods for assessing non-conformities (qualitative and quantitative assessment methods).
120. Cause-and-effect analysis.
121. Enterprise and organisational architecture frameworks.
122. Solution development techniques.
123. Analysis of business rules.
124. Risk management – impact analysis of solutions.
125. Solution evaluation methods and tools (SWOT, cause-and-effect analysis, etc.).
126. Focus groups.
127. Solution development technologies.
128. Cost assessment methods.
129. Brainstorming and other idea generation methods.
130. Process analysis.
131. Risk management.
132. Dependency of requirements on changes in the business environment.
133. Interdependencies between requirements.
134. Requirements traceability methods.
135. Impact of changes to requirements on the solution and its development process.
136. Requirements prioritisation methods.
137. Requirements management methods.
138. Fundamental principles of planning.
139. Fundamental principles of risk management.
140. Methods and tools for change management.
141. Solution assessment methods.
142. Methods for managing stakeholder engagement.
143. Conversation management methods.
144. Methods for promoting and supporting requirements approval.
145. Conflict resolution methods.
146. Functionality of the solution.
147. Cooperation and communication methods and tools.
148. Determination and design of solution requirements.
149. Fundamental principles of conflict resolution.
150. Business communication.
151. Business correspondence.
152. Principles of professional ethics.
153. Cooperation and communication techniques and tools.
154. Active listening techniques.
155. Professional terminology
General knowledge
1. Grammar and language functions.
2. Language styles and types of verbal interaction.
3. Diversity of language and communication in different contexts.
4. Sector-specific vocabulary and professional terminology.
5. Public speaking.
6. Concept of cultural diversity.
7. Verbal and non-verbal communication in a multicultural environment.
8. Use of professional terminology in English.
9. Intercultural communication principles in a multicultural environment.
10. Intercultural interaction.
11. Fundamental principles and use of statistics.
12. Use of scientific methods for implementing research results in practice.
13. Development of sector-specific technologies and their potential applications.
14. Information and device security technologies and evaluation characteristics, personal data protection requirements.
15. Principles of developing and formatting business documentation and presentations.
16. Business organisation.
17. Strategic management.
18. Company’s record-keeping and financial accounting system.
19. Financial planning, forecasting, and management methods.
20. Project development and management.
21. Social and political structure of society.
22. Methods for studying socio-technical problems and mechanisms for addressing them.
23. Manifestations/indicators/criteria of social welfare.
24. Business communication, the social and information exchange environment of different generations.
25. Regulatory enactments governing employment relationships.
26. Fundamental principles of conflict resolution and stress management methods.
27. Regulatory enactments establishing occupational safety, personnel training and instruction requirements.
28. Fire safety, electrical safety, and civil defence regulations.
29. Principles and equipment for organising an ergonomic workplace.
30. Potential injuries and illnesses related to the use of sector-specific technologies, their systems, and equipment.
31. Technologies for the use of renewable energy resources.
32. Methods and techniques for reducing emissions and greenhouse gas outputs.
33. Environmentally friendly technologies for work organisation and performance.
34. Regulatory framework for emergency situations and states of emergency.
35. Field-specific regulatory enactments.
36. Classification of regulatory enactments in the IT sector.
37. Databases and information resources related to regulatory enactments and standards.
38. Scope and requirements of Latvian, EU, and international regulatory enactments and standards applicable to the performance of work tasks.
39. Self-assessment principles and mechanisms.
40. Professional development and growth.
41. Facts, theories, and paradigms in the development of the professional field.
42. Research methods and methodology.

Professional skills and attitudes
1. To select the most appropriate requirements analysis and work planning approach based on project needs.
2. To select the required level of formality and detail for analysis results.
3. To define analysis activities.
4. To select a resource volume estimation and work planning approach.
5. To identify risks.
6. To assess and classify risks.
7. To identify stakeholders.
8. To define the types and methods of stakeholder collaboration.
9. To identify the types and requirements of stakeholder communication.
10. To develop requirements classification principles.
11. To plan the prioritisation process.
12. To define the procedures for escalating decision-making.
13. To define the procedures for requesting changes.
14. To define methods for describing changes.
15. To develop procedures for evaluating changes.
16. To define the impact assessment process.
17. To obtain approval for the analysis plan and approach.
18. To determine the procedures for structuring and organising the information to be analysed.
19. To determine the level of information abstraction.
20. To plan the traceability approach.
21. To plan the requirements reuse.
22. To determine the form of storage and accessibility of requirements.
23. To determine the types of requirement attributes.
24. To determine assessment criteria.
25. To analyse work performance.
26. To analyse the obtained results.
27. To recommend improvements in the analysis performance.
28. To identify the potential and requirements for the development and improvement of a solution.
29. To determine the priority of solution development requirements.
30. To provide an assessment of the development and sustainability of a solution.
31. To identify the boundaries of a solution and its context (business environment).
32. To identify the factors influencing the business environment.
33. To conduct research on business environment, following the principles of professional ethics.
34. To develop and analyse business environment models.
35. To identify and respect regulatory documents related to the solution.
36. To assess the impact of proposed solutions on the business environment.
37. To identify and study existing solutions.
38. To compile and study documentation on existing IT solutions within the company.
39. To develop a set of assessment criteria for available solutions.
40. To conduct a comparative analysis of IT solutions available on the market.
41. To define the roles and main responsibilities of the users of IT solutions.
42. To study the technical and user documentation of IT solutions.
43. To assess the sustainability of IT solutions.
44. To comply with the norms of professional ethics when analysing IT solutions.
45. To develop the information flow, process, use case and data models for the solution.
46. To develop representative scenarios for the use of IT solutions.
47. To develop documentation describing the solution.
48. To analyse the strengths and weaknesses of the solution.
49. To collect feedback from stakeholders.
50. To identify changes to the IT solution in line with business environment processes.
51. To propose the most appropriate plan for implementing the necessary changes.
52. To determine the impact of improvement proposals on the overall performance of IT solutions.
53. To structure the results of the current IT solution analysis in a way that is understandable to stakeholders.
54. To present the results of the current IT solution analysis to stakeholders.
55. To identify the objectives and scope of requirements elicitation.
56. To identify stakeholders.
57. To select requirements elicitation techniques.
58. To develop and coordinate a comprehensive requirements elicitation plan for an IT solution.
59. To identify the objectives and scope of the elicitation session.
60. To define the content of the elicitation session and select elicitation techniques.
61. To develop an elicitation session plan.
62. To ensure the necessary resources. To prepare stakeholders.
63. To open the elicitation session and remind of its objectives and procedures.
64. To engage and prepare the elicitation session participants for active involvement in the process if their attitude and level of engagement are found to be insufficient.
65. To manage the elicitation session according to the plan.
66. To respond to new aspects uncovered during the elicitation session and adjust the session plan if such aspects have been identified.
67. To document the final result of the elicitation session.
68. To format the elicitation results according to the recipients’ needs.
69. To compare the elicitation session results to those of other elicitation sessions, identify inconsistencies, and rectify them.
70. To review the elicitation session results together with the stakeholders, obtain and process feedback and comments.
71. To coordinate the elicitation session results with stakeholders.
72. To define communication objectives and information recipients.
73. To communicate the elicitation session results to stakeholders.
74. To verify the information recipients’ understanding of elicitation results.
75. To incorporate elicitation session results into related artefacts (work plan, requirements specification, and others).
76. To periodically monitor the stakeholder engagement activity and efficiency.
77. To apply motivation methods to engage stakeholders if any stakeholder shows insufficient level of activity or efficiency.
78. To analyse requirements elicitation results.
79. To determine the necessary level of detail for requirements based on the type and level of abstraction of the requirements.
80. To describe requirements and their attributes.
81. To define solution use cases.
82. To develop data models, business process models, functional models, and user interface prototypes.
83. To cooperate with developers in the implementation of data models.
84. To participate in system architecture design and the selection of technologies.
85. To develop requirements documentation according to the standards, best practices,
86. and principles of secure data exchange.
87. To perform requirements quality assurance.
88. To review requirements documentation against compliance and quality criteria.
89. To identify the stakeholders’ assumptions about the solution.
90. To define measurable assessment criteria to assess the results of solution implementation.
91. To assess the conformity of requirements with the solution framework and stakeholder needs.
92. To describe the possible solution acquisition approaches, such as purchase, development, or a combination of both.
93. To describe the possibilities of improving the business process or the existing solution.
94. To apply requirements to related and impacted solution components, organisational units, processes, etc.
95. To calculate and describe potential benefits for each proposed alternative.
96. To calculate potential implementation and operational costs of solutions.
97. To determine the potential value of solutions for stakeholders.
98. To evaluate alternatives and develop recommendations for the most valuable solution.
99. To participate in the development of the business case.
100. To develop solution assessment criteria.
101. To validate the assessment criteria with stakeholders.
102. To assess the solution according to the criteria.
103. To compare the performance of the current solution against expectations.
104. To identify risks and detect anomalies and deviations in the solution.
105. To identify non-conformities.
106. To identify dependencies between solution and organisational competences and determine whether those dependencies impose limitations on the solution.
107. To identify operational issues in the solution and their causes.
108. To assess the impact of contextual factors to the solution.
109. To assess the organisational culture.
110. To perform the stakeholder impact analysis.
111. To assess the impact of the solution on the organisational structure and its changes.
112. To assess the organisation’s ability to adapt the solution.
113. To develop additional assessment criteria, if necessary.
114. To determine the most appropriate solution development strategy based on the solution assessment results, improve solution performance, and leave the solution unchanged or discontinue its use.
115. To develop recommendations for improving solution performance, implementing organisational changes, and reducing complexity.
116. To communicate recommendations to stakeholders.
117. To identify and document relationships between various requirements.
118. To identify and document relationships between requirements and other solution development artefacts.
119. To organise and promote the requirements prioritisation and approval process.
120. To create requirement attribute schemes and maintain information on requirement attribute values.
121. To update requirement artefacts in line with changes to requirements during their lifecycle.
122. To ensure the possibility of requirements reuse within a project or across several projects.
123. To assess the impact and resource intensity of changes.
124. To cooperate with experts when assessing changes to requirements.
125. To organise the process of reviewing and accepting changes.
126. To document and communicate changes to requirements.
127. To organise the process of reviewing and approving requirements.
128. To resolve conflicts and reach a compromise in case of conflict situations during the approval of requirements.
129. To document and communicate the results of requirements approval.
130. To provide consultations on the current functionality of the solution.
131. To provide consultations on the possibilities of developing and improving the solution.
132. To participate in assessing the resource intensity of the solution.
133. To communicate verbally and in writing with stakeholders.
134. To seek compromises in achieving assigned tasks and goals.
135. To organise the communication process.
136. To document the communication result.
General skills and attitudes
1. To communicate and express own opinion in the official language both verbally and in writing while performing professional work duties.
2. To use professional IT terminology in the official language.
3. To follow business communication principles in the official language.
4. To follow intercultural communication principles in a multicultural environment.
5. To use professional terminology in English for verbal and written communication in various professional situations and cultural environments.
6. To assess appropriate models for selecting problem-solving strategies in complex situations.
7. To evaluate the significance of results obtained through data analytics models and methods.
8. To apply conceptual and mathematical models, methods, algorithms, and structures to find a solution.
9. To use information resources, systems, databases, and software to retrieve and process information.
10. To use information technologies, tools, and specialised software to perform sector-specific duties.
11. To use secure and legal information technology tools and services.
12. To ensure secure storage of electronic documentation and data.
13. To follow sector-specific standards and best practice recommendations when performing daily work tasks.
14. To comply with information technology security and personal data protection requirements.
15. To set individual and collective work goals and implement them according to the established business plan.
16. To use financial planning and forecasting methods to implement a business idea.
17. To critically evaluate risks associated with planned activities for the implementation of a business idea.
18. To assume individual and collective responsibility for creating new values.
19. To work in a team, communicate with subordinated employees, resolve operational conflicts, and find compromise solutions.
20. To understand client needs and interest, following the principles of best practices and building a foundation for long-term cooperation.
21. To communicate efficiently in a multicultural environment, cooperating with specialists at different levels and communicating with individuals involved in IT processes.
22. To improve own social and civic skills depending on the specifics of information technologies and professional duties in the field of professional activity.
23. To respect the rights and obligations of the employer and employee.
24. To comply with internal rules and professional and general ethical principles of the organisation.
25. To engage in addressing issued of shared or public interest, including contributing to sustainable development of society.
26. To participate in/initiate the development of socially responsible initiatives.
27. To comply with regulations regarding employment relationships.
28. To observe the norms of professional ethics and code of conduct.
29. To respect the rights and obligations of the employer and employee.
30. To plan own working time efficiently and prioritise assigned work.
31. To meet work performance deadlines and quality requirements.
32. To apply regulatory occupational safety requirements when completing tasks.
33. To act in accordance with fire safety, electrical safety, and environmental protection requirements.
34. To analyse and use environmentally friendly technologies.
35. To assess the environmental impact of a project.
36. To select the most efficient solution for completing a task when designing system operations.
37. To fulfil the requirements of sector-specific standards and regulatory requirements.
38. To select appropriate regulatory enactments and standards for completing a work task.
39. To apply field-specific standards when completing a work task.
40. To critically evaluate the relevance of own professional experience, skills, and knowledge to the performance of professional duties.
41. To improve own professional competences in response to the emergence of new technologies and changes in professional duties and sector-specific regulatory requirements.
42. To keep track of sector developments.
43. To demonstrate understanding and ethical responsibility regarding the scientific results or the impact of professional activity on the environment and society.

Professional competences
1. Ability to decompose the scope of work.
2. Ability to identify, anticipate, and assess project risks.
3. Ability to evaluate stakeholders’ experience, cultural differences, and the impact of location for planning the analysis process.
4. Ability to evaluate the suitability of available approaches for the specifics and goal of the work.
5. Ability to plan work according to the context and constraints of the project.
6. Ability to identify stakeholders involved in the business process.
7. Ability to identify mutual influence between stakeholders.
8. Ability to identify risks associated with stakeholder engagement.
9. Ability to plan and organise cooperation with stakeholders for the purpose of requirements elicitation.
10. Ability to adapt the change approval process in line with the specifics of the business domain and organisational culture.
11. Ability to plan the analysis process, its activities, and activity performance controls.
12. Ability to organise and classify information, ensuring its comprehensive management throughout the requirements lifecycle.
13. Ability to use information management tools suitable for sector-specific practice and organisational policies.
14. Ability to evaluate information storage and accessibility criteria in line with requirements for the protection of information, devices, and personal data.
15. Ability to assess work performance in line with the established criteria and identify possible improvements.
16. Ability to distinguish primary needs from secondary needs.
17. Ability to assess the maturity of requirements.
18. Ability to present comprehensible proposals for IT development in various formats, according to stakeholder needs.
19. Ability to substantiate choices with reasoned arguments.
20. Ability to explore, model, analyse, and represent the business environment (goals, issues, business system structure, and processes) in sufficient detail.
21. Ability to link business environment developments related to the system with the functionality of an IT solution.
22. Ability to identify and represent the current state of business environment.
23. Ability to identify and represent the desired state of business environment and the corresponding solutions.
24. Ability to identify, represent, and evaluate the transition from the current business environment to the desired business environment.
25. Ability to explore and represent the functionality, constraints, and related aspects of IT solutions.
26. Ability to apply the established requirements to the capabilities of the IT solution to be studied.
27. Ability to assess the quantitative indicators of IT solutions.
28. Ability to conduct market research on available IT solution offers.
29. Ability to describe the operation of an IT solution in a manner understandable to stakeholders.
30. Ability to distinguish the most important functionality of the IT solution from less important.
31. Ability to understand the data structure and processes of an IT solution.
32. Ability to distinguish and understand the static and dynamic aspects of an IT solution/
33. Ability to create unified descriptions of the operation of an IT solution.
34. Ability to identify and assess shortcomings and improvement opportunities in an IT solution.
35. Ability to link changes in the business environment with the functionality of an IT solution.
36. Ability to propose the most suitable direction for technical solution development for implementing identified suggestions.
37. Ability to assess the positive features of IT solutions.
38. Ability to describe the analysis results in a manner understandable to stakeholders.
39. Ability to organise information in a document in a structured manner.
40. Ability to develop technical documentation.
41. Ability to substantiate the selection of the proposed solution with reasoned arguments.
42. Ability to acquire knowledge of the relevant business domain.
43. Ability to define and plan the scope of work.
44. Ability to decompose the scope of work.
45. Ability to identify and manage risks.
46. Ability to define and plan the scope of work.
47. Ability to decompose the scope of work.
48. Ability to organise the performance of own work and work of other individuals related to the project.
49. Ability to manage work groups.
50. Ability to acquire knowledge of the relevant business and solution domain.
51. Ability to manage the knowledge retrieval session and adapt according to the situation and conditions.
52. Ability to document information obtained during the knowledge retrieval session (including data, stakeholder response, and other information).
53. Ability to identify and manage conflict situations.
54. Ability to methodically acquire new knowledge and develop existing knowledge.
55. Ability to methodically organise and structure information.
56. Ability to document the requirements elicitation result.
57. Ability to visualise information in a comprehensible manner.
58. Ability to identify inconsistencies and shortcomings in the scope of information.
59. Ability to reach compromise in cases of conflicting information.
60. Ability to conduct negotiations.
61. Ability to organise the process of approving requirements elicitation results.
62. Ability to present information according to the stakeholders’ level of comprehension and skills.
63. Ability to assess the information recipient’s understanding of provided information.
64. Ability to organise the performance of own work and work of other individuals related to the project.
65. Ability to manage work groups.
66. Ability to motivate people.
67. Ability to efficiently communicate in a multicultural environment, following the principles of intercultural communication.
68. Ability to analyse information.
69. Ability to specify and model requirements at the appropriate level of abstraction.
70. Ability to use requirement modelling methods.
71. Ability to define and model the data structure, processes, and objects of a solution.
72. Ability to define and model the company’s business processes.
73. Ability to organise and structure information.
74. Ability to use standards and best practices for the documentation of requirements.
75. Ability to acquire and understand standards and guidelines.
76. Ability to assess requirements in accordance with standards, guidelines, and criteria.
77. Ability to communicate requirements to stakeholders and obtain their approval.
78. Ability resolve conflicts and represent requirements in various formats, according to stakeholder needs.
79. Ability to objectively develop and present alternative recommendations.
80. Ability to resolve conflicts.
81. Ability to substantiate the potential value, costs, benefits, and shortcomings of the proposed solution options.
82. Ability to verify the operation of a completed IT solution according to the requirements.
83. Ability to agree with stakeholders on solution assessment criteria.
84. Ability to assess the solution.
85. Ability to assess the compliance of the solution with standards, regulatory requirements, and requirements.
86. Ability to analyse the obtained data.
87. Ability to analyse the structure and components of the solution and determine their dependencies.
88. Ability to read and analyse technical documentation.
89. Ability to analyse processes, organisation, and risks.
90. Ability to professionally develop and communicate recommendations.
91. Ability to identify and analyse relationships between requirements.
92. Ability to identify and analyse relationships between other solutions, related artefacts, and requirements.
93. Ability to identify requirement prioritisation criteria.
94. Ability to apply the defined criteria for requirement prioritisation.
95. Ability to assess the relevance of information included in the requirements and identify the need to update them.
96. Ability to identify additional metadata describing requirements and determine the necessary list of requirement attributes for storing that metadata.
97. Ability to assess the reuse potential of requirements and identify common and general requirements.
98. Ability to analyse the positive and negative impact of changes to the development of a solution.
99. Ability to define the decomposition of changes and resource capacity and plan the implementation of changes.
100. Ability to conduct negotiations with stakeholders.
101. Ability to acquire knowledge of the relevant domain of solution development project.
102. Ability to conduct negotiations.
103. Ability to organise the process of reviewing and approving requirements.
104. Ability to gain deeper insights into the technical aspects of requirement implementation.
105. Ability to gain deeper insights into the business aspects of requirement implementation.
106. Ability to communicate with developers and involved business representatives.
107. Ability to express own opinion to stakeholders in a comprehensible manner and with reasoned arguments.
108. Ability to present information according to the other party’s cognitive characteristics.
109. Ability to collaborate in a team.
110. Ability to use appropriate business terminology in the context of the solution.
111. Ability to reach compromise in opinion clashes.
112. Ability to get acquainted with terminology relevant to the business domain.
General competences
1. 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.
2. Ability to engage in construction discussion and express reasoned opinions, while providing information in a correct, comprehensible, and linguistically appropriate manner.
3. Ability to communicate in English, using professional terminology.
4. Ability to read, understand, and translate professional, specialised, and technical literature.
5. Ability to efficiently communicate in a multicultural environment, following the principles of intercultural communication.
6. Ability to use mathematical thinking to project future developments (in the sector, field, and profession), substantiate arguments, and test and compare the proposed solutions.
7. Ability to apply insights gained from observed data and industry research findings in practice.
8. Ability to comply with information technology security requirements and occupational safety requirements when performing professional duties.
9. Ability to use information resources, systems, databases, specialised software, and other information and communication technologies when performing sector-specific duties.
10. Ability to use mathematical thinking to project future developments in the sector, substantiate arguments, and test and compare the proposed solutions.
11. Ability to use specialised software to perform related duties.
12. Ability to determine a business model and develop business plans to achieve the set goals under changing conditions.
13. Ability to critically evaluate risks in the implementation of business ideas and creation of new values through individual and collective work towards the set goals.
14. Ability to use social skills in business and professional communication in the work setting and civil situations.
15. 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.
16. Ability to take responsible decisions and apply norms in professional activity in accordance with professional ethics and labour law requirements.
17. Ability to complete tasks in accordance with professional ethics and regulatory framework.
18. Ability to responsibly complete tasks individually or in a team, meeting the established work performance deadlines and quality requirements.
19. Ability to apply analytical thinking and analyse problems.
20. Ability to responsibly ensure and organise the task execution by complying with occupational safety requirements and using safe work techniques and work organisation principles.
21. Ability to monitor the compliance with occupational safety, environmental protection, electrical safety, and fire safety requirements during the work process.
22. Ability to assess the environmental impact of a project.
23. Ability to respond to an emergency situation while contributing to the implementation of management decisions.
24. 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.
25. Ability plan, make decisions, and assume responsibility for own professional development, including the forms and directions of developing professional skills and knowledge.
26. Ability to apply an analytical approach in professional activity, research, and field-specific development.