Work Product Descriptor (Artifact): Project Requirement

The Project Charter or Requirement defines the "system" to be architected and built. It outlines the roles and responsibilities of the participants, including stakeholders. It defines the project objectives and the authorities of the project manager. It is produced outside of UAM but is an important input into its processes.

The Project Charter defines the "system" to be architected and built. It is the project description, project charter, or project definition and is an input to many UAM based IT Architecture activities and tasks. It is created by business and other (planning) experts within the enterprise. It includes descriptions of any issues or problems (business & technical) that are to be addressed by the project. A Project Charter is also used when updating a system based upon a Change Request—it documents the plan for the project that implements the change. See the overview of inputs here: Inputs.

If the "system" to be architected is the Enterprise, a Business Line, or Business Unit then this document defines the objectives of the IT architecture project.

There is an extensive project process defined within enterprises. This involves the creation and review of a number of artifacts that the IT architect needs to review, as summarized in the figure below.

IT architecture and project deliverables and Gate reviews

See: Activity: Enterprise Planning and Milestone: Gate 3.