Mood:
celebratoryTopic: VCSY
This from programmersheaven:
http://www.programmersheaven.com/c/MsgBoard/read.asp?Board=810&MsgID=353384&Setting=A9999F0001
one step beyond tomorrow...
By: Portuno_Diamo on February 03, 2007 at 11:14:08 AM
: : Click on the IBM - emPath® HRMS for DB2 link from this link:
: :
: : http://www.ibm.com/search/?q=empath&v=14&lang=en&cc=us&en=utf
: :
: : I have never seen this message before??????Hmmmmmmmmmmmmmmmmmmm!
: : Now, you just have to ask yourself one question,
: : Do I feel lucky? Well...punk???? LOL
: : GLTAL's
: : Poscash
: :
: :
: :
: :
: When you get a chance to see things in a more inter-related view the architecture will always tell you what pieces and parts are in the box.
:
: Now we can look at what emPath does as a processing model (since I come from the process industry - it's where software actually senses what it's doing and adjust it's performance to optimize what one wants at the sensors).
:
: There are three results for the above search:
: 1. IBM - emPath® HRMS for DB2
: Empath® HR and Payroll suite : A completely secure 100% browser and web based best-of-breed HRMS solution. The solution provides
: URL: http://www.developer.ibm.com/gsdod/solutiondetails.d...
: 2. IBM developerWorks : Blogs : Power Architecture zone editors' notebook
: have many thermal sensors; even the system boards have sensors to measure power consumption in different areas of the machine. Empath is the name of the controller that manages the PowerExecutive features. It hooks into the Power6 processor, the
: URL: http://www-03.ibm.com/developerworks/blogs/page/powe...
: 3. IBM Smalltalk User's Guide (updated for Version 5.5.2)
: This book discusses how you can build applications using IBM Smalltalk and the Smalltalk browsers. It also discusses how your team can collaboratively develop software components.
: URL: http://www-1.ibm.com/support/docview.wss?uid=swg2700...
:
: 1. empath takes software applications and modules and glues them together so they can run as one system.
:
: 2. empath takes hardware sensors and modules and glues them together so they can run as one system.
:
: 3. empath takes VHLL language and modules and glues them together so they can run as one system.
:
: The power system empath is applied to is intended to control the operational load of a server farm.
: http://en.wikipedia.org/wiki/Temperature_control
: What happens when you can make those server farms themselves "smart".
: http://en.wikipedia.org/wiki/Process_control
:
: Smalltalk - think in terms of modular software components making up the language instead of individual statements. The "program" runs by passing messages between the modules... or agents.
: http://en.wikipedia.org/wiki/Smalltalk
: "...was created in a few mornings on a bet that a programming language based on the idea of message passing..."
:
: Now I think we see where we are going. Now we see why Critical Path is so... uhhhh... critical.
:
So now take the TPF concept where an agent exists as a standalone module interconnected with other TPFs. All the TPFs watch over, gate or govern the actions all the various software components and report the pass or fail happenstance along to the next in the command chain. This determinism is what made the IBM OS so powerful and bulletproof.
Now, we are talking about attaching those TPF modules and their interconnecting messages to a layer of operational modules that were themselves overlayed by a humon oriented diagram and specification and model of how the software is supposed to work. The result is a programmed system when the modeling and concept is completed. Human programmers will build libraries of modules to synthesize the actions of standardized modular blocks.
The machine does the programming using the standard model modules. This sounds like what IBM passed to NASA embodied into framework (like "a wedding dress" is a framework for your daughter to select all the premium components and the more expensive accessories) to build the James Webb Space Telescope operational system.
(That's ironic. James Webb gets a monument in space. James Gray gets a question mark. Volatile name that "James".)
So, does there exist some way to modularly create a diagram of what you want to do with an attached specification? Yes. Visio. Then are each member of the language module diagram set associated with a software module built along those specifications? Yes. Smalltalk. And are each module associated with or better accompanied by a functional module to achieve the intended work? Yes. But it's capability is in MLE.
The functional model facility arrives when you can select a portion of "code" to do just the job you want and no more. If you have one leetle piece of code in a huge application that you want to use, traditionally, you either have to download the entire application into the OS and run just the one function you need, OR cut that piece of code and fit it as an object like a dll and get it into the right library and write an application to use it OR uuuuuhhhh... that's it.
With an interconnected virtualized framework, arbitrary means you can place that section (module) of code in a virtualizing wrapper to synthesize any necessary interaction the stub needs to enact with the rest of the application (like phantom pain in an amputation) and inputs outputs the relevant data flow through the module as needed by the rest of the newly cobbled together application.
When it's no longer needed it disappears. (Does not clutter up the object library as the system should signal a cutout had to be used to do that function so the design staff will build a version with no amputation pain. Once built, a defined standard module is added to the lexicon of services the system may search through first.)
It does not matter how large an application is at that point. The system accesses what resources are useful according to the specifications and governance described to the system.
The user gets only what he needs to do a task. Modular function blocks will naturally be preferred to such a circus act, but with the kind of tech we are looking at, the above virtualization scenario is a doable thing and is a key example of the power of this "virtualization" buzzword so many will speak and ride on the next wave. It's like surfing in a turd sea.
It was not doable in the commercial world until now. NThe above three component uses cover:ow everybody will say they do it.
But, they can't do this:
content - the glueing of all applications in a system to become one operable system - i.e. all the knowledge embedded to express the thing becomes the constraining expression of the user's intent in design
form - the physical manifestation of all the various components necessary to encapsulate and maintain the desired existence - i.e. the surrounding environ and the look and feel of the thing
function - the facility to actively translate the human's desired model into an operable appliance - i.e. building out the way the thing works
We want to go from the machine to higher levels of usability beginning with machine language, then a grainy level, then elemental, aggregated, abstracted up to systemized which would be the end of the "services" concept need to know level just as "programming" will fade in use. Then move on to the "relative" concept where software becomes as important and as ubiquitous in your life as all your "relatives".
These become services and step out of the 'programming' jargon world and allow users to morph look and feel to fit their own user jargons.
You know what would be really neat in this day and age? A functional module that happens to be a transactional module at any of the above entity unit levels and with any facility to become services on through relatives. I wonder how long this age will last?
accident prone