Few of these tools support transformations from use case models to another analysis or design model. What is your opnion on why?
Can you describe in more detail what "fine-grained use cases" are? I think most tools support use cases as they are part of UML. I'd have to look up the UML spec again, but I think its no problem somehow linking e.g. activity diagrams with use cases. If you were referring to some textual use case description, then maybe it is because there is no standard?
What I really mean when I say fine-grained use case (UC)specifications:
Use UC during the whole software development process, so different role (RE engineer, analyst, designer, programmer) read this UC specification and semantically reach it, so programmer (luckily for him) has everything on one place.
Fine-grained UC specification means that all details are specified or connected in that UC specification.
What would such a fine-grained specification entail? A UML Use Case Model? A textual description as introduced by Jacobson? Or the more elaborate forms of e.g. Constantine or Cockburn?
Yes I know it. Now Visual paradigm, EA contain way to specify use case steps (action), but there is now way to generate some other artifacts automatically, because there is no meta-model of use case actions. You must refine action if You want, but it can guaranty always traceability.
- Badges
- Science topic
- Similar topics
- Geoscience
- Cartography
- Mapping