Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: mchiuminatto on November 24, 2004, 10:57:27 am
-
Hi EA team
I've posted this issue before, but I couldn't find it.
I would like a lot (and some potential customers too) that Element Tasks has the same properties that Model Task have, above all:
Assigned to
Start
End
Total Time
Actual Time
Percent
Is there any reason for not to implement this request?.
-
I support this request !
-
Hi EA Team.
If you don't listen to me, please listen the Guru:
I support this request!
-
My vote doesn't weigh more than yours. So we are only two :-[
-
Three, if you count me in :-)
I would also like the same on the "Issue" elements.
My vote doesn't weigh more than yours. So we are only two :-[
-
Hi Bruno, Thomas.
I hope we keep on counting votes, and EA team look down this topic.
Thanks guys.
-
Hello EA Team, regarding this request; and as Pink Floyd said:
Hello, hello, hello, is there anybody in there?
Someone who can hear me,
Is there anyone at home?
:'(
-
Hi Marcello,
it sounds here more like the Cumbia de los muertes :-) We should probably submit it to Sparx as a feature request.
Bruno
Hello EA Team, regarding this request; and as Pink Floyd said:
:'(
-
I don't think that number (or guruness) of supporters is the deciding factor - if you've presented your case well and the Sparx guys'n'gals see it to be a good feature, then they'll consider it.
I'm sure they read all the issues posted here, and shouting or nagging won't make any difference ;-)
Well, that's the basis I work on anyhow ...
-
G'day,
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.
-
mikewhit, you are right:
I'm sure they read all the issues posted here, and shouting or nagging won't make any difference
Taking Bruno’s advice, why don’t we elaborate a formal requirement here and then we post it to Sparx as a feature Request?
I will start, pleas review and comment.
Feature proposal.
1. Tasks and issues properties.
Tasks and issues should have the following properties:
Task name
Type.
Status
Priority
Owner
Assigned to
Total time
Actual time
Start date
End date
Percent
Description.
Comments (History).
Benefits.
- Increased work assignment and tracking capabilities.
- A better integration with planning tools (i.e. MS Project and others)
2. New task element in Custom diagrams
A new Task element should be added to the existing: Requirement, Change and Issue. This element should have the properties described in Requirement 1.
A task, should have the same capabilities to be linked to another element, same as Requirements.
If a task is linked to an element, it will be viewed in the element Maintenance window. If it is not, the parent element will be the model, so it will be viewed in the System (model) window (as a model task).
Benefits:
Increased usability in element task assignment.
(CJ you could have better arguments regarding benefits)
Ok guys, please make your comments, corrections, recommendations and so forth. After we all agree on this, I will post it to Sparx as a Feature Request. To be copied on that mail, please send me your e-mails via private message.
-
Hi Marcello,
I agree. Maybe we should also mention CJ's suggestion:
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).
That definitely makes sense and would make usage of the tasks much more efficient!
Thanks,
Bruno
-
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.?
-
Done
Feature proposal V1. R1
1. Tasks and issues properties.
Tasks and issues should have the following properties:
Task name
Type.
Status
Priority
Owner
Assigned to
Total time
Actual time
Start date
End date
Percent
Description.
Comments (History).
Benefits.
- Increased work assignment and tracking capabilities.
- A better integration with planning tools (i.e. MS Project and others)
2. New task element in Custom diagrams
A new Task element should be added to the existing: Requirement, Change and Issue. This element should have the properties described in Requirement 1.
A task, should have the same capabilities to be linked to another element, same as Requirements.
If a task is linked to an element, it will be viewed in the element Maintenance window. If it is not, the parent element will be the model, so it will be viewed in the System (model) window (as a model task).
Besides implementation of tasks, all other items in the System and Maintenance tabs/workspaces should be converted to elements (just like the requirement and change elements).
Benefits:
Increased usability in element task assignment.
(CJ you could have better arguments regarding benefits)
-
I think the two are closely related, let's keep them together (and hope we can get them soon).
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.?
-
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.
-
Please, a last review.
Feature proposal V1. R2
1. Tasks and issues properties.
Description.
Tasks and issues should have the following properties:
Task/Issue name
Type.
Status
Priority
Owner
Assigned to
Total time
Actual time
Start date
End date
Percent
Description.
Comments (History).
Benefits.
- Increased work assignment and tracking capabilities.
- A better integration with planning tools (i.e. MS Project and others)
2. Implementation of Project Related Artifacts.
Description.
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, we mean the following:
- System artifacts (model tasks/issues/glossary)
- Maintenance artifacts (element defects/changes/issues/tasks)
- People artifacts (authors/clients/resources/roles)
By system-related artifacts, We 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.
Benefits:
i) The big advantages 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).
ii) 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.
[/color]
-
Looks good to me. Good job, Marcello! :-)
-
Take my applause too :)
Sparx: it's okay if you deliver by end of the week ;D
Honestly: having these features would make EA really a lot more valuable!
-
My thread fellows.
I've sent the Feature Request.
Thomas, you are giving them too much time. ;).
I bet Sparx will answer soon our request.
Let's see what happen.
-
Nice structural requirements guys - now about behaviour ;)
I think we are really onto a good thing here. I will try and put together my thoughts on these aspects over the weekend.
A couple in advance -
1) defects and issues need an impact severity attribute as well as priority (the field is actually there at the moment in the db but notr exposed.)
2) All status, categorisation, impact and like attributes need to be soft - i.e. settable for the project.
3) I am strongly for the separate browser idea for management elements. In fact would even like to suggest that a totally separate interface for the management of management elements might be advantageous.
4) All management elements should apply to connectors as well as elements!!!!!
Bruce
-
Wow!,
You guys have been busy :-) I have received the email request, and I will pass it on. Good to see some healthy communal action!
-
Bruce: welcome aboard.
Great!!! TomO.
-
Setup elements for system, maintenance, and testing artifacts that are sort of like the Requirement, Change, and Issue elements.
Proposal:
"Project management artifacts (pma's) should be placeable in a diagram. That is it should be possible to represent a pma as a model element and to place the icon for the pma in a diagram."
This differs from creating a special element that is a project management artifact in that the current aspect of viewing pma's within an element, as an element feature or in the maintenance window lists remains and a functional change is introduced that lets us place a pma from the above lists into a diagram as an UML extension element.
This would alleviate some of the difficulties we have with external requirements.
Bruce
-
Does anyone have a CVS server we could use to share a repository for this work??
-
Hello EA team, Happy new year for you and all the forum members.
Is there any news regarding this Request/Suggestion?
-
Yes! An update would be nice :D
-
Persuant to my other post in General,
Requirement: EA should provide a search mechanism for pma's.
bruce
-
I've been following this thread and would also like to see it happen. I'm currently trying to push the EA Object Maintenance for our project change and defect tracking. My problem is that the current Priority, and Status selections don't match what management wants and there isn't a way to modify the selections.
-
Hi
Here are some news, coming from Sparx, regarding this thread.
I had a read through the suggestions and make the following comments:
1. Changing the database structure in EA is very difficult at this point in time. Version 5 may see a revamp of the database, at which time it would be possible to add additional fields as suggested in your note. Until then we are stuck with the current implementation.
2. The additional project management custom types would almost be better implemented as a Profile. With the new structured tagged values it would be possible to define very complex and detailed tagged properties based on time/date format, masked input, set lists & etc. It would be possible to add the suggested ones if required – but the profile is a very flexible mechanism now for adding very specific properties and information.
3. A separate docked window creates a few problems – especially with regard to differentiating between element types and intent. A better option I would suggest would be to put a new Project Root node in the main Project View to hold all project management information. It is still separate, but doesn’t require EA to make decisions on how to split artifacts between windows.
Also note that version 4.51 has moved the Project Management dialogs into a single docked window – so Assigned Resources, Metrics, Risk and Effort are now in one dockable window.
In addition version 4.51 includes updates to the RTF generator to include Metrics, Risks, Effort, System Issues, System Tasks and Glossary in the RTF output.
I would be interested in knowing if the option of a UML profile to implement the custom project management items is of interest? We could look at implementing something in the near future along these lines. Additional custom elements would take longer.
Best regards,
Geoffrey Sparks,
CEO Sparx Systems p/l
-
I wasn't much aware about this profile-thing. Fiddled around a bit. This might really help (for now ;)).
-
Hi Geoffrey,
your suggestion to use a profile seems to be even more than a good workaround. (However, the realisation of above request would be better ;D). One thing I'm missing now is the possibility to create a drop down tag of ALL people (authors, clients and resources) since an issue can be attached to any of those. Also you might think of polishing the tag creation interface a bit...
-
I just wanted to bring this up again (keeping the topic "hot"). There is something to additionally remark. When you define requirements in an element, you have these handy in the properties. You can also move them externally and place them in a diagram. This technique could also be used with element changes, issues, a.s.o. I really would appreciate having some kind of element related things in one or more lists and also the possibility to fiddle around with these as own elements. I know this will mean some major redesign (not to forget the system issues, glossary, to do!).
Eagerly awaiting EA 6.0 ;)