Embed Size (px)
DESCRIPTION
Requirements Bucket Req’s Design Impl. Test Install & & Integ. Operate Increment Planning standard waterfall Evolutionary Development risk reduction prototyping Review current Req’s Bucket; categorize items for risk and priority Highest priority with acceptable risk, assign to current increment “Medium” priority with acceptable risk, tentatively assign to some future increment Low priority, low risk; leave in Req’s Bucket for future consideration Unacceptable risk, assign to prototyping Review current Req’s Bucket; categorize items for risk and priority Highest priority with acceptable risk, assign to current increment “Medium” priority with acceptable risk, tentatively assign to some future increment Low priority, low risk; leave in Req’s Bucket for future consideration Unacceptable risk, assign to prototyping increment 0 (a.k.a. MEC) increment 1 increment 2 increment 3 and so on
Citation preview
MSJ-1
Simplified View of the Simplified View of the Standard WaterfallStandard Waterfall
Test &IntegrationDesign Implement
Install &OperateRequirements
MSJ-2
““Pure” Incremental DevelopmentPure” Incremental DevelopmentAlso known (more in the military than the civilian world) as PPPI, Pre-Planned Program Improvement
Design Impl. T & IReq’s
Design Impl. T & IReq’s
Design Impl. T & IReq’s
and so on
ProjectPlanning
increment 0 aka “Core System”
increment 1
Increment 2
• High level requirements or objectives or capabilities are assigned to increments at the start of the project
• Each increment is a complete waterfall in and of itself, no planning for feedback from one increment to the next
• Increment 0 is often the biggest and hardest - a basic operational system is usually bigger than any functional enhancement
• Probably have to build/integrate OS, DBMS, networking package, etc• Probably have to develop pretty complete HMI
RequiremeRequirements nts BucketBucket
Req’s Design Impl. Test Install & & Integ. Operate
Increment Planning
standard waterfallstandard waterfall
Evolutionary Development
risk reduction prototyping
Review current Req’s Bucket; categorize items for risk and priority• Highest priority with acceptable risk, assign to current increment• “Medium” priority with acceptable risk, tentatively assign to some
future increment• Low priority, low risk; leave in Req’s Bucket for future consideration• Unacceptable risk, assign to prototyping
increment 0(a.k.a. MEC)
increment 1
increment 2
increment 3
and so on
MSJ-4
The The MinimumMinimum Essential Core (MEC) Essential Core (MEC)
• Imperative to keep increment 0 as small and simple as possible
• Feedback process from real users can’t start until MEC is fielded
• Basic philosophy – a feature or capability doesn’t go into increment 0 unless the customer is willing to say, “we won’t pay for the development without this” or “there’s no point in delivering such a system, it can’t be used by anyone for anything useful”
