No modern war has been won without air superiority, and no future war will be won without air, space and cyberspace superiority.

Size: px

Start display at page:

Download "No modern war has been won without air superiority, and no future war will be won without air, space and cyberspace superiority."

Shonda Norton
5 years ago
Views:

Grdn Lng Chief Engineer, Naval Aviatin Systems, The MITRE Crp N mdern

1 Jhn Richardsn PMA-290, FS Prttyping Chief Engineer, VP Savvee Cnsulting Inc. Dr. Grdn Lng Chief Engineer, Naval Aviatin Systems, The MITRE Crp N mdern war has been wn withut air superirity, and n future war will be wn withut air, space and cyberspace superirity. 1 Authr Unknwn

An abstract definitin Participating as a part f a cntinuusly-evlving, cmplex cmmunity f peple, devices, infrmatin and services intercnnected by a cmmunicatins netwrk t achieve ptimal benefit f

relates t human activity within any given dmain and their assciated crss dmain activities; by utilizing a cmmn cmmunicatin infrastructure in rder t achieve increased awareness, cntrl, and respnse

2 An abstract definitin Participating as a part f a cntinuusly-evlving, cmplex cmmunity f peple, devices, infrmatin and services intercnnected by a cmmunicatins netwrk t achieve ptimal benefit f resurces and better synchrnizatin f events and their cnsequences Wikipedia A mre rbust definitin Net-Centricity is the insertin and applicatin f evlving infrmatin and cmmunicatin technlgies as it relates t human activity within any given dmain and their assciated crss dmain activities; by utilizing a cmmn cmmunicatin infrastructure in rder t achieve increased awareness, cntrl, and respnse thrugh the explitatin f infrmatin. There are many terms and abbreviatins used t reference Net-Centric: Net-Centric Warfare: NCW (US) Net-Centric Operatins: NCO: (US and NATO) Netwrk Enabled Capability: NEC (UK) Netwrk Based Defense: NBD (Sweden) 2

3 The gal is t increase the Net-Centricity f warfighter, business, intelligence, DD enterprise management, and enterprise infrmatin envirnment management peratins by enabling increased reach amng the GIG users, increased richness in the infrmatin and expertise that can be applied t supprting peratinal decisins, increased agility in rapidly adapting infrmatin and infrmatin technlgy t meet changing peratinal needs, and increased assurance that the right infrmatin and resurces t d the task will be there when and where it is required. The value f this visin is characterized by fur main pints f tpic: An increased ability t share infrmatin. DD Acquisitin Guide Greatly expanded surces and frms f infrmatin, and related expertise t supprt rapid, cllabrative decisin making. Highly flexible, dynamic, and interperable cmmunicatins, cmputing, and infrmatin infrastructures that are respnsive t rapidly changing peratinal needs. Assurance and trust that the right infrmatin t accmplish assigned tasks is available when and where needed, that the infrmatin is crrect, and that the infrastructure is available and prtected. Rapidly prvide the Jint Warfighter an advanced Netwrk Centric Warfare envirnment able t explit the unprecedented velcity f technlgical change while utpacing threats. Maj. Jeff Guimarin USAF 3

4 This visin encmpasses much mre than just Enterprise Architectures, it represents a paradigm shift in: Data disseminatin and exchange, The establishment f new data usage and dctrine, systems architecture and interperability, missin rientatin/conops, missin effectiveness mdels, business prcess management. Multiple abstractin layers between applicatins and the underlying cmputing and netwrk infrastructure and hardware. Slidifies the Systems f Systems (SS) apprach int a Family f Systems (FS) apprach thrugh the aggregatin f Net-Centric Dmains. The true success f Net-Centric military systems is the rapid applicatin f infrmatin technlgy applied within the cntext f human activities and prcesses. 4

5 5

6 Gals f Net-Centric supprting architectures Prvide an Open Architecture (OA) apprach based n accepted cmmercial industry standards and best practices. Prvide sftware integratin bundaries defined by abstract service bundaries. Prvide highly prtability applicatin envirnments Prvide increased mdularizatin and cmpnentizatin Prvide variable data exchange pathways Prtect and maintain existing system integrity Prvide fr system capability migratin Prvide fr resurce scalability (prcessing, memry etc.) Enable data expsure and prvide fr managed infrmatin exchange Enable business prcess autmatin utilizing cmmercial Business Prcess Management (BPM) slutins. 6

7 Managing Cmplexity with Scalable Architectures is Key t Managing Cst and Cycle Times 7

