The Curious Engineer

All blogs / Software / engineering practice

Inside Architecture

learn.microsoft.com/en-us/archive/blogs/nickmalik

Notes on Enterprise Architecture, Business Alignment, Interesting Trends, and anything else that interests me this week...

Software / engineering practiceEngineering management / careersMicrosoft blogsMSDN archive

’05’10’15’20’25
Posts
632 from 14 Sep 2004 to 13 Sep 2016
Posting
archived, read-only
Kind
personal blog
Feed
https://learn.microsoft.com/en-us/archive/blogs/nickmalik/feed.xml

2016 1

  1. Where Is Nick Blogging Now?

2015 5

  1. Never Waste A Good Crisis
  2. Sharing the Solution Domain Taxonomy
  3. Alternatives to the EPSC Model
  4. How brand-thinking can kill you, and capability thinking can save you
  5. Moving Towards a Theory of Enterprise Architecture

2014 10

  1. Do you perform Information Architecture or a Data Architecture?
  2. The Architecture Manager – the Forgotten Enterprise Architecture Role
  3. When does EA start to care about sociocultural influences?
  4. Call to survey – Is your EA program valuable?
  5. Being Forgotten in the Internet of Things
  6. EA Debt
  7. Enterprise Initiatives – A Train Built By Monkeys
  8. Does anonymity promote ill-informed consensus?
  9. Business Architects: What’s at the “core”?
  10. Climbing the ladder from EITA to EA

2013 22

  1. Enterprise Architecture as Story
  2. Diversity Versus Replication of Organizational Processes and Information
  3. The Purpose of an Enterprise Architecture Framework
  4. What makes models interesting
  5. Ten Ways to Kill An Enterprise Architecture Practice
  6. Enterprise Architects are more than “problem solvers”
  7. Business Architects: Do Not Start With Strategy
  8. Business Models in Business Architecture
  9. We do what you say we will do – Integrity By Architecture
  10. Placing Architecture Properly into Scrum Processes
  11. A practical set of EA deliverables
  12. The “Right” Representation of the EA Value Cycle
  13. Accelerating Business Architecture
  14. How to Become a Hero for Growth
  15. Unraveling the Developer Bias in Agile Development Practices
  16. Has in-person communication become the unwilling victim of technology?
  17. AGILE architecture vs. agile ARCHITECTURE
  18. Humility and the Art of Enterprise Architecture
  19. Should Business Architects use the Business Model Canvas at the Program level?
  20. Rumination on the concept of “best practice”
  21. All Effective Enterprise Architects Are Agile
  22. The most important personality trait of an Enterprise Architect

2012 29

  1. Steps To Create a Core Diagram
  2. Everything you’ve read about IT Project Failure is wrong
  3. The Story behind “Stories That Move Mountains”
  4. Is Enterprise Architecture accountable for improving customer experience?
  5. Many (flawed) Definitions of Business Architecture
  6. Taking a Careful Slice – Defining Business Architecture
  7. Podcast on the Enterprise Architecture profession–Interview with CIPS’s Stephen Ibaraki
  8. The EA Metamodel behind the Business Model Generation
  9. Aligning the EBMM with Archimate
  10. Speaking at TechEd New Zealand on Business Architecture
  11. Will Enterprise Architecture Ever “Cross the Chasm?”
  12. Positioning an Enterprise Architect for Success
  13. Conversational Antipatterns on Message Boards
  14. On My Move To Consulting Services
  15. Three Schools of Thought for Enterprise Architecture
  16. Setting Up A New EA or BA Practice
  17. EA Certifications Distilled
  18. On the road to a Business Architecture Manifesto
  19. Should We Kill The Architecture Review Board?
  20. Podcasts with the Canadian Information Processing Society
  21. Analysis, Synthesis, and Scope: Business Architecture vs. Business Analysis, part two
  22. The difference between business architect and business analyst
  23. Time-to-Release – the missing System Quality Attribute
  24. How Enterprise Architects can cope with Opportunistic Failure
  25. MSBI–Part 2—What is a core diagram?
  26. Creating a Core Diagram for Agile Business
  27. Do you address the complaint, address the root cause, or both?
  28. A Modern Update to The Blind Men and The Elephant
  29. Wikipedia’s EA article, second pass

