dependency
Let an agent explain and map project-task prerequisites, identify scheduling risks and distinguish required task order from unrelated uses of dependency.
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 8 findings · 16 questions
Understand What dependency means.
Concept
The relation.
Concept
Concept.
- What does it mean for one thing to depend on another in this context, and in which direction does the relation run? definition
- How does dependency differ from correlation or association? definition
Senses
Other senses.
Senses
Other senses.
- Is a dependent territory, economic dependency, substance dependence or a relation meant? boundary
- Which entry fits? action
Model Modelling dependencies.
Graph
Dependency graphs.
Graph
Graphs.
- How can the dependencies in this system be modelled as a graph, and are there cycles? action
- What order does a topological sort give? action
Conditions
Conditional dependencies.
Conditions
Conditions.
- How does a status such as copyright depend on facts like publication date and formalities, and how can such rules be expressed? definition
- Which facts must be established? action
Domains By domain.
Software
Software dependencies.
Software
Software.
- What are the dependencies of this software, and how are versions and licences managed? provenance
- Which vulnerabilities do dependencies introduce? provenance
Data
Data and schedule dependencies.
Data
Data and schedules.
- What are functional dependencies in a database, and how do they drive normalisation? definition
- How are task dependencies used in project schedules and critical path analysis? definition
Manage Risk and change.
Risk
Dependency risk.
Risk
Risk.
- Which dependencies are critical single points of failure, and how can they be mitigated? action
- How is dependency drift managed? action
Change
Changing dependencies.
Change
Change.
- How does a change in one component propagate through dependencies? action
- Which tools analyse impact? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Cross-cutting context
- Entry kind
- thing
- Plane
- XCT
- Domain
- XCT.REL
- Other names and narrower kinds
- published 95 years ago or less, published before 1978, not compliant with US copyright formalities, published between 1 March 1989 and end of 2002, registered or first published in the US, created before 1978, published 70 years ago or less, published more than 70 years ago
What it is Filled
A prerequisite relationship between project tasks in which one task requires another task to be completed before it can begin.
Why it exists Filled
Let an agent explain and map project-task prerequisites, identify scheduling risks and distinguish required task order from unrelated uses of dependency.
Distinguishing features Filled
- The relationship runs from a prerequisite task to a dependent task.
- The prerequisite task must finish before the dependent task can begin.
- The relationship constrains a project schedule.
- Task dependencies can be represented in a directed graph.
What robots and AI may and may not do Filled
Must not
- Remove or change a task prerequisite without checking its effect on dependent tasks.
- Present coinciding tasks or a preferred task order as a verified prerequisite relationship.
- Hide a known task dependency that puts a project schedule at risk.
- Invent task prerequisites without supporting project information.
Only with a human decision
- Changing dependencies in shared project schedules.
- Resolving disputed prerequisites that affect team commitments.
May
- Map and report prerequisites between project tasks it is authorized to read.
- Flag circular, missing or hidden task dependencies before a schedule change is made.
Moral aspects Filled
- Hidden task dependencies can pass delays and burdens to teams that did not choose the risk.
- Unsupported claims about task prerequisites can assign blame or credit wrongly.
Who is affected
- People responsible for prerequisite and dependent tasks are affected.
- Project managers and schedule maintainers are affected.
- Teams working on shared schedules are affected.
Owners Filled
Steward
Nobody owns the relation; the responsible project owner answers for the dependencies recorded in the project plan.
Links to other meta-models Filled
parent
- Q1191527 - registry parent class
related
- relation - category
- bridge - critical links in dependency graphs
- open-source software - software dependencies
- cause - causal dependency
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.dependency-q5260617
- Wikidata: Q5260617 (https://www.wikidata.org/wiki/Q5260617)
Direct properties not applicable Not applicable
Not applicable
Plane XCT: no invented physical properties.
Recognition optional Filled
- A project schedule links a prerequisite task to a dependent task.
- The link indicates that the prerequisite must finish before the dependent task begins.
- Tasks appearing together or near each other do not by themselves establish a dependency.
- Not physical; arrows in dependency graphs and conditions in rules.
Capabilities and actions required Filled
- explain kinds of dependency
- model dependencies in software, data and projects
- analyse dependency risks
- separate other senses
Hazards and failure modes required Filled
- Circular prerequisites can prevent dependent tasks from starting.
- Hidden or missing prerequisites can cause scheduling failures.
- Treating a preferred task order as a required dependency can unnecessarily constrain a schedule.
Standards and interfaces required Filled
- Package management and software bill of materials standards
- Database normalisation theory
- Project scheduling standards
Context of use required Filled
- Modelling what relies on what.
- software and package dependencies
- functional dependencies in databases
- task dependencies in scheduling
- logical, causal and conditional dependencies
- dependency of legal status on facts
Sources Filled
- Wikidata item Q5260617: dependency - identity and sense of the item
- Wikipedia: Dependency (project management) - general description of the item
Open questions
- Should software dependency be a separate entry?
- How should dependency tooling be linked?
- How should other senses be split?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q5260617/spec.json