Change Management and Project Management items/types

[Modesto Vega]

I have a few questions about Change Management and Project Management items/types,

1) Is it possible to create new Change Management and Project Management types, such as assumptions and scenarios?
2) Is it possible to customise the statuses for specific Change Management and Project Management types?
3) Where in  the database are Project Management types stored?
4) Other than duplicating functionality, is there a reason for having the same type multiple times in Sparx EA. For example, issue is an element type, a change management type, project management type; something similar applies to risk and requirement.

P.S.: For context, I am using Sparx EA v16.1.

[Eve]

1) Is it possible to create new Change Management and Project Management types, such as assumptions and scenarios?

No. I'd recommend instead of using those built-in windows you create a stereotyped requirement (or similar)

2) Is it possible to customise the statuses for specific Change Management and Project Management types?

No. I'd recommend using a stereotype property with your own enumeration.

4) Other than duplicating functionality, is there a reason for having the same type multiple times in Sparx EA. For example, issue is an element type, a change management type, project management type; something similar applies to risk and requirement.

Basically preference. There are items internal to an object, that makes some things easier. The project management ones are effectively the same as the ones owned by the object, but are intended to apply to the repository as a whole.

The elements mean that you can link them to multiple other elements in different ways. You can customize them with profiles, put them hierarchies etc. If you can't tell, that's my preference.

[Modesto Vega]

Thanks Eve and Happy New Year.

4) Other than duplicating functionality, is there a reason for having the same type multiple times in Sparx EA. For example, issue is an element type, a change management type, project management type; something similar applies to risk and requirement.

Basically preference. There are items internal to an object, that makes some things easier. The project management ones are effectively the same as the ones owned by the object, but are intended to apply to the repository as a whole.

The elements mean that you can link them to multiple other elements in different ways. You can customize them with profiles, put them hierarchies etc. If you can't tell, that's my preference.

I can see the logic behind having element change management items. I can also see the logic behind having project and enterprise change and project management types. By the way, I use the term "project" in the PMO sense of the word.

2 great enhancements, in my opinion, will be to have
1) items out-of-the-box covering the full RAID spectrum at element and repository level - i.e., Risks, Assumptions, Issues, Decisions, and perhaps even Dependencies,
2) the ability to move of copy them between levels - i.e., from element to project or repository level.

The fact that assumptions are missing is an unfortunate limitation, it can contribute to making EA look like an incomplete product. It is good that the limitation can be overcome via customisation - i.e., create a stereotyped requirement. But customisation is a double-edged sword, constant use of it can also be viewed as a limitation.