based on Systems Engineering as it is defined by INCOSE Russian Chapter and http://system-school.ru/ Eng + Ru

1. СИСТЕМНОЕ МЫШЛЕНИЕ
Иван Подобед для #DreamFest

2. PRE-INIT
Disclaimers
GOOD LUCK!
• Based on http://system-school.ru/
• Language & terminology
• Interactions
• Not a workshop
• Not a training
• Just an opportunity
Expectations

3. ALTERNATIVES
Sciences and Methodologies
• …
• Cybernetics
• Operations Research
• Synecology
• System Dynamics
• Nonequilibrium Systems
• System Analysis
• …

4. THINKING
• Technical, Managerial,
Entrepreneur Thinking
• Many dynamic trends
• Systems Thinking
• Some defined practices
• Rational, Logical Thinking
• Few stable disciplines

5. Небольшие улучшения на базовых
уровнях мышления дают
возрастающий эффект вверх по
пирамиде 

6. CORE PRINCIPLES
1. Abstraction
2. Adequacy
3. Awareness
4. Rationality

7.  Абстрагирование – работа с классами
сущностей.
 Адекватность – построение моделей
с должным уровнем реалистичности.
 Осознанность – способность
описать/коммуницировать/воспроизв
ести процесс принятия решения.
 Рациональность – способность
принять эффективное решение.

8. MOTIVATION
Foundation of Systems Engineering
• Apollo Missions (on the pic)
• NASA
• Nuclear Power Engineering
• Private Space (Musk et al)
• Automotive
• …

9. SPACEX
Systems Engineering whitepaper
“Systems Engineering is a discipline
established to protect the enormous
investment of large scale, complex
system development by anticipating
and solving integration problems
ahead of time”
https://www.aiaa.org/uploadedFiles/Events/Conferences/2012_Conferences/2012-Complex-
Aerospace-Systems-Exchange/Event/Detailed_Program/CASE2012_2-4_Muratore_presentation.pdf

10. PRE-REQUISITES
To Make It Efficient
• Concept over the Terminology
• Bayesian Probability
• Rationalists Community to the rescue: lesswrong.ru
WARNING: Сounter-intuitive!

11. © system-school.ru11
Словарные сообщества
тачка
Понятийное сообщество
car машинка автомобиль

13. CORE CONCEPT
System
• 4D Realization through Lifecycle
• Stakeholders-driven
• Integrity
• Emergence
• Duality
• Virtual vs Materialized
• Model vs Realization
• Functional vs Constructive
WARNING: Сounter-intuitive!

14. 4D LIFECYCLE

15. EMERGENCE
© system-school.ru

16. DUALITY

17. 4D EXTENSIONALISM
Two different views of the single EXTENT means
that they relates to the SAME entity.
• 4D Temporal part as a name of the entity’s STATE
• Key relationship type is COMPOSITION
• *Also applicable to “HOLES”
 Allows to model, collaborate and negotiate

19. PROCESS
Activity, Work, … Change
• IS 4D Entity
• IS COMPOSED by participating entities
• EVENT is a 3D snapshot (4D Extent but w/o Temporal part)
 Allows to manage Changes

21. FUNCTION
ROLE-based behavior, ASSIGNED to the entity
• FUNCTIONAL entity (aka ROLE) is ideal
• But it can be materialized by assigning to 4D Extent
• Primary FUNCTION is used to NAME a system
 ROLES are used to manage knowledge about systems

23. SOFTWARE
 4D Extent
 Usually a subsystem of the bigger system
IDEAL MATERIALIZED
Source Code Web site instance, hosted
on the cloud serverProject Documentation
Logical Architecture Content, uploaded to the
site
Database Schema User profiles, stored with
web site instanceBusiness Plan
 Example: retail web site

24. STAKEHOLDERS
ROLE (individual or group), interfering with system
lifecycle, inc. design, production and operation
• 2 way interference
• Can be positive or negative
• Always SUBJECTIVE, never objective
• STAKEHOLDERS are defining system function and scope
 STAKEHOLDERS are defining a SUCCESS criteria of the project

25. © system-school.ru

26. SYSTEM ENGINEERING
Scope
• Dealing with COMPLEXITY
• Understands STAKEHOLDER needs
• Explore OPPORTUNITIES
• Document REQUIREMENTS
• Synthesizing, verifying, validating, and evolving SOLUTIONS
• Considering the complete problem through its LIFECYCLE from system
concept exploration to system disposal

27. HOLON & HOLARCHY
Systems and their relations
System of Interest
Subsystems
Using System
Systems in operational environment

29. 5TH ELEMENT
Enabling System
Enabling System

30. МЕХАНИЧЕСКАЯСИСТЕМА СЭЛЕКТРИЧЕСКИМИ
ЭЛЕМЕНТАМИ
 Целевая система: центробежный насос
 Сервис/функция: повышение давления жидкости
 Подсистема: ротор
 Использующая система: насосная станция
 Один из внешних стейкхолдеров: владелец-
оператор насосной станции
 Потребность: бесперебойная работа насосной
станции
 Требования: перекачка 10000 л/час, наработка на
отказ 5000 часов
 Системы в операционном окружении: мотор,
трубопровод
 Обеспечивающая система: КБ, завод, проектант
и строитель насосной станции
30
© system-school.ru

31. СИСТЕМНОЕ МЫШЛЕНИЕ
 Нет однозначного «объективного»
ответа, всегда учёт стейкхолдеров
 Нет процесса, гарантирующего
результат (последовательность шагов
неизвестна)
 Напоминает высшую математику,
только «необъективную»
 Даёт определения, но не рассказывает,
что с ними делать. Но эти определения
позволяют компактно и просто
описывать сложный мир!

32. ENTREPRENEURSHIP
and System Engineering
• Doesn’t help to PREDICT the future
• Accepting RISKS
• Use MODELING
• Apply CHECKLISTS
• …
• Think Systems
Avoid simple MISTAKES

33. НАШ ПРОГРЕСС
 4D, функция, холархия, stakeholders

34. А ЧТО ДАЛЬШЕ
 4D, функция, холархия, stakeholders
 Функциональный анализ и конструктивный синтез
 Компоненты и модули
 Modeling: View & viewpoint
 Interface, stack, platform, service
 Requirements & architecture
 Configuration Management & Lifecycle
 4 времени и 7 альф
 Practice as a Discipline + Technology
 Capability as a Practice + Resources
 Organizational Engineering & EA
 Системное лидерство

35. SPECIAL THANKS
Anatoly Levenchuk
http://ailev.ru
And personally