1 / 7

model: ICT lifecycle in a company

model: ICT lifecycle in a company. market conditions, vision&mission statements. 1. business needs & business strategy. business requirements (ideally all aspects of business incl. measures; usually in description of future business processes). legacy situation

sanura
Download Presentation

model: ICT lifecycle in a company

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. model: ICT lifecycle in a company market conditions,vision&mission statements 1. business needs & business strategy business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) legacy situation (e.g. system architecture, bussiness processes, applications&data) 2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan feedbackchanges in legacy situation (2-5 years need to update the whole ICT strategy) required target ICT architecture, ICT organization existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows), 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. feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget, ...) 4. in-house development - analysis & design & implementation - tests - roll-out 5. using packages - configuration - test - roll-out new or updated ICT systems, new or updated user behavior 6. maintenance & support - user help desk - configuration management - risk management & security

  2. subchapter 1. detail 1. 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 conditions,vision&mission statements business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) 2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan

  3. subchapter 2. detail 1. business needs & business strategy business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) 2. 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 legacy situation (e.g. system architecture, bussiness processes, applications&data) feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) required target ICT architecture, ICT organization 6. maintenance & support 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. subchapter 3. detail 2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan required target ICT architecture, ICT organization 3. project feasibility existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows), • 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 feedback (maintainance changes, requests for new features) 6. maintenance & support project charter (project sponsor, manager, team, schedule, budget, ...) 4. in-house development - analysis & design & implementation - tests - roll-out 5. using packages - configuration - test - roll-out

  5. subchapter 4. detail 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. project charter (project sponsor, manager, team, schedule, budget, ...) 4. 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) new or updated ICT systems, new or updated user behavior 6. maintenance & support - user help desk - configuration management - risk management & security

  6. subchapter 5. detail 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. project charter (project sponsor, manager, team, schedule, budget, ...) 5. 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 new or updated ICT systems, new or updated user behavior 6. maintenance & support - user help desk - configuration management - risk management & security

  7. subchapter 6. detail 4. in-house development - analysis & design & implementation - tests - roll-out 5. using packages - configuration - test - roll-out new or updated ICT systems, new or updated user behavior 6. 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 feedbackchanges in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) 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. 2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan

More Related