A

Ambassador User (KEY)

The ambassador user participates in workshops. This project role is empowered by the project
sponsor to refine and prioritize requirements. The ambassador user provides information about their
business objectives and the ways in which their units operate and responds to events in order to
achieve those objectives. The ambassador user describes the problems they face and requirements
for the computer system. This project role writes the initial user guide.

Application/Product Specialist (APS)

The application/product specialist provides knowledge and guidance regarding application and other
product functionality and implementation strategies. This project role also supports and provides
interpretation for tools, templates and methods.
Back to Top

B
Bid Manager (BM)
The bid manager prepares the bid, negotiation, and award. This project role assists in the hand over
of materials and information accumulated during the bid to the project manager at the start of the
project.

Business Analyst (BA)

The business analyst should be familiar with the business area that the system covers and the
terminology and practices.
The business analyst performs many activities that define the scope of the project. They examine the
client's business and define what the system should do. They obtain information from existing
documentation, when available. The business analyst identifies interviewees who might be
representative client staff, management, and technical support staff. The business analyst obtains
information by conducting interviews, working sessions, and site visits. These analysis activities
determine the technical, interfacing, and operational requirements and constraints.
In most cases, the business analyst is responsible for modeling the client's existing business
processes and capturing relevant process data.

Business Line Manager (BLM)

The business line manager participates in interviews and working sessions providing information
about business objectives and ways in which the units operate and respond to events in order to
achieve those objectives. The business line manager hosts site visits with staff in order to collect
information. Additionally, this project role is responsible for allocating staff time to provide detailed
information about the day-to-day business. Also, this project role describes problems the business
unit faces and requirements for the computer system.The business line manager should review the
content of the analysis documentation to make sure it accurately describes the business and
requirements. The business line manager role should be filled by someone who will manage one of
the business units that uses the system.
Back to Top

C
Change Management Specialist (CMS)
The change management specialist provides the client with expertise in the human and organizational
facets of change management. Change management specialists support the Organizational Change
Management (OCM) process by identifying and mitigating risks, generating change momentum,
fostering effective communication, and supporting end-user acceptance. The change management
specialist works directly with executives to gain their commitment and put in place a project
governance model.
Depending on your project (e.g., large, complex, etc.), various change management specialists
focused in specific areas may be involved (e.g., communication, leadership, human performance,
organization development, and risk assessment).
In many cases, the change management specialist role may be fulfilled by a consultant with advanced
facilitation skills and the ability to relate and effectively communicate with senior executives.

Client Data Administrator (CDA)

The client data administrator ensures that data structures and data quality meet the needs of the
business in the context of the Information Systems Strategy. The data administrator also evaluates
team findings regarding legacy data quality and ensures that corrective action is taken where legacy
data is inadequate.

Client Executive (CE)

The client executive participates in the strategic decisions regarding implementation and project
strategy and defines business performance expectations and metrics. The client executive also
appoints steering committee members and is involved in measurement of business results.

Client Project Manager (CPM)

The client project manager is responsible for the daily management of the client's contractual
commitments to the project. This project role must understand the client's business objectives for the
project to form the basis for resolving problems, conflicts of interest, and making compromises.The
client project manager obtains physical resources such as space accommodation, office equipment,
computer equipment, and materials. The client project manager assists in the availability of users and
endeavors to gain user commitment. Additionally, this project role assists in the allocation of client
time to the project. The client project manager introduces the consulting staff to the other client staff.
This project role monitors the project's performance, progress against milestones, appropriateness of
work, quality of work, and seeks to resolve any problems with work or relationships between the
development and business staff. The client project manager assists in obtaining user review and sign
off of work products. This role usually performs intermediate and phase-end acceptance.

Client Project Sponsor (CPS)

The client project sponsor controls the budget and finances the project. This project role is usually a
member of senior management. On large, cross-functional projects the project sponsor may be a
board member. This project role must have a clear understanding of the project objectives,
particularly concerning delivery of the business benefits. The project sponsor empowers the key
users to refine and prioritize requirements. The project sponsor is the ultimate arbiter on conflicting
business requirements and scope changes. The project sponsor makes sure the project is delivered
on time and within budget. The project sponsor is responsible for ensuring other members of the
management share commitment to the project. This project role may provide the resources,
particularly staff time, required to make the project a success. The project sponsor usually performs
the final approval on the recommendation of the verification coordinator, internal auditor and data
administrator.

