Dependencies
Define hard requirements between landmarks for impact analysis. Learn about dependencies →
Relationships
Relationships are what make Legend more than a list of entities. By connecting landmarks, people, and teams, relationships create a knowledge graph that answers questions like “Who owns this service?”, “What depends on this database?”, and “Who should I contact about this project?”
Legend supports three primary relationship types:
- Ownership assigns responsibility for a landmark to a team or person
- Dependencies show when one landmark relies on another to function
- Associations connect related entities without implying dependency
Associations
Create loose connections between related entities for discovery and context. Learn about associations →
Ownership
Assign responsibility for landmarks to teams or people. Learn about ownership →
How Relationships Work Together
Section titled “How Relationships Work Together”The relationship types complement each other. A single landmark can have all three:
- It is owned by a team, so everyone knows who to contact
- It depends on other landmarks, so you can trace impact chains
- It is associated with related items, so people can discover context
Membership is a fourth, implicit relationship: people belong to teams, and those memberships appear throughout the interface and in the topology explorer.
Visualizing Relationships
Section titled “Visualizing Relationships”The Topology Explorer renders all of your relationships as an interactive graph. Dependencies appear as directional arrows, ownership as links to owners, and associations as simple connections between entities.
Next Steps
Section titled “Next Steps”Start with Dependencies to model service requirements, or jump to Topology Explorer to see how relationships are visualized.