2011 31

  1. Customer 2.0 Strikes
  2. Wikipedia and the definition of Enterprise Architecture
  3. Using Enterprise Architecture To Get The CIO To The Strategy Table
  4. The End of Flash
  5. To create a roadmap, we need to know what it is supposed to accomplish
  6. Governance in an Organic Enterprise
  7. When IT Architects Describe EA to other IT Architects
  8. Explaining Capability Modeling to Business Process Professionals
  9. Enterprise Business Motivation Model version 3.5
  10. Finding Common Ground: in response to a BPTrends article on Process and Capability
  11. The Rule of EA Governance
  12. What EA Means to One Agency of the Federal Government
  13. Putting the brakes on “capability obesity”
  14. Business Strategy and Kindergarten Soccer
  15. EA Schools of Thought
  16. Video Podcast: How Microsoft Does Enterprise Architecture
  17. IT is part of the business, but not for the reasons you think
  18. On the Hunt for the One-Page View of an Enterprise
  19. Has the concept of “alignment” entered the infamous “trough of disillusionment?”
  20. Metamodel 101
  21. Segment Architecture in a Commercial Setting
  22. Myths of Microsoft Culture
  23. The ivory tower is a distant memory
  24. Perhaps the most valuable conversation you can have… starts with a question
  25. The responsibility of architecture is to create an architecture of responsibility
  26. It’s not about cost savings… it’s about value
  27. The difference between selling EA and performing EA
  28. Three word definition of Enterprise Architecture: Reduce Unnecessary Effort
  29. What is misalignment?
  30. The Day that Star Trek Died
  31. In the white space between stakeholders

2010 59

  1. Essential Project–Open Source EA Metamodel
  2. Can EA Data be independent of the Metamodel?
  3. Kudos to Cambridge for refusing to cover up security holes in “Chip and PIN”
  4. Enterprise Architecture and the Lessons of History
  5. How (not) to convince an architect
  6. Will Wikileaks be responsible for the next attack on the United States?
  7. Creating a compelling visual story
  8. EA Leadership and Compromise: Sometimes, success is not what you think it will be
  9. The Little Town of Busit
  10. Are we documenting the wrong things?
  11. Enterprise Architects Are The Gears, Not The Grease
  12. Business Architecture Apprentice Training Model
  13. How many business architects do you need?
  14. How to know if your application is “strategic”
  15. Cool Idea – replacing the escalator
  16. Enterprise Strategic Architecture in Product Development
  17. Can Federal EA ever include the full scope of Enterprise Architecture?
  18. Linthicum’s Challenge: Where does SOA stop and EA start?
  19. A roadmap to BPM democratization
  20. Who among us uses the EABOK?
  21. Enjoying the BPM 2010 Conference
  22. Evolving the Enterprise Business Motivation Model
  23. Assumptions under a Zachman Framework presentation
  24. Introducing: Ecosystem Quality Attributes
  25. On vacation
  26. When demand management is confused with alignment…
  27. The Mission, Capabilities, and Business Output of Enterprise Architecture
  28. A reasonable canonical definition of Enterprise Architecture
  29. Tangled
  30. Avoiding Business Architecture Paralysis
  31. Can Enterprise Architecture be effective if we ignore the needs of the customer?
  32. Zachman’s Fatal Flaw: No Row for the Customer
  33. Our own worst enemy: BPM pros tell horror stories about working with EA
  34. A Rough Primer on Enterprise Architecture
  35. Creating context between BPM and EA
  36. Design for Business Agility: Can Mathematical Models be developed?
  37. Inserting Architectural Governance into the IT Program Funding Cycle
  38. Improving how you measure the maturity of a business capability
  39. It has value… but do you need it?
  40. What process gives a tool to a fool?
  41. Is the concept of a “roadmap” working against Enterprise Architecture?
  42. Update to Blogging Site
  43. Doing Business without EA is like building a chain of “open” links
  44. Drawing Effective Technical Diagrams
  45. Service Oriented Architecture Conceptual Model
  46. Building less than you know you’ll need
  47. Does app portfolio simplification solve the wrong problem?
  48. Azure – Practitioners Guides
  49. How the Program Management Office Views Enterprise Architecture…
  50. Should IT run “like a business” or “like a non-profit?”
  51. Is there a Minimum Age for Enterprise Architect
  52. What does the brand of “Enterprise Architect” stand for?
  53. The cost of “SOA-fication”
  54. Business Architecture --- includes process architecture?
  55. Job Description for Business Architecture
  56. When feasibility of integration is a measure of capability…
  57. When Traceability is a “Bridge to Nowhere”
  58. Architects Working Alone
  59. Read A Little Blasphemy