Client Staff Member (CSM)

The client staff member reports directly to either the project manager or client project manager.This

project role may be responsible for technical support of the client's systems. The client staff member
may provide information about existing systems with which the new system is to interface or replace.
This project role provides information about any IS standards with which the project must comply,
supports the business' software systems, and takes over support of the system during production.
Finally, a client staff member may participate in training programs for the system initially as
consumers and later, possibly as providers.

Consulting Business Manager (CBM)

The consulting business manager is the practice manager in the consultant's organization responsible
for the successful execution of the project. This role manages the practice which makes the
consulting staff available and coordinates resources needed by the project with other practices. The
consulting business manager represents the consulting organization in the contractual agreement with
the client and resolves business issues with the project sponsor. The consulting business manager
participates in project reviews with the client as well as internal practice reviews of project progress.
Back to Top

D
Database Administrator (DBA)
The database administrator installs and configures database software for the development
environment; creates the various databases required during the development lifecycle (for example,
the data dictionary, unit testing, system testing, training); and maintains database access controls.
Additionally, this project role provides consultation on performance; monitors growth and
fragmentation of the development database; and provides database backup and recovery.
Depending on your project (e.g., large, complex, etc.), various database administrators focused in
specific areas may be involved (e.g., development database administrator and production database
administrator).
During system development, the development database administrator works closely with the system
administrator. This person is responsible for installing and configuring database software for the
development environment, creating the various databases required during the development lifecycle
(for example, the data dictionary, unit testing, system testing, training), and for maintaining database
access controls. This role also provides consultation on performance, and is responsible for
monitoring growth and fragmentation of the development database, and for ensuring database backup
and recovery. The development database administrator should involve the production database
administrator as soon as this person has been identified, and ensure the transfer of the practical skills
needed to manage the production database. This does not replace the need for DBA training and
certification, but provides specific guidance on monitoring of the new system during transition into
production.
Once the system is ready for production, the production database administrator installs and
configures the production database and maintains database access controls. After the system "go
live" this person provides consultation on performance, monitors growth and fragmentation of the
production database, and ensures database backup and recovery.

Database Designer (DD)

The database designer produces the Logical and Physical Database Designs. This project role
reviews the module designs to provide efficient access to the database.The database designer must
understand how to translate application logic into a System Data Model and have a thorough
understanding of the System Data Model. The database designer is responsible for producing the
System Data Model, the Logical Database Design, and the Physical Database Design.The database
designer reviews the application design to check database access efficiency. Additionally, an
understanding of the technical architecture and functionality of the system is required so that trade-

offs in the design can be made where different functions place conflicting requirements on the
database. The database designer may make design suggestions in order to mitigate conflicts
between the application design and the technical requirements.

Designer (DES)
The designer defines and maintains the responsibilities, attributes, relationships and special
requirements of the classes making sure that each class fulfills its requirements. The designer is also
responsible for the analysis of packages within which the classes are maintained. There may be
several designers with varying areas of expertise depending on the size and needs of the project
(e.g., object designer, SOA designer), each of which may be responsible for certain classes and
packages assigned to them.
Depending on your project (e.g., large, complex, etc.), various Designers focused in specific areas
may be involved (e.g., object designer, module designer, user interface designer).
If your project involves Object Oriented (OO) design, you may require an object designer. The object
designer is responsible for translating a subsystem analysis object model into a subsystem design
object model. The object designer takes the technical architecture and technical requirements and
fashions a design object model that meets these requirements.
The module designer produces the application and module designs. This person communicates
closely with the database designer to make sure the database design meets the data requirements of
the module functionality and module access data efficiently. The module designer also produces
module and link test plans. During the various testing activities and the Production phase, this person
diagnoses faults and determines corrections.The module designer understands the requirements from
the business analysis and how to meet these requirements using the technical and system
architectures and System Data Model. The module designer is responsible for production of the enduser layer, query, and report module designs. The module designer also designs the version control
module for the data access component of the data warehouse and technical specifications for data,
governor limits, and user project role access. The module designer communicates closely with the
database designer to make sure the database design meets the data requirements of the module
functionality and that the modules access data efficiently. The module designer also produces module
and link test plans. During the various testing activities and the production phase, this person
diagnoses faults and determines corrections. The module designer must understand the data access
requirements and how to meet these requirements using the technical and data warehouse
architectures and data warehouse, data mart, and metadata data models.The module designer
understands both the application model and the legacy system requirements. The module designer
may be responsible for creating a seamless architecture for the transfer of data to and from the legacy
system. The module designer may translate a subsystem analysis object model into a subsystem
design object model. The module designer takes the technical architecture and technical
requirements and fashions a design object model.
User-interface designers are responsible for visually shaping the user interface. They are responsible
for developing the user interface prototype for the use cases assigned to them.

