1 / 6

CLR 252 Developing Requirements

CLR 252 Developing Requirements. Greg Prothero. Lesson #1: Requirements Foundation. User Needs and Types of Requirements. Evolutionary Acquisition. Source : DoDI 5000.02; Dec 2008. Evolutionary acquisition is the preferred DoD strategy for rapid acquisition of mature

tejano
Télécharger la présentation

CLR 252 Developing Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CLR 252Developing Requirements Greg Prothero

  2. Lesson #1: Requirements Foundation User Needs and Types of Requirements

  3. Evolutionary Acquisition Source: DoDI 5000.02; Dec 2008 Evolutionary acquisition is the preferred DoD strategy for rapid acquisition of mature technology for the user. An evolutionary approach delivers capability in increments, recognizing, up front, the need for future capability improvements. The objective is to balance needs and available capability with resources, and to put capability into the hands of the user quickly. The success of the strategy depends on phased definition of capability needs and system requirements, and the maturation of technologies that lead to disciplined development and production of systems that provide increasing capability over time.

  4. No spirals! Evolutionary Acquisition From two processes… To one process… • Capability delivered in increments, recognizing up front need for future capability improvements • Each increment: • depends on mature technology • is a militarily useful and supportable operational capability • Successive Technology Development Phases may be needed to mature technology for multiple increments • Incremental Development: End-state is known; requirements met over time in several increments • Spiral Development: End-state is not known; requirements for increments dependent upon technology maturation and user feedback.

  5. Evolutionary Acquisition • Developmental Approach • Evolutionary acquisition requires collaboration among the user, tester, and developer. In • this process, several increments meet a needed operational capability over time. Developing each increment depends on available mature technology. • Technology development preceding the initiation of an increment shall continue until the program achieves the required level of maturity and produces either the system or key system elements. • Successive Technology Development Phases may be necessary to mature technology for multiple development increments. • Source: DoDI 5000.02; Dec 2008 • .

  6. Evolutionary Acquisition Source: DoDI 5000.02; Dec 2008 . • Each increment is a militarily useful and supportable operational capability that DoD can develop, produce, deploy, and sustain. • The user will set the threshold and objective values for each increment. • Block upgrades, pre-planned product improvement, and similar efforts that provide a significant increase in operational capability and meet an acquisition category threshold specified in this document shall be managed as separate increments under DoDI 5000.02.

More Related