Inconsistent within book

SD 4.6.4.3 five or six elements?

Submitted by skeptic on Fri, 2009-10-30 09:20

Page 143 mentions the five elements within the framework are as follows:

However the book actually mentions 6:

1. Control

2. Plan

3. Implement

4. Evaluation (should be evaluate – see figure 4.26)

5. Maintain

6. Security governance

This would make the ISMS (figure 4.26) either incomplete or wrong

ITIL V3 Service Operation disconnect between Incident and Problem Management

Submitted by skeptic on Mon, 2009-09-07 08:40

There seems to be a major disconnect between ITIL V3 Incident and Problem Management.

Known Error sub-process

Submitted by aroos on Wed, 2008-10-22 07:44

There are two references to Known error sub-process in the SO book.
For example Chapter 4 states:
Problem Management involves root-cause analysis ... and a Known Error sub-process to allow quicker diagnosis and resolution if
further incidents do occur.

In the Problem Management Process there is no reference to this sub-process and I cannot find the description anywhere.

CSI Model diagram

Submitted by Alison Adams on Mon, 2008-03-24 11:55

The CSI Model diagram on pages 15 (fig 2.3) and 30 (fig 3.2) both start with "What Is The Vision", followed by "Where Are We Now".

Page 163 of the same book has fig 8.4 also described as the CSI Model but without "What Is The Vision" step, starting instead with "Where Are We Now".

Clarification/justification required urgently as an exam question in V3 Foundation hinges on an understanding of what is the first step of the CSI Model.

Source: Robert Falkowitz on the itsmfi forum

Release management also defines release policy

Submitted by aroos on Sat, 2008-03-15 07:58

Transition planning defines release policy [ST 4.1.4.2 p 36], which makes sense. Release management [ST 4.4 p84] also defines release policy which makes less sense.

the new name for Configuration Management, SACM

Submitted by aroos on Sat, 2008-03-15 07:56

the new name for Configuration Management, SACM appears only in the process itself. Not even the authors of other chapters in the same book are aware of the name change.

ST p223 CAB/EC to ECAB

Submitted by vinodka on Tue, 2007-11-20 16:59

The 'not-so-obvious' V2 abbreviation of CAB/EC (CAB Emergency committee) for the subset of CAB taking decisions on emergency changes is changed to EmergencyCAB or ECAB. No objections to that.

Note: Even I saw a question on this in the foundation paper regarding who authorizes emergency changes - where both the options were given!! If you missed this change in V3, you (I mean V2 aware people) can rest assured that you lost one mark!

Now about the inconsistency:

Syndicate content