Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - CJ

Pages: [1] 2 3 ... 20
Suggestions and Requests / Change the implementation
« on: December 08, 2004, 08:36:33 am »
Okay, I think I've managed to put number 2 into a more coherent form than what I originally posted:

I'd like to request a change in the implementation of project management artifacts: setup the implementation of those artifacts to match the implementation of system-related artifacts.

By project management artifacts, I mean the following:
- System artifacts (model tasks/issues/glossary)
- Maintenance artifacts (element defects/changes/issues/tasks)
- People artifacts (authors/clients/resources/roles)

I haven't included testing artifacts (unit/integration/system/acceptance/scenario) in the list above, as I haven't used them yet an am not sure of any benefits in including them in this request.

By system-related artifacts, I mean all of the elements available in the UML toolbox.

Setup elements for system, maintenance, and testing artifacts that are sort of like the Requirement, Change, and Issue elements.  Set people artifacts as actors.

Setup a new "browser" window for project-management artifacts, maybe called "Project Management Artifacts"; all of the above artifacts would be found and maintained in this new browser.  Maybe rename the "Project Browser" as "System Artifacts".  I think two browsers would keep things tidy.

The big advantages to me are the ability to link any project management artifact to any other project management artifact (for example, a hierarchy of tasks) and then link any project management artifact to any system artifact (for example, linking a task to any number of system elements).

If project management artifacts are elements, then they can appear in the relationship matrix.  A HUGE BONUS, as the matrix can then be used for linking defects/changes/issues to any number of other elements for assigning tasks to any number of people.

Suggestions and Requests / Re: element tasks properties
« on: December 08, 2004, 07:59:47 am »
Would it make sense for me to move that suggestion of mine to a separate thread/topic, just to keep the first request neat, tidy, focused, condensed, etc.?

Suggestions and Requests / Re: element tasks properties
« on: December 08, 2004, 05:07:56 am »

It is a pretty good Pink Floyd tune, though.

I'm in for this request, but I want to expand on it.

I would like to see the implementation of tasks (and all other items in the System and Maintenance tabs/workspaces) converted to elements (just like the requirement and change elements).

Tasks can still be viewed in the System and Maintenance tabs/workspaces, but can be dropped on to diagrams and linked to other elements.  Tasks can still be presented the same way in documentation and reports.  But the ability to do with tasks the same as with requirement and change elements would be awesome!

edit: It would be nice if "People" (under the configuration menu) were implemented the same way: as "Actor" elements located in a "People" workspace.

edit 2:I like to keep project management/maintenance artifacts in their own "browser", separate from the "Project Browser" which shows system-related artifacts.  But I really really want to be able to link elements from both browsers on my diagrams.

Suggestions and Requests / HTML output: attribute link to class type
« on: December 10, 2004, 07:49:08 am »
G'day g'day,

We have many class attributes with types set to classes with stereotype <<type>>.

It would be nice if EA's generated HTML documentation included, in the attributes sections, links to the classes for those attributes whose types are <<type>> classes.

Suggestions and Requests / Re: Association control
« on: December 08, 2004, 06:20:36 am »

very often in generalization relatioship superclass has many descendants (children) and I prefer to link all descendants into superclass using one point - one generalization triangle

I think you're looking for "Tree Style Hierarchy";  look up that string in EA's help file index.

Suggestions and Requests / Re: Hide operations selectively
« on: November 05, 2004, 04:27:25 am »

Until elision becomes a feature, how about putting those functions (that you want to make visible) in an interface class?

Make the functions in the interface class visible, and hide all functions in the class that realizes the interface?

Suggestions and Requests / Re: Some visual questions
« on: October 26, 2004, 06:52:58 am »

Scratch that anwer of mine to question 1 ... that's for something else.

Sorry, haven't had enough caffeine yet.

Suggestions and Requests / Re: Some visual questions
« on: October 26, 2004, 06:49:11 am »

Question 1:

Lookup "Object Appearance" in EA's help file index.  There is an option called "Allow elongated Use Cases".  I think that will do the trick.

Suggestions and Requests / Re: Alias and Name Display
« on: October 22, 2004, 05:15:22 am »
G'day folks,

Some kind of voting mechanism would be a great idea.

How's about letting us indicate, in our profile, our top three requests from some list?

Make that list available in the same way as the list of Members is available.  Some link to a list that show all requests and, for each request, the number of members that have indicated interest in that request.

Suggestions and Requests / Must modify "Delete ... Are you sure?"
« on: April 08, 2004, 07:13:50 am »
G'day g'day,

I don't (YET) have a need for multiple select in the project browser, but if that feature does get added, then please include this requirement:

- Make sure that the "Delete ... Are you sure?" message box really highlights that I'm about to delete a bunch of stuff ... ideally a list of every item I'm about to delete.

I hate not having an opportunity to avoid making a really bad mistake.

Suggestions and Requests / Re: Request Module! - Template Designer(Document)
« on: September 12, 2004, 07:06:37 am »

I wouldn't waste too much effort here, Thomas.  Sounds like BIG BOSS has already made the decision.

We're extremely satisfied/impressed with EA's  functionality  (including, as per EA help file index entry, "Creating Documents").  I can certainly appreciate how "projectgroup" would be frustrated in having to work with something other than EA.

Suggestions and Requests / Re: Composite Elements: Auto-create aggregations
« on: September 02, 2004, 04:33:29 am »

I wanted to modify that original post a bit ...

It would be nice if EA automatically, with prompting via dialog(s), optionally created aggregation (or other, or no) relationships between elements that are, in the project tree, "subsidiary to" a composite element.

Suggestions and Requests / Composite Elements: Auto-create aggregations
« on: September 01, 2004, 11:28:30 am »

It would be nice if EA automatically, or by prompting, created aggregation relationships between elements that are, in the project tree, "subsidiary to" a composite element.

Good idea or just plain crazy?

Suggestions and Requests / Re: Make Copies of Use Cases
« on: August 25, 2004, 07:29:48 am »

This may be overkill or just a completely useless/silly suggestion...

Have you tried out patterns in EA?  Check out in EA's help file contents:  Modeling with UML ... UML Patterns.

Suggestions and Requests / Re: Make Copies of Use Cases
« on: August 24, 2004, 12:02:46 pm »

Is the current "copy diagram element" feature (as per EA help file's index) what you are looking for?

Pages: [1] 2 3 ... 20