re-ADA for C4ISR Sheldon X. Liang, PhD

Computer Science

re-ADA for C4ISR Reliable Ada-based Descriptive Architecture via a Quantifiable Interoperating Model Why re-ADA? Scalable re-ADA Formal re-ADA A C4ISR Case Study Practical re-ADA Quantifiable re-ADA

Why re-ADA? Excellence and DrawbacksThe International Language for SEThe Language for a Complex WorldThe first ISO-standardized OOPLThe Quantitative ADL for C4ISR

re-ADA for C4ISRWhy? Ada95 has the meaning of OOP but does not have the class-like formWhat an embarrassing a C++ or Java programmer who has expertise in OOP may not be able to write code in Ada95

Why re-ADA? Expectations and Accomplishmentsre-ADA for C4ISROOPLMean / FormPerfect OOPLLike Java/C++Not just OOPLBut ADLre-AdaAda95re-ADA

Why re-ADA? Approach against Drawbacksre-ADA for C4ISRre-AdaAda95re-ADAC4ISR

Why re-ADA? Quantitatively Modeling Interoperabilityre-ADA for C4ISRDependable Interoperability with respect to RT constraintscan be monitored at runtime

Scalable re-ADA An Evolutionary Approachre-ADA for C4ISRInteroperability forC4ISRSystemInteroperabilityInformationInteroperabilityDependableInteroperationEffectiveIntercommunicationSoftwareInteroperabilitySeamlessInterconnection

Scalable re-ADA An Evolutionary Approachre-ADA for C4ISRre-ADA aims to enable legacy (heterogeneous) components to work together over the network by using interoperability technologies: data unification, message-sending, and interoperable shell.

Scalable re-ADA An Evolutionary ApproachSeamless Interconnectionre-ADA for C4ISRSoftware interoperability refers to inconsistent representation of the same real world entity in various legacy component systems.By data unification andOOMI (Object-Oriented Model for Interoperability), the heterogeneous legacy component can be abstracted as a coarser-grained object that is unified into a standard representation.

Scalable re-ADA An Evolutionary ApproachSeamless InterconnectionEffective Intercommunicationre-ADA for C4ISRFor the sake of effective SMS/RMI betweendistributed components, a set of explicit functionalities needs to realize effective intercommunication. Information interoperability refers to two message-sending ways: Simple Message Sending (SMS) and Remote Method Invocation (RMI) via message-sending.

Scalable re-ADA An Evolutionary ApproachSeamless InterconnectionEffective Intercommunicationre-ADA for C4ISR

Scalable re-ADA An Evolutionary ApproachSeamless InterconnectionEffective IntercommunicationDependable Interoperationre-ADA for C4ISRSystem interoperability refers to joint task execution over the network that is realized via message-sending in a dependable wayDependable Interoperability with respect to RT constraintscan be monitored at runtime

Scalable re-ADA An Evolutionary Approachre-ADA for C4ISRInteroperability forC4ISRSystemInteroperabilityInformationInteroperabilityDependableInteroperationEffectiveIntercommunicationSoftwareInteroperabilitySeamlessInterconnection

Scalable re-ADA An Evolutionary Approachre-ADA for C4ISR

Formal re-ADA Quantitative Interoperating ModelFormal dependability modelre-ADA for C4ISRConstructing formal dependability model for C4ISR the process that incorporates three views of dependability throughout software development process Quantitative view Conceptual view Semantic viewacquiring dependability requirementsthat refer to fundamental attributes:mapping attributes into measurable constraintsbinding attributes onto architectural artifacts, like the role, style, and protocol

Formal re-ADA Quantitative Interoperating ModelFormal dependability modelre-ADA for C4ISRConstructing formal dependability model for C4ISR the process that incorporates three views of dependability throughout software development process Quantitative view Conceptual view Semantic view

Formal re-ADA Quantitative Interoperating ModelFormal dependability modelre-ADA for C4ISRDependable Interoperation between two collaborative components in production-consumption (Prepare Respond) pattern. Three kinds of timing constraints have been developed to reflect dependability attributes, such as availability or reliability:

MET (maximum execution time) for client side, MRT (maximum response time) for server side, and LATENCY (maximum delay during communication)

Formal re-ADA Quantitative Interoperating ModelFormal dependability modelre-ADA for C4ISRClient/PublisherServer/SubscriberThe client prepares message (constrained by MET), and sends it out as a RMI message (constrained by LATENCY), and then expects response from the server (constrained by MRT)

Formal re-ADA Quantitative Interoperating ModelFormal dependability modelre-ADA for C4ISR

