UC Specification best practise - Module or Text?
In JKE Banking there are some sample UC Specifications
They are artifacts of type Text
If I go to create a UC Specification by default it creates a module. If I use the template it populates the module with many headings and text artifacts.
It seems like there was a change in direction of best practice during the evolution of the sample project.
Which is considered the better approach for formal UC Specifications - Modules with many individual text objects for each step or one single Text artifact containing all the steps?
It seems to me that the Text artifact approach would be better in most cases unless traceability to individual steps is required.
|
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.