Book a Demo

Author Topic: EA 8.0 step and extension  (Read 3430 times)

remek

  • EA Novice
  • *
  • Posts: 13
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
EA 8.0 step and extension
« on: March 23, 2010, 11:47:42 pm »
I have examined the new API for EA 8.0.
I have find a small issue.
Enumeration ObjectType has 2 new Items
they are: otStep and otExtension.
To be consistient they should be named otScenarioStep and otScenarioExtension.
BR
Remek

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: EA 8.0 step and extension
« Reply #1 on: March 24, 2010, 11:11:23 am »
Have you formally reported it?

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

remek

  • EA Novice
  • *
  • Posts: 13
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: EA 8.0 step and extension
« Reply #2 on: March 24, 2010, 09:38:20 pm »
Yes, I did.
Remek

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: EA 8.0 step and extension
« Reply #3 on: March 25, 2010, 08:27:31 am »
The only times when I see a two word qualification on the names is when it is required to remove ambiguity.

eg. otAttributeTag, otConnectorTag.

On the other hand there are plenty of items that aren't qualified.

eg. otSwimlane is not otDiagramSwimlane
otTest is not otElementTest
otScenario is not otElementScenario
which would then imply otElementScenarioStep and otElementScenarioExtension (except of course that an extension actually comes from a step)

So, please explain how it's more consistent to add the word scenario into those types.

remek

  • EA Novice
  • *
  • Posts: 13
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: EA 8.0 step and extension
« Reply #4 on: March 25, 2010, 06:51:24 pm »
otAttributeTag has a corresponding AttributeTagClass and interface AttributeTag

the same for
otConnectorTag - ConnectorTagClass,  ConnectorTag
otSwimlane - SwimlaneClass, Swimlane
otTest - TestClass, Test
otScenario - ScenarioClass, Scenario

the same for Step and Extension

otStep - ScenarioStepClass, ScenarioStep
otExtension - ScenarioExtensionClass, ScenarioExtension


As you can see the naming pattern is not the same, to the "old" object
and "new" ones.

BR
Remek