Book a Demo

Author Topic: Spell checking the Name field  (Read 3590 times)

bcrier

  • EA User
  • **
  • Posts: 30
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Spell checking the Name field
« on: August 06, 2009, 12:38:55 am »
Hello everyone,

Spellchecker skips the Name field of an element while scanning.  I tried it a number of times and even checked on the forum, and did not find any posts related to this.

I think this is a major limitation.  Models lile BPMN, Activity, Data Model etc all need to have english language words in their names.  Without the spell check, a lot of errors can go unnoticed until later.

I noticed that that the requriements element has a short description field instead of Name, and the spell checker does scan it.

I think there should be an option for the users to select whether they want to spell check the Name field or not.  I personally believe that this is an extremely high priority.

EA in our organization is being used by BAs, DBAs, Project Managers and even Business Users, they have no interest in understanding that  the techies like us may use non-english language words as Names and hence we do not want to put spell checker on it.  But they do have an option of mandating that we do not use the tool.

Please help.  Thanks.

Bobby

Martin Terreni

  • EA User
  • **
  • Posts: 672
  • Karma: +0/-0
  • Sorry, I can't write
    • View Profile
Re: Spell checking the Name field
« Reply #1 on: August 06, 2009, 02:40:07 pm »
This is somw what problematic. It could be done, but then you will have to give the user the option to skip names.
You wouldn't want EA to spell check you classes names, most of them have composed names unreconizable for the speller. This would mean you willbe getting alot of messages which most of them will be useless.
Recursion definition:
If you don’t understand the definition read "Recursion definition".

bcrier

  • EA User
  • **
  • Posts: 30
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Spell checking the Name field
« Reply #2 on: August 07, 2009, 12:32:48 am »
Thanks for the reposnse.

I think the defauylt could be skip element names, but then in some models like BPMN, Activity, Database etc. user may want to check the spellings of the element names.

I think it is better to have the flexibility and then users use their best judgement.  This should also work well with search within a package option, because then you could use for BPMN packages and not use it for other.

In our company there is already a debate whether we should use EA or revert to Visio for BPMN, because the process analysts do not want to go through the hassle of printing reports, then doinf spell check and then making the changes manually.

Regards,
Bobby