2009 46

  1. Why the Zachman Framework is not an ontology
  2. Does IEEE-1471 Define Enterprise Architecture?
  3. Modeling User Experience Scenarios
  4. How to Develop a Governance Program (that doesn’t suck the life out of your organization)
  5. Collaboration without common values is fruitless
  6. The most difficult things
  7. The Value of Enterprise Architecture
  8. Does EA need a name change?
  9. Microsoft annual Day of Caring becomes part of National Day of Service
  10. On becoming and being a Mensch
  11. SOA Optimistic Data Synchronization considered harmful
  12. Why Business Capabilities are not in the Zachman Framework
  13. Work-back Enterprise Architecture
  14. When is the “flow” in a use case part of the system requirements?
  15. Very Funny – Trailer for Office 2010 – The Movie
  16. Why strategy statements are necessary, but insufficient, solutions
  17. Should some requirements be called out as “architectural” requirements?
  18. The Semantic Language of Architecture
  19. Suggested Curriculum: MBA in Business Architecture
  20. reworking my Architecture blogroll
  21. Test yourself: 25 most dangerous security programming errors
  22. Why “good” doesn’t happen
  23. Make IT appear as simple as possible, but not simpler
  24. Architecture makes Agile Processes Scalable
  25. When Johnny comes marching home medicated
  26. Are we ready to prove the “Architecture hypothesis?”
  27. The Process of Strategic Planning
  28. Ouch
  29. Rubik’s Enterprise Architecture
  30. Why Agile Development Requires Agile Architecture
  31. Towards an Enterprise Business Motivation Model
  32. Reducing IT overhead by managing the list of IT standards
  33. Will there be a battle between Archimate and the UML?
  34. All the questions fit to answer
  35. Systematic Simplification
  36. An interesting EA Maturity Model
  37. Collecting requirements from business processes
  38. How do you measure Enterprise Architecture?
  39. Is it time to create an MBA in Business Architecture?
  40. Update to root cause analysis for poor software requirements
  41. Understanding the root causes of poor software requirements
  42. Architecture in a hot air balloon
  43. A first look at TOGAF 9.0
  44. On the federated ownership of a conceptual domain
  45. Ship It!
  46. An examination of the OMG Business Motivation Model

