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 - mchiuminatto

Pages: [1] 2 3 ... 8
1
Suggestions and Requests / Re: element tasks properties
« 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





2
Suggestions and Requests / Re: element tasks properties
« 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?

3
Suggestions and Requests / Re: element tasks properties
« on: December 09, 2004, 02:29:37 pm »
Bruce: welcome aboard.

Great!!! TomO.

4
Suggestions and Requests / Re: element tasks properties
« 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.

5
Suggestions and Requests / Re: element tasks properties
« 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]

6
Suggestions and Requests / Re: element tasks properties
« on: December 08, 2004, 08:00:50 am »
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)




7
Suggestions and Requests / Re: element tasks properties
« on: December 08, 2004, 07:38:33 am »
mikewhit, you are right:

Quote
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.

8
Suggestions and Requests / Re: element tasks properties
« on: December 07, 2004, 09:10:54 am »
Hello EA Team, regarding this request; and as Pink Floyd said:

Quote
Hello, hello, hello, is there anybody in there?
Someone who can hear me,
Is there anyone at home?



:'(

9
Suggestions and Requests / Re: element tasks properties
« on: December 01, 2004, 03:39:16 am »
Hi Bruno, Thomas.

I hope we keep on counting votes, and EA team look down this topic.

Thanks guys.

10
Suggestions and Requests / Re: element tasks properties
« on: November 30, 2004, 08:42:46 am »
Hi EA Team.

If you don't listen to me, please listen the Guru:

Quote
I support this request!


11
Suggestions and Requests / element tasks properties
« 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?.


12
Suggestions and Requests / Re: Locate in Browser
« on: February 10, 2005, 03:27:37 pm »
Great!!!!!

Thanks Bruce  ;D

13
Suggestions and Requests / Locate in Browser
« on: February 10, 2005, 12:50:52 pm »
Hi EA Team

Why did you restrict the Option Locate in Browser to Locate Classifier in Browser?

What if I want to locate an element (Class Instance)  in the browser instead of its classifier?


14
Suggestions and Requests / Re: extend target activation
« on: December 14, 2004, 06:32:51 pm »
easy, easy!!!  :o , you can better model it using a Par combined fragment. Check Superstructure, page 410 and 411 (an example)


15
Suggestions and Requests / Re: Export tag definitions
« on: December 14, 2004, 05:27:59 am »
EA Assigns a s_GUID to each "instance" of a tag. The only way I see to relate tagged values "instances" ( t_objectproperties  for instance) with your tag master list ,stored in  t_propertytypes, is by name field  :(

I don't know if that is what you are trying to do.

Pages: [1] 2 3 ... 8