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

Sunday, August 3, 2014

The 5 Rules of IT Architecture


It is perplexing that after nearly 20 years since the emergence of IT Architecture as a discipline, there is still so much confusion surrounding what architects do (or more precisely, what they are supposed to do).

Many people in IT refer to themselves as "Architects" now - yet how can employers or colleagues quantify or otherwise validate that they are indeed actually Architects? I will propose five simple rules or tests to help clarify this:

Rule 1 - Architects architect, just as writers write. Architecture is by definition a design process. Any architect who doesn't or can't produce design is not functioning in the assigned role. An important corollary to this is that you cannot be an effective Architect and focus only on one 1 thing in IT - for example 1 tool / product. Architecture is a discipline, not SME knowledge in one particular area. The reason why this is the case is that most of the time focus on one product leads to a very myopic view of how to solve a problem (every issue begins to look like a nail for your one hammer).

Rule 2 - Architects follow a design process; whether it is geared towards EA frameworks or application design is somewhat irrelevant. What is crucial is that an approach is followed. Not having an approach means not having standard design expectations or deliverables. A lack of design diligence is analogous to a brick and mortar architect using cocktail napkins instead of blueprints to design skyscrapers.

Rule 3 - Architects are honest brokers, not blind followers. Why is this important? Well, it matters because the design process is where most key IT decisions get made. The Architect must take a certain level of responsibility for the outcomes associated with their work - just as brick and mortar architects do. If a client building a Summer house on the beach demands that the structure be built atop sand without concrete or wooden supports, the Architect must let them know the house will likely suffer a structural failure shortly after completion (if not before).

Rule 4 - Architects are problem solvers. Anyone working as an architect who deliberately avoids facing and resolving the tough issues is unlikely to achieve any sort of measurable project success.

Rule 5 - Architects must be able to communicate with the organization they are serving. This applies both to having personal effective communication skills, but also to the projects themselves. Projects that aren't transparent or collaborative tend to take longer and experience high failure rates.

IT Architects tend to be placed in high-profile, high-pressure roles. We who serve as IT Architects are constantly being judged not only personally but also as a profession. Part of the reason the latter half of the previous statement is true is due to the inconsistencies in outcomes for architecture-related projects.

However, if both Architects and their colleagues used the 5 rules above to define what should be happening, the outcomes for most architecture projects would improve dramatically.


Design requires visualization - effective visualizations can be notation-driven or conceptual (as in the above example) 


Copyright 2014, Stephen Lahanas


#Semantech
#StephenLahanas

Saturday, June 8, 2013

Integrating Design & Architecture

We're going to take a short break from Physics and dive back into IT - actually pretty soon we will see them intersect in our discussions - but for now we're going to expand on a topic I introduced on Dice.com last year: Integrated Design.

Many people view design work and architecture within IT as separate disciplines and perhaps as many different disciplines. It's my firm belief that all design-related effort (and architecture most definitely falls into that bucket) are related and contextual. The challenge of course is finding a way to integrate these activities - first from a process perspective and eventually through some sort of automation. One of the best ways to achieve this is through the development of an Integrated Solutions Framework.

One of the interesting characteristics of most Enterprise Architecture frameworks is that they are built atop meta-models. Those meta-models are in fact usually a 3NF (3rd normal form) relational data model (or ERD – entity relationship diagram). Having the models allows for the ability to deploy design artifacts to architecture repositories – it also provides a metadata framework that allows for reporting based upon the information resident within the designs. But most importantly perhaps, this illustrates how important it is to have a logical “mapping framework” for all information related to design. While using one of those frameworks within an actual software solution dedicated to architecture management is nice, it isn't necessary. One can recreate the logical framework as an organizational construct and still receive quite a number of benefits from it.

Here is a visual representation of what that standard framework might look like...

A prototypical framework for integrating design and architecture

In the following sections, I will provide potential benefits and explain the framework in more detail.

Benefits:

  • This framework provides a clear linkage between specific elements of the architecture/design and requirements.
  • This framework allows for consistent and logical descriptions of all solution elements across and within a given organization (and is scalable across organizations as well).
  • This framework allows for management of all non-architecture designs alongside formal architecture deliverables. This is extremely important as in most organizations the majority of IT design is not captured as architecture (and in some organizations, none is).
  • This framework can be used with no automation, some automation or total automation – it is also easily translatable to most EA frameworks.
  • This framework can be integrated with / into any solution methodology and any standards management paradigm.

Levels (vertical):

  1. Enterprise
  2. Segment
  3. Capability
  4. Detail

Concepts (horizontal):

  1. Design Activity or Description
  2. Design Deliverable
  3. Example/s

