Custom Modelelements vs. Profiles vs. Docking Wind

[tfischer]

Hi there,

I notices some inconsistency in the systemmodel of EA for a while: There are serveral ways to create Defects:

a) By Adding Custom Model Element of type Defect to a Diagram
b) Via the Project Menu Item Issues
c) By Creating a own UML Profile for Software Engineeing that contains UML Model Elements such as Defects

Unfortunately do these three ways not integrate into oneanother. This means is you create a Defect as Model Element using a) or c) it is not listed in the Issues Window b).
The same is true the other way around.

Please Geffory let us know which way EA will develop in furture. Will you implement a UML Profile for Software Engineering like referenced in the OMG's Software Process Engineering Meta Model (SPEM) or will you stick to the windows. Even the Documentation says different things at some time. When it comes to relationships matrixes there it is said that you could model your staff as Model Elements and assign it to features and have a look at the assignments in the matrix.

All this is true, but I think we would all benefit from a consistent usage model when it comes to Custom Model Elements, even Sparxsytems would benefit.

Hope to hear from you, soon.

Best Regards

Tim.

[gsparks]

Hi Tim,

It is a perplexing problem - as it is possible to describe testing, maintenance, requirements management, resourcing etc. all using UML (which could be conveniently packeged in Profile form) ... while some of these features already exist in a built in manner in EA.

I would be happy to listen to any opinions on the matter. And if someone would like to contribute a profile or two that can be used for these purposes - even better. The Profile mechanism is a good way of providing extended behaviour with no additional application update. The reports are already there in HTML and RTF format.

Over time it is my guess that the Profile mechanism would provide the most flexible and extendable option for using EA to model and capture all aspects of project development.

Regards,
Geoff Sparks