picture 1

model: ICT lifecycle in a company

1. business needs & business strategy1. business needs & business strategy

2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan

2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan

3. project feasibility - ICT project goals & objectives - gap analysis to-be vs. as-is(processes/ICT) - business case (cost&benefit analysis) - decision on package or in-house devel.

3. project feasibility - ICT project goals & objectives - gap analysis to-be vs. as-is(processes/ICT) - business case (cost&benefit analysis) - decision on package or in-house devel.

4. in-house development - analysis & design & implementation - tests - roll-out

4. in-house development - analysis & design & implementation - tests - roll-out

5. using packages - configuration - test - roll-out

5. using packages - configuration - test - roll-out

6. maintenance & support - user help desk - configuration management - risk management & security

6. maintenance & support - user help desk - configuration management - risk management & security

legacy situationlegacy situation(e.g. system architecture, (e.g. system architecture, bussiness processes, bussiness processes, applications&data)applications&data)

market conditions,market conditions,vision&mission statementsvision&mission statements

existing ICT systems,existing ICT systems,user requirementsuser requirements (e.g. to-be processes including (e.g. to-be processes including material flows & data flows),material flows & data flows),

business requirementsbusiness requirements(ideally all aspects of business incl. measures; usually in (ideally all aspects of business incl. measures; usually in description of future business processes)description of future business processes)

required target ICT architecture,required target ICT architecture,ICT organizationICT organization

feedbackfeedbackchanges in legacy situation changes in legacy situation (2-5 years need to update the whole (2-5 years need to update the whole ICT strategy)ICT strategy)

feedback feedback (maintainance changes, (maintainance changes, requests for new requests for new features)features)

project charter project charter (project sponsor, manager, (project sponsor, manager, team, schedule, budget, ...)team, schedule, budget, ...)

new or updated ICT new or updated ICT systems, systems,

new or updated user new or updated user behavior behavior

picture 2

2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan

2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan

business requirementsbusiness requirements(ideally all aspects of business incl. measures; usually in (ideally all aspects of business incl. measures; usually in description of future business processes)description of future business processes)

subchapter 1. detail

1. business needs & business strategy1. business needs & business strategy

• running a successful company requires a clearly

defined strategy integrated into day-to-day operations

• business strategy and its translation into action plans

(at least one of them is describing business processes)

• ITC strategy as a part of / implication of business

strategy

• how to prepare for ITC strategy when a business

strategy does not exists

market market conditions,conditions,vision&mission vision&mission statementsstatements

picture 3

3. project feasibility - ICT project goals & objectives - gap analysis to-be vs. as-is(processes/ICT) - business case (cost&benefit analysis) - decision on package or in-house devel.

3. project feasibility - ICT project goals & objectives - gap analysis to-be vs. as-is(processes/ICT) - business case (cost&benefit analysis) - decision on package or in-house devel.

required target ICT architecture,required target ICT architecture,ICT organizationICT organization

subchapter 2. detail

2. ICT strategy2. ICT strategy

• ITC assessment

(e.g. why?)

• ITC strategic plan

(e.g. what?, risk?)

• ITC implementation and tactical plan

(e.g. how?, when?, who?, how much?, security?)

• ITC business, application & hardware architecture

• ITC strategy team roles and responsibilities

1. business needs & business strategy1. business needs & business strategy

business requirementsbusiness requirements(ideally all aspects of business incl. measures; usually in (ideally all aspects of business incl. measures; usually in description of future business processes)description of future business processes)

legacy situationlegacy situation(e.g. system architecture, (e.g. system architecture, bussiness processes, bussiness processes, applications&data)applications&data)

feedback changes in feedback changes in legacy situation legacy situation (2-5 years need to update (2-5 years need to update the whole ICT strategy)the whole ICT strategy)

6. maintenance & support6. maintenance & support

picture 4

4. in-house development - analysis & design & implementation - tests - roll-out

4. in-house development - analysis & design & implementation - tests - roll-out

5. using packages - configuration - test - roll-out

5. using packages - configuration - test - roll-out

