- Visit the website: http://patternsbasedengineering.net/
- Review sample content – contains the foreword and the first chapter.
Tuesday, June 29, 2010
New book on Patterns-Based Engineering
Saturday, March 27, 2010
Henry Ford on Facebook
Tuesday, July 14, 2009
Asset Intelligence Part 1
Introduction
Over the next couple of blog enteries I will continue to examine the barrier to entry around enabling the consumption of assets. I will also look at a proposed solution to some of these problems by leveraging the ISO standard of topic maps and show how they can be used to represent and unite assets in different domains. I will also look to understand the types of assets used in application development and to understand the context in which these assets are used. Using this context as guide, we will propose a novel approach for suggesting the best asset to be used in a particular context to the end user.
The importance of assets
Ireland is the last country in Western Europe that is still throwing roads at a traffic congestion problem was one statements I remember hearing from my childhood. Back then I could not understand why more roads would not solve a traffic problem however as I traveled the world and had the opportunity of living in cities like LA, NYC, Boston and London, it became painfully obvious that more roads was not the solution. The solution then becomes how do we better utilize the existing transportation infrastructure? Put more simply how do we do more with less?
Recently at a future of application development conference in NYC a lead architect from a world bank echoed these exact same sentiments but this time applied to application development. Now this is a major global bank and their lead architect was telling us that the last thing he wanted, to fix their problems with application development, was to throw more developers at it. Again on first hearing this statement it seems counter intuitive but just like the roads problem above on deeper reflection it makes more sense. The problem, with application development, is the steep learning curve needed to bring these developers up to the point of where they can be productive. Application development, in a radically changing IT landscape, irrespective of the programming model used in not easy. This quickly becomes a problem of managing complexity, a problem that will only get worse tomorrow as this complexity increases. However as with the road problem the solution is similar but first let us pose the proper question. How do we better utilize and empower the existing staff to be more productive?
To better utilize and empower the existing staff we need to move them to an asset based development model[1]. The maintenance of, reuse of, and enablement of these assets (in this case software development assets) is core to managing the complexity inherent in application development today. These assets need to introduced as early as possible in the life cycle to maximize their benefit and their impact and these assets need to constantly be maintained and updated to help maximize their reuse and impact.
The problem with assets
In our article on Enabling asset consumability we have already looked at the problem of findability of assets. Finability is one of the main problems associated with assets. This problem of findability is outlined in that article in the multi bucket problem. However findability of assets is just one of the many barrier to entry to enabling asset consumability andmoving to an asset based devevelopment model. Here are some of those issues:
- Findability - trying to find the correct asset for the problem at hand
- Reuablability - Once we have found the assets can it be reused easily to address the problem at hand
- Tracability - Once we find and reuse and asset to help us solve a particular problem how can repeat this discovery are reuse for similar problems
- Consistancy of assets Glossary and variants
In particular here we was to examine the problems around asset reuse. The point here is that finding an asset is only part of the problem. If you find the asset and the asset is too complex to use then it is useless. But to understand the problem reusablity let us go back to the movies. Let us turn to the mother of all automators, The Terminator and discuss a scene from James Cameron Sci Fi film classic: Terminator 2: Judgment Day.
Context | Value |
Where | North America, California, LA, mall |
When | June 8th, 1995 |
Who | Terminator (reprogramed as a protector) |
What | Ensure the survival of John Connor |
What - immediate | Persue John Connor |
How | At all costs |
- Confine ourselves to simple assets e.g. use the pony and trap as against the Fat Boy
- Better educated the practioners in the use of complex asset
- Engineer or re-engineer complex assets with a view to achieving an acceptable balance between effectivity and complexity
Thursday, July 9, 2009
Time travel, context and The Tube
Wednesday, July 8, 2009
Presentation best practices
Yesterday we kicked off the first meeting of the presentation best practices course (to be held monthly on the last Tuesday of ever month here at the IBM SWG Littleton Campus).
Presentation best practices course: This course would be a hands on where we would try and teach presentation (and in particular technical presentation) best practices. It would be different from the formal presentation course in that this course would be more of a discussion of current best practices and style along with some demonstrations and the chance for participants to present and try out different styles and techniques in a sandbox. In particular this would again hopefully target the more junior technical people starting out on their technical career to try and guide them in terms of presentation content and style.
The two books that will be referenced during the talking are:
- Give Your Speech, Change the World: How to Move Your Audience to Action (Paperback)
- Made to Stick: Why Some Ideas Survive and Others Die
Here is the presentation that I gave:
Further reading on some of the topics we covered yesterday can be found here
- Asset findability and The good, bad and the ugly
- Asset findability and The multi bucket problem
- Asset resuse and Terminator 2
- Topic Maps and the London underground
The following material are also relevant
Also links that came out of the presentations
Wednesday, January 7, 2009
I'll be back - the problem with asset reuse
Context | Value |
Where | North America, California, LA, mall |
When | June 8th, 1995 |
Who | Terminator (reprogramed as a protector) |
What | Ensure the survival of John Connor |
What - immediate | Persue John Connor |
How | At all costs |
- Confine ourselves to simple assets e.g. use the pony and trap as against the Fat Boy
- Better educated the practioners in the use of complex asset
- Engineer or re-engineer complex assets with a view to achieving an acceptable balance between effectivity and complexity
Saturday, September 6, 2008
To iPhone or not to iPhone?
From The hogs 8/9/... |
- Did you know that President Ronald Reagan make the GPS system available for public use following the shooting down of Korean Air Lines Flight 007 in 1983,
- Did you also know that the pix above of our hogs was taken outside that quaint Harvard general store and since I took it with my iPhone camera is it also geotagged and you can see it on the map here