Modeling Task Object Relationships with Product Context Analyzer
A Conceptual Model shows how task objects derived from multiple tasks relate to each other. It represents a user-centred, non-technical model of how users conceptualize the domain. This model helps teams define information architecture, structure navigation, and inform data modeling decisions, ensuring the system reflects real user concepts.
Specify the activity you want to analyze. The activity can be a single task, a responsibility, or a multi-phase journey
Example: Order Pizza from a delivery service for a business meeting
Describe the activity in a single sentence without prescribing a particular product or solution.
Optionally include context such as who is performing the activity and under what circumstances.
Adding context helps make the analysis more domain-specific.
A broader analysis can reveal task objects and relationships across multiple related tasks
The analysis takes several minutes depending on the scope and number of tasks identified
Insights are synthesized views of the context-of-use analysis across tasks and stakeholders
To view each task object individually, select Task Objects on the left
To view task objects related to a specific task, select the task and switch to the 'Task Objects & Resources' view
Select the Conceptual Model to see relationships between task objects identified across the analysis
The model combines task objects identified across multiple tasks
Relationships show how objects are connected from the user's perspective
Use the model to understand how users conceptualize the objects within the domain
Use object relationships to inform information architecture and navigation
Use the model as input for a human-centred domain and data model
Follow links to explore individual task objects and their underlying context in more detail
Organize information around the objects and relationships users encounter in their work rather than around an arbitrary application structure.
Use relationships between task objects to identify meaningful paths through the product and connect information users naturally expect to find together.
Give engineering a human-centred domain model that can inform technical entities and relationships before implementation decisions reshape the problem space.
Check whether the system's technical representation reflects the objects and relationships that matter from the user's perspective.
Provide generative development tools with an explicit model of the domain so generated applications are structured around meaningful user concepts and relationships.