Developer (DV)
The developer understands the requirements from the business analysis and how to meet these
requirements using the Technical Architecture and Data Model.The developer produces application
and module designs and generation of modules. This project role interfaces closely with the lead
system developer to make sure the database design meets the data requirements of the module
functionality and module access data efficiently. The developer may create the object structure, the
database object logic, and the test scripts for the database. The developer produces working code
that meets the module specifications and diagnoses and corrects faults found by tests. The
programmer must have a thorough understanding of the specifications for the modules to produce the
appropriate code.The developer also produces partition integration test plans and performs testing of
partitions and system. During the various testing activities and the production phase, this project role
diagnoses faults and determines corrections. Developers produce the initial versions of online help
text, user reference, and technical reference documents. There may be several developers with

varying areas of expertise depending on the size and needs of the project, for example, a J2EE
developer or a SOA developer.
Depending on your project (e.g., large, complex, etc.), various Developers focused in specific areas
may be involved (e.g., Lead Developer, Lead System Developer, J2EE Developer).
A lead application developer may be assigned to coordinate the development efforts across functional
areas of the application. The lead application developer is responsible for examining the client's
business and defining what the system should do. This person obtains information by participating in
workshops and may also obtain information from existing documentation. The lead application
developer must understand the business objectives and requirements and documents the analysis
and creates the high-level business models. The lead application developer also determines the
technical, interfacing and operational requirements and constraints and conducts reviews of their
findings with client management and their staff.It is preferable that an lead application developer
already be familiar with the business area that the system is to cover and generally understands its
terminology and practices. The lead application developer leads the application development.
The lead system developer is a cross-team designation, responsible for defining the system and
technical architectures, including the major software components of the system and their interfaces,
and the hardware configuration and software foundation. The lead system developer is generally the
senior or lead technical designer on the project. The lead system developer must understand the
business and technical requirements for the system. The lead system developer is responsible for
producing the Logical and Physical Database Designs. This person also reviews the module designs
to ensure efficient access to the database. The lead system developer must have a thorough
understanding of the Data Model and the technical architecture and functionality of the system. The
lead system developer makes tradeoffs in the design where different functions place conflicting
requirements on the database. The lead system developer is responsible for the production and
maintenance of the Capacity Plan and for reviewing all aspects of the design to ensure that it
performs within any capacity constraints. This person is also responsible for performing any
benchmarking exercises required to measure the performance of hardware or software. The lead
system developer writes the initial operations guide.
If your project involves J2EE architecture, you may require a J2EE developer. J2EE developers create
small or large application that will be deployed in a heterogeneous or Internet environments. They are
able to use object-oriented design concepts, model J2EE components using UML, understand Unified
Software Development Process principles, and use design-by-contract technique, to effectively design
and build component-based applications. They successfully perform quality assurance tasks, such
software inspections and code review, on work products produced by other team members. They are
familiar with Java technology and Oracle's Java Products at a technical level. They utilize Java
component model, such JavaBeans, Enterprise Java Beans, Web Beans, and BC4J, to construct
J2EE applications from new and existing components. They are familiar with Oracle's other Java
products and frameworks, such JDeveloper, 9iAS MVC Framework for J2EE, BC4J, and UIX, and
rapid application development tools such as JHeadstart.
The developer may also be called upon as a tool specialist in order to provide knowledge and
guidance regarding specific tool functionality. This designation also supports and provides
interpretation for the tool capabilities and customization and design of the end-user layer.
Back to Top

E
Enterprise Architect (EA) [Envision-only role]
The enterprise architect is responsible for the process of translating the business vision and strategy
into an effective enterprise-level change, restricted to the subject under discussion. This is done by

