Can some one explain the view which is available in https://www.enterprise-architecture.org ... l_labs.php
Is it one time exercise?
Will there be a transaction type record saved when we do a principles adherence for an application ?
How to see the past records?
We find a need for this view, but could not understand the actual flow behind the usage.
Design Authority View
This view was intended as an opportunity for a project to say I am building a solution using these apps/services, these technologies/components and adhering to these principles. If there is any deviation from strategy, i.e. the tool says waiver required, then the user should refer to the EA team. It saves every project being reviewed, allowing EA to focus on the big issues. It is a Labs view and we are working on a more elegant version which brings in standards.
At the moment there is no transactional element, we're looking at producing both a printout version and a way of allowing approvals (for importing into Open Source and automatically updating in Cloud/Docker). It may be that we use the Assessment class for this but we'll see.
At the moment there is no transactional element, we're looking at producing both a printout version and a way of allowing approvals (for importing into Open Source and automatically updating in Cloud/Docker). It may be that we use the Assessment class for this but we'll see.