2008 71

  1. Feedback requested: Information driven process design
  2. Understanding SOBA
  3. Adopting a new technology like Oslo
  4. Creating a distinction between business services and SOA services
  5. Software Reflects The Process That Creates It
  6. Using the PMO to measure the behavior of the customer
  7. The business value of elegant design
  8. The bizarre assumption of functional decomposition
  9. Non-Functional Requirements: the "All-Other" classification
  10. "Correct" is a point of view
  11. Alignment - the missing Viewpoint
  12. Understanding Governance as Decision Rights
  13. Extending Professional Software Architecture
  14. Input sought: Actor - Role - Process Activity... an interesting domain model question
  15. It takes a village to raise an idiot (Wiki Non Wisdom)
  16. On IEEE-1471
  17. EA Poster - The Business Functions of Enterprise Architecture
  18. Clarifying the Concept of Metadata
  19. Civil Engineering Analogy to Enterprise Architecture: Flawed
  20. How BPM does, and does not, support people
  21. What do .Net Solution Architects need to know?
  22. Applying DDD to IT Management: First failure
  23. Working in the dark
  24. Traceability, the Solution Model, and Metamodeling
  25. Malik's Laws of Service Oriented Architecture
  26. Merging EA Frameworks
  27. Enterprise SOA needs a Federated Evolutionary Modeling Environment
  28. Excellence depends on the environment you are in
  29. Everybody, Somebody, Anybody, and Nobody
  30. Clarifying the Use Case
  31. Using Business Process Models as the source for software requirements
  32. Building Conceptual Models, Building Relationships
  33. Graduation
  34. Growing Rice in the Desert - the Garden of BPM
  35. As the sun rises on Web2.0, what to do about companies that 'don't play along?'
  36. Preventing Ownerless Activities -- the "Blame the Computer" process modeling antipattern - part 2
  37. Why Automated BPM will never live up to its hype
  38. New eyes on an old favorite
  39. Blame the Computer: A Business Process Modeling Anti-pattern
  40. Open Question: Common vocabulary: Blessing or Curse?
  41. The Usefulness of the Use Case?
  42. An open question about Enterprise Architecture, the noun
  43. One EA Team, Three EA Functions
  44. The non-overlapping responsibility set: Solution Architect and Enterprise Architect
  45. Example of modeling requirements in a process diagram
  46. How FEA handles Capability and Process Modeling
  47. IT to Business: "I won't read your mind"
  48. Leaving technology out of requirements gathering
  49. As-Is versus To-Be... what to model first
  50. Rant: Avoiding the Problem Duck Hunt
  51. Merging Capability Modeling with Process Modeling
  52. Measuring Maturity in BPM - Automation is the wrong answer
  53. The ROI of Building an Internal Community
  54. Root Cause Analysis for Software Problems
  55. Put perspective on both short and long term problems
  56. The Problem with Process
  57. JaBoWS is the Enemy of Enterprise SOA
  58. Right-sizing the Event Message
  59. Why can't Open Source be used to fix problems like this?
  60. Enterprise Architecture: Earning our keep
  61. Inversion of control, part two
  62. Teaching Science with Mythbusters
  63. Introducing the "Double Iron Triangle" of Enterprise Architecture
  64. What is the tradeoff with Inversion of Control (IoC)
  65. Want the Software Quality Attributes of a service? -- ask the customer!
  66. Standardization works with a limited, and rational, scope
  67. Standards and Innovation
  68. The future can be seen, if we decide to look
  69. Engineering for Serendipity
  70. Towards a shared global integration model
  71. Flattened by the flu