8 Learn by ding Grw infrastructure incrementally Develp real applicatins intended fr deplyment Chse meaningful class f applicatins Develp fr Tactical Edge Unstable underlying netwrk tplgy Size, weight, and pwer (SWaP) cnstraints Cgnitive sftware / missin-riented applicatins Use mdern techniques and technlgy Agile sftware develpment apprach (SCRUM) Leverage existing tls and appraches 8

9 P-8A Mdular Open Systems Architecture (MOSA) Scalable Netwrk Applicatin Prxy (SNAP) Architecture Future Airbrne Capability Envirnment (FACE) 9

10 P-8A MOSA Prvides an pen architecture reference Prvides a standardized, cmpnent-riented envirnment Fr bth develpment and deplyment Emplys Infrmatin Technlgy (IT) cmmercial industry best practices and standards. Utilizes pen-surce technlgies and sftware cmpnents. Is fcused n scalability and crss-platfrm applicatin reuse Leverages mdern architectural cncepts In particular, a Services Oriented Architecture (SOA) and OSGi Fcuses n abstractin within the OSI Mdel layers 5 thrugh 7, with framewrk integratin at the applicatin layer SNAP Prvides an pen architecture reference Prvides a standardized, cmpnent-riented envirnment Fr bth develpment and deplyment Cnsists f a Gvernmentmanaged set f pensurce sftware cmpnents Is fcused n scalability and crss-platfrm applicatin reuse Leverages mdern architectural cncepts In particular, a Services Oriented Architecture (SOA) and OSGi Fcuses n abstractin within the OSI Mdel layers 5 thrugh 7, with framewrk integratin at the applicatin layer FACE Prvides an pen architecture reference Develped by a gvernment/industry cnsrtium Supprts integratin thrugh well-defined interface standards. Fcuses n abstractin within the OSI Mdel layers 1 thrugh 4, with lw level abstractin at the POSIX interface Can hst ther architectures and applicatin framewrks. Many cmmnalities, with sme differences n apprach. Hwever, all fcused n the same set f gals 10

Defined Standard Expses infrastructure as an abstractin Allws fr cnsistency frm develpment thrugh deplyment Applicatin Level Abstractin Abstractin: allws the system t be defined similar t its actual

Bundles r Deplyable Applicatins: In the wrld f the OSGi mdel, these are typically JAR files with manifest infrmatin attached, but in essence these translate t standardized deplyment cmpnents which

11 Defined Standard Expses infrastructure as an abstractin Allws fr cnsistency frm develpment thrugh deplyment Applicatin Level Abstractin Abstractin: allws the system t be defined similar t its actual meaning (semantic intent) but hides the actual implementatin details. OSGi: the standard prvides an envirnment fr the mdularizatin f applicatins int smaller bundles. Bundles r Deplyable Applicatins: In the wrld f the OSGi mdel, these are typically JAR files with manifest infrmatin attached, but in essence these translate t standardized deplyment cmpnents which represent applicatins; the deplyment is cnstrained by the framewrk thrugh the use f standardized xml schema(s). These schemas and/r manifests define hw the framewrk will deply and assciate the applicatin acrss the enterprise space. Services: The services layer dynamically cnnects bundles by way f ffering a publish-find-bind fr the packaged applicatin and its bject space; this includes breadth and depth, depth being any expsed shared resurces and breadth as applicatin r service reusability acrss the applicatin space. Service Registry: A key cmpnent t Management Services, this expses a well defined API r service frnt fr cmmn interface, resurce sharing, as well as shared applicatins themselves; these cncepts are articulated as part f the publish-find-bind mentined abve. Life-Cycle: The key cmpnent fr Life Cycle Management (LCM), it expses a well defined set f API(s) r services fr the management f applicatin end t end life cycle t include install, uninstall, start, stp, and pause. Mdules r Dependency Management: This layer defines the encapsulatin and dependency expsure fr internal and crss applicatin dependency that will be managed by the framewrk (hw applicatins expse/exprt and cnsume/imprt cde). 11

12 Adaptable Architecture Supprts: Service Oriented Infrastructure Open Standardized Develpment OSGi Mdel Lsely Cupled Applicatins, Data, and Services Rapid Capability Insertin Net Centric Enablement Existing Cmputing Envirnment Reduced cmplexity fr integratin with an existing legacy cmputing envirnment Integratin Layer Service Oriented Infrastructure Cre Enables prcess autmatin and rapid capability insertin and exudes the tenants f the OSGi Mdel Intelligent, Managed Data exchange 12

