Call me back
Call Close
We will call you back!

Systems Engineering

apply the latest world knowledge on the model-
oriented systems engineering to your working draft
Prerequisites:

- postsecondary engineering or technical education;
- taken course of "Systems Approach in Management and Engineering", the workshop "Systems Thinking" or the online course "Systems Thinking";
- read the textbook "Systems Thinking" (in addition, we recommend reading the textbook "Systems Engineering Thinking" - it contains more materials on systems engineering);
- a summary of your working draft (1-3 paragraphs)
What can be learnt from this course
  • it trains systems thinking in its application to model-oriented engineering;
  • introduces the best practices of model-oriented systems engineering: developing a system concept, requirements engineering, developing a system architecture, system design, implementation, as well as verification and acceptance;
  • shows the relationship of engineering, management and entrepreneurship;
  • Introduces international standards and public documents on systems engineering.
What other challenges can be solved after taking this course
Understand the role of a systems engineer in a project
  • Systems Engineering is a transdisciplinary approach and practices for creating successful systems. Systems engineering is inextricably linked with systems management and entrepreneurship.
  • The systems engineer, in the first place, makes the basic engineering decisions (expressed in requirements and systems architecture, program and test procedures, etc.), and also plays the role of a task manager, bringing these solutions to engineers of various specialties.
  • It is the systems engineer who is responsible for ensuring that the feasibility studies, technical specifications, private technical specifications, programs and procedures, operational and other documents take into account the needs of a wide variety of people that are interested in the project; and on the other hand, doable.
  • A systems engineer is often the link between an engineering team, a project manager, and a product manager.
Master the competency of systems modeling
In order to discuss important details without losing the integrity of the project, the systems engineer has a special competence in systems modeling. In this workshop, as a systems modeling tool, we will use our own development of the Systems Management School - Product studio.
What will you gain from this course
Except mind clarity
Systems crash test of your project

based on the project system diagram
Systems Models of
Requirements and Architecture
with the possibility of export and further use in real projects
Access to the training center for systems modeling

free of charge - subject to successful presentation of the project at the end of the course
Who is this course for?
  • Systems engineering competencies are very useful in the positions of team leader, development manager, systems analyst and systems architect, business analyst, chief engineer, chief designer and even technical director (especially in technology companies).
  • System engineering (in the agile version) is very effective in technological startups, where each team member must take on many roles.
  • Understanding the principles of systems engineering can significantly increase the effectiveness of specialists in organizational engineering (as well as organizational development, organizational architecture, etc.)
  • The course is highly recommended for product managers and project managers. The ability to compactly and quickly place complex objects in the head allows managers to understand well what their team is doing. To a greater extent this applies to interdisciplinary projects.
Course program
12

classes
2

twice a week
2

hours - each class
1. Systems thinking in engineering
  • Systems levels and emergence: functions, roles, modules, etc .;
  • Design in classes and the problem of the multiplicity of uppersystems;
  • Features decomposition of interfaces and streams;
  • Consequences of the subjectivity of systems boundaries.
2. System engineering in one day
      • Briefly about the history of systems engineering;
      • System contexts and the area of interest of a systems engineer. The intersection of the interests of the systems engineer, project manager and product manager;
      • Classical V-model of the life cycle, work products of systems engineering and the relationship between them;
      • The systems diagram of the project. Crash test of a working draft.
      3. The concept of using the system (OPSCON document)
          • Economic justification of the system: organization's mission, marketing research, benchmarks, etc .;
          • Uppersystem and systems in the environment;
          • Context diagram;
          • Scenarios for using the system (use cases).
          4. Engineering requirements
              • Role interests, needs, requirements;
              • Types and attributes of requirements;
              • Trace requirements;
              • How is the technical task different from the requirements.
              5. Systems architecture and design
              • Role interests in the system, types of architectural models, methods of documenting architecture;
              • Functional and modular circuits;
              • DSM and compliance matrix;
              • The choice of modules and the definition of their attributes (modular synthesis). Generative design.
              6. Systems analysis
              • On the subject and boundaries of system analysis;
              • Building multi-criteria models based on requirements;
              • Building mathematical models of systems and predicting behavior;
              • Search for optimal engineering solutions.
              7. Configuration Management
              • Definition of configuration bases and support of their integrity;
              • Issue of engineering documentation;
              • Change management;
              • Management of engineering data / documentation.
              8. Implementation, verification and acceptance
              • The use of artificial intelligence and virtual reality in the processes of manufacturing, integration, verification and acceptance;
              • Types of verifications and acceptance, digital doubles;
              • Modeling a test system in conjunction with requirements and architecture;
              • Agile systems engineering and early / frequent / continuous acceptance.
              Video for you to learn more about this course:
              Still unsure about the course?
              in the chat you can ask colleagues and lecturers questions that interest you and make an informed decision after you receive an answer to your question

              (if you can't use the link, you can find the chat via the search: @welcomeSSM)


              This course is lectured by
              Vyacheslav Mizgulin
              Ph.D., INCOSE Member, Systems Engineering Expert
              Since 2005 he has been working in large systems engineering projects. During this time, he managed to found the first master's degree in systems engineering in Russia at UrFU, write a book "Systems Engineer. How to start a career in a new technological order ", and in 2018 become the president of INCOSE RUS.
              You really want to but cannot be present for the course physically? Then join us online!
              Pick type of enrollment on the page that appears after you click on the button "I want to join group".
              Получите чек-лист и начните его применять прямо сейчас!
              Хотите самостоятельно убедиться, что с вашим проектом все в порядке? Чек-листы по проектному анализу - удобный и эффективный способ диагностики проекта на любой стадии. Пользуясь чек-листами, вы:
              • проверяете, все ли гипотезы, перспективы и риски учли на этапе планирования;
              • структурируете имеющуюся информацию по проекту;
              • получаете обратную связь от команды;
              • определяетесь с дальнейшим курсом;
              • можете быть уверены в том, что "белых пятен" не осталось - чек-листы охватывают все возможные стороны проектного управления.
              Чек-лист - это документ, по которому мы проверяем себя. Например, список действий, которые необходимо совершить, или предметов, которые нужно не забыть взять с собой. Чек-листы используются в авиации, медицине, строительстве - то есть там, где ошибки недопустимы. Если вы ответственно подходите к проектному управлению, предлагаем вам использовать чек-листы - по-настоящему надежный метод контроля.
              Это бесплатно!
              Not ready yet to enroll in our courses? Well, we created something very useful and absolutely free for you: project analysis check-list
              Обратно к описанию
              Практикум «Системная инженерия. Моделирование концепции продукта»: старт 18.11
              12 занятий по понедельникам и средам
              ул. Щипок, д.11, стр.1, офис АНО «НИСИПП»
              Научим инженеров и технических руководителей разрабатывать системы «с чистого листа» с помощью практик моделе-ориентированной разработки концепции продукта на языке ArchiMate 3.0.

              Цена курса при ранней регистрации — 24 000₽
              За 7 дней до старта цена увеличивается
              Вид участия