Archive

Archive for the ‘Enterprise Architecture’ Category

An enterprise web based solution should follow Customer and not Business needs

December 10th, 2009

conectwritten by gunther gerlach-2009

Many midsize corporations have enterprise solutions based on created more than a decade ago with no strategy or architecture in mind. From a time where and ecosystems didn’t even exist. Today, those systems became a monster hard to deal with and, extremely high to maintain. Corporations need to make a decision now and chose the appropriate technology to update or rebuild their solutions with customers on mind.

Gunther Gerlach

Conversational Service Interactions

June 22nd, 2009

z-crosswritten by gunther gerlach-2009

Internet commerce has created newer forms of service interactions than traditional marketplace transactions. Amazon/UKOnline, single-consumer-to-service transactions – e.g., making customer listings, doing basic look-ups and verification checks, and purchasing goods – are giving way to more distributed, pull-oriented and data streaming modes of interaction on the web. Marketplace auctions, voting, and subscription-based RSS feeds are enhancing wider spans of participants and semistructured, audio and video data in conventional transactional forms.

Gunther Gerlach

Service Discovery and Planning

June 22nd, 2009

spher3written by gunther gerlach-2009

Current provisions for discovery are based on keyword searches through repositories. Keywords are nominated by service providers through publication and advertising features of as a service () functions. Details of message inputs, outputs, and methods are also captured from file scans and factored into searches.

Such discovery techniques are suitable in tightly coupled and well-scoped domains where service consumers can determine what services offer and how they can be independently utilized from search results. In other words, users are expected to know what they want before they search.

Gunther Gerlach

What is a Pair Programming?

May 16th, 2009

peoplewritten by gunther gerlach-2009

An XP practice where two programmers work alongside each other, trying to get a task accomplished. Two minds at one problem!

 

How this help?

 

·         It brings up productivity if the pair knows what it is up to. A chatty pair can cause more damage to the project than getting done

·         It keeps each person honest. If you don’t know something its apparent in the fifth minute.

·         It helps keep the quality of the code. Since the pair is helping code.

·         This is where design happens.

Gunther Gerlach