Requirements Do Not Have to Be Perfect

 

                                                                  

First Plan Should Get You Close

 

Requirements are where you plan to go, what you plan to do and how you plan to do it. If your plan is perfect, you will get there as you planned. If not, adjustments may be needed along the way.

 

Minor adjustments are OK. A minor adjustment should not have to be made twice. Major adjustments are not OK. If major, the initial plan was not good enough.

 

When is a Change Minor or Major?

 

A change to one level should not ripple above its parent level. Minor changes are those which do not. Major changes are those which do.

 

These same rules apply to work breakdown structures (WBSs).Development Process is Top-Down

 

Development is an iterative process. The amount of iteration can be minimized by using appropriate top-down and validation techniques.

 

Higher-level requirements must be validated and released before they can be used to derive subordinate-level requirements.

 

If a subordinate-level design or process cannot achieve a parent-level requirement, one or both must be changed.

 

A controlled validation, release and change cycle must exist at each level. It is preferable that each cycle at each level be highly robust.

 

 

           

                          

Institute of Configuration Management Scottsdale, AZ 85261-5656 Tel: (480) 998-8600 Fax: (480) 998-8923 Email: info@icmhq.com