2007 158

  1. RIP Netscape
  2. Measuring Risk in Application Portfolio Management
  3. Measuring the agility of a SOA approach
  4. The battle for the net-top heats up
  5. Fitting SOA+BPM into the software lifecycle
  6. Get BPM into IT project funding
  7. Alignment through "honeypot" funding
  8. IT Funding Processes
  9. What's in your wallet?
  10. All bloggers are Customer 2.0, but not every Customer 2.0 is a blogger
  11. Focusing on Customer 2.0
  12. Politically, Can I live without an enterprise canonical data model?
  13. SOA in the Diversification Model
  14. SOA in the Replication Model
  15. SOA in the Unification Model
  16. SOA in the Coordination Model
  17. SOA and the CISR Operating Models
  18. A Tale of Two Visions
  19. If you don't like the senator's politics, attack his clothing
  20. The culture of art vs. the culture of engineering
  21. The New Life of Joe - Part Three - The Users Are Coming!
  22. The new life of Joe - Part Two - Managing Complexity
  23. The New Life of Joe - Part One - Off to a cold start
  24. Asking IT to perform Business Process Management...
  25. Paying for SOA
  26. Momentum and Inertia
  27. SOA Economic Model: Avoiding Chargebacks with Transaction Ratio Funding
  28. Good intentions - bad SOA
  29. Creating a constrained definition for a measurable business process
  30. How often do I get to be part of the "next" big thing?
  31. WSPER quietly, then go away
  32. Beware of SOA in a box
  33. Washing fences
  34. SOA drives an odd data model
  35. Replace SOA Governance with SOA Marketing
  36. IBM comes around, agrees with Microsoft on SOA
  37. When they are not ready...
  38. Enterprise Architect: Breadth, Depth, and Interchangable Parts
  39. Actionable Enterprise Architecture through Feedback
  40. Agility, Feedback, and Enterprise Architecture
  41. Business Case for Integration, part two
  42. Is it time to bring the FEA concepts to the commercial space?
  43. Agile Enterprise Architecture
  44. The Business Case For Integrated Systems
  45. SOA and BI support the same goals
  46. Writing down thoughts - harder than it should be
  47. The perfect service oriented architecture is... small
  48. Does APM reduce cost? That depends.
  49. Put a ruler to the blueprint... is it useful?
  50. We are going to miss... do we stretch out the Sprint?
  51. SOA is not a disruptive technology (selling SOA, part three)
  52. Politecture
  53. A Maturity Model for Data Integration
  54. When we talk to the business, should we sell SOA?
  55. EDA: Avoiding "coupling on the name"
  56. I want one of those SOA thingamajiggies
  57. When do you need an abstraction
  58. Killing the Command message: should we use Events or Documents?
  59. Binding SOA to BPM instead of BPM to SOA
  60. The business services of SaaS
  61. Putting Application Portfolio Management into the picture
  62. Why Business Process Management is more than BPEL
  63. Free Code - Getting IT out of the Applications business
  64. Using Massive Multiplayer Online Concepts to Build a Shared Architecture
  65. How is Business Process Management related to Service Oriented Architecture?
  66. Should corporate bloggers go "internal only?"
  67. All models are wrong, some models are useful
  68. What you need to make middle out SOA architecture work
  69. SOA without executive support
  70. Is Durability in messaging 'bad'? Libor thinks so.
  71. Mort no more - A whole new list of "developers"
  72. What are the requirements for enterprise event security?
  73. Avoiding the Ivory Tower
  74. Building a better horse
  75. Random thought on ethics and rights
  76. Applications ARE the leaky abstractions
  77. Having something to govern with
  78. Windows Logo on the steering wheel
  79. A little forced time off
  80. How do I fix the broken stuff?
  81. Bottom-up SOA is harmful and should be discouraged
  82. Getting the Enterprise Canonical Data Model right
  83. As the role changes...
  84. What I like about Acropolis
  85. The Unimportant SOA Catalog
  86. Enterprise IT Integration and Data Security in the Canonical Data Model?
  87. Simple Lifecycle Agility Maturity Model
  88. Mort and the Economics of Unmaintainable Code
  89. Tools for Mort
  90. Microsoft ESB as a toolkit
  91. Martin Fowler wants to see Ruby on Microsoft to save the alpha geek
  92. Canonical Model, Canonical Schema, and Event Driven SOA
  93. Showing up can be the hardest part
  94. What is the REST high-order bit?
  95. Waterscrum vs. Scrummerfall
  96. Debunking SOA myths
  97. System Reliability requires Message Durability (immature WCF)
  98. Reliability in SOA is HUGE
  99. Go Build an Enterprise Architecture
  100. Is an entity service an 'antipattern'
  101. Layers and Layers of Services... yep... no confusion there
  102. Why you need an Enterprise SOA Planning Governance Framework
  103. Partitioning in an Integrated System Design
  104. The Value of Intermediation, part two
  105. The value of Intermediation in SOA
  106. Excellent Primer on Canonical Data Models
  107. Is it Service Oriented if the message cannot be intermediated?
  108. Happy Mother's Day
  109. Mining for Services with Solution Domain Architecture
  110. Bad assumptions yield false conclusions
  111. Why "Service Oriented Analysis and Design" Starts Late and Ends Early
  112. SOA by Wiki
  113. Testing in a SOA world
  114. Improper use and the SOA free market
  115. Redefining SOA Governance
  116. SOA Governance - Software is about 20 percent
  117. One more word for the heap: governance
  118. To boldly crawl where no one has crawled before
  119. SOA Question: should we carve service independence into the database?
  120. Is Central Planning impossible?
  121. Simplification happens
  122. When "Quick Win" is an oxymoron
  123. Relinquish control... trust the Wiki
  124. Architecture... Is it code, or is it data?
  125. Self Improvement in a team
  126. Microsoft, BPEL and Open Standards
  127. If you don't trust your experts, how expert are they?
  128. Getting a system to consume a "fictional" service
  129. Web 2.0 vs. the IT department
  130. Understanding Enterprise Architecture
  131. When a task consumes your life
  132. Hero or Rebel
  133. So what's in a roadmap, anyway?
  134. fun activity for kids: count to 1000 on your fingers
  135. Sharepoint Business Data Catalog and system adapter patterns
  136. An Agile Business Planning Model
  137. Perhaps it is time to declare victory in the battle of Rules Engines vs. Dependency Injection
  138. The importance of a name
  139. Top 100 patterns: Building from a nascent catalog
  140. Top 100 patterns: how to pick the list
  141. Why create a list of the top 100 patterns?
  142. What are the top 100 patterns that every developer must know?
  143. The minimum amount of architecture needed for Test Driven Design
  144. IFaP : Middle Out Architecture
  145. The best employee I ever had
  146. A case study in breaking up a tightly coupled integration
  147. Managing the bindings from systems to EAI infrastructure
  148. What about a Software Development Guild?
  149. Gently pushing
  150. Systems Architecture Interview Questions
  151. What do you want said at your funeral?
  152. Case study: create and use Platform Goals to reduce churn
  153. IT Parable: It's 10 o'clock... do you know where your requirements are?
  154. Should IT report to the CFO?
  155. Should a performance cache query run through your EAI hub?
  156. Your SOA is JABOWS (Just A Bunch Of Web Services) and I can prove it
  157. Apply API design guidelines to SOA?
  158. Build TDD adoption through Support-First efforts

