state is NOT a classifier

[ersin eser]

Why not ?

[Kyle Brown]

I give up ersin. What do you mean by this?
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.

[Matts Smith]

Simple question/simple answer.
Because!

[ersin eser]

sorry for the delay..

A classifier is a model element that describes behavioral and structural features of a model. Classifiers include classes, actors, use cases, data types, components, interfaces, signals, nodes, subsystems.
Some things are not classifiers: collaborations, interactions, relationships and states

I thought during the given time frame "state" could be a classifier . Any brain droppings ?

[Michael Ernest]

What are you quoting?
------------------
Michael Ernest, co-author of: The Complete Java 2 Certification Study Guide

[Jane Griscti]

Hmmm ... a 'state' usually represents 'data' and as they are defining a classifier as a 'behavioural or structural' feature then it makes sense to say a state is not a classifier. Then again, why say a 'relationship' is not a classifier. Don't relationships describe either a structure or a behaviour???
Hey, you asked for brain droppings

[ersin eser]

from schaum's uml outlines