Component-based Architecture And Modeling and Simulation 07/03/2002 9:33 1

Transcription

1 Component-based Architecture And Modeling and Simulation 07/03/2002 9:33 1

2 SBA Observations Dr Sega Platform-centric network centric Common vision representation Multiple function areas Joint, interoperable, re-useable models Dr Dahmann System focus mission focus Systems of systems pose new challenges Dr Castro Multi-scale, multi-view Contractors funded by systems, not by compatibility Mr Schade Seamless data exchange/interface standards Knowledge retention Ms. Zimmerman Rapidly composable and scalable M&S Strong CM focus Build only what is needed Mr Lunceford M&S best practices still a mystery Begin shift of M&S from craft to scientific/engineering discipline 07/03/2002 9:33 2

3 Today s Goals Discuss Describe AF component-based strategy and approach The picture and the pieces Apply lessons learned to M&S Components and the DoD capabilities vision Components are a way of thinking about systems and organizations Not just IT Challenges Generate ideas, discussions, and excitement 07/03/2002 9:33 3

4 Background Projects Component-based Supply Chain Modernization 100+ Separate Logistics Systems Integrated Logistics Enterprise SBSS REALM Base ERP DLA EXPRESS DII-E CMOS SCS Base GCSS Modernize Supply Chain Contractor Depot Supply Base Warfighter SCS Warehouse DLA EDW AAM Depot Base Maintenance Joint Asset Visibility Today Tomorrow Air Force Logistics Collection of stovepiped systems Pieces do not connect Picture not complete Integrated picture across IL Complete connectivity Total Asset Visibility (TAV) factory-to-foxhole 07/03/2002 9:33 4

5 Background Projects 3D Component-based M&S Framework Arete Ocean Model Ocean heights Radiance function (point) Reflections Dynamic grid sampling Rendering Rendering Transmission RenderWorld Visualization Framework TM Transmission Sensor Motion Object Interaction Coordinate Transformations Scattering Volumetric Integration Arete Cloud Model Liquid water content Scattering phase function Serves as reference not recommendation 07/03/2002 9:33 5

6 Background Projects Component Based Environment Simulator Commercial Product (with DoD origins) Component architecture makes it very flexible Plug in model to numerous rendering packages 07/03/2002 9:33 6

7 What is a component? Software building blocks Structured interfaces Clear purpose Build complex apps Basic Examples Legos (complex and general purpose) Dictionary in MS products Complex Component-based development 07/03/2002 9:33 7

8 Components Examples AF Logistics Modeling and Simulation Supply Chain Vocabulary OrderManagement Inventory Catalog History Security Financial M&S Vocabulary SceneManagement Sensor Target Vehicle Terrain Atmosphere 07/03/2002 9:33 8

9 Component Granularity Granularity Type Example Example # Comp. Detailed Business Modeling Patterns Business Objects Database Interfaces Inventory, Catalogue Target Signature Terrain, Sensors General Applications Base Supply Chain Virtual Environment Need right granularity: Too granular exceedingly complex Too general limits reusability 07/03/2002 9:33 9

10 How do you get components? Use Case Modeling User description Application architecture Examples Withdraw $$ Order item Fly thru The hard part Drives Order Manager Financial Inventory Catalogue Users describe what they do Architects map into components (with users) Use case modeling Text, activity diagrams User-centric Components and interactions Architects map into enterprise components Mission-focused, not platform centric 07/03/2002 9:33 10

11 How components work together (Order Item Use Case) Supply Clerk Orders Manager Inventory Audit History Security Catalogue validatelogin(user) submitorder(order) checkandresolveitems(itemlist) ValidateOrder() getinventory(item) writetransactionhistory(transaction) ConfirmOrder(Order) 07/03/2002 9:33 11

12 Use Case Modeling Results Suite of components with Interfaces Components Interfaces Interfaces define expected component behavior 07/03/2002 9:33 12

13 Components and Interfaces Interfaces Define Component Behavior Plug and play architecture Swap approved components in and out of scenario Supports multiple modeling and visualization methods Dynamic multi-scale modeling Tunable rendering times TS insertion/interfaces Self-assembling, capability-focused applications Components provide powerful toolkit Use cases provide instruction manuals Mission-focused, not platform centric 07/03/2002 9:33 13

14 Challenges Human factors Legacy people and legacy systems Invite users to be part of change Knowledge drain SME and architects need to stay with projects Cultural change Funding DoD funds systems, not enterprise Initial development costs significantly higher But, DoD primed for transformation Resistance is futile Technology Component technology well-defined Frameworks are immature Emerging technologies from web services to intelligent agents to self organizing networks 07/03/2002 9:33 14

