This question is locked. New answers and comments are not allowed.
Hi
This idea is essentially building on the Persona functionality where you can quickly create and describe an 'actor' in the system.
By taking the persona functionality and making it generic, TeamPulse could be used to capture and describe any system artefact.
For example, use cases and user stories are often peppered with domain specific terminology, e.g. CDOs, CLOs, Cedent, retrocession etc etc.
If TeamPulse allowed you to create definition artifacts, subsequent readers of the user story would be able to click on the artefact and get a description. You would also be able to trace all references to particular artifact.
I first came across this functionality in Objectory (Ivar Jacobson's casetool) in the early 1990s.
It was an immediate hit with the BAs because they now had a defined data dictionary.
Developers new to the domain benefitted from the extra information allowing them to come to terms with the domain (if you pardon the pun).
Regards
Aidan
This idea is essentially building on the Persona functionality where you can quickly create and describe an 'actor' in the system.
By taking the persona functionality and making it generic, TeamPulse could be used to capture and describe any system artefact.
For example, use cases and user stories are often peppered with domain specific terminology, e.g. CDOs, CLOs, Cedent, retrocession etc etc.
If TeamPulse allowed you to create definition artifacts, subsequent readers of the user story would be able to click on the artefact and get a description. You would also be able to trace all references to particular artifact.
I first came across this functionality in Objectory (Ivar Jacobson's casetool) in the early 1990s.
It was an immediate hit with the BAs because they now had a defined data dictionary.
Developers new to the domain benefitted from the extra information allowing them to come to terms with the domain (if you pardon the pun).
Regards
Aidan