Check out practical tips for using arc42, organized by template sections:

  1. Introduction and goals: Requirements, stakeholder, (top) quality goals (23 tips)
  2. Constraints: Technical and organizational constraints, conventions (5 tips)
  3. Context and scope: Business and technical context, external interfaces (19 tips)
  4. Solution strategy: Fundamental solution decisions and ideas (6 tips)
  5. Building block view: Abstractions of source code, black-/whiteboxes (28 tips)
  6. Runtime view: Runtime scenarios: How do building blocks interact (11 tips)
  7. Deployment view: Hardware and technical infrastructure, deployment (10 tips)
  8. Crosscutting concepts: Recurring solution approaches and patterns (10 tips)
  9. Architecture decisions: Important decisions (7 tips)
  10. Quality: Quality tree and quality scenarios (8 tips)
  11. Risks and technical debt: Known problems, risks and technical debt (6 tips)
  12. Glossary: Definitions of important business and technical terms (6 tips)

Our tips are tagged by 54 keywords that will help you navigate. Three of these stand out:

  • lean: You are looking for opportunities to shorten or streamline you documentation pragmatically. You want to reduce efforts without loosing content or value. You are working in an agile environment and want to have lightweight documentation – based on the motto: travel light.
  • thorough: You are working in a more formal environment, e.g. developing very large or critical systems with hard quality requirements. Your stakeholders require thoroughness, accuracy and attention to detail. Maybe your systems and there documentation have to be audited.
  • essential: Despite lean and agile, there are some informations about your system that you should always document; i.e. quality goals of your architecture.

Still have questions?

??
… then try our extensive FAQ, answering more than 120 frequently asked questions.

Need further assistance?

!!
… let us know here, we’re listening.

We're offering architecture training!

The dynamic duo, always two trainers in parallel, practically applicable knowledge from Peter Hruschka and Gernot Starke. See arc42.de for details, and schedule.

We’ve successfully trained more than 1000 developers in software architecture, many of them passed the iSAQB CPSA-F certification. (sorry - public training currently German-only, English for inhouse trainings.)