creating, communicating and improving the key principles and models that describe the enterprise's
future state in order to enable its evolution through a feasible roadmap.
The enterprise architect provides enterprise-tailored advice on the application and technology product
portfolio under discussion to enterprise-level decision makers in order to help them incrementally
transform the Information Systems and meet the business objectives. They oversee the collaborative
process of working with enterprise-level decision makers to realize the full value of their investment in
acquired products and services. While doing so, the enterprise architect develops a long-term trusted
business and technical relationship with the decision makers.
The enterprise architect brings together the people, processes, information and technology of the
enterprise, and maps their relationships to one another and to the external environment. An enterprise
architect works across multiple solution domains and is responsible for bringing elements from those
domains together into a feasible enterprise-level solution. The enterprise architect works with solution
architects to develop a consistent actionable future state through guidance and governance at the
program level.
Depending on the subject under discussion, an enterprise architect with expertise and experience in
Business Architecture may be involved. These enterprise architects are referred to as business
architects (BAR).
There is usually a client counterpart enterprise architect role.
Back to Top

F
Back to Top

G
Back to Top

H
Healthcheck Specialist
The healthcheck specialist is part of the consulting organization but should not be a member of the
project team. The healthcheck specialist is usually a member of the quality assurance organization.
The healthcheck specialist conducts the Project Healthcheck, which is designed to ensure compliance
with the organization's policies and procedures and validates the overall "health" of the project. The
purpose of the healthcheck is to review key aspects of a project and provide guidance to the project
manager and project team in order to correct any noted deficiencies.
Back to Top

Internal Auditor (AU)

The internal auditor provides requirements for the system to make sure it complies with the security
and auditing practices of the client. The internal auditor may also be responsible for specifying
acceptance tests to make sure these requirements have been met.

IS Operations Staff (OS)

The IS operations staff operates the existing computer systems and new systems and provides
information on operational requirements. This project role acts as a consumer of the training
program.

IS Support Staff (SS)

IS support staff is responsible for technical support of the client's systems. This person provides
information about any IS standards with which the project must comply, supports the business'
software systems, and takes over support of the system during production. The IS support staff
participates in any training program for the system initially as consumers and later, possibly as
providers. Finally, the IS support staff provides information about existing systems with which the new
system is to interface or replace. This project role may be filled with members of the client's
Information Systems organization, who work with or work as part of the project team.
Back to Top

J
Back to Top

K
Back to Top

L
Back to Top

M
Back to Top

N
Network Engineer (NE)
The network engineer provides network consultation and impact assessment to the project team. The
network engineer works with the development team to determine and implement the network
hardware requirements of the application. The requirements include designing and implementing

components such as cabling, terminals, bridges, and routes.The network engineer also acquires tools
and establishes procedures to monitor network components to ensure sufficient capacity. This project
role also consults with the development team to determine and implement any foreign host access
requirements.
Back to Top

O
Back to Top

P
Program Manager (PGM)
The program manager role is separate and distinct from that of the project manager. Program
Management is focused on getting projects to work effectively together so that they achieve a
common objective. The program manager works with each project manager to provide support and
guidance on the individual projects and ensure the work effort achieves the necessary business and
IT strategy objectives. The program manager must provide the project members with program
standards, organization, ability to have integration across projects and most importantly, the ability to
have shared learning and reuse. Coupled with providing project team members with the ability for
team and deliverable integration, the program manager must provide any infrastructure needed to
build, deploy and maintain common business systems.

Project Administrator (PAD)

The project administrator is a staff role responsible for assisting the project manager in the day-to-day
management of the project, by performing routine or repetitive activities, tasks or task steps. The
project administrator prepares or maintains reports, records, logs, and other written communications;
collects routine data from project leaders; and distributes project calendars, meeting agendas and
meeting minutes. Specific duties are delegated by the project manger, but will normally include and
are not limited to some or all of the following:

Ensure that phase management sub-processes are coordinated and executed effectively.

Maintain the Project Workplan and Finance Plan.

Monitor and perform analysis of risks, issues, and problems for trends requiring project
manager corrective action.

Perform routine coordination and communication functions within the project organization.

Maintain the Project Library.

Orient new project members to the project environment, policies, and procedures.

Coordinate with administrators in client and subcontractor organizations.

Prepare project progress reports.

Record and distribute minutes, decisions, and actions from management meetings.

Prepare correspondence from the project management to external organizations.

Prepare and maintain equipment records.

Maintain information on project staff such as grade qualifications, training, parent business
unit or subcontractors, telephone/address, project assignment history, etc.

For applications implementation projects, the project administrator also performs work product and
template version management, gathers and checks out work products, assigns document names and
records new documents into the library. This project role also provides some advice regarding process
integration, and provides work product status. Again, specific duties are delegated by the project
manger, but will normally include and are not limited to some or all of the following:

