A few items from the past week...starting with one from this week in 2007:
I've always liked concept maps, so I really liked Mindmeister, a collaborative mind mapping tool, when I first ran across it last year.
Seems like I'm seeing more news items about what might be called "mashable hardware." There's nothing new about the concept (e.g., Lego's Mindstorms has this flavor), but the combination of Moore's Law, standardized components that are more "external-facing" than "internal-facing" (I'm using ESB terms here as an analogy), and the spread of the "mashable" meme seems to be sparking some interesting experiments. Here's a couple:DARPA is pursing something similar for satellites. The dynamic is very TRIZ-like, and reminds me of a basic innovation strategy.....continually re-evaluate how you've coupled/decoupled capabilities, and how you might reconfigure capabilities (at varying levels of granularity) to do something interesting. The Design Structure Matrix (I say "Design", not "Dependency" since Steven Eppinger at MIT has done so much to popularize this tool) doesn't have a TRIZ flavor to it, but has the same focus on coupling.
The whole topic of "zzz-as-a-Service" is getting a bit tired....however, Phil Wainewright had a nice summary this week. If you're unfamiliar with the architectural revolution that's emerging from SaaS, SOA, composability, etc., his post is one of the best short summaries I've seen. It clearly highlights the fact that all this composability/mashability comes at a price.....and that the price may well exceed the benefits for certain capabilities/needs. Much of the current discussion/exploration is focused on what mixes of generic/specific capabilities provide a positive ROI (along with how they fit various types of contexts/needs).....a landscape that continually shifts as the technological & memetic landscapes shift.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment