« previous next »
Pages: 1 [2] 3

Author Topic: element tasks properties  (Read 26183 times)

CJ

  • EA User
  • **
  • Posts: 288
  • Karma: +0/-0
    • View Profile
Change the implementation
« Reply #15 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.
« Last Edit: December 08, 2004, 08:37:37 am by jasonv »
Logged
Cheers and best regards.

mchiuminatto

  • EA User
  • **
  • Posts: 113
  • Karma: +0/-0
    • View Profile
Re: element tasks properties
« Reply #16 on: December 09, 2004, 04:22:36 am »
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]
Logged
Regards.

Marcello

Bruno.Cossi

  • EA User
  • **
  • Posts: 803
  • Karma: +0/-0
    • View Profile
Re: element tasks properties
« Reply #17 on: December 09, 2004, 05:07:31 am »
Looks good to me. Good job, Marcello! :-)
Logged

thomaskilian

  • Guest
Re: element tasks properties
« Reply #18 on: December 09, 2004, 07:11:26 am »
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!
Logged

mchiuminatto

  • EA User
  • **
  • Posts: 113
  • Karma: +0/-0
    • View Profile
Re: element tasks properties
« Reply #19 on: December 09, 2004, 11:33:36 am »
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.
Logged
Regards.

Marcello

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: element tasks properties
« Reply #20 on: December 09, 2004, 01:43:10 pm »
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
« Last Edit: December 10, 2004, 04:18:06 pm by sargasso »
Logged
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.

TomO

  • EA Administrator
  • EA User
  • *****
  • Posts: 79
  • Karma: +6/-0
  • EA - Bridging the gap between Business and IT
    • View Profile
    • Sparx Systems
Re: element tasks properties
« Reply #21 on: December 09, 2004, 02:01:32 pm »
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!
Logged

mchiuminatto

  • EA User
  • **
  • Posts: 113
  • Karma: +0/-0
    • View Profile
Re: element tasks properties
« Reply #22 on: December 09, 2004, 02:29:37 pm »
Bruce: welcome aboard.

Great!!! TomO.
Logged
Regards.

Marcello

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: element tasks properties
« Reply #23 on: December 10, 2004, 04:14:47 pm »
Quote
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
« Last Edit: December 10, 2004, 04:17:24 pm by sargasso »
Logged
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: element tasks properties
« Reply #24 on: December 10, 2004, 04:19:37 pm »
Does anyone have a CVS server we could use to share a repository for this work??
Logged
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.

mchiuminatto

  • EA User
  • **
  • Posts: 113
  • Karma: +0/-0
    • View Profile
Re: element tasks properties
« Reply #25 on: January 17, 2005, 02:00:21 pm »
Hello EA team, Happy new year for you and all the forum members.

Is there any news regarding this Request/Suggestion?
Logged
Regards.

Marcello

thomaskilian

  • Guest
Re: element tasks properties
« Reply #26 on: January 19, 2005, 01:44:50 am »
Yes! An update would be nice :D
Logged

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: element tasks properties
« Reply #27 on: January 19, 2005, 01:26:35 pm »
Persuant to my other post in General,

Requirement: EA should provide a search mechanism for pma's.

bruce
Logged
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.

bollwahnk

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: element tasks properties
« Reply #28 on: January 21, 2005, 05:41:04 am »
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.
Logged

mchiuminatto

  • EA User
  • **
  • Posts: 113
  • Karma: +0/-0
    • View Profile
Re: element tasks properties
« Reply #29 on: January 23, 2005, 02:24:03 pm »
Hi

Here are some news, coming from Sparx, regarding this thread.

Quote
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

Quote




Logged
Regards.

Marcello
Pages: 1 [2] 3
« previous next »