I have been looking into EA and Archimate for requirements management. The idea being something like:
- Create "Archimate 3 Outcome"
- Using the properties window - Outline any Requirements, constraints and Scenarios internally to the element
- Once an internal requirement is approved, move to external requirement for further refinement.
EA creates the external requirement element as a native EA requirement type, rather than an Archimate Requirement, which i cannot change the stereotype of, so it does not look like Archimate. Creating Archimate requirements manually does not work too well either. Archimate Requirements elements are classes, not EA requirement type elements, so i have to do more around them to get the same level of support (e.g. in document generation, searches, etc.).
For that matter, i have other internal element properties i cannot externalize with EA, but have Archimate element counterparts.
e.g.
Internal element constraints -> Archimate Constraint
Internal internal scenarios -> Archimate Course of Action
So i am trying to think about approaches. On one hand, Archimate types are visible and usable by others. On the other hand, EA native types offer features that are not available to classes.
Are others using architect in this way? any advice or ideas (other than don't use EA!)
