<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Software Engineering Education in Russian Federation: Speci cs of Bachelor, Master, and Postgraduate Study Programs?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Gleb Radchenko</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ludmila Haluchenko</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ksenia Repina</string-name>
          <email>repinakv@susu.ru</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>South Ural State University</institution>
          ,
          <addr-line>Chelyabinsk</addr-line>
          ,
          <country country="RU">Russia</country>
        </aff>
      </contrib-group>
      <fpage>38</fpage>
      <lpage>49</lpage>
      <abstract>
        <p>The article examines the education system in the direction of \Software Engineering" in Russia for bachelor's, master's and postgraduate studies. The results of the analysis of Federal state educational standards in the direction of \Software Engineering", based on the comparison of competencies to the international body of knowledge on software engineering SWEBOK are presented.</p>
      </abstract>
      <kwd-group>
        <kwd>Software Engineering</kwd>
        <kwd>SWEBOK educational standard (FSES)</kwd>
        <kwd>competencies</kwd>
        <kwd>Russian federal state</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Finishing graduate school in Russia today doesn't necessarily include Ph.D.
theses defense and therefore getting a Ph.D. degree. While studying at graduate
school, students can select a specialty to prepare and defense Ph.D. theses. The
analysis of the o cial Russian dissertation library (http://diss.rsl.ru/) over the
past 10 years reveals that the majority theses in Software Engineering were
defended within two specialty directions: 05.13.11 \Mathematical Support and
Software for Computers, Computing Complexes and Networks" for theses
concerning mathematical and technical aspects of software design, testing and
construction and 08.00.05 \Economics and Management of National Economy" for
theses devoting to software management [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
      </p>
      <p>
        Thus, the current Russian circumstances in the eld of higher education in
software engineering make it possible to perform an e ective analysis of the
FSES coupled with the programs for bachelor's and master's degrees from the
Russian leading universities. This analysis will reveal how the programs cover
the contents of SWEBOK [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], a body of knowledge on software engineering
supported by IEEE and ACM and accepted in most developed countries for
training and certi cation in the eld of software engineering.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        The issue of compliance with the educational standards requirements of
employers is one of the most important in Russian and international education to date.
To analyze this problem in the eld of Software Engineering, several researchers
resorted to the comparison of the competencies obtained by the graduates with
the recommendations presented in the SWEBOK { \Software Engineering Body
of Knowledge" [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. SWEBOK V3.0 is an updated guide describing the body of
knowledge (15 areas) on software engineering jointly organized by the
organizations IEEE Computer Society and ACM (Association for Computing
Machinery). SWEBOK V3.0 today is the most authoritative guide to the fundamental
knowledge of the profession of software engineering and adopted in most
developed countries for training and certi cation in the eld of software engineering.
      </p>
      <p>
        Authors of [
        <xref ref-type="bibr" rid="ref2 ref3 ref4">2, 3, 4</xref>
        ] provide results of research in the eld of competencies and
knowledge that should be possessed by graduates of the \Software Engineering"
direction based on the comparison of curriculum content with the SWEBOK
topics. The authors of [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] have developed an expert system that enable companies
to select the most suitable candidates for their jobs, considering personal and
social skills, along with technical knowledge.
      </p>
      <p>
        On the other hand, authors of [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ] argue that the structure of the
SWEBOK can't be a strict requirement for the structure of the educational programs
in software engineering. The author of [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] presents the following ve speci c
comments-traps, based on the idea of crowding out on human and social
aspects of the technical component of the training of software engineering based
on SWEBOK:
1. A software engineering course needs an industrial project. The introduction
of a real industrial project in training is not useful for the student because of
the overload of students in junior courses by programming disciplines. The
author calls to simplify the program, by making a gradual introduction of
students into software engineering, as possible.
2. Software engineering is like other branches of engineering. The author
persuades to develop student's social competencies, along with technical
knowledge, for their better adaptation in professional life.
3. Planning in SE is poorly done relative to other elds. The article gives
examples of real well-known projects that are economically ine cient due to
inaccurate planning. Risk management, according to the author, is the most
critical area in software engineering, which requires the attention of students.
4. The user interface is a part of a low-level design. In the SWEBOK little
attention is devoted to the user interface design, which in uences the
functionality of the system and improves it. Curricula for software engineering
should include at least a course on the introduction of Human-Computer
Interaction.
5. SWEBOK represents the state of the practice. The SWEBOK lags behind
the state of the practice in some areas and runs ahead of the herd in others.
Outpacing reality, in the future, lead to an even greater distance between the
university and industry, because industry prefers evolution over revolution.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref7 ref9">7, 9</xref>
        ] authors introduce a model of development of software engineering
student's competencies through vocational training. They propose a model of
universal competencies as a requirement to the intellectual foundation of a
professional software engineer.
      </p>
      <p>
        The paper [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] discusses changes in the nal version of the SWEBOK V3.0
(adopted and published in December 2013), as well as the emergence of new
documents such as the SWECOM competency model (January 2014) [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] and
the change in the IEEE CS professional certi cation system. On the basis of the
analysis, a model of the profession is built.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], the technology of development of the IT education system was
considered on the basis of the internationally standardized curriculum. The analysis
of the current state of the international standards of programs for the
preparation of bachelors and masters in the eld of information technology is given.
Recommendations are given on the use of foreign experience in the development
of the national IT education system.
      </p>
      <p>Thus, the rapid development of the elds of knowledge of software
engineering requires the constant update of educational standards and a curriculum for
the preparation of students adapted to real industrial tasks. The identi cation of
the best professional competencies, the analysis of existing curriculum and the
formation of recommendations for the training of software engineering, which
reduce the distance between university knowledge and the requirements of
industry, is an urgent area of research not only in Russia but also in the world.</p>
    </sec>
    <sec id="sec-3">
      <title>SWE in Russian Federal Bachelor's Standard</title>
      <p>Russian federal state educational standard (FSES) in software engineering
explicitly de nes the minimum list of skills and competences which all graduates
in direction 09.03.04 \Software Engineering" should obtain, as well as speci es
the structure and scope of the educational program. In addition to the minimum
requirements for the results of the program, the standard provides the possibility
of supplementing the set of competencies based on the program orientation in
speci c areas of knowledge and/or professional activities.</p>
      <p>According to the standard, all the skills and competencies are divided into 3
groups: general cultural, general professional and professional ones.
3.1</p>
      <sec id="sec-3-1">
        <title>General Cultural Competences (GC)</title>
        <p>
          General cultural competences are not professionally oriented; on the contrary,
they are to relate to all graduates regardless of the activity area as they form
the basis for training and further implementation [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ].
        </p>
        <p>Among the general cultural competencies the most attention should be paid
to the following skills:
{ use of economic fundamentals (GC-3) and legal knowledge (GC-4) in various
spheres of life;
{ communication in oral and written forms for solving problems of
interpersonal and intercultural interaction (GC-5);
{ teamwork (GC-6);
{ self-organization and self-education (GC-7).</p>
        <p>Analysis of the contents of these competencies allow us to conclude that they
cover the following chapters in SWEBOK body of knowledge: Software
Engineering Economics (Chapter 12) and Software Engineering Professional Practice
(Chapter 11).
3.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>General Professional Competences (GPC)</title>
        <p>The GPC chapter include skills and knowledge for graduates in broad elds
of computer science and software engineering. The following skills can be
referred: possession of basic concepts, principles, theories, and facts of Informatics
(GPC-1), knowledge of computer architecture and systems (GPC-2) and basics
of programming (GPC-3). Direct correspondence is found in SWEBOK chapters
Computing Foundations (Chapter 13) and Mathematical Foundations (Chapter
14).
3.3</p>
      </sec>
      <sec id="sec-3-3">
        <title>Professional Competences (PC)</title>
        <p>PC establish restricted scope for software engineers re ecting professional
requirements and demands. Professional competencies mentioned in the federal
standard can be divided into nine subgroups, somewhat covering the following
chapters of SWEBOK:
1. Software Requirements (Chapter 1) - formalization of the software domain,
speci cation development for software components (PC-16);
2. Software Design (Chapter 2) - basic techniques and software development
tools (PC-1), various software development technologies (PC-3),
programming interfaces development (PC-22);
3. Modeling (Chapter 9) and Software Construction (Chapter 3) - modeling
skills, analysis and use of formal methods for software implementation
(PC19);
4. Software Maintenance of (Chapter 5) - basic concepts and models of
software evolution and maintenance (PC-10), peculiarities of evolutionary
activity (inherited systems, re exive planning, reengineering, migration, and
refactoring) (PC-11), reading and understanding of the source code and
documentation (PC-21);
5. Software Engineering Management (Chapter 7) - classical concepts and
models in project management (PC-6), control software development (PC-7),
project control (PC-9);
6. Software Engineering Process (Chapter 8) - standards and models of life
cycle (PC-5);
7. Software Quality (Chapter 10) - concepts and attributes of software quality
(reliability, safety, usability), including the role of people, processes,
methods, tools and quality assurance techniques (PC-4);
8. Group Dynamics and Psychology (Chapter 11.2) - basics of group dynamics
and psychology speci c to software engineering (PC-8);
9. Software Engineering Economics (Chapter 12) - initial assessment of software
project di culty, risk and cost; working plan formation (PC-17); Preparation
of commercial proposals (PC-18);
10. Computing Foundations (Chapter 13) and Mathematical Foundations
(Chapter 14) - the use of operating systems, network technologies, various
languages and formal speci cation methods, database management systems
(PC-2), evaluation time and space complexity of the software (PC-20).</p>
        <p>The analysis showed that the FSES of the bachelor's direction 09.03.04
\Software Engineering" covers SWEBOK by 87 % (table 1). The following two
SWEBOK sections are not included in the standard:</p>
        <sec id="sec-3-3-1">
          <title>1. Software Con guration Management (Chapter 6); 2. Engineering Foundations (Chapter 15).</title>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>SWE in Russian Federal Master's Standard</title>
      <p>To review the federal standard of master studies in the eld of software
engineering, we would also analyze the minimum required competencies of graduates
in the general cultural, general professional and professional spheres.
4.1</p>
      <sec id="sec-4-1">
        <title>General Cultural Competencies (GC) and General Professional</title>
      </sec>
      <sec id="sec-4-2">
        <title>Competencies (GPC)</title>
        <p>Among the general cultural and general professional competencies, it is worth
paying special attention to the ability to self-education (GC-3), acquisition by
means of information technologies, new knowledge and skills in new areas of
knowledge (GC -7), possession of methods and means of obtaining, storage,
processing and transmission of knowledge through modern computer technology
(GPC-5). These competencies can be related to the \Software Engineering
Professional Practice" (Chapter 11). Also, much attention is paid to the skills of
organizing research and design works and team management (GC-5).</p>
        <p>In addition to the above competencies, the standard presupposes the
possession of modern methods of scienti c research (GC-3) and the preparation of
reports on the conducted research work, including the preparation of
publications (GC-9) and compilation of analytical reviews with valid conclusions and
recommendations (GPC-6). It is worth saying that the competencies relating to
research activities, are not directly mentioned in the body of knowledge for a
software engineer.
4.2</p>
      </sec>
      <sec id="sec-4-3">
        <title>Professional Competencies (PC)</title>
        <p>With regards to the professional competencies of master of software
engineering, the Federal standard places particular emphasis on the mastery of methods
and algorithms of decision of tasks of recognition data and data processing
(PC4), including digital signals processing (PC-5), and their subsequent design and
software implementation (PC-15); the design and software implementation of
distributed information systems (PC-7, PC-13) and high-performance systems
with parallel data processing (PC-8, PC-14). Much attention is paid to the design
and programming capabilities of translators and interpreters of programming
languages (PC-9, PC-16), network services (PC-10, PC-17), the main
components of operating systems and real-time systems (PC-11, PC- 18), systems for
creating three-dimensional images (PC-21), designing auxiliary and specialized
programming languages and data representation languages (PC-12). The above
competencies cover the Software Design (Chapter 2) and Software Construction
(Chapter 3) sections on software design and software implementation, as well as
the sections of the Computing and Mathematical Foundations (Chapter 13 and
Chapter 14) re ecting more speci c knowledge on the basics of data
representation and processing and the organization of computing system with di erent
architecture.</p>
        <p>Knowledge of software veri cation approaches (PC-6), which are part of the
Software Quality section (Chapter 10), and the organization of industrial testing
of the created software (PC-20) from the Software Testing section (Chapter 4)
are also mentioned in professional competencies.
1. Software Requirements (Chapter 1);
2. Software Maintenance (Chapter 5);
3. Software Con guration Management (Chapter 6);
4. Software Engineering Management (Chapter 7);
5. Software Engineering Process (Chapter 8);
6. Software Engineering Models and Methods (Chapter 9);
7. Software Engineering Economics (Chapter 12);
8. Engineering Foundations (Chapter 15).</p>
        <p>Master's education assumes a basic bachelor's degree in software
engineering. That allows to consider the competencies of the standard for master's, as
addition to the competencies of the standard for bachelor's software engineering.
Then, the overall coverage of the SWEBOK chapters is 87 %. \Software
Conguration Management" and \Engineering Foundations" are not covered in the
standards.
5</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>SWE in Russian PhD Education</title>
      <p>FSES for postgraduate studies forms a program for training highly quali ed
personnel in various areas. FSES for postgraduate study in the \Software
Engineering" direction does not exist. Graduate students can study in the following
two areas, close to software engineering:
{ 09.06.01 Computer science and engineering;
{ 02.06.01 Computer and information technologies.</p>
      <p>FSES in the directions of postgraduate study is a list of universal and general
professional competencies that a graduate of graduate school should receive.
But FSES does not de ne the list of professional competencies. Professional
competencies are determined by the specialty, for which academic degrees are
awarded.</p>
      <p>In Russia, the degree of candidate or doctor of science is awarded by the
Higher Attestation Commission (HAC), the state body under the Ministry of
Education and Science of the Russian Federation, on the recommendation of the
Dissertation Council. Under the guidance of the Higher Attestation Commission
in some Russian universities, Dissertational councils have been formed, carrying
out work on certain specialties.</p>
      <p>The analysis of the o cial Russian dissertation library (http://diss.rsl.ru/)
over the past 10 years reveals that the majority of theses in Software Engineering
were defended within two specialty directions:
1. 05.13.11 \Mathematical Support and Software for Computers, Computing
Complexes and Networks" - theses on the mathematical theory of
programming, creation, maintenance and operation of software for various purposes
for computers and computer systems, as well as complexes built on their
basis, computer and neural networks.
2. 08.00.05 \Economics and Management of National Economy" - theses in the
eld of management of software development projects.</p>
      <p>The eld of research in each specialty is determined by the specialty passport
developed by the HAC. The passport of the specialty is a document that xes
the eld of research for which a scienti c degree of a candidate or a doctor of
sciences in the relevant specialty can be awarded.</p>
      <p>The passport of the specialty 05.13.11 \Mathematical Support and Software
for Computers, Computing Complexes and Networks" includes the following
professional competencies, covered by the chapters of SWEBOK:
1. Models, methods and algorithms for the design and analysis of programs and
software systems, their equivalent transformations, veri cation and testing
cover 3 chapters of SWEBOK { \Software Design" (Chapter 2), \Software
Testing" (Chapter 4) and \Mathematical Foundations" (Chapter 14).
2. Programming languages and programming systems, program semantics -
relate to the \Computing Foundations" (Chapter 13).
3. Models, methods, algorithms, languages and software tools for organizing
the interaction of programs and software systems are re ected in SWEBOK
Chapter 9 \Software Engineering Models and Methods", and partly in
Chapter 13 \Computing Foundations" and \Mathematical Foundations" (Chapter
14).
4. Database and knowledge management systems, software systems of symbolic
computing and operating systems also a ect the 13th chapter \Computing
Foundations".
5. Human-machine interfaces; models, methods, algorithms and software tools
for computer graphics, visualization, image processing, virtual reality
systems, multimedia communication { \Software Design" (Chapter 2),
\Software Construction" (Chapter 3), \Computing Foundations" (Chapter 13).
6. Models and methods for creating programs and software systems for parallel
and distributed data processing, languages and parallel programming tools
- \Computing Foundations" (Chapter 13) and \Mathematical Foundations"
(Chapter 14).
7. Models, methods, algorithms and software infrastructure for organization
of globally distributed data processing - \Software Engineering Process"
(Chapter 8).
8. Quality assessment, standardization and maintenance of software systems
are covered in chapter 5 \Software Maintenance", chapter 7 \Software
Engineering Management", chapter 10 \Software Quality".</p>
      <p>Thus, the passport of the specialty 05.13.11 \Mathematical Support and
Software for Computers, Computing Complexes and Networks" covers the following
chapters of SWEBOK.</p>
      <p>Analysis of the specialty passport 05.13.11 \Mathematical Support and
Software for Computers, Computing Complexes and Networks" showed SWEBOK
compliance 80 % (table 3). The following SWEBOK knowledge areas are not
included in the passport of the specialty:</p>
      <sec id="sec-5-1">
        <title>1. Software Requirements (Chapter 1);</title>
        <p>2. Software Con guration Management (Chapter 6);
3. Software Engineering Professional Practice (Chapter 11);
4. Software Engineering Economics (Chapter 12);
5. Engineering Foundations (Chapter 15).</p>
        <p>The passport of the specialty 08.00.05 \Economics and Management of
National Economy" includes the following professional competencies, covered by
the chapters of SWEBOK.
1. Development of the methodology, economic theory, and management
methods in the eld of communication and information is re ected in chapter 12
Software Engineering Economics and partly in Chapter 7 Software
Engineering Management.
2. Economic analysis of the activities of enterprises and organizations of
communication and information, carried out at the level of the industry and
individual structural units, as well as in the territorial (regional) section
chapter 12 Software Engineering Economics.
3. The study of the in uence of communication and informatization on the
development of markets, productive forces, the e ciency of social production,
socioeconomic progress and economic security of the country is re ected in
the chapter 12 Software Engineering Economics.
4. Assessment of the quality of servicing the economy and the population of the
country by means of communication and information - chapter 10 \Software
Quality".
5. Determination of economic e ciency of modernization of the material and
technical base of enterprises and organizations of communication and
information - chapter 12 Software Engineering Economics.
6. Study of the economic e ciency of new forms and methods of information
support using various types of communication - chapter 12 Software
Engineering Economics.
7. Investigation of regularities and principles of distribution of information
ows over networks of di erent types of communication at the country level
and individual regions - chapter 13 Computing Foundations.
8. Planning and analysis of production, business and commercial activities of
communication and information enterprises - Chapter 7 Software
Engineering Management.
9. Organization of licensing and certi cation of the activities of communication
and information enterprises - Engineering Foundations ( 15).
10. The study of the laws, relations of production, scienti c principles, forms,
methods and means of formation of information infrastructure - chapter 8
Software Engineering Process.
11. Research of nancial and organizational methods and mechanisms of
management of innovative development of communication and information
facilities - Chapter 7 Software Engineering Management.
12. Problems of improving information security and sustainable development of
the communications and information technology market - chapter 13
Computing Foundations.
13. Development of the methodology for auditing information systems, including
the development of guidelines, organizational, methodological and regulatory
documents, methods for justifying the choice of hardware and software,
procedures for managing the development process, methods for assessing risks
and measures to minimize the consequences of their occurrence - Software
Engineering Management (Chapter 7), Software Engineering Process
(Chapter 8), Software Engineering Economics (Chapter 12).
14. Development of new information technologies that ensure e cient
functioning of electronic business - Computing Foundations (Chapter 13), and partly
in chapter 12 Software Engineering Economics.</p>
        <p>The passport of the specialty 08.00.05 \Economics and Management of
National Economy" covers the following chapters of SWEBOK (table 4).</p>
        <p>The analysis showed that the passport of specialty 08.00.05 \Economics and
Management of National Economy" corresponds to SWEBOK by 40 %. The
following competences are not re ected in the passport of specialty 08.00.05:</p>
      </sec>
      <sec id="sec-5-2">
        <title>1. Software Requirements (Chapter 1); 2. Software Design (Chapter 2); 3. Software Construction (Chapter 3);</title>
      </sec>
      <sec id="sec-5-3">
        <title>4. Software Testing (Chapter 4);</title>
        <p>5. Software Maintenance (Chapter 5);
6. Software Con guration Management (Chapter 6);
7. Software Engineering Models and Methods (Chapter 9);
8. Software Engineering Professional Practice (Chapter 11);
9. Mathematical Foundations (Chapter 14).</p>
        <p>So, on the whole, it turns out that the total coverage of SWEBOK in
postgraduate study in Russia is 80 %. The following chapters of SWEBOK are not
included in the passports of specialties for graduate students:</p>
      </sec>
      <sec id="sec-5-4">
        <title>1. Software Requirements (Chapter 1); 2. Software Con guration Management (Chapter 6); 3. Software Engineering Professional Practice (Chapter 11).</title>
        <p>6</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Conclusions</title>
      <p>An analysis of the FSES for Software Engineering for bachelors and masters has
shown that the aggregate requirements of both standards do not in any way
cover Engineering Foundations and Software Con guration Management. This
means that to obtain a master's degree in software engineering in Russia, the
graduate does not need to have knowledge of these two topics, since they are
not included in the list of mandatory requirements for the implementation of
the educational program formed within this standard and can be included in the
curriculum only at the discretion of the head of the educational program and
university.</p>
      <p>The review of passports of specialties on the postgraduate study has shown
that in Russia there are adjacent specialties on which it is possible to defend
the master's thesis in many elds of research related to software engineering.
But, unfortunately, there are three areas of research, such as Software
Requirements, Software Con guration Management and Software Engineering
Professional Practice, which are not re ected in the list of areas of research adjacent
to software engineering specialties. This means that today in Russia to defend a
Ph.D. thesis on these areas of research is not possible.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>O.V.</given-names>
            <surname>Barinova</surname>
          </string-name>
          ,
          <article-title>Formation of key competences (general cultural and professional</article-title>
          ) // NovaInfo.Ru.
          <year>2014</year>
          . No. 19. P.
          <volume>126</volume>
          {
          <fpage>129</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>A.</given-names>
            <surname>Pyster</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Turner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Henry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lasfer</surname>
          </string-name>
          , L. Bernstein,
          <article-title>Master's degrees in software engineering: An Analysis of</article-title>
          28 University Programs // IEEE Software.
          <year>2009</year>
          . Vol.
          <volume>26</volume>
          , №5. P.
          <volume>94</volume>
          {
          <fpage>101</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>L.E.</given-names>
            <surname>Snchez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Santos-Olmo</surname>
          </string-name>
          , E. lvarez, M. Huerta,
          <string-name>
            <given-names>S.</given-names>
            <surname>Camacho</surname>
          </string-name>
          , E. FernandezMedina,
          <article-title>Development of an expert system for the evaluation of students' curricula on the basis</article-title>
          of competencies // Future Internet.
          <year>2016</year>
          . Vol.
          <volume>8</volume>
          , №2. P.
          <volume>1</volume>
          {
          <fpage>18</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>M.</given-names>
            <surname>Ardis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Bourque</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Hilburn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lasfer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Lucero</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>McDonald</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Pyster</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Sha</surname>
          </string-name>
          , Advancing software engineering professional education // IEEE Software.
          <year>2011</year>
          . Vol.
          <volume>28</volume>
          , №4. P.
          <volume>58</volume>
          {
          <fpage>63</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>H. Van Vliet</surname>
          </string-name>
          , Re ections on software engineering education // IEEE Software.
          <year>2006</year>
          . Vol.
          <volume>23</volume>
          , №3. P.
          <volume>55</volume>
          {
          <fpage>61</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>B.</given-names>
            <surname>Bruegge</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Krusche</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Alperowitz</surname>
          </string-name>
          ,
          <article-title>Software engineering project courses with industrial clients // ACM Transactions on Computinig Education</article-title>
          .
          <year>2015</year>
          . Vol.
          <volume>15</volume>
          , №
          <volume>4</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>E.N.</given-names>
            <surname>Reshetova</surname>
          </string-name>
          ,
          <article-title>Universal competencies of the student of the educational direction \Software Engineering"</article-title>
          // Information technologies.
          <source>2016</source>
          . Vol.
          <volume>22</volume>
          , №12. P.
          <volume>938</volume>
          {
          <fpage>945</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>S.M.</given-names>
            <surname>Avdoshin</surname>
          </string-name>
          , \
          <source>Ecosystem SWEBOK V3</source>
          .
          <volume>0</volume>
          " // CEE-SECR 2015 Moscow, Digital Center,
          <volume>22</volume>
          {
          <issue>23</issue>
          <year>October 2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>E.N.</given-names>
            <surname>Ishakova</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.V.</given-names>
            <surname>Medvedev</surname>
          </string-name>
          ,
          <article-title>About the professional competence of bachelors and masters in the eld</article-title>
          of software engineering // Vestnik of Orenburg state University.
          <year>2012</year>
          . №2. P.
          <volume>55</volume>
          -
          <fpage>59</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10. V.
          <article-title>A. Sukhomlin, Analysis of the international standards of master's education in the eld</article-title>
          of information technolog // Vestnik of Saint Petersburg University. Series 10. Applied mathematics. Informatics.
          <article-title>The management processes</article-title>
          .
          <year>2013</year>
          .
          <article-title>Issue 1</article-title>
          . P.
          <volume>95</volume>
          {
          <fpage>105</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <given-names>P.</given-names>
            <surname>Bourque</surname>
          </string-name>
          and R.E. Fairley, eds., Guide to the
          <source>Software Engineering Body of Knowledge, Version</source>
          <volume>3</volume>
          .0, IEEE Computer Society,
          <year>2014</year>
          ; URL: www.swebok.org.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <article-title>Portal of Federal State Educational Standards of Higher Education</article-title>
          . URL: http://fgosvo.ru.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <article-title>Electronic library of dissertations</article-title>
          . URL: http://diss.rsl.ru.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <article-title>Passports of scienti c specialties - VAK</article-title>
          . URL: http://vak.ed.
          <source>gov.ru/316.</source>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <given-names>A.</given-names>
            <surname>Burgess</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.M.</given-names>
            <surname>Kelly</surname>
          </string-name>
          ,
          <string-name>
            <surname>E.M.</surname>
          </string-name>
          <article-title>Butter eld</article-title>
          , J.
          <string-name>
            <surname>Keppler</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>McClenahan</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Guillemette</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Phon</surname>
          </string-name>
          ,
          <source>Software Engineering Competency Model, Version</source>
          <volume>1</volume>
          .0, IEEE Computer Society,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>