Ingen bildrubrik

1
TIME FINANCING ORGANISATION PRODUCT DELIVERABLES
TIMEPLAN SW HW PW TID EKONOMI RISCS SOFTWARE
PROJECT MANAGEMENT PLAN Braudes Book
73-94 Case Study 1 123-131
2
(No Transcript)
3
GOAL ROADMAP - METHOD RESOURCES (SW-HW-PW) -
ORGANISATION INFORMATION - COMMUNICATION
4
Priorities and trade-offs GOAL

• The customer wants all this at the same time
• Short time schedule
• High functionality
• High Quality
• Low cost
• This is a balancing act in all software
  development projects.
• The customer can take hold of any two corners,
  but not all.

Quality
Functionality
Schedule
Cost
5
Management
DELIVERABLES
Functional Baseline
Product Baseline
System Baseline
Requirements
Code Units
Functional PARTS
Physical PRODUCT
DESIGN
INTEGRATION
ANALYSIS
CODING
TESTING
SRR
PDR
DDR
TRR
TRR
FCA
PCA
6
V-model
ROAD - METHOD
Contract Reqs
Acceptance Test
FB
PB
SRS
Validation
Integration
Allocation
Build
Test Report
PSDD -SDD
Code - Unit
Subsystem
7
(No Transcript)
8
User-interface prototyping

• Purpose
• Quickly explore the UI design and systems
  requirements
• Process
• Decide at the beginning of the project whether to
  evolve the prototype or throw it away. Be sure
  that both management and technical staffs are
  committed to the course of action that has been
  selected.
• Strive for creative Hollywood facade
  implementations of prototyped features that are
  not yet definitely in the product.
• Involve end-users, actively solicit their
  feedback, and limit their interaction with the
  prototype to controlled settings.

9
Evolutionary delivery

• Purpose
• Deliver working parts and use feedback to improve
• Process
• Do preliminary requirements analysis.
• Define the architecture and systems core
  carefully.
• Decide whether to use much prototyping or not.
• Order the functionality in your releases from
  most certain to least certain. Assume that
  the number of changes will increase in the later
  releases.
• Develop and deliver a version.
• Elicit and incorporate customer feedback into the
  next version.
• Manage user expectations affecting schedule,
  budget and performance.

10
Evolutionary delivery - continued METHOD
Functional growth
Deliver final version
Accept
Develop deliver
Feedback
5-50 iterations
Develop deliver
Feedback
Nothing
Develop deliver
Feedback
Architecture Core
Requirements analysis
Time
11
Organisation
PROGRAMUTVECKLING
SYSTEMERING
PROGRAMMERING
PROVNING
Processflöde
12
(No Transcript)
13
Organisation
PROJEKT
KVALITET
DELPROJEKT
OBJEKT
SYSTEMPROV
HJÄLPMEDEL
PROVNING
KONSTRUKTIONSOBJEKT
14
PROJEKTLEDNING
KVALITETSSÄKRING
PROVNING
SYSTEMARKITEKTUR
BASSYSTEM
PROGRAMMERING
Nõtverk
15
(No Transcript)
16
Software Project Management Plan
17
Software Project Management Plan
18
Development fundamentals - management

• Risk assessment
• Estimation
• Estimate size, effort, cost and schedule
• Planning
• Resources, competence, organization, life-cycle
  model, integration, deliveries, etc
• Tracking
• Manage the project towards schedule, cost and
  quality targets
• Reporting
• To customer, management and project

19
Development fundamentals - technical

• Requirements Engineering
• Analysis, modeling, user-interface prototyping,
  interviews, etc
• Design
• Object, structured, data structured
• Information hiding, modularity, abstraction,
  encapsulation, inheritance, etc
• Architectural schemes, anathomy
• Coding
• Coding practices, data types, recursion,
  assertions, etc
• Debugging, unit testing and integration
• Tools and libraries
• Software Configuration Management
• Critical in large projects!

20
Software Project Management Plan
21
Development fundamentals - quality assurance
Development time

• Testing
• Demonstrate that it works
• The messenger of bad news
• Technical reviews
• Software Inspection
• Find the root of the problems
• Improve working processes to avoid repetition

90 95 100
Percentage of defects removed
22
(No Transcript)
23
Top-10 risks list

• Purpose
• Raise awareness of risks
• Process
• Create a list of the top-10 risks in the project
  and publish it within the project so that
  everybody easily can see the risk situation.
• Review and update the list regularly.
• Be alert to changes of importance and track
  actions to closure!
• You may consider to appoint a Risk Officer
  which should play devils advocate - to look for
  all the reasons that the project might fail.

24
Top-10 risks list - continued

• Example

Pos.
Prev. pos.
Risk level
Slogan
Action
Resp.
Date.
1
3
25
Contact supplier new suppliers
JN.
4 Aug
New comm. card overheats
2
1
20
Memory leakage! ODBC?
Pinpoint the leak
MK.
3 Sep
3
2
16
Eric is leaving the project
Try getting a new GUI expert
LL.
14 Aug
4
4
16
Database too slow
Find the bottleneck
BA.
4 Aug
5
new
12
Card driver SP3 dont work
Get a correct driver from supplier
JN.
10 Sep
6
5
8
Customer wants better MTBF
Negotiate. Find cheaper solutions
BA.
23 Oct
7
6
5
Management changes priority
Remind about our contract, warn!
LL.
10 Oct
25
- Jag undrar om du skulle vilja tala om för mej
vilken väg jag ska gå nu? sade Alice. - Det beror
rätt mycket på vart du ska? svarade katten. - Det
gör nästan detsamma...sa Alice. - Då gör det
detsamma åt vilket håll du går, sa katten. - Bara
jag kommer nånstans, lade Alice till som en
förklaring. - Jo, det gör du säkert, sa katten.
Om du bara går långt nog.
26
Summing it up

• Select a life-cycle model as a framework for your
  project
• Plan the project and keep to the plan (or change
  the plan!)
• Reduce risk and increase confidence on success
• Build a team
• Use development fundamentals and best practices
• Avoid classic mistakes
• Focus on the primary project goal - customer
  satisfaction
• Use your creativity and imagination

27
Ändringsfrekvens
Tidsaxel - nyhetsaxel
Ta bort gamla Lansera nya tjänster
Hög
Tjänst1
Tjänst2.2
Tjänst3
Tjänst2
Produkt - består av 12.2
Tabetalt??
Driftochsupport
Kundstöd - CCR
Mittemellan ...
Plattform - infrastruktur - nät
Låg
Teknikbas - Ny teknik/ny generation
Planning for Evolution of SW Systems
28
Thats all folks! Thanks for your
attention! Next time Test I Questions??