Establish project baselines and determining the content of project releases.

Establish change control so that no unauthorized changes are made to a project baseline.

Develop, document, and implement Configuration Management plans and procedures, and
enforce Configuration Management procedures across all project processes.

Establish the Configuration Management Repository and assist in the maintenance and
protection against damage or loss.

Verify that the standards and procedures that have been defined for the project in the Project
Management Plan are implemented.

Verify and track that quality reviews and quality audits are conducted as required.

On large projects, this role may be performed by more than one person or a by project office staff. In
addition, on large projects, there may be specialized project administrators, e.g., a configuration
management project administrator, etc.

Project Manager (PM)

The project manager represents the project to both the business and IS management. This project
role is ultimately held responsible for the success or failure of the project. The project manager must
understand the project business objectives and have a clear vision of how to achieve those
objectives. The project manager must resolve the conflict among the differing objectives of the
various parties to the project. The project manager primarily faces outwards from the project and
handles political conflicts and issues and makes sure they do not impede the project. The project
manager agrees on the scope of the project with the client, makes sure the implementation remains
within the agreed upon scope, and guards against scope creep. The project manager should review
major work products - particularly those from the earlier phases of the project. The project manager is
responsible for comparing the project planning, resourcing, monitoring, and reporting progress against
the plan. This project role obtains any physical resources required for the project, recruits staff, and, if
necessary, dismisses staff. The project manager is responsible for ensuring that activities are
performed in accordance with the Project Management Plan. Internal responsibilities of the project
manager should be delegated to subordinate team leaders, as documented in the Project
Management Plan. In addition, projects may use specialized managers that report to the project
manager, for example, configuration managers, quality managers, etc.

If you are using a Scrum approach, read the Managing an OUM Project using Scrum technique. Use
this link to access the role-specific guidance.

Project Sponsor (PS)

The (consulting) project sponsor controls the consulting budget and finances the project. This role is
usually a senior management member. This role must have a clear understanding of the project
objectives, particularly concerning delivery of the business benefits. The project sponsor is the
ultimate arbiter on conflicting business requirements and scope changes with the client. The project
sponsor ensures the project is delivered on time and within budget.
Back to Top

Q
Quality Auditor (QA)
The quality auditor conducts quality audits of the project to include a review of the Project
Management Plan. This project role should be filled by a project role independent of the project staff
in the consulting organization. The quality auditor needs training in the audit process. This project
role prepares for, conducts, and reports on the quality audit or audits undertaken, following up on any
actions raised.In the case of a data warehouse project, the quality auditor monitors the data integrity
and quality by auditing the processes used to acquire and transform the source data. This project role
verifies that the extracted and transformed data are in agreement with data considered accurate by
the client. The quality auditor works with the client to resolve incompatibilities between source
systems and the warehouse. The quality auditor also establishes the plans for data cleansing and
evaluates and influences the selection of data cleansing tools.

Quality Manager (QM)

The quality manager, with guidance from the project manager, plans and prescribes all matters
affecting quality of a project. This project role makes sure that the specific quality requirements
defined in the contract and Project Management Plan are achieved. The quality manager also makes
sure the standards and procedures which have been defined for the project in the Quality
Management Plan are implemented and quality reviews and quality audits are conducted as required.
If your project does not have a quality manager, the project manager is responsible for performing
these duties.
Back to Top

R
Back to Top

S
Solution Architect (SOLA) [Envision-only role]
The solution architect is responsible for developing and presenting a solution architecture that
addresses domain-specific issues and concerns, keeping a keen eye on the enterprise architecture,
principles and roadmap. Examples of such domains can be customer relationship management (in the
case of Application Architecture), customer data management (in the case of Information Architecture)
and a SOA Reference Architecture (in the case of Technical Architecture).

The solution architect proposes specific solutions that fit within the enterprises business environment
and business objectives and can be shown to address the business problems and exploit
opportunities. Through the discovery process, the solution architect is able to understand business
drivers and current IT environment.
The solution architect evaluates the solution's feasibility and mitigates risk by leveraging a network of
subject matter experts in the adjacent domains, as well as (other) specialists in the same domain. The
solution architect is also capable of proposing a roadmap to realize the proposed solution. The
solution architect is deployed operationally in either a holistic manner across multiple business
domains utilizing their broad knowledge of a specific solution portfolio to identify the components
required to construct the most appropriate solution per domain, or within a specific domain utilizing
their deep specialization to ensure maximum benefit to the enterprise.
Depending on the domain(s) under discussion, a solution architect with expertise and experience in a
given domain may be involved. These solution architects may be referred to as application architects
(AA), information architects (IA) or technical architects (TA).
There is usually a client counterpart solution architect role.