Definitions:

  • Core / Holistic Architecture – The Holistic Architecture can exist potentially at several levels – it is roughly equivalent to an Enterprise Architecture (EA). Like an EA, the Holistic Architecture can encompass one or many domains and organizations. The main idea is that within some defined boundary the Holistic Architecture covers the comprehensive solution in question.
  • Architecture Tier - An Architecture Tier tends to represent a logical layer within a holistic solution – for example this could be the shared Cloud Hosting environment that all other elements of the solution reside within. 
  • Reference Architecture– A Reference Architecture can be a tier (more horizontal) or it could be a vertical segment (crossing tiers) within the larger Holistic solution. For example, a BPM workflow capability may stretch from to the infrastructure level to the User Interface and be considered the standard approach towards providing workflow capability to that organization (thus it is a vertical segment).  
  • Core Capability – A capability is often associated with a slightly lower level of detail than the Reference Architecture. An example of this might be a BPMN design tool for business users to create their own workflow. Within the example Reference Architecture listed above, the design tool is located on one of several servers and provides its own unique interface that may not be generally available to the rest of the users in the presentation layer (for the BPM / workflow tool). Capability definition is used to facilitate requirements development and Use Case modeling. A Capability in this framework approach is roughly equivalent to a complex pattern.
  • Complex Pattern – A Complex Pattern simply means that more than one pattern is being employed. Although allocation of scope to patterns is a somewhat subjective exercise, the goal within the paradigm presented here is provide as narrow of a pattern as possible in order to help drives specific decisions regarding solution allocation and configuration standards. The above Capability example represents a complex pattern as there are several distinct elements to the workflow mapping solution (each of which may involve different options to realize). 
  • Simple Pattern – A Simple Pattern is the lowest level of architecture or design control; in other words this is where we specify the details for how the solution ought to work. For example, using the ongoing example, we might assign separate Simple Patterns for the Design UI approach for the modeling tool based upon whether it is being delivered to a PC or a mobile device. 
  • An important consideration here is the notion that an organization can have more than one methodology; and in fact many organizations now have at least two, a traditional Waterfall approach and an Agile approach of some type. More complex organizations may have any number of methodologies to deal with; for management of Data Centers ITIL could be considered a methodology, for government Acquisition DoD 5000 is used, for data-centric projects many groups create approaches based upon DAMA’s DMBOK (Data Management Body of Knowledge) and so on. The design mapping described and illustrated below could be applied to any / all of those situations. 



copyright 2013, Stephen Lahanas

Thursday, October 11, 2012

Metaphors for Design

Innovation is often driven by design, modeling or architecture - but what drives those?  Often times it's a cultural interaction - an application of metaphors or symbols. "Windows "are a metaphor for how we choose to manage User Interfaces for example.

My all time favorite example of the use of metaphor goes back to the middle ages; traveling bards used to present stories and poems to audiences from town to town before the advent of print. This was an interesting variation of storytelling tradition that occurs in most cultures – but what many of the bards did to manage their storytelling experience was construct the story-telling experience out of a metaphor. The metaphor was often imagining a house – and within each room the storyteller would locate an important part of the plot, items within the room would trigger specific details in the retelling. In many ways what this represented was a mental discovery and / or content management application. We’ve all variations of this them today – the most obvious example is what we refer to as a “Chat Room,” but other applications have used the room and structures metaphors for similar functionality. 


So why metaphors, what’s the value proposition we’re describing here? A metaphor is generally only useful if it applied as a means to leverage existing knowledge to help facilitate some other action. That action might be story telling or driving heavy equipment, but in most cases the action we’re hoping to facilitate is somewhat complex in nature. So the question is; can someone learn everything they need to know about fulfilling this new complex action in a reasonable timeframe, and if the answer is no, then what exactly can be done to reduce the learning curve? Simply because someone is using a new technology to accomplish a familiar task it doesn’t mean that all aspect of the task need to change also. There are many other benefits to this type of continuity besides a reduction in learning costs; they include:
  • Greater likelihood of acceptance and adoption of the capability
  • A Greater likelihood that the new capability will be able inter-operate with examples of the old capability still in place elsewhere
  • The ability to improve on but maintain process approaches that have proven themselves to be effective.
Example
The best example of something I’ve been involved with that is essentially a metaphor is an online magazine or newspaper. Perhaps this was an easy step to take due to the nature of Internet and it’s ability to disseminate information, but the fact of the matter is that it allowed for massive restructuring of the previous business model (including operations such as printing and delivery) without significantly changed the user perception of the capability or product. The biggest difference of course is the lack of paper involved with the Internet versions; however this is something that is being worked out by vendors right now – new delivery interfaces that are nearly as thin as paper and are bendable will be available in the next several years. Along with anti-glare screens this will come fairly close to the hands-on tactile experience of reading a real magazine (and much more efficiently as the device can upload any magazine’s content through wireless connection and is not disposable). 

Following the metaphor then, all aspects of content design (including advertising) would approximately the current look and feel of typical magazines. The one area that the current manifestation of the metaphor cannot handle which the new one can is the ability to embed interactivity with other applications. For the interactivity, the only guidepost we have with current publications are written games such as crossword puzzles. In these types of situations though, I think what actually happens though is that we tend to borrow from multiple metaphors to build a new capability. So, the new magazine borrows metaphors from video gaming, broadcasting, old publishing models and B2B web applications to achieve a new type of approach. This is not too different than what has just happened with the new i-Phones.


Copyright 2012, Semantech Inc. All rights Reserved