Skip to content

Latest commit

 

History

History
44 lines (30 loc) · 1.24 KB

continuous_behaviours.md

File metadata and controls

44 lines (30 loc) · 1.24 KB

< Back

Day to day Behaviours

Continually visualise the technical architecture

Read more here

Keeping documentation close to code

Read more here

Identifying 'non' requirements

Quality Attributes or Non Functional Requirements need to be considered and balanced as they are normally a trade off, examples could be:

  • Performance
  • Interoperability
  • Deployability
  • Reliability
  • Availability
  • Security
  • Maintainability
  • Observability
  • Testability
  • Scaleability
  • Modifiability
  • Reusability
  • Audibility

Managing risk

Risk Storming

  • A visual and collaborative risk identification technique
  • Can be applied to architectures, business processes, workflows, etc
  • Can be applied multiple times during the lifetime of the thing being risk stormed
  • More information here

Communicating into the future

Read more here

< Back