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 Services Oriented Architecture. Show all posts
Showing posts with label Services Oriented Architecture. Show all posts

Wednesday, November 28, 2012

Exploring Governance Process - part 2


Part two of the Exploring Governance post focuses on prototypical process steps. As noted in the previous post, this example relates to an enterprise-wide SOA governance initiative. Governance process can be applied to any number of areas or can be made available universally to all IT functions (e.g. Data, SOA, Security, SDLC/ALM). Each organization needs to determine for itself how lean or robust the process (and its steps) should be - those decisions will determine which steps (or variations thereof) listed below might be appropriate. 

  1. Submission – submission can involve "ideation" but usually is handled as requirements management. The goal is to make this as flexible and open-ended as possible in order to allow the process and the SARB to serve as a funnel for all the necessary information to build an enterprise roadmap for services across the enterprise. Given that this process will be occurring before any automation is in place and at the beginning of a SOA adoption initiative it is important to make sure that we provide paths for different types of information to come in. So there will be legacy capabilities without specific designs for formal requirements. There will be functional requirements without designs. There will be functional requirements with designs and there will be designs without functional requirements. All of this could be viewed as idea submission. Depending upon whether or not designs or requirements were included the governance process would obviously have to coordinate with related processes to make sure that the service submission met basic standards.

  1. Requirement Acknowledgement – this is a relatively straightforward step in that the SARB would simply be providing some sort of formal acknowledgement that an idea or requirement had entered the services governance process.

  1. Capability Allocation – capability allocation or classification is somewhat more complicated. This involves mapping requirements to a specific set of definitions for capability from the retail enterprise perspective. As noted previously this will require the prerequisite of some sort of preliminary capability inventory. This inventory will take the form of a taxonomy or ontology that can later be applied to a variety of process automation tools including ALM tools, project portfolio management tools as well as configuration management software (including SOA CM).

  1. 1st Level Analysis / Review – the first level analysis and review step involves coordination between review board members and designated technical staff to ensure that the idea or requirement submission meets basic technical standards. The deliverable provided by this step in the process would be a checklist indicating that those initial criteria have been met or not and based upon that a determination would be made whether or not the requirement satisfied the standards necessary to achieve first level approval. It is important to note here that the governance process is not the design process nor is it meant as a replacement for the application lifecycle management process. Governance is meant to provide technical and business oversight and to ensure that enterprise standardization is occurring.

  1. Requirement Logging – requirement logging is a fairly straightforward step in the process and that it merely represents annotations being made by the CM point of contact within the SOA COE wiki.

  1. Initial Approval – initial approval then merely represents that the requirement has been properly submitted and formatted and meets basic criteria for moving forward in the process.

  1. 2nd Level Analysis – second level analysis represents the most complex part of the overall process. This requires coordination through a small group or integrated product team including board members, technical staff and business stakeholders. This is not meant to be a complex engineering endeavor, but rather an examination to determine whether the well-defined service requirements provided from the previous steps in the process conflict or overlap with other requirements or other existing services. In this sense then we are dealing with enterprise or systems level reconciliation as opposed to validation of the service logic in its own context. This analysis involves technical review of service contracts, WSDL's and other service logic at the functional level. It also involves comparison of business logic, rules and functional expectations.

  1. Recommendation & Architecture Update – The result of the second level analysis is a consensus recommendation that is then properly documented by the SARB and included into the SOA architecture roadmap. It is likely then that the architecture board would support some sort of “to be” reference architecture which would include all of the recommendations that had been approved up to this stage.

  1. Handoff to ALM – any artifacts that reach SARB recommendation level would then be provided as roadmap updates to the ALM process. No actual work would occur on these until management approval was obtained.

  1. Deployment Preparation – the CM point of contact would then prepare the service information for final potential deployment. This would include any standardization for modification to WSDLs or service contracts.

  1. Final Approval - this step is provided to ensure that management retains control of the service release process and/or any follow-on work that may need to occur.
The PMO must govern a wide spectrum of IT processes and capability

Process Implementation Considerations
As noted previously, all the roles defined in this process may not necessarily be used. For example the CM role may represent a member of the SARB. This process provides a general guideline and the templates for future governance processes, but in order to test its efficacy within the enterprise environment we would need to demonstrate it utilizing actual requirements and working with the likely participants among the stakeholders. In order to engage in that sort of dry run activity, the prerequisites would also need to be in place.


Copyright 2012  - Technovation Talks, Semantech Inc

Tuesday, November 27, 2012

Exploring Governance Process - part 1


Today's post presents a Governance Case Study; in this case the introduction of SOA Governance within an enterprise environment. 

