Atlantis Online
April 19, 2024, 03:40:07 pm
Welcome, Guest. Please login or register.

Login with username, password and session length
News: FARMING FROM 6,000 YEARS AGO
http://www.thisislincolnshire.co.uk/displayNode.jsp?nodeId=156622&command=displayContent&sourceNode=156618&contentPK=18789712&folderPk=87030
 
  Home Help Arcade Gallery Links Staff List Calendar Login Register  

What hit the Pentagon?

Pages: 1 [2]   Go Down
  Print  
Author Topic: What hit the Pentagon?  (Read 520 times)
0 Members and 5 Guests are viewing this topic.
Martial Law
Full Member
***
Posts: 35



« Reply #15 on: September 06, 2009, 03:52:08 pm »



OV-2:  Operational Node Connectivity Description
      The OV-2 contains data on needlines and information exchanges between operational nodes.  Through our forms interface, FrameWork allows you to enter one or more IERs per needline, as well as record specific characteristics for each IER.  Our OV-2 model diagram also offers you the capability to organize operational nodes according to functional and process areas.

(Image not available)
OV-3:  Operational Information Exchange Matrix

      The OV-3 matrix reports on the IER specifications including media, quality, quantity, and direction, emphasizing the logical and operational characteristics.  In FrameWork, the matrix is created through our code generation capability and output as a spreadsheet file. 
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #16 on: September 06, 2009, 03:52:34 pm »



OV-4:  Command Relationships Chart
      The OV-4 depicts relationships among organizations in your architecture.  FrameWork supports Command, Coordination, and Internal Command relationship types, and also includes a feature designed to create user-defined relationships. 
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #17 on: September 06, 2009, 03:53:03 pm »



OV-5: IDEF-like Activity Model
      The OV-5 describes activities and the exchange of information between those activities.  In FrameWork, you can build activity hierarchies, and IDEF-like activity models, including ICOMs and external exchanges. 
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #18 on: September 06, 2009, 03:53:36 pm »



OV-6a:  Operational Rules Model
      The OV-6a captures business requirements and their relationshsips with operational activities in the form of structural assertions, action assertions and derivation assertions.  FrameWork also allows you to relate rules to Guidance Statements and Information Exchanges. 
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #19 on: September 06, 2009, 03:54:08 pm »



OV-6b:  Operational State Transition Description
      The OV-6b describes the sequencing of activities in your operational architecture according to external or internal events, and business rules.
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #20 on: September 06, 2009, 03:54:50 pm »



OV-6c:  Operational Event/Trace Description
     

The OV-6c may be used in conjuction with the OV-6b to highlight a critical sequence of events.  The OV-6c also incorporates operational nodes that must take action based on  certain events within a specified time frame
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #21 on: September 06, 2009, 03:55:10 pm »

System Architecture Products

CURRENTLY AVAILABLE SYSTEM ARCHITECTURE PRODUCTS:

SV-1:  System Interface Description

      The System Interface Description behaves as an intermediary between operational and system views, showing generalized representations of communication pathways and networks.  FrameWork gives you the ability to make internodal, intranodal and intrasystem perspectives. 

SV-2:  System Communications Description

      While the Interfaces on the SV-1 represent logical constructs, the Links depicted on the SV-2 represent actual physical pathways between Systems.  System and Link specifications such as status, classification, and interoperability level, are entered through supporting forms. 
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #22 on: September 06, 2009, 03:55:26 pm »

SV-3:  System2 Matrix

      The SV-3 matrix reports on the system-to-system interface relationships created on the SV-1.  FrameWork creates the matrix through our code generation capability, whose output may be accessed through any spreadsheet application. Our matrix organizes systems according to their applicable functional and process areas. 

SV-4:  System Funtionality Description

      The SV-4 depicts the data flows between system functions.  In FrameWork, you can drill-down into the data flows to relate them with data exchanges and specific data elements.  You may also use the SV-4 to depict system functionality hierarchies. 

SV-5:  Operational Activity to System Funtion Traceability Matrix

      The SV-5 reports on interrelated leaf-level operational activities and system functions.  In FrameWork, you can automatically generate the SV-5 matrix as a spreadsheet report, once all the associations between activities and system functions exist in your architecture. 

SV-6:  System Data Exchange Requirements Matrix

      The SV-6 report is similar to the concept of the OV-3. It is a detailed report about all system data exchange requirements and the actual data exchanges that satisfy them. 

SV-7:  System Performance Parameters Matrix

      The SV-7 report is a detailed report that expresses the hardware and software elements that make up systems along with the parameters against which the system or element's performance will be measured, and to record details about the measurement. 
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #23 on: September 06, 2009, 03:55:30 pm »

SV-3:  System2 Matrix

      The SV-3 matrix reports on the system-to-system interface relationships created on the SV-1.  FrameWork creates the matrix through our code generation capability, whose output may be accessed through any spreadsheet application. Our matrix organizes systems according to their applicable functional and process areas. 

SV-4:  System Funtionality Description

      The SV-4 depicts the data flows between system functions.  In FrameWork, you can drill-down into the data flows to relate them with data exchanges and specific data elements.  You may also use the SV-4 to depict system functionality hierarchies. 

SV-5:  Operational Activity to System Funtion Traceability Matrix

      The SV-5 reports on interrelated leaf-level operational activities and system functions.  In FrameWork, you can automatically generate the SV-5 matrix as a spreadsheet report, once all the associations between activities and system functions exist in your architecture. 

SV-6:  System Data Exchange Requirements Matrix

      The SV-6 report is similar to the concept of the OV-3. It is a detailed report about all system data exchange requirements and the actual data exchanges that satisfy them. 

SV-7:  System Performance Parameters Matrix

      The SV-7 report is a detailed report that expresses the hardware and software elements that make up systems along with the parameters against which the system or element's performance will be measured, and to record details about the measurement. 
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #24 on: September 06, 2009, 03:56:25 pm »



SV-8:  System Evolution Discription Description

      The SV-8 describes plans for modernizing an enterprise over time, capturing the sytems involved, the migration timeline and pertinent milestones. 

SV-9:  System Technology Forecast Matrix

      The SV-9 report is a detailed spreadsheet of the impact and timing of changing technologies on selected systems. 
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #25 on: September 06, 2009, 03:57:04 pm »



SV-10a:  System Rules Model
      The SV-10a  captures contraints of system design or implementation as they are related to system functions.  These system rules may be structural assertions, action assertions or derivation assertions. 

SV-10b:  Systems State Transition Description

      The SV-10b is the systems counterpart to the OV-6b.  It describes events and states at the system level, and shows the sequencing of system functions. 

SV-10c:  Systems Event/Trace Description

      The SV-10c extends the SV-10b to allow the tracing of a critical sequence of events.  On the systems side, the SV-10c reflects the system aspects of the events described in the operational event/trace description. 
_____________________________________________________________
Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #26 on: September 06, 2009, 03:57:49 pm »

perspective-corrected graphical/mathematical analysis of the released Pentagon footage from the CCTV location over on Above Top Secret right now...

http://www.abovetopsecret.com/forum/thread498700/pg1

Report Spam   Logged
Martial Law
Full Member
***
Posts: 35



« Reply #27 on: September 06, 2009, 03:58:11 pm »

Report Spam   Logged
Pages: 1 [2]   Go Up
  Print  
 
Jump to:  

Powered by EzPortal
Bookmark this site! | Upgrade This Forum
SMF For Free - Create your own Forum
Powered by SMF | SMF © 2016, Simple Machines
Privacy Policy