ISP Architectural Views

One the most important part of an Information Support Plan
(previously known as a C4ISP) is the Architectural Views.
The DoD Architecural Framework Document describes each veiw
in painful, painful detail.  Since the C4ISP has been
changed into the ISP, the DoD Architectural Framework is a
bit out dated.  For example it doesn't mention "ISP" and
also includes some old views that have been phased out such
as OV-3 and SV-1.  The following gives my view on some of
the views.

In my limited experience creating views is very interative
process. Meaning you create a little then your tweak and
change them as you go.

AV-1 Overview and Summary Information is a breeze if you
have all the appropriate information readily available.

Operation Views (OV)
These are fun for me because I feel like I understand
them.  OV-1, High-level Operational Concept Graphic is
one that I've had the pleasure of not having to do. 
Merely starting it was a bit of a challenge.  It is
intended to look pretty. I've seen it done affectively
with MS Word and PowerPoint.

OV-2 is Operation Node Connectivity.  As a network guy,
this is my favorite.  I use Visio for this one with
simple shapes representing the nodes or you can get
fancy and use computer Icons OV-4, Organizational
Relationship Chart is another fun easy diagram that can
be created with Visio or Word using simple shapes. 
Ov-5 is the Activity Model.  Since it is so closely
tied to SV-4, fuctional description and SV-5,
Operational Activity to System Function Traceability
Matrix, it is very, very interative and not one of my
favorites. I complete these three one after another. 
Both SV-4 and OV-5 must be completed before you do SV-5
since all the info in SV-5 comes from those two.
OV-6c, Operational Events-Trade Description requires a
very good understanding of what happens to the data
upon entering the system.  But once you have that
nailed down it is fairly straight forward.  The logical
data model, OV-7, can get a bit convoluted, I imagine. 
In it you are supposed give a visual representation of
the various domains.

System Views (SV)
The SV's can get a little gray as some of the views can
touch on things that involve your system but you have
perhaps only heard of.  For example, if your system "A"
connects with System "B" you may have to show that
connection even though you don't know much of anything
about System "B". I haven't seen SV-1 on the Teao Saic
site so I assume it has been phased out. But it deals
with Interfaces.  SV-2, System Communication Description
is very much like the example of system "A" in relation
to "B".  SV-2 shows how your system communicates/connects
with other systems.  Its almost like a birds eye veiw of
OV-2. SV-4, System Functionality Description, like I said
in the OV section closely related to OV-5 and SV-5.  So
if one changes, they may all have to change.
SV-5 is a large table that shows the direct relationship
between Operational Activity to System Function.  It is a
pain in the ass for reason stated above. SV-6 can be a
very complex table.  It is the System Data Exchange
Matrix.. you'll note that anything with the word "matrix"
in it sucks.  That is because one change on a seperate
veiw can affect change in other views and almost always
includes the matrices.

Technical View (TV)
TV-1, Technical Standards merely lists all the capabilities
of the system and references each of the technical standards
used.

That is my oppinion of the ISP views.  I hope you find them as relatively painless
as I did and if not this site will help you out --->
http://www.teao.saic.com/cbrtraining/archpro01.asp