The larger context for SOA Governance 

Process Context
The process depicted in the figure above represents one of several related processes. We've referred to this process as the SOA Service Approval and Governance process. This is used to help document to provide oversight for SOA service development and management. The other processes that this will become integrated to will include a modified project and portfolio management process, an engineering design process and an application lifecycle management process. Each of those processes will have hooks into and out of the governance process. Both the governance and design-related processes will definitely involve collaborative small group involvement (and that involvement will include collaboration between both technical and business representatives). The eventual goal would be to further integrate the related processes and to provide automation for all of them. 

Process Overview
The SOA Approval and Governance Process is at its heart both a requirements management process as well as a configuration control process. We've also included some elements of design review within the process in order to provide  the most flexible approach and least number of processes possible. The primary objective of this process is to help provide a documentation baseline of all potential service opportunities within the enterprise. The primary role within the process is that of the SARB - this could be translated to either Services Architecture Review Board or Software Architecture Review Board. At first the focus will primarily be directed to SOA services but eventually the board can extend governance across all business logic . The other roles presented in this process include:

  • Stakeholder - stakeholders represent business analysts, management and possibly even customers.
  • Developer - developer represents any technical resource that would be involved in either constructing a service or utilizing a service as a system-level consumer. Developers and stakeholders are the primary participants in both design process activities as well as design review activities within the governance process.
  • CM - CM stands for configuration management and in this context would represent one person designated as the point of contact and responsible for documenting specific configuration information within the SOA Center of Excellence (COE) wiki.
  • Manager - this is self-explanatory and of course the management role is responsible for integration of governance with project portfolio management.
Prerequisites
There are several prerequisites for the governance process; these include a Center of Excellence wiki, a preliminary capability inventory, templates for the process deliverables and extended guidelines splitting the function of this process in the SARB which would be posted on the wiki.

Goals
There are several critical goals associated with this process:
  1. Standardization of requirements capture, documentation and management.
  2. Standardization of SOA services design through enforcement and oversight.
  3. The ability to reconcile requirements and designs across the retail enterprise.
Service Level Versus Enterprise Engineering
One of the key concepts associated with this particular process is the separation of design and design review as well as the separation of discrete design from enterprise design. All these considerations are managed through the first and second level analyses within the process. In other words, we are viewing the SOA designs at two different stages in the governance process – stage I allows us to ensure that the granular service is constructed according to agreed upon standards. Stage II allows us to ensure that services fit within the enterprise in the most efficient way possible.

part 2 of the post will examine the process steps...


Copyright 2012  - Technovation Talks, Semantech Inc

Monday, October 22, 2012

Capability-Based SOA


Two of the most complex problems facing all SOA implementation projects tend to be:
  • The determination of what to do with existing capabilities.
  • The determination of how to define the specific nature of new or transformed capabilities.
Existing capabilities are usually systems but of course can include services or other code that could be readily included within some type of SOA development effort. We tend to refer to this as legacy capability, but the term legacy often has a negative connotation. Perhaps "realized" capabilities better describes the situation in that it reflects that these elements were at some point already successfully deployed and adopted.

The up front portion of most SOA engagements tends to be the most critical part...
 Deciding upon the nature of the new capabilities is also extremely important. If one approaches the situation with the assumption that the development of standards-based services code will magically allow for a plug & play enterprise they are likely to be fairly disappointed. Building service applications does not represent a solutions architecture - with the advent of SOA we must now be more cognizant than ever before of the various inter-dependencies and relationships between infrastructure, application logic and data architecture. This then implies that we need to consider and plan how all of these will fit together or else will leave our fate in the hands of unforgiving chaos.

The fact that all of this involves SOA doesn't change the fact that one must apply a number of basic system engineering techniques and principles to help manage these issues. The diagram below illustrates one possible approach; it breaks the process into three parts:

Part 1 - Capability Taxonomy
Understanding our domain starts here - this ensures that everyone is on the same page from day one, skipping this step (especially in a large enterprise) will place most transformations at risk from the get go.

Part 2 - Capability Granularization
First of all, you need to decide what this is going to look like - are you going to manage like services within some sort of module framework (i.e. statically determined compositions), or are you going to make more discrete services available - ones that can be combined by the users at run-time or added to pages / portals. Or perhaps there will be a mixed approach - whatever that approach is though there will need to be rules guiding how certain capabilities are going to be developed.

Part 3 - Capabilities to Systems Allocation
Then, systems analysis needs to occur to determine if existing capabilities (within systems etc.) can be parsed or transformed into the various new forms defined in the previous step. Only then will the eventual reuse and migration paths become clear.


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