2006 137

  1. Taking your name off of a project
  2. Internet-wide Services Integration Architecture needed now!
  3. The roadblock to Software As A Service
  4. Declaring architecture in the code
  5. A SOA Infrastructure Reference Model
  6. Finally got to read the SOA Reference Model from OASIS
  7. Requirements for an Enterprise Service
  8. Encouraging Enterprise Services
  9. Should SOA be Top Down or Bottom Up
  10. Is SOA just an implementation of Responsibility-Driven Architecture?
  11. Responsibility Driven Architecture
  12. Enterprise vs. Application Architect
  13. Should the name of a department be encoded in a namespace?
  14. Enterprise Architecture Lessons from City Planning
  15. Stories
  16. Is there value in consistency?
  17. Can your software be TOO functional?
  18. Iterative... agile... architecture
  19. Should our next generation of languages require us to declare the applications' architecture?
  20. Introducing a culture of code review
  21. going quiet for a while
  22. Should an interface be stable when semantics are not?
  23. Change agent, change administrator?
  24. Should Enterprise Architecture rock your world?
  25. Architecture as eye candy
  26. Alas, We must differ...
  27. SOA and database coupling
  28. declared, visible, and open coupling
  29. What would you say are the requirements that all services should meet?
  30. We do Scrumbut
  31. What SHOULD a sequence diagram show?
  32. What is the scope of a governance project?
  33. Speaking to "yes"
  34. If you don't lead, others will
  35. Lead and harness the passion in those around you
  36. Definition of an architectural model
  37. A distributed systems' logical data model
  38. Claiming credit
  39. multiple architectures - many ghosts in the machine
  40. On Work Life Balance, burnout, and EA
  41. The event driven Persistent Data Grid
  42. When to stay redundant
  43. The architecture that people fight about
  44. We will miss you, Steve
  45. Selling the EA story
  46. The blurry line between event driven data management and grid architecture
  47. Unit tests do not solve every problem... but they do solve a few...
  48. Contribute to Event Driven Architecture
  49. Say "no" to the ever-creeping meeting request
  50. Clear responsibilities, clear leadership
  51. Just how to best describe an interface
  52. Creating a set of shared principles
  53. Facing uncertainty in your architecture
  54. Sitting, silently, spinning
  55. The gift that keeps on giving
  56. The corporate IT balancing act: agility vs. stability
  57. Third attempt - definition of an application in a SOA environment
  58. Agreement, Consensus, Unity and other fables
  59. Corporate personal bad habits
  60. If your app uses MSDE and you want it to run on Vista... UPGRADE to SQL Server Express
  61. The art of listening
  62. Be careful of the 'stack' diagram
  63. Mistakes in the business show up in IT
  64. Finding the Root Cause of IT Systems Complexity
  65. Achieving a balance between policy and process
  66. Simplification requires dev capacity - like aircraft maintenance
  67. How to get IT involved in projects earlier
  68. Winning by whining
  69. When an executive "assigns" a task to a department, does that change it's purpose?
  70. Social process development, ERP, and Software as a service
  71. Things I learned on vacation with kids
  72. Manual administrative process - to automate or to discard
  73. An apology, and opportuniity, and a promise
  74. The SOA and simplification paradigm shift
  75. Just when is standing your ground a Career Limiting Move (CLM)?
  76. Becoming more visionary
  77. Giving names to two different roles within Corporate IT Governance
  78. The difference between creating a new app and updating an existing one
  79. Can we measure agility? Can we afford not to?
  80. Don't walk in with a problem until you have a solution
  81. Cop out: failing to perform app portfolio management
  82. Is IT a commodity that a corporation would be well-justified to outsource?
  83. Who owns the application, the process, and the solution?
  84. Can a committee simplify anything?
  85. Seperating Simplification Patterns from Migration Patterns
  86. Simplification patterns as a subset of migration patterns
  87. Family loss -- offline for a week
  88. Patterns of IT Simplification
  89. The leader of the band is tired...
  90. A single taxonomy of business capabilities
  91. Just say "no" to your architect
  92. Consider: are there Patterns of IT Simplification?
  93. Leverage, Buy, Build - the EA Simplifiation Motto
  94. Pent up Karma - 2 HD failures in 3 days
  95. Allowing feedom within the machine
  96. What incentives lead to an optimum portfolio?
  97. Help wanted: who pays to simplify your IT portfolio?
  98. Do we need a new measure of software complexity to calculate the TCO of a portfolio?
  99. Architecture is an attitude, not a model
  100. How Enterprise Architecture enables Web 2.0
  101. Is IT software development BETTER than embedded software development?
  102. Ahead of the curve... again
  103. We didn't start the fire, so when do the hoses arrive?
  104. The service repository concept is incomplete
  105. What is a SOA application, part deux
  106. SOA Services are Guilty until proven Innocent
  107. The Elevator Speech: Why Workflow
  108. In the SOA world, what does the word 'application' mean?
  109. Maria will find out
  110. Design review is not a test of your UML skills
  111. TCO and the number of applications
  112. IT Capabilities Assessment tool... ?
  113. Jacob and the data
  114. Will WCF Indigo empower SOA in your enterprise
  115. Governance is knowing who holds the key
  116. When good design is not an accident
  117. When emergent design doesn't
  118. Why a workflow model is not code
  119. Interesting tool for schema-first design
  120. If we improve a process in a forest, and no one hears it... did it happen?
  121. What standards to enforce, and who are the enforcers
  122. Do we have the courage to take ourselves out of the loop?
  123. Would a six-sigma business architect support Agile methods?
  124. No one will read it
  125. Better software cost estimation tools are needed
  126. Paying to get to the new Enterprise Architecture
  127. Patterns and the Peter Principle - The positive effects of recognizing good application design
  128. A service by any other name...
  129. The Estimation Game: Do not confuse cost with size
  130. Agile definition: Chickens and Pigs
  131. Workflow visibility: driving levels of abstraction into functional requirements
  132. Project Management Antipattern 3: Guesses for Estimates
  133. Project Management Antipattern 2: Pardon My Dust
  134. I have a dream of software
  135. Using BITS to move private data
  136. Does SOA make eXtreme Programming (XP) obsolete?
  137. Project Management AntiPattern - PMs who write specs