Steering Committee Member (SCM)

The steering committee guides the overall project review, adopts the recommendations, and provides
sponsorship for implementing the changes. The steering committee includes senior management and
a consulting director. Regular meetings should be held to review progress and resolve outstanding
issues. The steering committee members are responsible for the program approach buy-in, funding,
issue resolution, and sign-off.

System Administrator (SAD)

The system administrator is responsible for administering a development system. This project role's
responsibilities include ensuring hardware is correctly configured; installing, configuring, and
maintaining operating and development software; and ensuring daily backups of the system are
performed. The system administrator designs and maintains the system's security; for example,
establishing system accounts. The system administrator provides first-line support for development
system problems and makes sure faults are quickly rectified. This project role may perform the set-up
and initial maintenance of a production system or advise the client's operational staff on these tasks.
The system administrator works with the project team to optimize system performance.

System Analyst (SAN)

The system analyst is responsible for the development of the system requirements as use cases. This
includes functional and non-functional requirements (those that are tied to use cases, business
objects as well as those that apply to the system as a whole). The analyst ensures that the use case
model is complete and consistent and addresses all requirements.
The System Analyst role works to provide a bridge between the business requirements as described
in the Use Case Specifications and the technical definition of the system. In order to accomplish this
the System Analyst works closely with the Business Analyst. The System analyst identifies and
models the system scope, identifies System actors and use cases and develops the glossary. The
analyst is not responsible for detailing every single individual use case, but rather works with the
Business Analyst to look at the business use Cases and determine additional Use Cases at the
System level. System analysts assists in turning user requirements into the functional specifications
that are the blueprint for the system. They may also assist the Data Administrators in the design of the
data needed to support the functional specifications.
During a Business Intelligence project, the system analyst examines the client`s business and defines
what data and information is needed to support the requirements. In a BI Project, the analyst must
understand the business objectives, events, and drivers to document the information requirements
and create the data warehouse and data mart data models. In addition, the analyst must document

multidimensional structures and summary/aggregation requirements in order to satisfy all the

requirements.
Depending on your project (e.g., large, complex, etc.), there may be one or more system analysts
working together as a team coordinated by the System Architect.

System Architect (SA)

The system architect defines the system and technical architectures including the major software
components of the system, interfaces, and hardware configuration and software foundation. The
system architect is generally the senior or lead technical designer on the project. This project role
must understand the business and technical requirements for the system.
In the case of an application implementation, the system architect establishes the application
architecture of that system. In order to accomplish this, the application architect translates the future
vision of the business into an application and data deployment strategy. This strategy includes
decisions about centralizing or decentralizing business data and processing, identification of interface
points and specific requirements for data transfer and synchronization across the business, critical
setup of applications to support the business process mapping, strategies to support the reporting
needs of the business, and other less general requirements that may impact the architecture such as
multilingual requirements.
In the case of other types of solution implementations (e.g., security and identify management,
document management, etc.), the system architect establishes the architecture of that solution in the
context of the systems it impacts. For example, this may include a migration strategy that specifies
how these systems will leverage that particular solution.
The system architect provides input to more detailed technical design efforts such as interfaces and
custom components, to promote compatibility with the overall system architecture. The system
architect oversees the overall architecture activities. This project role reviews and approves the data
deployment strategy and decisions. This project role works very closely with the specialist to make
sure the physical layers of the architecture are consistent with, and fully support, the business and
information systems vision of the enterprise. This synergism may extend all the way from scoping and
planning the project through to the final architecture work products and client review.
The system architect also produces and maintains the Capacity Plan and reviews all aspects of the
design to make sure it performs within any capacity constraints. This project role also performs any
benchmarking exercises required to measure the performance of hardware or software. Often, on
smaller projects, this project role is undertaken by the staff performing the system architect project
role. On projects developing large systems, this project role is likely to be filled by a separate project
role who has the specialized skills required for systems sizing and capacity prediction. The system
architect is responsible for architecting the physical components of the database, hardware, and
network in support of the system's architecture, strategic technical architecture and the increment
technical architecture. In order to accomplish this, the system architect needs to design the detailed
database, hardware, and network architecture to support the system's architecture and deployment
strategy. This includes decisions about the physical distribution of processing across the network,
capacity planning of the technical infrastructure, detailed design of the layout of databases, and
identification and advisement about performance risks. The system architect oversees detailed
technical work on interface, system, data acquisition, data access, and metadata design to make
sure the detailed work is consistent with the overall technical architecture.
There may be several system architects with varying areas of expertise depending on the size and
needs of the project, for example, integration architect, J2EE architect, information architect, etc.)
Depending on your project (e.g., large, complex, etc.), various system architects focused in specific
areas may be involved (e.g., Integration Architecture, J2EE Architecture, Information Architecture). In
those cases, there typically is one lead system architect.

For projects that involve SOA and Integration, an integration architect helps with the definition of the
overall integration, participates in the definition of the strategy and design of the project, Identifies
internal and external interfaces risks and defines strategies to deal with such risks, defines different
integration mechanisms between the application and EAI, defines integration infrastructure and
concepts (eHub, pub-subscribe, synchronous, asynchronous) and provides leading practices and
guidelines for solutions related to integration.
If your project involves J2EE architecture, you may require a J2EE architect. A J2EE architect works
with project managers, system analysts, ERP/CRM application architects, ambassador users, and
DBAs to define the software architecture that will support project functional and non-functional
requirements. To do so, they are intimately familiar with J2EE technologies and products and their
relationship to other infrastructure components at a highly technical level. Also, J2EE application
architects must be well versed with object-oriented analysis and design techniques and able to model
the architecture via software architecture description models using UML.
Information architects help with the definition of the overall performance and design of the information
(data) architecture, the definition of the database-oriented auditing and logging mechanisms, and may
assist in the definition and/or review of the logical and physical database designs. Use this link to view
BI and Analytics supplemental role guidance.
All system architects must be able to work under the project's delivery and management method's
framework, mentor and lead developers and technical team leaders. They can also be asked to play
the role of software reuse enablers since they understand application assembly of server side
components as well as other specific enterprise software components within the business domain
across a multi-tier architecture. They frequently perform software architecture quality assurance tasks
such peer-reviews.
There is usually a client counterpart system architect role.
Back to Top

Team Member (TM)

The team member is any member of the project team. This role is used all project team members
regardless of their primary role, e.g., team members are responsible for accurately tracking time and
expenses, and team members participate and share views on what worked and what could be
improved for collecting lessons learned.

Technical Writer (TW)

The technical writer becomes familiar with the business and technical requirements of the system and
how the architecture, design, and modules achieve those objectives. The technical writer specifies,
produces, and edits the user, technical, and operational documentation. This project role provides
skills in language and presentation.

Tester (TE)
The tester develops and executes test script. Testers make sure test scripts are reviewed by the
appropriate business analysts prior to test execution. This project role records test results during
testing activities and documents test faults in the problem log. Testers update test scripts due to
approved change requests or software faults that were not anticipated in the original development.
When problems are resolved after re-testing, testers update the problem log.
On large or complex projects, a lead tester is often assigned to oversee the test script planning,
development, and execution activities. The lead tester reviews and approves the test scripts. This

person manages the test execution, monitors the progress of testing activities, and ensures the test
results and problems are logged. The lead tester also helps prioritize problem log entries. They
provide skills in common testing tools and in structured testing techniques.

Training Specialist (TRS)

The training specialist is an individual with expertise in training. The training specialist defines the
training requirements, prepares a training plan, produces training material, and delivers courses. The
training specialist is responsible for working with the client to develop and deliver the necessary
project team and user training.
Back to Top

U
User (USR)
The user is a member of the client`s staff who actually uses the production system. This project role
acts as a consumer of the training program and reports problems about the production system. The
users are involved in testing in the later stages of development and assist the ambassador users in
performing the pre-production validation.
Back to Top

V
Validation Coordinator (VC)
This validation coordinator validates the requirements, prototypes, results of each development
iteration, and pre-production validation.The validation coordinator is usually also one of the key users.

Visionary (VS)
The visionary promotes the new system and explains the business case to all team members and
stakeholders. This is usually a client role. The visionary may also be the project sponsor although
this is not necessary. Often the visionary obtains sponsorship at a high level in the client organization,
before the project begins.
Back to Top

W
Back to Top

XYZ
Back to Top