Potential EUP Artifacts

Follow @scottwambler on Twitter!

By Michael Vizdos and Scott W. Ambler

The major artifacts of the Enterprise Unified ProcessTM (EUP) are summarized below.

NOTE: This article will soon be updated to reflect the evolution of EUP to be based on Disciplined Agile Delivery (DAD). Please stay tuned.

Artifact Description

Something that requires immediate attention while monitoring systems in a production environment.


Communicates the availability of an asset.

Asset criteria

Defines the requirements that an existing asset must conform to for you to consider generalizing it into a reusable asset.

Asset rework plan

Defines your approach to generalizing an existing asset to make it reusable.


This is the media where data is stored for restoration purposes.

Benefits Package

Supplementary advantages to people within your organization.

Candidate Architecture

A potential technology or concept that you may want to integrate into your enterprise architecture.

Configured Asset

An asset created for a specific use.


A legally binding document between two entities.

Defect report

A type of change request that defines a system-related problem; that is, the system is not working the way that it is supposed to.

Development case

Defines the particular process tailoring that will be used on a specific project.

Disaster Recovery Plan (DRP)

Defines the steps you will follow to get your critical systems back up and running in case something catastrophic happens.

Education Plan

Defines the strategy to train and mentor an individual.

Enhancement Request

A type of change request describing an addition or modification to one or more systems.

Enterprise Architecture Model

Depicts the frameworks, networks, deployment configurations, supporting technical infrastructure, and domain infrastructure for an organization.

Enterprise Business Architecture Requirements

Non-technical requirements applicable to the enterprise architecture.

Enterprise Business Glossary

Defines a common vocabulary within your organization.

Enterprise Business Process Model

Captures the fundamental business processes, external entities (customers, suppliers, partners, or competitors), and the major workflows between them.

Enterprise Business Rules Specification

The definition of the constraints that influence or guide the everyday workings of an organization.

Enterprise Computing Infrastructure Plan

This documents the infrastructure plans, including both hardware and networks.

Enterprise Data Guidance

Describes standards and guidelines pertaining to data-oriented development issues. Includes, but is not limited to, logical naming conventions, standard logical data definitions, and physical naming conventions.

Enterprise Data Model

A detailed model depicting the major business entities, their attributes, and their relationships applicable across your organization.

Enterprise Development Guidance

Standards and guidelines applicable to all systems within your organization.

Enterprise Domain Model

A high-level representation of the business entities and their relationships within your organization.

Enterprise Facilities Guidance

Standards and guidelines for facilities, which address building design and usage issues.

Enterprise Facilities Plan

Describes the plans for the facilities within the organization.

Enterprise Goals and Targets

Used to develop organizational strategies and vision and to gauge the effectiveness of your organization.

Enterprise Intellectual Property (IP)

This includes patents, trademarks, service marks, Copyrights, and trade secrets that your organization owns and maintains.

Enterprise Licenses

These are licenses to software products that your organization utilizes across departments.

Enterprise Mission Statement

A statement of the strategies to be followed to achieve the enterprise vision.

Enterprise Network and Hardware Guidance

Standards and guidelines for networks and hardware that address common configurations, common protocols, and so on.

Enterprise Risk List

Involves identifying and assessing the risks to the enterprise at both a program and portfolio level; this is sometimes referred to as risk discovery.

Enterprise Risk Management Plan

Lists the enterprise risks and the associated risk mitigation strategies.

Enterprise Security Guidance

Standards and guidelines for security that address both IT and physical security protocols.

Enterprise Security Plan

Describes the plan for use of both physical and IT security.

Enterprise Technical Requirements

Requirements to which all IT assets within your organization must conform.

Enterprise Vision

A statement of the primary goal(s) of an organization.

Existing Processes

These are the existing processes within your organization.

Federal Regulations

Rules that your organization must comply with on a federal level.

Hot Fix

A fix/patch addressing one or more defects, which is inserted directly into a production environment by a support developer.

Individual Career Plan

Describes the career plan, including goals and educational needs, for an individual IT professional.

Industry Guidance

This includes industry best practices and commonly used standards and guidelines.

IT Process

Addresses the full IT lifecycle, defining procedures, templates, and examples for software development, operations and support, and cross-system issues such as enterprise architecture and portfolio management.

Legacy Data Source Documentation

This includes information about your enterprise data model.

Long Term Succession Plan

Defines how the organization will fill both technical and business positions within the organizations as people leave the team.

Modeling Guidance

Describes techniques such as naming conventions, layout style guidelines, and even notation style guidelines for how models should be organized and documented.

Needs Assessment

A document describing needs in an organization.

Organization Assessment

A description of the organization including structure, culture, competencies, and skills.

Organization Model

Describes your organizational units (teams, groups, divisions, and so on), the primary positions, the senior people, the roles and responsibilities that the people and organizational units fulfill, and the relationships (potentially including both reporting and flow of control) between them all.

Organizational-level Development Case

A development case with a wider scope; it describes process tailorings that are applicable across many projects.

Portfolio Plan

Describes project and program priorities that are required to fulfill the overall business goals of your organization.


A collection of programs, projects, and systems for your organization to meet its business objectives.

Position Definitions

Describes the roles and responsibilities for the different positions within your organization.

Process Implementation Plan

The plan to roll out a process within your organization.

Process Vision

Describes how you would like to see a process implemented within your organization.

Program Definition

Defines a collection of related projects or systems.

Program Plan

Prioritizes projects within the program.

Project Proposal

A document to identity a possible new project for the organization.

Published Asset

A robust asset that is made publicly available within your organization for potential reuse.

Reference architecture

An architectural approach designed and proven for use in a particular domain, together with supporting artifacts to enable their use; it often provides the basis for creating an application architecture.

Request for Information (RFI)

Issued to vendors to request interest and availability for a contract.

Request for Proposal (RFP)

An announcement to solicit proposals from vendors in order to address a specific organizational need.

Reuse guidance

Defines techniques and guidelines for succeeding at reuse.

Reuse measurement plan

Defines the measurement goals and related metrics to be collected regarding your reuse program.

Reuse program plan

Encompasses all of the information required to manage your reuse program, including staffing requirements, the vision and projected milestones, and a description of how your team intends to support project teams.

Robust asset

A well-documented asset that is generalized beyond the needs of a single project; it is thoroughly tested and has several examples to show how to work with it.

Service Pack

A fix to a defect inserted directly into a production environment by a support developer using different types of media.

Staff Review

A document that reflects the current staffing levels within your organization.

Staffing Forecast

A plan to fulfill the human resource requirements of your organization; this can include a combination of full-time employees and contractors.

System Operations Plan

Describes the approach for operating systems in a production environment. Includes contact personnel, the operations SLA, system operating procedures, and backup and restore procedures.

System Support Plan

Describes the approach for supporting systems in a production environment. Includes how support will be provided, system contact personnel, defect reporting and change request strategy, the support service level agreement (SLA), and how to deliver fixes outside a normal production release.


A working software-based product in a production environment.

Trouble ticket

An issue from an end user about the system that can either become an enhancement request or defect report.

Usage Reports

A summary of system logs produced during the normal monitoring of a production system.