Building IERs

You wake up Saturday morning and your wife tells you she wants the bathroom painted. She leaves to go out of town to visit her folks and you go to the hardware store, pick up a couple of gallons of Hunter Green paint, your favorite color, and get to work. You’re complete by the time she gets home and are feeling very good about what you’ve accomplished in such a very short time. She sees the product and is speechless. Not because of the great job you’ve done but because she really wanted it pink, to go with everything else that’s already in the bathroom. You didn’t have to ask questions, you got right to the task of completing the assignment – paint the bathroom - and it turned out wrong. You didn’t have the information you needed, mainly because you didn’t ask, and now you’ve got to do the job all over again.

After having read the changes to 3170 that defined the JCIDS, one thing immediately jumps out to the document writers - I don't have to do an Information Exchange Requirements (IER) Matrix (OV-3) ever again! Although there is no requirement per the 3170 to include the IER matrix in any of your documents, not going through the analysis and putting together an OV-3 will:

  1. hinder the ability to see ALL of the requirements
  2. make development of an SV-6, a required document for both the CDD and CPD, very difficult


What are the Recommended Fields?

OV-1/SV-1

What are the Recommended Fields?
Here's a detailed explanation of the fields you need. . more...

OV-1/SV-1
The contents and purpose for the Operational View and System View. more...

Architecture Framework

SISSU (soon)

Information Assurance (soon)

References

Links

MODAF

Defense Link

Wiki Enterprise Architecture Framework

Architecture Framework Forum

ISO 15704

     
page last modified August 5, 2007