customise meta-model to reflect architecture standards
Posted: 23 Jan 2023, 07:48
Hi,
We are a Essential Cloud client. We have a need to make application architecture standards recommendation on each of our applications . We were thinking of adopting TOGAF 10 architecture standards classification namely Proposed, provisional, Active, Phasing out and retired standards. This construct would be equally applicable to other architecture layers such as business, information, tech in the future.
Please note this is different to lifecycle status such as prototype, pilot, production etc.
A few questions:
1) Is this currently captured in any of the enumerations or elsewhere in the Essential Meta Model.
2) Is there any specific documentation on guidelines to customise the meta model.
I would appreciate any advise or pointers to documentation.
regards
Vivek
We are a Essential Cloud client. We have a need to make application architecture standards recommendation on each of our applications . We were thinking of adopting TOGAF 10 architecture standards classification namely Proposed, provisional, Active, Phasing out and retired standards. This construct would be equally applicable to other architecture layers such as business, information, tech in the future.
Please note this is different to lifecycle status such as prototype, pilot, production etc.
A few questions:
1) Is this currently captured in any of the enumerations or elsewhere in the Essential Meta Model.
2) Is there any specific documentation on guidelines to customise the meta model.
I would appreciate any advise or pointers to documentation.
regards
Vivek