Object-oriented analysis

An apparatus, system, and method are disclosed for managing inbound transactions from an SAP application. A transaction ID module is included that receives a transaction identifier (“TID”) associated with an event from an SAP application by way of an ALE interface for an asynchronous transaction. A recording module is included to record an event record in an event tracking repository by way of an XA transaction, the event record comprising the TID and an associated transaction status. An intermediate document module is included to receive an intermediate document (“IDoc”) containing transaction data from a transaction associated with the event and the associated TID from the SAP application by way of the ALE interface using a Transaction Remote Function Call protocol. A conversion module is included to convert the IDoc to a service data object (“SDO”) and an SDO transmit module is included to transmit the SDO to an endpoint using the XA transaction.

Apparatus, system, and method for asynchronous complex inbound transactions from sap applications using service oriented architecture

Disclosed is a method, system, and program for error checking raster objects including pixel information for a print job. A plurality of raster objects form the print job. A raster object is received including sequence information indicating an ordering of the raster object with respect to other raster objects in the print job. A determination is made from the sequence information as to whether the raster object is received in a correct order with respect to other raster objects in the print job. This ensures that the pixel information for the raster object is intended for a current pixel line being processed. An indication of error status is made if the sequence information indicates that the raster object was not received in the correct order with respect to the other raster objects in the print job.

Method, system, and program for error checking raster objects

An apparatus, system, and method are disclosed for managing outbound transactions in a service oriented architecture. An execution module is included to receive a J2EE Connector Architecture (“J2C”) execute command associated with a service data object (“SDO”) containing transaction data from a client application. A conversion module is included to convert the SDO to an Intermediate Document (“IDoc”). A transmission module is included to transmit the IDoc and an associated transaction identifier (“TID”) to an SAP application using a transaction Remote Function Call (“tRFC”) protocol for processing the embedded transaction data. A confirmation module is included to transmit the SDO updated with the TID to the client application in response to acknowledgement of receipt of the transaction data from the SAP application.

Apparatus, system, and method for asynchronous outbound transaction event processing into an sap application using service oriented architecture

Network protocols are complex systems implemented by collections of equally complex software components. In many cases, the realization of such protocols requires extensive prototyping and experimentation with different alternative implementations.In this paper, we present ProtoTalk, a generative, domain-specific software framework that utilizes model driven software engineering principles for prototyping state and message driven protocols with emphasis on telecommunication and network protocols. The framework allows first, for modeling a variety of common protocol features by using mappings from state machines, sequence diagrams and packet encodings to ProtoTalk models, and second, for the consequent automatic generation of prototype Smalltalk code from the aforementioned ProtoTalk models. In this respect, the paper attempts to shed light on the use of generative model driven programming techniques within reflective object oriented programming languages and environments. As a proof of concept, we have specified in ProtoTalk and consequently generated in Smalltalk, several core features of the Session Initiation Protocol.

https://www.softlab.ntua.gr/~kkontog/publications/conferences/C1-2009.pdf

ProtoTalk: A Generative Software Engineering Framework for Prototyping Protocols in Smalltalk

The main motivation for the present work stems from the wide gap which exists between the research efforts devoted to developing formal descriptions for communication protocols and the effective development methodologies used in industrial implementations. We apply Object-Oriented (OO) modelling principles to networking protocols, exploring the potential for producing re-useable software modules by discovering the underlying generic class structures and behaviour. Petri Nets (PNs) are used to derive re-useable model elements and a slightly modified TTCN notation is used for message sequence encoding. This demonstrates a formal, practical approach to the development of a protocol implementation through OO modelling. Our utilisation of PNs in the context of object based modelling allows for isolation of the behavioural characterisation of objects into a separate design plane, treated as a meta-level object control. This separation permits greater execution flexibility of the underlying object models. It is that very aspect of our modelling approach which can be utilised in software implementations where dynamically determined “re-programming” (i.e., change of procedures) is needed. For example, one of the requirements in wireless networking software is the ability to cope with ever-changing transmission/reception conditions and that, in turn, creates greatly varying error rates. Similarly, handoff procedures create situations where dynamically determined change of operational modes is required. To illustrate the modelling concepts, the paper addresses the problem of inter-layer communication among multiple protocol entities (PEs), assuming the standard ISO/OSI Reference Model. A generalised model called the Inter-Layer Communication (ILC) Model is proposed. An example of a PE based on the Alternating-Bit Protocol (ABP) is also discussed. The final example demonstrates how meta-level object control (PNs) allows for the dynamic selection of different ARQ based algorithms.

/pdf/communication-protocol-design-to-facilitate-re-use-based-on-50lk36601v.pdf

Andrew A. Hanish

Papers

Communication protocol design to facilitate re-use based on the object-oriented paradigm