Churchill on Risk Management

Here’s an excellent quote form Winston Churchill, eminently applicable as the proper attitude to adopt in risk management.  The sentence comes after Churchill summarises the beliefs and convictions taken by the then British Prime Minister Neville Chamberlain on what Hitler will do the the limits of what he will do, taking the position that he (Chamberlain) has taken the measure of Hitler, and that he (Hitler) has satisfied his territorial conquest needs:

“The Prime Minister is persuaded that… He believes that… Mr. Chamberlain is convinced that… But all this lies in the region of hope and speculation.  A  whole set of contrary possibilities must be held in mind.  He may ask us to submit to things which we cannot endure; he may be forced to ask us to submit to things which we cannot endure.”  (Churchill, the Second World War Volume 1, The Gathering Storm)

I like this ‘a whole set of contrary possibilities must be held in mind’ assertion.  For this is what risk management is about – that things may not work out as we thought, or hoped, and we must be able to survive and recover when they do.

The Ten Qualities of Good Requirements

A solid database design provides a firm and extensible base an organisation’s data.  A well-architected solution brings with it a sense of integrity and elegance that allows systems to be extended easily, and yet retain its integrity.

If any of these are badly done, the resulting solution is flaky, troublesome, and a menace to update.

But bad requirements are even worse, for they are our map to what should be built.  If the requirement is wrong, the solution built is wrong.  If the requirement has gaps, then the solution will have gaps.  If the requirement is misunderstood, then the solution is wrong.

There is an art to producing requirements.

1. Requirements Must Have an Owner

2. Requirements Must be Singular

3. Requirements Must be On the System and Not the Operator

4. Requirements Must be Unambiguous

5. Requirements Must Not Specify the Solution

6. Requirements Must have a Rationale

7. Requirements Must be Tied to the Concept of Operations

8. Requirements Must be Justified

9. Requirements Must be Prioritised

10. Requirements Must be Contextualised

Comparing the BABOK and the SEBOK, Part 5

I want to take a second look at the Knowledge Areas identified by the BABOK and those by the SEBOK, specifically where there is an overlap between the two sets. 

I want to do this in preparation for a deeper comparison of their treatments of their Knowledge Areas and Tasks and Activities.

The table below lists the Knowledge Areas for the BABOK, and what to me might be the corresponding Knowledge Area addressed in the SEBOK.  As can be immediately seen, the SEBOK Knowledge Areas cover a lot more topics.

BABOK Knowledge Area	SEBOK Knowledge Area	Remarks
	Systems Fundamentals
	Systems Science
	Representing Systems with Models
	Systems Approach Applied to Engineered Systems
	Life Cycle Models
	System Deployment and Use
	Product and Service Life Management
	Systems Engineering Standard
Business Analysis Planning and Monitoring
Elicitation	Concept Definition	This SEBOK KA contains the following Activities: Mission Analysis Stakeholder Needs and Requirements
Requirements Management and Communication	System Definition Systems Engineering Management	“Requirements Management” is very briefly treated in the SEBOK under the “System Requirements” topic, which is under the System Definition KA. Configuration Management is considered part of the BABOK KA “Requirements Management and Communication”. In the SEBOK, Configuration Management is discussed under the Systems Engineering Management KA
Enterprise Analysis	Concept Definition	This SEBOK KA contains the following Activities: Mission Analysis Stakeholder Needs and Requirements
Requirements Analysis	System Definition	The topic of "System Requirements” addresses assessing the quality of the requirements and their prioritisation. System Requirements is a topic under the KA System System Definition
Solution Assessment and Validation	System Realization	This SEBOK KA contains the following Activities: System Implementation System Integration System Verification System Validation
	Product Systems Engineering
	Service Systems Engineering
	Enterprise Systems Engineering
	System of Systems
	Enabling Businesses and Enterprises
	Enabling Teams
Underlying Competencies	Systems Thinking Enabling Individuals
	Systems Engineering and Software Engineering
	Systems Engineering and Project Management
	Systems Engineering and Industrial Engineering
	Systems Engineering and Procurement / Acquisition
	Systems Engineering and Specialty Engineering

In the next post on this topic, I will start comparing the contents of the matching Knowledge Areas.