effrt Use f Java prvides OS-independence and enables crss-platfrm reuse Well supprted by a wide array f slid develpment

13 OSGi Implementatin Lifecycle Mgmt Dependency Mgmt Service Authenticatin Messaging SNAP Services, APIs and run-time infrastructure define the executin envirnment Strng reuse f existing third party cmpnents dramatically reduces cst and effrt Use f Java prvides OS-independence and enables crss-platfrm reuse Well supprted by a wide array f slid develpment and test tls (e.g., Eclipse, Hudsn) Interface mechanisms t external sftware accelerate re-hsting t meet near-term bjectives 13

14 Java / JDK Runtime Services & Supprt OSGi Framewrk / Karaf Apache ServiceMix Camel messaging JBOSS SOA-P Testing Other JUnit autmated unit testing Hudsn cntinuus integratin testing Maven (dependency management) ANT Nexus (artifact repsitry) Subversin (versin cntrl) Bugzilla (defect tracking) Eclipse IDE NASA Wrld Wind (GUI develpment, mapping sftware) 14

15 Requirements Acceptance Test Feedback Implementatin Example Tests Drive the implementatin f a requirement thrugh a set f autmated, executable acceptance tests aligned thrugh Agile Prcesses. Specificatin Wrkshp Sessin Cding Testing Architecture Dcumentatin Other Activities Feature Cmplete Feature nt cmplete until tests are met Team clarifies and implement the feature tgether Test are executable at the end f the ATDD Wrkshp Sessin 15

the cde) Integratin Tests Hudsn: cntinuus integratin Runs

16 Unit Tests JUnit: autmated unit testing Experimenting with testdriven develpment (write JUnit tests first, then write the cde) Integratin Tests Hudsn: cntinuus integratin Runs whenever new cde is checked in Starts with Test Driven Develpment 16

17 Testing shuld be cntinuus Need representative hardware and simulated peratinal envirnment These envirnments shuld be available t all develpers during develpment Requires netwrked simulatin and test facilities 17

18 Dne is Dne! Cmprehensible examples ver cmplex frmulas Clse Cllabratin with develpment, testing, and quality assurance. Well defined definitin f Dne Trust and cmmitment Testing nt nly at the unit level, but at the systems level t! 18

19 19

20 20

Vertical Dmain Exchange Driven by cst reductin needs Intrduced B2B Exchange paradigm

the B2B Exchange Paradigm Initiates crss dmain exchange.

frm disparate surces Middleware standards spur the develpment f Message Oriented

21 Vertical Dmain Exchange Driven by cst reductin needs Intrduced B2B Exchange paradigm Prduced prprietary slutins Hrizntal Dmain Exchange Prvided further cst reductin Refined the B2B Exchange Paradigm Initiates crss dmain exchange. Hybrid Exchange Mdel Adptin f cmmunity driven standards Expsure f infrmatin and services frm disparate surces Middleware standards spur the develpment f Message Oriented Middleware (MOM). SOA emerges as a primary supprting architecture. Nt just fr B2B, but intrduces the prducer-cnsumer relatinship 21

The GIG is represented as a hetergeneus aggregatin f: Family f Systems Dmains (FS) Vertical exchange dmain Cmmn systems, missin, rganizatin, business

Cmmunity Integratin Grids (CIG) Self-frming, hetergeneus, Hrizntal Exchange Dmain. Aggregatin f FS Dmains and ther Ndes.

22 The GIG is represented as a hetergeneus aggregatin f: Family f Systems Dmains (FS) Vertical exchange dmain Cmmn systems, missin, rganizatin, business structures, and behavir mdels Prmtes supprting architectures, disseminatin mdels, data strategies, and taxnmies. Cmmunity Integratin Grids (CIG) Self-frming, hetergeneus, Hrizntal Exchange Dmain. Aggregatin f FS Dmains and ther Ndes. Prmtes crss dmain interperability and supprting standards. Manages multi-dmain IT infrastructure Service Integratin Grids (SIG) Aggregatin f CIG Dmains Singular Ndes and Transients Ndes r assets that freely perate acrss CIG, SIG bundaries. 22

CA CMDB Connector for z/os

PRODUCT SHEET: CA CMDB CONNECTOR FOR Z/OS CA CMDB Cnnectr fr z/os CA CMDB Cnnectr fr z/os discvers mainframe cnfiguratin items (CIs) and enables ppulatin f that infrmatin int the CA CMDB repsitry. Designed