To search text in use case scenario documentation

[MarkDavies]

Hi there

When writing basic flows and alternate flows many evolve into lengthy descriptions. It would be especially useful to be able to perform basic textual searches on such use cases.

This feature request is probably related to this one: "Rich text for use case scenario documenting" - http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=suggestions;action=display;num=1172253652;start=0

Surely most EA users must spend considerable time using these use case text editors (the core detail of any specification) but they just don't seem to cut the mustard!

I think EA is a great product although, in my opinion, the use case scenario text editor is way too simple for the daily demands put upon it.

Come on Sparx! This area needs a revamp! Doing so would provide substantial added-value to the product and would be well worth the effort.

Could you at least examine the cost/benefit of this solution soon?

[«Midnight»]

Are you just asking for text search, or do you have other specific suggestions?

There's much that can be done here. Perhaps some features would be easy for Sparx to add, but they would have to be well specified. Otherwise this runs the risk of getting sidelined while Sparx works on the 'next major release' of EA. In that case we'd likely be left right where we are now, trying to start the improvement process.

[thomaskilian]

Try advanced search / SQL / t_objectscenarios

[MarkDavies]

Good point Midnight.

Ok, I will start the ball rolling by compiling a list of feature requests for the use case scenario text box, with MoSCoW prioritisations.

Then you and others can chip in and brainstorm what features we collectively want. Eventually, we can hand this all over to the good people of Sparx to consider further.

How does that sound?

1. Rich text formatting (M)
1.1 Bold/Italic/Underline (M)
1.2 Font type (M)
1.3 Font colour (M)
1.4 Bullet points (including hierarchically numbered bullet points) (M)

2.  Text search features (M)
2.1 Find (M)
2.2 Find and Replace (M)

3. Tables (C)

4. Insertion of images (C)

Any formatting would also need to show through on the reports.

Furthermore, this type of rich text box control could be reused elsewhere in the system. Perhaps use case constraints, or requirements.

[thomaskilian]

This was a bit mean, David. You should have pointed out all the hopeless requests for RTF in the past...