Smelser.NET

This is a continuation of a previous post and focuses on one of six tenets identified in the previous post.  In this post I will focus on service orientation.

The single most important advancement that will, by itself, define the future of modern systems and applications is the adoption of net-centricity using service-oriented approaches. In the last five years, “Network-centricity” has led the way to Net-centricity. That is to say, prior to the last five years, the emphasis has been on information sharing within a particular domain—whether via IP networks or otherwise. The key difference between the two is the service-oriented approach, which will most likely become the foundation for the bulk of future capabilities and information resources ranging from simple weather information to raw sensor information from a wide range of industries. While products within todays environment have relied heavily on network-centricity for many years, the information they provided has not, for many reasons, been consumable by many third-party applications. Service-oriented approaches espouse more discrete interfaces ranging from raw data access to interfaces optimized for specific application requirements. This approach focuses on information sharing across domains through open standards, and not through defined relationships between systems or programs of record using a mix of standards and proprietary protocols. Modern initiatives are helping to flush out the requirements, standards, specifications, and best practices for service-oriented environments.

A service-oriented architecture is comprised of a number of different components (known as services) that can be consumed by any number of client products. Service-oriented architectures (SOA) define specific dependencies and produce artifacts that can be molded to meet wider service needs then seen in most applications today, whether they are available on the network as a service or otherwise. Within SOA there are provisions for policy controls, information contracts, and the more technical data definitions, state management, and more. Service-orientation can be implemented with a wide range of technologies and formats as needed to meet performance, size, and/or openness requirements.

With this foundation established it opens the door to a wider range of information leveraging and capability composition options. Given this model, applications can become more malleable so they can change to meet the demands of the operating environment, establish new data partnerships & communication paths, and survive incremental service changes without risking the total capability set.

Within modern/future, applications would be modeled to publish discrete data and applications (whether application or information services) and composed to create capabilities as needed.

Tags: soa

This one was a bit of a brain bender... In this project I didn't write any code at all. I was asked to try and define key developmental trends that might define the tenets for any number of new projects. In this great big world of ours there are a lot of opinions on this issue, so I read and I read, but in the end, I was left to come up with my own... Ohhh no! I had to think for myself and in this case I could not rely on the genius of Microsoft, MSDN, or any other resource I had come to rely on. Ok... Here it goes...

In order to understand long range technological impacts to the systems and products of the Future, we need to take a look at key industry and government transformations and architecture trends that are forming today. In the last decade, the requirements for applications and information interoperability, and more importantly, cross-domain information sharing have widened significantly. Technologically speaking, these changes have influenced a number of elements related to how these and related stakeholders are developing systems, applications, and information resources today. The following areas constitute some of the key transformational elements of modern solutions:

• Service-orientation (SOA)
• Human Factors Engineering
• Distributed, Parallel and Adaptive Information Processing
• Presence and Discovery Enabled Solutions
• Appliance-based Solutions
• Localization, Globalization, and Internationalization

As part of this endeavor I also put together an HCI Concepts brief. At a high level, the goal was to expand on the Human Factors Engineering material, with specific emphasis on graphical interfaces. As with most complex issues, the most important thing is to (a) define a common vernacular, (b) define measurements for success,  and (c) come up with a jingle... In this case "Sex Sells" and I don't mean porn.

Over the next few posts I will explore these ideas in more depth so stay tuned 

HCI Considerations.pdf (2.77 mb)

Tags: soa, human systems, distributed processing, appliances, localization, globalization