Locating diagram discussions

[Uffe]

Hi all,


Discussions don't seem to work properly in 15.0.1512. I can find nothing in subsequent release notes that addresses these issues.
Can someone check whether they're still there in 15.1?

You can create new discussions linked to elements and diagrams by selecting the element / diagram and creating a new discussion in the Collaborate window.
You can list ongoing discussions using Start -- Collaborate -- Discussions -- Discussion History / Recently Discussed Elements.

Issue 1: Locating diagram discussions
Discussion History, according to its tooltip, is used to "Access recent discussions in the model". But it only lists discussions linked to elements. Diagram discussions cannot be located this way.
Recently Discussed Elements (a search) also doesn't locate diagram discussions, but that's consistent with the name -- but there should also be a Recently Discussed Diagrams.

Issue 2: Discussion History omits recent discussions
If you create a discussion on an element, it doesn't show up in the Discussion History until you restart EA (or possibly reload the project, but haven't tested).
Closing/opening the history window doesn't help.

Issue 3: Ghost discussions
If you create a discussion on an element and then delete it, it still appears in the Discussion History results. If you then try Edit Discussion, nothing happens (so at least EA doesn't crash).
(Recently Discussed Elements does not return ghost discussions.)
This also seems to resolve on restart.

So -- fixed or not fixed?


/Uffe

[steen.jensen]

Hmm So there ARE people that is using those functions, I was wondering if we should tests those functions, but everybody seams dislike Sparx EA inbuilt functions as Project, testing, collaboration etc...

[Uffe]

Oh we're not using them. I was just asked to look into it.

And it seems they are indeed unusable, or at least that Discussions are. Or at least in 1512.

As for project management, test management and all the other et ceteras, my advice is always not to bother. Integration of those kinds of functions into a documentation tool or IDE is nice, but the functions actually have to, well, work first. EA's take on project management for instance seems like it was cobbled together by someone who's never worked on an actual project with task breakdowns and dependencies and teams and reporting lines and deadlines and, you know -- project stuff.

If you do requirements engineering I'd say EA is actually a useful replacement for traditional tools, provided you spend the money to work out exactly how to use it in that capacity in your organization, but that's about it.

[qwerty]

I couldn't agree more.

q.