Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Typical Project Roles
Enterprise Architect performs a number of tasks that are suited to a variety of professions. This topic describes some common working practices with Enterprise Architect for a range of project roles. There are tools for the roles of:
Topic |
Link |
||||||
|---|---|---|---|---|---|---|---|
Business Analyst, to create high-level models of business processes
|
|||||||
Software Architect, to map functional requirements, perform real time modeling of objects, design the Deployment model and detail the deliverable components
|
|||||||
Software Engineer, to map Use Cases onto Class diagrams, detail the interactions between Classes, define the system deployment and define software packages
|
|||||||
Developer, to perform round trip code engineering, including reverse engineering of existing code and generation of code from Class elements
|
|||||||
Project Manager, to assign resources to elements, measure risk and effort, estimate project sizes, and manage element status, change control and maintenance
|
|||||||
Tester, to create test scripts against elements in the modeling environment
|
|||||||
Implementation Manager, to:
|
|||||||
Technology Developer, to create customized additions to the functionality already present within Enterprise Architect
|
|||||||
Database Developer, to develop databases, including modeling database structures, importing database structures from an existing database and generating DDL for rapidly creating databases from a model
|
You can review a summary of the typical tasks supported for each role, or click on the appropriate role title to explore how Enterprise Architect can assist you in carrying out that role within a model driven project.
Learn more
