Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: nilsandrey on March 21, 2013, 07:57:44 am
-
How can I relate in reports or Matrixes the "phase" attribute of packages and general objetcs with the packages at Project Model tree.
I'm interested on mapping requirements to versions of the project model withouth the need to explicit relations by using the phase attribute and the posibility of mass editing it.
-
I've tried both approaches: (1) using the 'Phase' attribute, and (2) linking elements to 'Phase' elements, and I always seem to end up using (2). Its so much more flexible. I can use the Relationship Matrix to quickly establish the relationships, or, link whole Packages to a Phase so the children of the Package 'inherit' the Phase.
I guess it's yet another debate like the one which DB designers have: create a new column, or create another table and a link the tables.
Linking stuff to a Phase is such a powerful idea, once you've got it to work (using which ever approach) I'm sure you'll want to use it more!
-
thanks Ian. I'm currently using the linking approach, and I'm agree it's very usefull. At this point the phase attribute it's little bit useless because it's hard to mantain the links to phase elements and the values on the attribute by hand.
Maybe with a custom stored proc on the EAP database...but I'm new on extending EA and don't know if this is a recommended extension approach.
Anyway, the concern on using the phase attribute it's because the field are there and can be using on reports or another autogenerated documentation. Personally, I have a continuous integration environment and I put the EA projects on build scripts together with the specific implementations.