15 Putting it all together Contractor Depot Supply Base Supply Warfighter Depot Maintenance Base Maintenance Joint Asset Visibility Integrated Air Force Logistics Vision 07/03/2002 9:33 15

16 Putting it all together UI Layer BASE Supply Integration Layer Integrated AF Logistics Enterprise Logistics Core Object Layer Puzzle Piece = Key Logistics System System functionality comes from Enterprise Components 07/03/2002 9:33 16

17 Putting it all together Enterprise is System of Systems serving different user communities Catalog Depot Supply Depot Maintenance Order Tracker GCSS-AF Integration Framework Base Supply Integrated AF Logistics Enterprise Base Maintenance Supplier Custom Enterprise Views Combat Support Portal User Custom Portal WarFighter Integration Framework - Connects components - Utility toolbox Integrated AF Logistics Enterprise 07/03/2002 9:33 17

18 Putting it all together Core Asset Repository Core Asset Repository Core Objects Application Layer Application Utilities Catalog Depot Supply Depot Maintenance Order Tracker GCSS-AF Integration Framework Base Supply Integrated AF Logistics Enterprise Base Maintenance Supplier Custom Enterprise Views Combat Support Portal User Custom Portal WarFighter Centralized repository Manages core assets Provides strict CM control Assembles applications Integrated AF Logistics Enterprise 07/03/2002 9:33 18

19 Putting it all together M&S Version Core Asset Repository Core Objects Application Layer Application Utilities Image Target Detection Battle Planning Analysis GCSS-AF Integration Framework Fly thru Weapons Platform Sensor Platform Custom Enterprise Views Combat Support Portal User Custom Portal WarFighter Integrated AF Logistics Enterprise Integrated AF Logistics Enterprise 07/03/2002 9:33 19

20 Key Factors Components represent a different way of thinking Both enterprise and mission-centric Collection of parts designed to work together Applications assembled around requirements, then disappear Not just technology Technical approach very mission-focused Driven by users, not technology Requires architecture oversight and expertise Design and configuration management key pieces 07/03/2002 9:33 20

21 SBA Observations (Revisited) Dr Sega Platform-centric network centric Common vision representation Multiple function areas Joint, interoperable, re-useable models Dr Dahmann System focus mission focus Dr Castro Multi-scale, multi-view Mr Schade Seamless data exchange/interface standards Ms. Zimmerman Rapidly composable and scalable M&S Strong CM focus Build only what is needed Mr Lunceford Begin shift of M&S from craft to scientific/engineering discipline 07/03/2002 9:33 21

22 What is a Software Product Line (SPL)? Software Product Line* a set of software-intensive systems sharing a common, managed set of features that satisfy the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way. * From the book Software Product Lines, by Paul Clements and Linda Northrop 07/03/2002 9:33 22

23 Software Product Line Deployed Applications Core Asset Properties Analysis/ Modeling Code Test Suite Documentation Core Asset Repository Core Components C1 C6 C4 C9 C2 C7 C5 C10 C3 C8 Application Layer Database Connectors GUI Templates Exception Handling Common Utilities App Layer App Layer App 1 C1 C2 C3 C4 App 3 C1 C3 C4 C7 Application Specific Code App Layer App Layer App 2 C1 C3 C5 C6 App 4 C1 C2 C3 Custom 07/03/2002 9:33 23

24 Why a SPL? SPL provides established methodology for reusable component development across multiple applications Core Asset Repository extends well beyond centralized code Standardized requirements for all objects Interface and functional Complete test cases Integrated with development/cm environment SPL provides mechanism for formal testing and configuration management of components Essential element to maintain plug-and-play capability Ensures components always compatible with current architecture 07/03/2002 9:33 24

25 Next Steps Embrace component-based approach Setup workshops to define scenarios and approach Focus on few key capabilities Keep others in mind Determine how existing pieces fit into this approach Begin with a demonstrable prototype Onward and upward! 07/03/2002 9:33 25

26 Thank You Me: Karl Garrison (C) Keane, Inc (O) 1410 Spring Hill Road McLean, VA 07/03/2002 9:33 26

27 But Where s The Data? Application interfaces separate from data sources Data Standards Critical to Plug and Play Live Data Base Order Manager Historical Atmosphere Model Depot Supplier Army Inventory Data Stores Inventory Data Object Inventory AF Logistics History DW M&S data Data accessed through components Some enterprise-wide Enterprise data warehouses Some local managed Local operational data stores Data volume Security constraints 07/03/2002 9:33 27