1. X36SSP Správa softwarových produktů Ing. Martin Molhanec ČVUT – FEL K13113

2. Co je obsahem předmětu? Procesy, které předcházejí, doprovázejí, následují či jinak souvisejí s tvorbou softwarového produktu (program, informační systém, webové sídlo).

3. Software, jako produkt. Podobně jako u kteréhokoliv jiného technického výrobku, je nutné zajistit: –Aby upokojoval požadavky zákazníka! Jak je ovšem zjistit? –Byl kvalitní! Jak toho docílit? –Byl dokončen v termínu! Jak toho docílit?

4. Software, jako produkt. Podobně jako u kteréhokoliv jiného technického výrobku, je nutné zajistit: –Aby upokojoval požadavky zákazníka! Jak je ovšem zjistit? –Byl kvalitní! Jak toho docílit? –Byl dokončen v termínu! Jak toho docílit? K dosažení těchto cílů nestačí být ovšem pouhý programátor!

5. Software, jako produkt. Podobně jako u kteréhokoliv jiného technického výrobku, je nutné zajistit: –Aby upokojoval požadavky zákazníka! Jak je ovšem zjistit? –Byl kvalitní! Jak toho docílit? –Byl dokončen v termínu! Jak toho docílit? Tvorba softwarových produktů je inženýrská disciplina – nikoliv umělecká tvorba!

6. Software, jako produkt. Podobně jako u kteréhokoliv jiného technického výrobku, je nutné zajistit: –Aby upokojoval požadavky zákazníka! Jak je ovšem zjistit? –Byl kvalitní! Jak toho docílit? –Byl dokončen v termínu! Jak toho docílit? K dosažení jmenovaných cílů se využívají metody projektového managementu!

7. Informační a komunikační technologie Je pojem, který v sobě zahrnuje –Výpočetní techniku Hardware Software –Telekomunikační techniku Dříve pouze hardware Dnes hardware i software ICT

8. Informační a komunikační technologie Je pojem, který v sobě zahrnuje –Výpočetní techniku Hardware Software –Telekomunikační techniku Dříve pouze hardware Dnes hardware i software V dnešní době se informační a komunikační technologie vzájemně bezprostředně silně prolínají!!!

9. Informační a komunikační technologie Je pojem, který v sobě zahrnuje –Výpočetní techniku Hardware Software –Telekomunikační techniku Dříve pouze hardware Dnes hardware i software Je to počítač nebo telefon?

10. ICT a softwarový produkt ICT jsou –Hardwarové produkty –Softwarové produkty –Služby –Koncepce –Metodiky –Názor na svět Toto nás bude zajímat nejvíce!

11. Životní cyklus ICT ve firmě! Modelová situace –Chceme ve firmě uskutečnit inovaci v oblasti ICT –Nebo toto po nás vyžaduje náš zákazník –Jádrem inovace může být nový softwarový produkt –Jeho naprogramování je pouze jedna z dílčích činností, které je nezbytné učinit!

12. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

13. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

14. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

15. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

16. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

17. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

18. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

19. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

20. 2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) stage 1. in 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&missio n statements

21. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

22. 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, ICT organization stage 2. in detail 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 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) Feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) 6. maintenance & support

23. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

24. 4. in-house development - analysis & design & implementation - tests - roll-out 5. using packages - configuration - test - roll-out project charter (project sponsor, manager, team, schedule, budget,...) Stage 3. in detail 3. 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 systems, user requirements (e.g. to-be processes including material flows & data flows) feedback (maintainance changes, requests for new features) 2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical plan 6. maintenance & support required target ICT architecture, ICT organization

25. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

26. Stage 4. in detail 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) 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 sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

27. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

28. Stage 5. in detail 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 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 sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

29. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

30. Stage 6. in detail 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 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 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. Feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features)

31. ICT lifecycle in a company 1. business needs & business strategy 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 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 situation (e.g. system architecture, bussiness processes, applications&data) market conditions, vision&mission statements existing ICT systems, user requirements (e.g. to-be processes including material flows & data flows) business requirements (ideally all aspects of business incl. measures; usually in description of future business processes) required target ICT architecture, ICT organization feedback changes in legacy situation (2-5 years need to update the whole ICT strategy) feedback (maintainance changes, requests for new features) project charter (project sponsor, manager, team, schedule, budget,...) new or updated ICT systems, new or updated user behavior

32. Alternativní životní cykly.