INFO 210

Aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process using the bare minimum requirements

The firm analyzes its end user business requirements and refines project goals into defined functions and operations of the intended system

The specific business requests the system must meet to be successful

Responsible for approving or rejecting all change requests

Offers procedures and policies managers can use to help manage change during system development

Includes a collection of procedures to document a change request and identifies the expected impact associated with the change

Estimates the shortest path through the project ensuring all critical tasks are completed from start to finish

A logical relationship that exists between the project tasks, or between a project task and a milestone

Establishes descriptions of the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation

Takes all the detailed design documents from the design phase and transforms them into the actual system

The person or group who provides the financial resources for the project

Breaks a project into four phases, and developers cannot continue to the next phase until the previous phase is complete