Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Application-Oriented Object Architecture - A Revolutionary Approach

Application-Oriented Object Architecture - A Revolutionary Approach

|Views: 10|Likes:
Published by Alexander Peter
Application-Oriented Object Architecture - A Revolutionary Approach
Application-Oriented Object Architecture - A Revolutionary Approach

More info:

Categories:Topics, Art & Design
Published by: Alexander Peter on Aug 25, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Application-oriented Object Architecture: A RevolutionaryApproch
Ramesh K. Karne
Department of Computer and Information Sciences, Towson UniversityTowson, MD 21252 USArkarne@towson.edu
Since last fifty years computer systems and architecturesfollowed an evolutionary path resulting in rapidly changinghardware and software. This paper proposes arevolutionary approach, application-oriented objectarchitecture (AOA), which is based on Application Object(AO) and self managed hardware units. We havedemonstrated sample applications such as sorting andediting using the above approach. Currently, we are in a process of understanding a Web server application to berun under AOA. When AOA becomes feasible, it providesa revolutionary approach that will change the informationtechnology horizon so that computer systems can be builtsimilar to engineering buildings.
Application Object(AO), Application-oriented ObjectArchitecture (AOA), and Embedded OS.
Current computer systems are rapidly changingenvironments including: hardware, operating systems,compilers, tools, programming languages, and so on.
Wemust build computer applications that are independent of operating systems and environments, yet extensible, secure,and stable
. The OSKit [2] approach attempts to avoidtraditional operating systems and provides a necessarykernel for applications. Exokernel [1] offers an applicationlevel kernel interface for fast server applications bypassingthe traditional operating system. The Oxygen project atMIT [4], and other distributed OS projects [5], offer hopeto build pervasive and distributed computing withembedded building blocks and natural language interfaces.Our goals are similar to the above research, but it differs inits approach. The application-oriented object architecture(AOA) [3] focuses on applications instead of computingenvironments. It is based on primitive computer applications such as sending a message, editing adocument, sorting data, computing FFTs, performing a purchase online, and so on. That means, these applicationsare abstract and will never change, however, they may needto be extensible. For example, they should not depend uponany OS or any devices attached to a system. Once weunderstand these primitive applications, the applicationobject (AO) can be designed, and it can be run in thehardware without any need for a particular environment.For example, a bubble sort program written today in agiven programming language such as C++ should be ableto run on any computer as long as the hardware providesexecution environment for this AO. This forces hardwarevendors to provide upward compatibility and keep the AOinterfaces stable so that old and new AOs can be runwithout any need for operating environment. When an AOcan run without any operating environment on a baremachine, then it offers total flexibility in AOs and stabilityin hardware and software evolution and impedes computer obsolescence and waste.As the operating environment is bundled or embedded intoapplication program, now the hardware has to manageitself and should provide direct interfaces to AOs. Thisembedded OS approach into applications forces thehardware to be self manageable and controllable. Initially,we can build these AO interfaces outside the hardware,however, once these interfaces are well understood, theycan be directly implemented in the hardware.
The AOA architecture is shown in Figure 1. It has AOs andself managed hardware units. A sample AO is shown inFigure 2. The AOs communicate to hardware directlythrough sample interfaces as shown in Figure 3. These areAO interfaces written using the lowest level of hardwareinterfaces such as (Basic Input Output System, BIOS) andshould be standard across all hardware elements. That is,all hardware units such as processors, memory, disks,network cards, and so on should provide AO interfaces.At any given time, there is only one AO running in thehardware. An AO is a self-controllable and self-executableunit that consists of all its program and data. When an AOis not running in the hardware, there is no code resident inthe hardware (it is a bare machine). Thus, an AO performs,its own boot, load, and execution. It carries with it the onlynecessary code required for its execution. When anexecution is done, it exists by carrying all its code and datawith it to be stored outside the hardware. It may be storedon a network server for later processing.An AO can communicate with another AO on a differentmachine using message objects (MOs). These messageobjects are traditional TCP/IP messages that can travel onthe network and can be sent and received by a pair of AOs.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->