ISP Architectural Views

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

In my limited experience creating views is very interativeprocess. Meaning you create a little then your tweak andchange them as you go.

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

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

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

System Views (SV)The SV's can get a little gray as some of the views cantouch on things that involve your system but you haveperhaps only heard of.  For example, if your system "A"connects with System "B" you may have to show thatconnection even though you don't know much of anythingabout System "B". I haven't seen SV-1 on the Teao Saicsite so I assume it has been phased out. But it dealswith Interfaces.  SV-2, System Communication Descriptionis very much like the example of system "A" in relationto "B".  SV-2 shows how your system communicates/connectswith other systems.  Its almost like a birds eye veiw ofOV-2. SV-4, System Functionality Description, like I saidin the OV section closely related to OV-5 and SV-5.  Soif one changes, they may all have to change.SV-5 is a large table that shows the direct relationshipbetween Operational Activity to System Function.  It is apain in the ass for reason stated above. SV-6 can be avery complex table.  It is the System Data ExchangeMatrix.. you'll note that anything with the word "matrix"in it sucks.  That is because one change on a seperateveiw can affect change in other views and almost alwaysincludes the matrices.

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

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

Popularity: 3% [?]