X36SSP Spr

1
X36SSPSpráva softwarových produktu

• Ing. Martin Molhanec
• CVUT FELK13113

2
Co je obsahem predmetu?

• Procesy, které predcházejí, doprovázejí,
  následují ci jinak souvisejí s tvorbou
  softwarového produktu (program, informacní
  systém, webové sídlo).

3
Software, jako produkt.

• Podobne 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 dokoncen v termínu!
• Jak toho docílit?

4
Software, jako produkt.

• Podobne 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 dokoncen v termínu!
• Jak toho docílit?

K dosažení techto cílu nestací být ovšem pouhý
programátor!
5
Software, jako produkt.

• Podobne 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 dokoncen v termínu!
• Jak toho docílit?

Tvorba softwarových produktu je inženýrská
disciplina nikoliv umelecká tvorba!
6
Software, jako produkt.

• Podobne 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 dokoncen v termínu!
• Jak toho docílit?

K dosažení jmenovaných cílu se využívají metody
projektového managementu!
7
Informacní a komunikacní technologie

• Je pojem, který v sobe zahrnuje
• Výpocetní techniku
• Hardware
• Software
• Telekomunikacní techniku
• Dríve pouze hardware
• Dnes hardware i software

ICT
8
Informacní a komunikacní technologie
V dnešní dobe se informacní a komunikacní
technologie vzájemne bezprostredne silne
prolínají!!!

• Je pojem, který v sobe zahrnuje
• Výpocetní techniku
• Hardware
• Software
• Telekomunikacní techniku
• Dríve pouze hardware
• Dnes hardware i software

9
Informacní a komunikacní technologie

• Je pojem, který v sobe zahrnuje
• Výpocetní techniku
• Hardware
• Software
• Telekomunikacní techniku
• Dríve pouze hardware
• Dnes hardware i software

Je to pocítac nebo telefon?
10
ICT a softwarový produkt

• ICT jsou
• Hardwarové produkty
• Softwarové produkty
• Služby
• Koncepce
• Metodiky
• Názor na svet

Toto nás bude zajímat nejvíce!
11
Životní cyklus ICT ve firme!

• Modelová situace
• Chceme ve firme uskutecnit inovaciv oblasti ICT
• Nebo toto po nás vyžaduje náš zákazník
• Jádrem inovace muže být nový softwarový produkt
• Jeho naprogramování je pouze jedna z dílcích
  cinností, které je nezbytné ucinit!

12
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
13
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
14
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
15
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
16
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
17
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
18
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
19
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
business requirements (ideally all aspects of
business incl. measures usually in description
of future business processes)
Again, in more details!
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
(costbenefit 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
20
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,visionmission 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
21
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
22
stage 2. in 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
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
Feedbackchanges in legacy situation (2-5 years
need to update the whole 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

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
(costbenefit analysis) - decision on package
or in-house devel.
23
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
24
Stage 3. in 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
25
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
26
Stage 4. in detail
3. project feasibility - ICT project goals
objectives - gap analysis to-be vs.
as-is(processes/ICT) - business case
(costbenefit 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
27
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
28
Stage 5. in detail
3. project feasibility - ICT project goals
objectives - gap analysis to-be vs.
as-is(processes/ICT) - business case
(costbenefit 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, SWHW, 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
29
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
30
Stage 6. in 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

Feedback changes 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
(costbenefit analysis) - decision on package
or in-house devel.
2. ICT strategy - ICT assessment - ICT
strategic plan - ICT implementation/tactical
plan
31
ICT lifecycle in a company
market conditions,visionmission statements
1. business needs business strategy
legacy situation (e.g. system architecture,
bussiness processes, applicationsdata)
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
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
(costbenefit 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
32
Alternativní životní cykly.
33
Alternativní životní cykly.
34
KONEC!