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 Enterprise IT. Show all posts
Showing posts with label Enterprise IT. Show all posts

Saturday, December 29, 2012

IT Predictions for 2013

Before we continue with our discussion regarding how to develop Conceptual Models, we're going to pause for a moment and look at the year ahead. In many ways, Enterprise IT seems to move a bit slower than the overall tech sector - that's often because the nature or mission of Enterprise Information Technology is the application of new technology rather than its invention (in most cases). Even still, the last two years have seen some fairly remarkably developments, including:

  • Industry-wide adoption of Cloud Computing models (both internally and externally)
  • Rapid movement towards the concept of Big Data (before that concept has been fully fleshed out).
  • Very rapid movement towards adoption of both social media and mobile applications (and integration of the traditional Enterprise IT with both).
Sometimes, the future is hard to read...

Two years is a quick turnaround and what it really represents is the turning of the ship in a new direction - as opposed to having reached the distant shores. While progress is being made in these new directions - they are in most places 'works in progress.' And of course they must be added to the backlog of works in progress that are already present - yesterday's hype-driven initiatives such as:
  • Cyber security
  • ITIL
  • SOA
  • EA
  • ERP (yes it's still out there and very much alive).
  • Business Intelligence
  • Semantic Technologies (the Semantic Web)   and so on...

Today's IT department is a busy place indeed - it is coping with more new technology expectations than ever before. Yet seldom do IT budgets reflect the widening scope of those expectations. Given this background we're going to make a handful of predictions for 2013...

  • Prediction 1 - Big Data will be redefined into a more actionable approach - this approach will become more architecture driven and less focused on roll-out of databases alone.


  • Prediction 2 - Big Data and Semantic Technology will begin to merge - this will occur through management of meta-data as well as through management of architecture-driven Big Data solutions.  
  • Prediction 3 - More project teams will be consolidated - much of this will happen onshore but some it will be near-shore and offshore. Why? Because more firms are beginning to understand that globally dispersed teams aren't that efficient - initial costs saved must be measured against overall lack of effectiveness in understanding client needs.
  • Prediction 4 - There will be some backlash against the frenzy of IT consolidation that's been occurring for the past several years (driven mainly by Google, Oracle and IBM). This may lead to more anti-trust actions.
  • Prediction 5 - There will be increasing pressure on Congress to examine H1b policy decisions. Most of the influence on these policies have been driven by a handful of the largest IT related companies - their arguments and contention that there is an IT skills shortage in the US will be called into question.
  • Prediction 6 - Mobile App development will become the hottest / most desired job title - at least near-term.
  • Prediction 7 - Massive Online Multi-player gaming environments will unveil new monetization strategies. Massively available online courses will do the same and move towards interchangeable content.

Of course, the most enjoyable part of our industry is how often we end up getting surprised - we're looking forward to that as well...


Copyright 2012  - Technovation Talks, Semantech Inc

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