Tabular interface for requirements?

[Ronaldo Juliatto]

Hi

I found this text in a press link inside Sparx Site:

"Users may now quickly enter requirements and edit lists of elements in a new tabular interface – or rapidly capture states and transitions in a new State Table editor."

This text is in the page at http://www.sparxsystems.com/press/articles/ea70.html

I could not find this "new tabular interface" to enter requirements. Does anybody know how can it be accessed?

Thanks in advance

Ronaldo Juliatto

[Martin Terreni]

 

[«Midnight»]

Ronaldo,

Perhaps this is what you were looking for: http://www.sparxsystems.com/EAUserGuide/index.html?state_table_diagram.htm

David

[Martin Terreni]

That explains state charts, which I new, but what about requirements? does it mean the require tab?

[Ronaldo Juliatto]

Well...

If you click with the right button over the parent package of the requirements, there will be the option "Show Element List". With this interface it seems to be possible to edit and insert elements, in this case, requirements.
is this the "Tabular interface to enter requirements"? I was thinking of something like the SysML Requirements table.

I don't if this is the answer, a way to the answer or yet another confusion ingredient to this doubt....



Thanks

Ronaldo Juliatto

[Eve]

The Element List is indeed what the website was referring to in the first half of that statement.  The second half refers to the state table diagram.

[thomaskilian]

I saw this feature by coincidence but was not aware of it's usefulness. Now when playing a bit around with it is looks like a very handy tool to manage also Issues and other things. Good enhancement!

[Ronaldo Juliatto]

OK

I think this is really a good enhancement. It helps a lot when registering features and requirements.

Thanks, guys

[Martin Terreni]

I developed a full application add in doing this a couple of months before 7.0 went out, what a waste of good work...

[Paolo F Cantoni]

I developed a full application add in doing this a couple of months before 7.0 went out, what a waste of good work...

Martin,

Since we have no road map - this is the frustrating problem for us poor users...

I'm going to shortly reactivate the postings on Formatted Text for the various textual fields.  We'd previously been given the impression that it would be coming for v7, but so far 'nada'.

It's now becoming critical for us to come up with a formatted text strategy.

[«Midnight»]

[1] Since we have no road map - this is the frustrating problem for us poor users...

[2] I'm going to shortly reactivate the postings on Formatted Text for the various textual fields.  We'd previously been given the impression that it would be coming for v7, but so far 'nada'.

Thanks for bringing these (once again) into the light.

[1] Sorely needed - it's necessary for us to plan as well as model. Without a road map we're in the tall grass.

[2] Yes, lets do.

Version 7.0 is out the door, so perhaps now Sparx can take some time to handle some of these real hot spots. The formatted text issue is probably the most highly anticipated  features. There are others, but we need to get some wheels moving on these 'legacy' issues.

Another 0.02 CAD FWIW...
David

[Ronaldo Juliatto]

Fellows

With respect to the RTF notes, I tend to think this is only important if you are exporting documentation and want it well-formatted.
In this case, I think that the "Linked documents" and "Document Artifacts" could solve the problem with some advantages.

Am I being too simplistic?

Ronaldo

[«Midnight»]

Fellows

With respect to the RTF notes, I tend to think this is only important if you are exporting documentation and want it well-formatted.
In this case, I think that the "Linked documents" and "Document Artifacts" could solve the problem with some advantages.

Am I being too simplistic?

Ronaldo

Not really. The issue of (better) access to rich formatting exists regardless. However, exporting documentation is not always the solution, particularly where something 'quick and easy' needs to be done for the weekly meeting or whatever.

We're looking for a way to highlight (for example) text within the scope of the model, which has a variety of uses.

An important example is use cases, where it would be helpful to hightlight (and perhaps tag for automation) the names of other use cases or model entities within the text of scenarios and such.

Nonetheless, solving the problem this thread refers to would be a good step in adding useful features, and value, to attached files and artifacts.

David

[Jan Pacovsky]

I'm afraid that Linked Documents and Document Artifact aren't enough. While creating analytical outputs you ALWAYS need well-formatted outputs. Plain text formating is really pain. :-(