Two Approaches

Why do we Write Things Down?

Dave Couture has given an excellent analysis of the principle of Viewpoints (Owner, User, Developer), and why viewpoints are useful.

Single vs. Multiple Documents

One of our challenges revolves around a concern for a “single document”. Even in this day of knowledge bases, hyper-links, search engines etc., we see a deep-seated preoccupation – a desire to put everything into a single file. Just yesterday, I heard somebody at a very large client tell me about the huge burden they have with each individual document going through their approval process. They tell me that if they have 30 pages of information to be approved, it makes a big difference whether that is in three documents or one.

This posting is inspired by comments from Dave Couture - in the discussion of Viewpoints. 

Macroscope embodies a very powerful principle of system ownership by the business. One of the major implications of this principle is to assign key responsibilities to the BSM role - with a supporting team drawn from the business, not from IT.  And Macroscope clearly defines the ideal qualifications of the BSM - deep business knowledge, excellent relationships inside the business - and uppermost - being clearly identified as "from the business", not IT.