Eclipse Community Forums: UML2 » UML Testing profile

Help

Home

Home » Modeling » UML2 » UML Testing profile

Show: Today's Messages :: Show Polls :: Message Navigator

UML Testing profile [message #472654]

Wed, 18 April 2007 22:08

Manar El-Kady

Messages: 78
Registered: July 2009

Member

Hi,

In the UML testing profile, why this document composed of two
components: the proposed testing profile and the MOF-based metamodel for
the same concepts identified in the profile? Do they have the same
target with different technique?or what?

Thanks in advance,

Manar

Report message to a moderator

Re: UML Testing profile [message #472655 is a reply to message #472654]

Thu, 19 April 2007 01:53

Kenn Hussey

Messages: 1620
Registered: July 2009

Senior Member

Manar,

You will see this often in OMG specifications - both a profile and MOF-based
representation of the metamodel are presented. The MOF metamodel is
typically provided to allow MOF-based (not UML-based) tools to claim
compliance with the specification...

Kenn

"Manar El-Kady" <manar.elkady@gmail.com> wrote in message
news:f064v8$sva$2@build.eclipse.org...
> Hi,
>
> In the UML testing profile, why this document composed of two components:
> the proposed testing profile and the MOF-based metamodel for the same
> concepts identified in the profile? Do they have the same target with
> different technique?or what?
>
> Thanks in advance,
>
> Manar

Report message to a moderator

Re: UML Testing profile [message #472680 is a reply to message #472654]

Thu, 19 April 2007 21:06

Eclipse User

Originally posted by: carrasco.ModelDrivenDevelopment.co.uk

Here we are again.

That is not the standard view of the metamodeling stack.
That is the viewpoint of those that have invested heavily in UML,
and want to avoid dispersion into many of what we now know as "Domain
Specific Languages"
(like testing).

The other viewpoint, of those whose drive is not aligned with UML industry,
is that the concepts are directly captured as instances of MOF,
but, if you have a UML tool,
you may use the lightweight extension mechanism
called "Profiles" (stereotypes onto UML classes).

Many use to do both: the metamodel as instance of MOF
(for conceptual undestanding, and driving model-driven-engines and
generators like EMF, GMF)
then also a UML Profile, for those that use Rational Rose, and the like.

That

Report message to a moderator