principles¶

• principles
• Terms
  • Software development
  • Architectures
  • Technical domains
  • Product categories
  • Business processes
  • Documents And Analyses
• Définitions
  • SOLID

---

Terms¶

• Design Patterns

Software development¶

• Encapsulation: functions hide their implementation and only expose their signature.
• Simplicity: functions have a single responsibility and don't mix nouns with verbs, which makes them fundamentally untangled.
• Stateless: functions are just code; they don't contain state or instance.
• Purity: functions can be pure (i.e. have no side-effects) which makes them easy to understand, reuse, test and parallelise.
• SOLID
• DCI
• DDD
• SOA

Architectures¶

• Hexagonal

Technical domains¶

• Infrastructure as code (IaC)
• Continuous integration (CI)
• Continuous delivery (CD)

Product categories¶

• Software as a service (SaaS)
• Platform as a service (Paas)
• Backend as a service (BaaS)
• Function as a service (FaaS)
• Internal developer platforms (IDPs)

Business processes¶

• Total quality management (TQM)
• Knowledge management (KM)

Documents And Analyses¶

• Request for Comments (RFC)
• Architecture Decision Record (ADR)
• Business Requirements Document (BRD)
• Value Stream Maps (VSMs)

---

Définitions¶

SOLID¶

S - Single-responsiblity Principle
O - Open-closed Principle
L - Liskov Substitution Principle
I - Interface Segregation Principle
D - Dependency Inversion Principle