arc42 Section 1: Requirements and Stakeholder

arc42 Section 2: Constraints

Question C-2-1: What are constraints?

Question C-2-2: What types of constraints exist?

Question C-2-3: What kind of constraints shall I document?

Question C-2-4: Can/shall we negotiate constraints?

arc42 Section 3: Context

Question C-3-1: What is the context?

Question C-3-2: What does _business_ and _technical_ context mean?

Question C-3-3: Does it make any sense to show the major components of my application in the context view?

Question C-3-4: In which cases shall I document the business context?

Question C-3-5: How can I simplify documentation of the business context?

Question C-3-6: Shall I document risks or problems in the context?

arc42 Section 4: Solution Strategy

Question C-4-1: What is the solution strategy?

Question C-4-2: How to document the 'solution strategy'?

Question C-4-3: Can you provide examples for the 'solution strategy'?

Question C-4-4: How is 'solution strategy' related to 'Quality goals' (section 1.2)?

arc42 Section 5: Building Block View

Question C-5-1: What is a 'building block'?

Question C-5-2: Do third-party libraries, frameworks or tools count among building blocks?

Question C-5-3: How does source code relate to building blocks?

Question C-5-4: How detailed shall we document or specify the building block view?

Question C-5-5: Can I refine a group of building blocks together?

Question C-5-6: How can I document or specify building blocks?

Question C-5-7: How shall I document building blocks for non-object-oriented systems?

Question C-5-8: How do I describe internal interfaces?

Question C-5-9: How do I describe external interfaces?

Question C-5-10: How can I avoid redundancy with interfaces in the building block view?

Question C-5-11: How does the hierarchy of building blocks relate to the arc42 sections (5.1, 5.2 etc.)?

Question C-5-12: What kind of building blocks don't I need to document or specify?

Question C-5-13: What kind of building blocks shall I document or specify?

arc42 Section 6: Runtime View

Question C-6-1: What is the runtime view? What are runtime scenarios??

Question C-6-2: What do I document or specify in the runtime view?

Question C-6-3: How can I describe scenarios or execution flows?

Question C-6-4: What are partial scenarios?

Question C-6-5: Which scenarios shall I describe or document?

arc42 Section 7: Deployment View

Question C-7-1: What does the deployment view show?

Question C-7-2: Why do I need a deployment view?

Question C-7-3: Who shall describe/document the deployment view?

Question C-7-4: Shall I use UML deployment diagrams for the deployment view?

Question C-7-5: Can there be different deployment scenarios or variants?

Question C-7-6: What shall I do when my building blocks get dynamically assigned an execution environment (node) - so I cannot statically assign them to infrastructure nodes?

arc42 Section 8: Crosscutting Concepts

Question C-8-1: What is a 'crosscutting concept'?

Question C-8-2: Our arc42 section 8 (on concepts) is a melting pot of information we couldn't put elsewhere? How can we keep an overview?

Question C-8-3: How shall I deal with the multitude of potentially crosscutting topics?

Question C-8-4: How shall I describe my business-/domain model?

Question C-8-5: Are there any general rules how to describe a 'concept'?

Question C-8-6: What are candidates for 'concepts'?

arc42 Section 9: Architectural Decisions

In software engineering literature you find both architecture decision and architectural decision.

Both mean the same thing…

Question C-9-1: What kind of decisions shall I describe or document?

Question C-9-2: How can I document an architectural decision?

Question C-9-3: What's an 'Architecture Decision Record' (ADR)?

Question C-9-4: How can we handle a 'large number' of architecture decisions?

arc42 Section 10: Quality Tree and Scenarios

Question C-10-1: What is 'Software Quality'?

Question C-10-2: What is a 'quality scenario'?

Question C-10-3: What is a 'quality tree'?

Question C-10-4: Are there examples for quality scenarios?

Question C-10-5: Why is the 'Quality' section one of the last in the template, rather than being at the start?

arc42 Section 1: Requirements and Stakeholder

arc42 Section 2: Constraints

arc42 Section 3: Context

arc42 Section 4: Solution Strategy

arc42 Section 5: Building Block View

arc42 Section 6: Runtime View

arc42 Section 7: Deployment View

arc42 Section 8: Crosscutting Concepts

arc42 Section 9: Architectural Decisions

arc42 Section 10: Quality Tree and Scenarios

arc42 Section 11: Risks and Technical Debt

arc42 Section 12: Glossary