Doug Mutart's Blog
The views and opinions expressed in these pages are strictly those of Doug Mutart.
Wednesday, September 15, 2010
Tuesday, February 13, 2007
United States Patent 7,177,634
I was just awarded a patent for a Method of voice access for vehicle services.
One aspect of the invention presents a method of providing vehicle services to a mobile vehicle. An access request is received at a call center. The access request is authenticated. An automated voice menu of vehicle services is presented to a subscriber. A subscriber selection input is received from the automated voice menu of vehicle services. A vehicle service control signal is sent from the call center to the mobile vehicle based on the subscriber selection input.
One aspect of the invention presents a method of providing vehicle services to a mobile vehicle. An access request is received at a call center. The access request is authenticated. An automated voice menu of vehicle services is presented to a subscriber. A subscriber selection input is received from the automated voice menu of vehicle services. A vehicle service control signal is sent from the call center to the mobile vehicle based on the subscriber selection input.
Labels:
Events
Monday, October 16, 2006
CIO Horror Stories
http://www.cio.com/specialreports/horror.html?source=nlt_cioleader
Check out this story from CIO magazine.
Check out this story from CIO magazine.
Sunday, January 29, 2006
Testing for Loosely Coupled Architecture
Testing for Loosely Coupled Architecture: "So, now that we know the basic differences between a tightly and loosely coupled architecture, as well as the advantages, perhaps it's a good idea to break down loose coupling in to a few basic patterns: Location independence, communication independence, security independence, and instance independence. "
I really appreciate David's observations on instance independence. A lot of times, our architects struggle to explain indempotence (one of our executives saw this word in a requirement spec and had to consult a dictionary), statefulness vs statelessness, etc. , when this really just sums things up nicely. Very simply, you should be able to invoke any instance any time and any place without any unintended consequences.
I really appreciate David's observations on instance independence. A lot of times, our architects struggle to explain indempotence (one of our executives saw this word in a requirement spec and had to consult a dictionary), statefulness vs statelessness, etc. , when this really just sums things up nicely. Very simply, you should be able to invoke any instance any time and any place without any unintended consequences.
Monday, January 23, 2006
Sunday, January 22, 2006
The Tao of the Software Architect
The Tao of the Software Architect by Philippe Krutchen has really gotten me through some of the disillusionment and frustration that is just part of the challenge of being a software architect. It was originally published in The Rational Edge.
Sunday, May 01, 2005
GigaWorld IT Forum
Hello, world. It's my first day at the GigaWorld IT Forum 2005. I've already met a bunch of really smart and interesting people, and I'm sure it's going to be an exciting week. For fun, we went on a tour of the Delaney Vineyard in Grapevine, TX
Subscribe to:
Posts (Atom)