2005 43

  1. Recollections on a year of change...
  2. Deciding what web services to build
  3. Coding Dojo Suggestion: Template Method Kata
  4. Application Adolescence
  5. SOA: The data aggregation layer
  6. SOA: Good fences make good neighbors
  7. For those of you who think that services solve everything...
  8. SOA: How to design a service
  9. Futurist wanted
  10. Measuring EAI Maturity
  11. Is placing the assembly in the database next?
  12. Developer accountability? How about PM accountability!
  13. Ajax and Soap, again
  14. Is SQL XML a bad idea?
  15. Killing the Helper class, part two
  16. Coding Dojo concept: one kata for each common design pattern
  17. Why Ajax can be safely ignored for a SOA adoption program
  18. Are Helper Classes Evil?
  19. Whose name is in the namespace?
  20. On Atlas/Ajax and SOA
  21. The link between strategy and standards
  22. Enterprise Architecture Agility
  23. Is it a change request?
  24. Coding Dojo suggestion: the decorator kata
  25. Developing a standard for naming web services within the enterprise
  26. A Case For and Against the Enterprise Library
  27. Preparing for Indigo -- an addition
  28. Agile also means fall early and get up
  29. Considering: Temporal database relationships
  30. Atlas = Ajax = asp.net 2.0 script callbacks and more
  31. Having a High Bus Factor
  32. SOA: Introducing the Business Event Schema
  33. Interesting problem in VS 2003 and how to fix it
  34. Nick's Law of Agility
  35. Does SOA create a new class of defect: passive-agressive behavior?
  36. Maintaining the ACID test in long running transactions
  37. Feedback Requested: Are groups responsible for business processes?
  38. Feature Driven Development vs. Traditional Project Planning, part deux
  39. Draw the distinction between a message bus and a services bus
  40. Feature Driven Development: Dev is different than PM
  41. A direct comparison between FDD and Traditional WBS
  42. How to get rid of circular references in C#
  43. On Security in Workflow

2004 20

  1. C#: a way to get around the lack of multiple implementation inheritance
  2. How is workflow different from a Finite State Automata?
  3. On XML Models of Process
  4. steps to transition a client server VB6 app to .Net
  5. On being offered MVP status
  6. How to learn Object Oriented Programming
  7. Storing configuration settings for your DLL to use
  8. Three levels of abstraction in BPM - Part 1: Business Unit Level
  9. SOA and BLOBs -- using SOA principles for block-oriented data transfer (Updated)
  10. Stateless is to service as commandless is to data
  11. Using Service Oriented Architecture concepts for database replication
  12. How to encourage your outsourcing partners to avoid waterfall processes
  13. Agile Vendor Management - removing waterfall from outsourced projects
  14. Workflow patterns - so much more left undone
  15. The infancy of workflow diagramming standards
  16. Document Management as a foundational technology for Workflow
  17. YAWL -- must see TV for Workflow practitioners
  18. Is workflow best represented by something other than a graph?
  19. Messages vs. Documents in a Workflow System
  20. Three levels of abstraction in Business Process Management