Formal re-ADA Quantitative Interoperating ModelFormal dependability modelReal-time constraints monitorre-ADA for C4ISRIn distributed computing environment, multi-threads dominate the interoperation between Publisher and Subscriber. , and Agent that plays a role of Publisher that delivers message for response, and a role Subscriber that observes message by giving response. Real-time constraints can be monitored at runtime on the basis of multi-threading communication.

Formal re-ADA Quantitative Interoperating ModelFormal dependability modelReal-time constraints monitorre-ADA for C4ISR(a) Preparation for deliveringconstrained by MET(b) Response for observingconstrained by MRT(c) intercommunication constrained by LATENCY

Formal re-ADA Quantitative Interoperating ModelFormal dependability modelReal-time constraints monitorA C4ISR case studyre-ADA for C4ISRA C4ISR system is generally composed of component systems in military applications for instance, airplanes in the sky, warships in the sea, submarines underwater or missiles on the land, all of which connects with the battle management infrastructure.

Formal re-ADA Quantitative Interoperating ModelFormal dependability modelReal-time constraints monitorA C4ISR case studyre-ADA for C4ISRDependable interoperability makes a lot of sense with C4ISR in regards to the collaborative interoperation of military commands in a coalition. C4ISR is usually established on the military internetworking infrastructure (network-centric warfare).

Formal re-ADA A C4ISR Case Studyre-ADA for C4ISR

Formal re-ADA A C4ISR Case Studyre-ADA for C4ISRC4ISR architectures aim to improve capabilities by enabling the quick synthesis of go-to-war requirements with sound investments leading to the rapid employment of improved operational capabilities, and enabling the efficient engineering of warrior systems.

Formal re-ADA A C4ISR Case Studyre-ADA for C4ISR

Practical re-ADA Class-like OOP in Ada95Syntactic class constructre-ADA for C4ISRIn re-ADA, all heterogeneous components are required to play a specific role -- either a Publisher or a Subscriber, or both. So we need an up-most ancestor class Role for defining generalized features for all descendant classes to inherit from, such as tagged, Controlled, Initialize and Finalize (Ada95/Ada05).In this Ada-based design approach, the pristine notion of class is introduced as a major program element in a package in support for more straightforward object-oriented construction; and through inheritance, many descendant classes can be derived.

Practical re-ADA Class-like OOP in Ada95Syntactic class constructre-ADA for C4ISRAn Ada-based pristine class in an Ada package is treated as program unit that encloses properties (data & subprograms)

Practical re-ADA Class-like OOP in Ada95Syntactic class constructre-ADA for C4ISRThere are five rules that have been developed as key points upon which a pre-compiler can be made to translate the pristine class into Ada95/Ada05 code. R-1 class and type: a class name always implies two types; R-2 member method: a member method is an access to a subprogram R-3 constructor and destructor: They are Initialize and Finalize R-4 prefix Current access within member methods body: R-5 object designator: Obj

Practical re-ADA Class-like OOP in Ada95Syntactic class constructre-ADA for C4ISR

Practical re-ADA Class-like OOP in Ada95Syntactic class constructInheritance and polymorphismre-ADA for C4ISRThe Collaborators connection provides a useful means by which a concrete component is assigned to play a specific role (Publisher orSubscriber). In terms of role-assignment, there are two ways toglue the concrete component on the specific role: Object embedment, and Object derivation. The object derivation is to derive a new class and override the existing member method (predefined by the framework) for instance, procedure Prepare is abstract. An abstract member method represents polymorphism and dynamic binding.

Practical re-ADA Class-like OOP in Ada95Syntactic class constructInheritance and polymorphismre-ADA for C4ISRThrough inheritance, the subclass can redefine a subprogram by overriding it, which means polymorphism

Practical re-ADA Class-like OOP in Ada95Syntactic class constructInheritance and polymorphismComputational collaborationre-ADA for C4ISRWe now take a closer look at the C4ISR case study. Although we already have an outlined configuration with Ada-based descriptive architecture, here we apply the 6th rule and the 7th rule to translate the Ada-based description into real Ada95 code

Practical re-ADA Class-like OOP in Ada95 Computational collaborationre-ADA for C4ISRCode and Semantics

Quantifiable re-ADA ConclusionC4ISR: Reliable InteroperabilityC4ISR architectures aim to improve capabilities by enabling the quick synthesis of go-to-war requirements, and enabling the efficient engineering of warrior systemsQIM/re-ADA: Quantitatively Modeling ArchitectureThe QIM/re-ADA provides the explicit loci around which designers are able to stress and evaluate the non-functional properties during architectural design.re-ADA/CORBA: Descriptive Architecture & Infrastructure re-ADA/CORBA maps dependability into quantifiable constraints as architectural (semantic) properties that are constructed on the basis of CORBA, so that dependable interoperation can be verified at runtime.re-ADA for C4ISR

re-ADA for C4ISR Questions