ASD-STE100
Make technical instructions easier to interpret through controlled language and consistent terms.
YOUR READING DESK
Keep a useful idea close.
Bookmarks and attempted exercises stay in this browser. No account or cross-device sync is involved.
Enable JavaScript to show saved activity.
You have no saved approaches yet. Explore the guide and use “Save approach” beside something you want to revisit.
Saved approaches
Plain language
Help the intended reader find, understand, and use the information they need.
Diátaxis
Choose documentation around whether someone is learning or working, and doing or understanding.
Minto Pyramid Principle
Organize a business explanation around one main point supported by logically grouped reasons.
DITA
Author reusable documentation topics and assemble them for different publications.
Concept mapping
Make relationships between concepts explicit with labeled connections.
Worked examples
Study a complete solution with reasons before attempting a related problem.
Self-explanation & teach-back
Explain a mechanism in your own words, then check the explanation against evidence.
Socratic questioning
Use focused questions to examine definitions, assumptions, evidence, and consequences.
Progressive disclosure
Reveal detail when it becomes useful while keeping essential information easy to find.
C4 model
Explain a software architecture through a small set of consistent levels of detail.
UML
Choose a defined notation for structure, interactions, activities, or state changes.
Entity–relationship modeling
Describe entities, relationships, and cardinality before designing or interpreting data.
arc42
Document architecture through a coherent set of questions about context, structure, behavior, quality, and risk.
Architecture decision records
Preserve why a consequential choice was made and what follows from it.
EARS
Give a textual requirement explicit context, trigger, and observable system response.
BCP 14 requirement levels
Distinguish mandatory requirements, recommendations, and genuine options.
Gherkin
Express a concrete behavior through starting conditions, an event, and an observable outcome.
Example Mapping
Explore a feature by separating rules, concrete examples, unanswered questions, and scope.
BPMN
Describe a business process through activities, events, decisions, and participant boundaries.
DMN & decision tables
Represent how input conditions produce an explicit decision outcome.
JSON Schema
Describe which JSON values have the structure and constraints your application expects.
OpenAPI
Describe an HTTP API’s operations, inputs, responses, and security requirements.
AsyncAPI
Describe message-driven interfaces through channels, operations, messages, and protocol details.
SKOS
Represent concepts, preferred terms, alternative labels, and their relationships consistently.
SHACL
Check RDF graph data against explicit shapes and constraints.
W3C PROV
Describe the entities, activities, and agents involved in producing an artifact.
Statecharts & SCXML
Describe which events can change a system’s state, including states where an action is no longer valid.
TLA+
Model possible system behaviors and state the properties those behaviors should satisfy.
Alloy
Explore structures and counterexamples described by relational constraints.