Prev | Next |
Typical Project Roles
Enterprise Architect is an effective multi-disciplinary modeling platform that supports common work practices and provides features to assist the entire spectrum of roles and disciplines across enterprise, business, engineering and software projects. Each role will typically use different features of the tool. A number of the roles and their responsibilities that the system supports are outlined here.
You can review a summary of the typical tasks supported for each role, or review the Help topic for the appropriate role title to explore how Enterprise Architect can assist you in carrying out that role within a model-driven project.
Roles and Responsibilities
Role |
Responsibilities |
See also |
---|---|---|
Business Analyst |
Create high-level models of business processes. |
Business Analysts |
Software Architect |
Map functional requirements, perform real time modeling of objects, design the Deployment model and detail the deliverable components. |
Software Architects |
Software Engineer |
Map Use Cases onto Class diagrams, detail the interactions between Classes, define the system deployment and define software Packages. |
Software Engineers |
Developer |
Perform round trip code engineering, including reverse engineering of existing code and generation of code from Class elements. |
Developers |
Project Manager |
Assign resources to elements, measure risk and effort, estimate project sizes, and manage element status, change control and maintenance. |
Project Managers |
Tester |
Create test scripts against elements in the modeling environment. |
Testers |
Implementation Manager |
|
Implementation Managers |
Technology Developer |
Create customized additions to the functionality already present within Enterprise Architect. |
Technology Developers |
Database Developer |
Develop databases, including modeling database structures, importing database structures from an existing database and generating DDL for rapidly creating databases from a model. |
Database Developers |