The tasks and deliverables presented in Volume 1 define the system lifecycle by which UCD intends to manage the development, enhancement and maintenance of information systems.
The ADM defines what deliverables are to be produced during the system development process as well as the tasks to be performed and who is to perform them. The ADM defines what should be created and what tasks are likely to be executed to create that deliverable. The ADM does not define how that deliverable is to be created.
The ADM identifies specific techniques that are to be employed in a task. The ADM does not identify the tools which are to be used to create the deliverables. It is left to the party managing the system development process to identify the specific tools which may be employed.
The ADM is not an optional process. The ADM lifecycle provides a uniform approach to managing systems development and yet provides sufficient flexibility for the developer to choose the techniques and tools best suited for a specific objective. The use of the ADM by all UCD staff is intended to ensure uniform terminology and procedures utilized in the development process.
The ADM was designed to accommodate the needs of all types of systems development efforts. The ADM lifecycle can be used for all work efforts including those which use purchased application software packages and turnkey systems, as well as those information systems developed entirely in-house.
The essentials of the ADM lifecycle will remain consistent in their application throughout UCD, regardless of project size or system solution. Minimum deliverable requirements are established for that purpose. These are the recommended deliverables.
The lifecycle contains optional or conditional deliverables to allow flexibility in the system development process. This optionality feature enables the system developer to produce only those deliverables which are appropriate to the complexity of the project. This flexibility ensures the ADM's use for both very short projects such as enhancements to existing systems as well as for major development efforts.
Beyond these standards however, the project leaders are expected to tailor the deliverables and tasks to the specific information system project. The project leaders may consolidate tasks in order to focus on producing the minimum set of deliverables permissible for the particular type of project. The intended result is the omission of inappropriate tasks and deliverables.
For example, the selected system solution may include the purchase of an application software package. In this case, some deliverables contained in the ADM lifecycle should be produced by the vendor - not UCD. Management of the development process requires assurance that the ADM recommended deliverables are present in the vendor supplied product. But, it is not cost effective that UCD reproduce those deliverables.
Section Overview : Introduction
Overview : Table of Contents