Blunder Dome Sighting  
privacy 
 
 
 

Hangout for experimental confirmation and demonstration of software, computing, and networking. The exercises don't always work out. The professor is a bumbler and the laboratory assistant is a skanky dufus.



Click for Blog Feed
Blog Feed

Recent Items
 
TiddlyWiki: Ohmygosh, I'm in Love.
 
3I: Individualized Interactive Instruction
 
Three Defects We Can Do Without: Memory Leaks, Buf...
 
Windows Genuine Advantage: So, did I fail the test...
 
Hark, Is That a Pattern I See Before Me?
 
NSS2: All Things to All People through Perfect Sof...
 
Are You A Problem Witch or a Solution Witch?
 
How Do You Know Your Discarded Disk Is Unreadable?...
 
Uh, lemme see, I'm gonna hack my router and expose...
 
Flaws in Genuine Software Still Exploitable in Tru...

This page is powered by Blogger. Isn't yours?
  

Locations of visitors to this site
visits to Orcmid's Lair pages

The nfoCentrale Blog Conclave
 
Millennia Antica: The Kiln Sitter's Diary
 
nfoWorks: Pursuing Harmony
 
Numbering Peano
 
Orcmid's Lair
 
Orcmid's Live Hideout
 
Prof. von Clueless in the Blunder Dome
 
Spanner Wingnut's Muddleware Lab (experimental)

nfoCentrale Associated Sites
 
DMA: The Document Management Alliance
 
DMware: Document Management Interoperability Exchange
 
Millennia Antica Pottery
 
The Miser Project
 
nfoCentrale: the Anchor Site
 
nfoWare: Information Processing Technology
 
nfoWorks: Tools for Document Interoperability
 
NuovoDoc: Design for Document System Interoperability
 
ODMA Interoperability Exchange
 
Orcmid's Lair
 
TROST: Open-System Trustworthiness

2005-05-14

 

Service Research: Focusing on Requirements for Technology, not the Technology

ACM News Service: Research in Development.  A possible new angle on addressing the problem-space vs. solution-space situation comes to mind as I look at the the discussion of service economies and exploration of services science described in this blurb.  Michael Fitzgerald's May 2005 Technology Review article may not remain on-line for long, so it is worth snagging for its deeper and important context. 

IBM provides mammoth research investments and there is a shift expected in the subject matter, reflecting changes in the business of IBM and other major corporations shifts strongly to a service orientation:

  • Until the packaged software business was “unbundled” from mainframe tie-ins in 1965 (with software often either tightly-bundled or freely distributed among user communities) as the result of an IBM-US consent decree, there was little interest in software as intellectual property: the copyright office did not accept software and software was considered basically un-patentable.  This was also the beginning of a tilt in the company’s research from hardware-focused toward software-focused.  This began the computer-science era for IBM Research.
  • Now the business of IBM is dominated by services (illustrated by the 2002 acquisition of PriceWaterhouseCoopers Consulting), reflecting a tilt in the overall economy as well.  One might now look to IBM’s research capacity as poised to delineate service science in the way it fostered computer science before.
  • The recognition of a hardware-software-services continuum is leading to some re-prioritizing of IBM research.  Because IBM has succeeded in shifting its business from boxes to services, it and other companies are very interested in whether there is a contribution that can be made in service science.
  • One difficulty in identifying benefits of service-research investment stems from how development work on services tends to wind up as part of a process, not a product.

It is becoming startling for me to see how much of what I dig into around trustworthiness of computing systems lies in the delivery of services and the use of technology as instruments of the larger business operation and the mission-related services of the business.  Although this article is not about trustworthiness as such, pretty much all service business has a trust dimension, and I am interested in what can be found in this area.

Resources Identified in the Article:

  • Center for Excellence in Service at the University of Maryland School of Business
  • Center for Open Innovation at the University of California, Berkeley, Haas School of Business
  • Elements of service business found in the IBM Autonomic Computing initiative
  • Work of IBM cognitive scientist Paul Maglio and colleague Rob Barrett looking outside the HCI to the business: what customers do with technology, what IBM consultants understand about what customers want, how the technology effects people
  • Business anthropologists such as Jeanette Blomberg are now in the picture at IBM Research, which has been looking into the coevolution of technology and business innovation and how much it involves people.  (Randy Trigg has a nice bibliography that reveals the power of an ethnographic perspective.)
  • WebFountain is a set of processes for data aggregation and analysis that came out of the research into customer service departments
  • The Center for Business Optimization is looking at the tightening of business operations, including refactoring for risk reduction.
  • The On Demand Information Services program farms out the talent of the research staff, and it is growing revenues dramatically, even though it is a small piece of the services business thus far.

I notice that there is a strong operations research, quantitative, and analytical component in the featured offerings, and this seems to be the foundation and point of departure into services science at IBM.

This could take me pretty far afield from my developing interest in process patterns (as opposed to design patterns as they have become so narrowly construed), but I will keep one eye glancing in this direction for more concrete material.


[updated 2005-05-14T22:08Z: There was just one type too many and I couldn't stand it [;<).]

 
Construction Structure (Hard Hat Area) You are navigating Orcmid's Lair.

template created 2004-06-17-20:01 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-04-30 22:33 $
$$Revision: 21 $