Practice: COTS Development
This practice describes a feasible process to build a solution based on pre-existing Commercial-Off-the-Shelf packages. It focuses on configuring the RUP process to evaluating, recommending, acquiring, installing, configuring, fielding and evolving Commercial-Off-The-Shelf (COTS) package solutions.
Purpose

The purpose of this practice is to discuss the following:

  1. Complications in COTS-based development and definitions of process drivers on system development.
  2. RUP for COTS Package Delivery process framework based on RUP phases, RUP iterations, EPIC principles, and RUP evolution cycles.
Main Description

This practice helps teams to build complex software systems based on pre-existing Commercial-off-the-Shelf (COTS) packages.

In this practice, we will find a list of key drivers that will have impact on COTS package delivery. These key drivers include the Four Spheres of Influences, commercial market-imposed constraints, and derived process requirements.

Based on these process drivers, this practice discusses a process framework derived from the RUP process to aim at evaluating, recommending, acquiring, installing, configuring, fielding and evolving Commercial-Off-The-Shelf (COTS) package solutions.


How to read this practice

Before reading this practice, you should familiarize yourself with the enablement materials.

Begin reading this practice by reviewing these key concepts: process drivers for COTS package delivery and RUP for COTS package delivery process framework.

Next, review the work products and tasks. When a work product or task refers to a key concept or more detailed guidance, review those elements at that time, or save the detailed reading for last.

Use templates and checklists associated with the work products to guide you as you complete and evaluate them.

Use measurements to guide you on assessing how well you are following the practice.

Relationships
Content References
Inputs