project charter project charter (project sponsor, manager, (project sponsor, manager, team, schedule, budget, ...)team, schedule, budget, ...)

subchapter 3. detail

3. project feasibility3. project feasibility

• ITC project goals and objectives• gap analysis of to-be vs. as-is processes / ICT• identify risk, operational & economic & technical feasibility of implementation alternatives • decision on package implementation or in-house development based on evaluation of implementation alternatives• business case (cost & benefit analysis)• prepare project management documents• prepare project infrastructure

existing ICT existing ICT systems,systems,user requirementsuser requirements (e.g. to-be processes (e.g. to-be processes including including material flows & data material flows & data flows),flows),

feedback feedback (maintainance changes, (maintainance changes, requests for new requests for new features)features)

2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan

2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan

6. maintenance & support6. maintenance & support

required target ICT architecture,required target ICT architecture,ICT organizationICT organization

picture 5

subchapter 4. detail

4. in-house development4. in-house development

• ICT system analysis (business & conceptual modeling)

• ICT system design

• ICT system implementation

(software programing and software generalization)

• tests (system, user acceptance, ...)

• roll-out

• project assessment

• techniques used for project management of in-house

development (devel. team roles, metrics, CMM, critical

path method, object-oriented vs. structural approach)

3. project feasibility - ICT project goals & objectives - gap analysis to-be vs. as-is(processes/ICT) - business case (cost&benefit analysis) - decision on package or in-house devel.

3. project feasibility - ICT project goals & objectives - gap analysis to-be vs. as-is(processes/ICT) - business case (cost&benefit analysis) - decision on package or in-house devel.

6. maintenance & support - user help desk - configuration management - risk management & security

6. maintenance & support - user help desk - configuration management - risk management & security

project charter project charter (project sponsor, manager, (project sponsor, manager, team, schedule, budget, ...)team, schedule, budget, ...)

new or updated ICT systems, new or updated ICT systems, new or updated user behavior new or updated user behavior

picture 6

subchapter 5. detail

5. using packages5. using packages

• conduce proof of concept (conference room pilot)

• migration plan of data, SW&HW, LAN

• configure package

• install computer assurance procedures and controls

• test configured system

• conduct integration & acceptance testing

• convert data

• optional: pilot implementation

• roll-out

• project assessment

3. project feasibility - ICT project goals & objectives - gap analysis to-be vs. as-is(processes/ICT) - business case (cost&benefit analysis) - decision on package or in-house devel.

3. project feasibility - ICT project goals & objectives - gap analysis to-be vs. as-is(processes/ICT) - business case (cost&benefit analysis) - decision on package or in-house devel.

6. maintenance & support - user help desk - configuration management - risk management & security

6. maintenance & support - user help desk - configuration management - risk management & security

project charter project charter (project sponsor, manager, (project sponsor, manager, team, schedule, budget, ...)team, schedule, budget, ...)

new or updated ICT systems, new or updated ICT systems, new or updated user behavior new or updated user behavior

picture 7

subchapter 6. detail

6. maintainance & support6. maintainance & support

• user help desk, its roles and organization

• support teams management

• configuration management

(software, hardware, LAN, communications,

documentation)

• training management

• vendors management

• risk and security management

4. in-house development - analysis & design & implementation - tests - roll-out

4. in-house development - analysis & design & implementation - tests - roll-out

5. using packages - configuration - test - roll-out

5. using packages - configuration - test - roll-out

new or updated ICT new or updated ICT systems, systems,

new or updated user new or updated user behavior behavior

2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan

2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan

3. project feasibility - ICT project goals & objectives - gap analysis to-be vs. as-is(processes/ICT) - business case (cost&benefit analysis) - decision on package or in-house devel.

3. project feasibility - ICT project goals & objectives - gap analysis to-be vs. as-is(processes/ICT) - business case (cost&benefit analysis) - decision on package or in-house devel.

feedbackfeedbackchanges in legacy situation changes in legacy situation (2-5 years need to update the whole (2-5 years need to update the whole ICT strategy)ICT strategy)

feedback feedback (maintainance changes, (maintainance changes, requests for new requests for new features)features)