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
 
Without Context, Every Open-Format Standard Is the...
 
Second-Guessing Microsoft on ECMA: Shape-Shifting ...
 
Lining Up Open Formats for Office Documents
 
Open Standards are not Open Source
 
Steve McConnell Beyond Myths of Rapid Development
 
The Distraction of User Personas?
 
Magical Thinking and the Universal Document Elixir...
 
My FUD is FUDDier than your FUD, so FUD this!
 
Agile Scope-Creep and How to Detect It
 
Sending Orcmid to (Code) Camp

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-12-22

 

Patterns: Starting in the Meta-Middle

It did not take long, during my investigations for TROST: Templates for Raising Open-Systems Trustworthiness, to determine that I had to figure out how to apply pattern languages.  This seemed perfect for characterizing activities that invest trustworthiness in software and related artifacts.  But digging into software-design pattern resources was unsatisfying.  Something was missing and I needed to seek out original sources tied to the work of Christopher Alexander in order to find a point of comprehension.  From there I could appraise recent work in software patterns, principles, and practices.  That approach worked.

Satisfied that I knew enough to begin applying pattern-language principles, I felt ready to set down some patterns of software development and deployment that reflect trustworthiness.  I began noticing patterns everywhere, and I made note of them.  I didn’t do much to articulate them.

My first barrier was settling on a format for pattern descriptions that is not locked too tightly to a software methodology.  The format must also be consistent with a stand for trustworthiness and how I symbolize it.  Finally, I was worried about refactoring pattern descriptions if I were to alter the format down the road and I wanted to be satisfied that I could tolerate any change that was called for. 

I have a format that I am now confident in being able to sustain with only minor adjustments as I record actual patterns.  The format features pattlets as summaries and as covers on expanded descriptions of patterns.  It lets patterns be developed progressively over time. 

This TROST Pattern-Template Approach is based on a ten-topic structure that can be elaborated as needed.  Although I have changed the usual nomenclature, the topics were synthesized from an analysis of several published formats.  It is not necessary to employ all ten features, though some are quite essential:

  1. Identification - how the pattern is known
  2. Situation - the setting in which the pattern can occur or be desired
  3. Intention - what is to be accomplished
  4. Concerns - issues to be balanced and addressed
  5. Approach - how to satisfy the intention - what to do
  6. Realization - strategy for specific implementations of the approach
  7. Considerations - additional matters to be aware of
  8. Consequences - the result of achieving the pattern: benefits and limitations
  9. Usage - actual cases, related patterns involved in completing the approach
10. Sources - acknowledgment of source materials and contributions

See TROST Pattlet Format for detail.

Now all I need are some worked examples that make sense of this nomenclature and how the format can be applied.   I’ve been shirking that.  I’ve avoided writing down patterns themselves using the format I have.  I distinguish patterns, I make notes about them, and I avoid documenting them. 

I think I’m afraid of my usual tendency to explode a can of worms and end up diverted from some critical work that I have on my docket.   The only way to dispel that is to get started and not be bashful about leaving dangling connections for filling in later on. 

Having the format is my starting point for arranging the actual content.  My next steps are to document those patterns that are applicable in work I am now doing, working my way toward building a pattern catalog and factoring out a pattern language.  It is interesting that I turn stupid in rolling up my sleeves for that.  I have no idea what formative childhood experience is being driven up with this, but I am confident there is one.


The summary of my approach was created as an appendix in my draft dissertation on TROST.  The appendix provided a brief summary and guide, with links to where the expanded description is found on the Internet.   I often write that way, making web pages and then writing a synopsis that then shows me a crisper way to present the material.  The synopsis may go on a blog or, in this case, into the back matter of a thesis.  I then back-factor the cleaner narrative to the web pages.   In this case, I’ve been sitting on that final step since late September.

Grady Booch has been blogging about the incorporation of patterns in his evolving Handbook of Software Architecture.  His December 10 post on the topic struck a chord with me and I sent him a link to my September 25th material.  Then on December 13–16 he posted some great information about sources and approaches, helping me to realize that I missed some key sources in my late summer researches.  On Tuesday December 18 he linked to my material and, gratified as I am for that, I’m suddenly embarrassed that company’s coming and I haven’t cleaned house.

OK, I dusted and swept and back-factored and refactored the pages and I’m now ready for the preservation-society tour.  Just don’t ask to see the kitchen.  [Oh, and bringing groceries in from the car just now, I got what it is about putting up actual patterns: fear.  I’m terrified.]

 
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 $