Cyber Security Predictions for 2017

2016 was a big year in the annals of Cyber Security, and 2017 promises to eclipse it.

Creating an Enterprise Data Strategy

An introduction to the process of developing comprehensive strategies for enterprise data manangement and exploitation.

A Framework for Evolutionary Artificial Thought

Let’s start at the beginning – what does this or any such “Framework” buy us?

The Innovation Dilemma

What things actually promote or discourage innovation? We'll examine a few in this post...

Digitial Transformation, Defined

Digitial Transformation is a hot topic in IT and big money maker for consultants - but what does it really mean?.

Showing posts with label Systems Engineering. Show all posts
Showing posts with label Systems Engineering. Show all posts

Thursday, October 18, 2012

Semantic Integration - The SI of Tomorrow




Currently when people use the acronym “SI” they tend to refer to something known as ‘Systems Integration’ or specifically to ‘Systems Integrators.’ However, the nature of what a 'system' is and how that concept is evolving are going to change the way that we look at this particular term in the relatively near future. I predict that within the next ten years, ‘SI’ in the context of information systems technology will primarily refer ‘Semantic Integration.’

The Evolution of Systems Integration

What I mean when I say that Systems Integration and the notion of Systems are evolving is that new design concepts and technologies are having a radical and disruptive influence on current integration practices, processes and design approaches. What was a ‘system’ under distributed computing environments is now undergoing a transformation – taking on aspects of both the distributed model used today and centralized models from yester-year. This is largely coming about due to the advent of Services Oriented Architecture (SOA) technology and design principles. It is important to note here that SOA, like Semantics, is a practice area based upon design philosophies and technical standards – the tools being developed in relation to those philosophies standards or applied to it are not the drivers for these trends. Folks who focus on the software tools only and not the underlying principles tend to run into many difficulties in implementing these types of new capability.

Our previous or current experience with System of Systems architectures is what led to the need for System Integration and Integrators largely as an afterthought or mitigating action in response to the need for rapid deployment of multiple, new distributed technologies. Most enterprises have spent the last twenty years playing catch-up in this environment and few are truly architected in any comprehensive sense of the term. System Integration is often a tactical activity – ensuring data passes between systems silos, connecting various applications point-to-point or through limited middleware capabilities, deploying portals and unified sign-on and security management and so forth. Piece by piece, an enterprise becomes more unified under this type of scenario, but at a cost – that cost is increased complexity and expense for maintaining non-standard integration.

The future is upon us; that future is just now promising something new – the ability to coordinate architectures across tiers, across federated domains and across all related lifecycles. The new enterprise can be viewed as a single organic system, consisting of dozens or hundreds of services that operate as a single unified yet dynamic entity that is often federated across geographic and logical domain or boundaries and orchestrated at runtime. This is SOA but it is more than SOA, because SOA doesn’t yet have the necessary philosophical framework for exploitation of Semantics to help achieve this enterprise unification. That’s where Semantic Integration comes into the picture. 

Semantic Integration is not a product, it's a new way to view Systems Integration & Engineering

What is Semantic Integration ?

Semantic integration is not is not confined to or restricted to the ability to operate or configure or utilize specific semantic technology or software packages. Semantic Integration represents a specialized field of practice dedicated to using Semantic Design Principles, Methodologies and technology as a facilitating mechanism (often alongside SOA) to help solve enterprise-level problems for IT. SI as a practice area is relatively new (it is only now being defined),  it is much more than the “Semantic Web” yet is obviously built upon the capabilities inherent within the emerging set of Semantic standards that can be used to express and ultimately visualize semantic entities, RDF, OWL and so forth). Over the next several months, I will introduce the specifics of this emerging practice discipline in this Blog. 


Copyright 2012, Semantech Inc. All rights Reserved 

Wednesday, October 17, 2012

Whatever happened to SOA?

Not too long ago Service Oriented Architecture (SOA) was the hottest IT trend around, at least if measured by the sheer amount of attention or hype that was associated with it. The fate of SOA is interesting for a number of reasons:
  • It helps to illustrate the nature of Hype Cycles in IT and how they influence both industry and individual enterprises.
  • It helps to provide context for why Cloud solutions have now become the "killer solution" (it can't be described as an app) that most folks are examining today.
  • It is an interesting case study in regards to the difference between product-based Hype-Cycles and architecture or standards based hype cycles.
So what did happen to SOA? Strictly speaking, it's still around and going strong, however it is no longer at the top of the 'must have' or 'must do' lists in most IT departments these days. Many SOA initiatives took the bridge to nowhere or have been merged into newer or perhaps more specific enterprise goals and objectives. Before we go any further though, let's recap what SOA represents:
  1. SOA is not limited to one product or product family.
  2. SOA encompasses both capabilities and process.
  3. SOA is very focused on a key set of (mostly W3C) interoperability standards, notably SOAP, XML, WSDL and UDDI.
  4. SOA is not merely a solution but also a solution strategy and architectural approach. This last point is both critical and very subtle. 
  5. SOA has an systems integration focus, not merely a software development one.
This diagram illustrates a number of the Use Cases associated with SOA Adoption
 Each of the last five points is important and several of them are relatively complex issues. Essentially, taken together they tend to imply that anyone wishing to deploy SOA in a significant way would in effect be attempting some form of enterprise-wide transformation. That's a big deal regardless of the technology or technological paradigm targeted in the transformation. Change is never easy - it's less so when dealing with an entirely new way of managing your IT portfolio. These are some of the reasons that SOA is not the driving force in industry it was just four years. So, let's look at what did happen with SOA:
  • SOA was and SOA is hard. There's no silver bullet solution - all options require a lot of work and some risk.
  • SOA initiatives usually become Systems Integration exercises. Many providers or organizations without that systems integrations background attempted SOA solutions and quickly realized it's a skill that takes years to develop (both personally and organizationally).
  • There's more than one way to do SOA - in fact there's quite a few ways. This implies a wide array of possible tools or software options. Navigating those decisions is confusing to say the least and since this happens up front it often short circuits projects before they ever get off of the ground. There's not one piece of software associated with a proto-typical SOA solution.  
  • Often times key elements of SOA infrastructure are not implemented as part of an initiative. Common examples of this include failure to deploy a SOA Registry or Governance paradigm. This tends to limit the effectiveness of the solution and eventually restricts the scope of the entire solution.
One of the reasons people were initially enthused about SOA was that it seemed to represent an easy path to bypass many of the ills associated with the ad hoc heterogeneous sprawl that had become the typical IT enterprise by the mid-2000's. That initial assessment was a misconception, but so too are similar assessments being made now about "Cloud Computing" and "Big Data." Behind the Hype and the marketing buzz, there are certain underlying problems that all IT trends are focused on resolving. More often than not however, no single trend is positioned to solve the challenges alone. We will talk more about Cloud Computing, Big Data and SOA in future posts and presentations. Also be sure to check out our Technovation Glossary page.


Copyright 2012, Semantech Inc. All rights Reserved