Enterprise Architect can be used to capture business requirements, design and management of all successive models, algorithms, process flows/workflows, design of business data objects and other artifacts.
The strong point is the ability to link the items in all models with each other, the more time the analysts and designers "invest" into making nice and clearly defined models, the higher the future pay-off by any successive changes to the systems.
Enterprise Architect is not a good tool for capturing rather unstructured business requirements, use e.g. Confluence or other solutions instead. EA should comprise the extracted models with very little unstructured information. Management of the changes process should not be done in Enterprise Architect, rather use JIRA/Confluence or similar.
The System Architects should not only hold programming skills, but they also require business and organizational expertise. They should also be able to give tasks to other members of the IT team so that they can focus on their area of expertise.
CommentairesAucun commentaire pour le moment
Suivre le flux RSS des commentaires
Ajouter un commentaire