presentation euroforum ibc copenhagen 6 nov 2003 ver handouts [2,2]

1

Volvo Information Technology

Volvo Information Technology Presentation 06.11.2003 Copenhagen

Invänta publiken II



Invänta publiken II

VOLVO INFORMATION TECHNOLOGY AB, SE-405 08 GÖTEBORG PHONE: +46 31 66 70 00 [email protected] WWW.IT.VOLVO.COM

2



Test Sida (Försättsblad presentation)

Development and Implementation of quality assured test methodologies

at Volvo IT

Copenhagen ConferenceEuroforum ibcKvalitetssisikring og test af softwaresystemer

Wednesday the 6:th of Nov 2003

VOLVO INFORMATION TECHNOLOGY



Start ----------------------- (Personlig Presentation)

Jacek Jack Janiczko

Method SpecialistTest & Configuration Management

Business Consultant & Business Analyst, Coach and mentor within change management


3



Ämnes titel

Practical introduction to testing methodology for new projects


- Practical experiences from progressive projects within Volvo IT.

- Importance of requirement work and its relation closeness to the test process.

- Clear communication is essential in a successful test process

- Volvo IT developed adaptations and development recommendationsfor improved quality assurance for organizations that work with the *RUP

* Rational Unified Process




GLOBAL ORGANISATION

4330 Employees

9 Counties

Volvo IT

EUROPANORD AMERIKASYD AMERIKAASIEN

BELGIENBRASILIENFRANKRIKESTOR BIRITANIENMALAYSIAPOLENSVERIGESPANIENUSA

Turnover

5,7 Billion sKR / 620 Euro

Incl. contractors

Established 1966Formed 1998

70 000 Users in 300 sites

4



GLOBAL ORGANISATION

Volvo IT (världs karta, var vi finns)

Spain

Sweden _________ 2790 EmployeesPolandBelgium

Great Britain

USA

South America

France

Asia



Villa verde (Madrid)

Limoges

Vénissieux – St-Priest(Lyon)

Bourg-en-Bresse

Blainville (Caen)

Dunstable

Umeå

EskilstunaKöping

SkövdeGöteborgOlofström

WroclawGent

Daventry

Trollhättan

VOLVO ITEurope and Sweden

3680 Employees

GÖTEBORGTROLLHÄTTANOLOFSTRÖMSKÖVDEESKILSTUNAKÖPINGUMEÅ

Volvo IT Europa

5




VOLVO CARS 38%

The VOLVO Group

Våra kunder

Main Customers

VOLVO Trucks 36%VOLVO Busses 3%VOLVO AERO 3%VOLVO PENTA 3%VOLVO construction equipment 7% Other Volvo companies Sweden 9%International 3%

External CustomersNOBEL BIOCARE ABBCONGSBERG AstraZenicaORD MOTOR SchlumbergerSEMAASSA ABLOY EuromationGAMBRO LINDEX


AB VOLVO VOLVO CARS (FORD) RENAULT V.I.MACK TRUCKS



Volvo Information TechnologyKap A : Ämne: ---” Avd. för metod och tekniker/kompbentes”

MY Home Department

Purpose:

To promote skills and methodology within the Volvo IT organization by educating skillful professionals that can participate and incorporate new techniques and methods into new system development projects and the efficient running of system administration operations.

Consulting Services and ADT (Application Development Techniques)

120 staff members

6



Volvo Information TechnologyVår grupp Vad vi gör !

RESOURCE CENTER- Operational staff skilled in- Project Management, Test, CM, QA

and Change management

INFORMATION POOL- First point of Contact

ACTIVE SUPPORT ORGANIZATION- Operational support , Start Up, Coaching, Mentoring

reviews and assessments

TOOL SUPPORT- Information and education

METHOD SUPPORT- Know how in RUP,PCM and MCM

CM , TEST & Project management

Consulting Services and ADT (Application Development Techniques)



Kapp I:------------ ”Införandet av ett gemensamt arbetssätt”

Quality TEST Cost

The test organizations dilemma

7



Test organisationens vardag

The test organization. A common ordinary day scenario

TEST

”Keep cost at minimum…”

”You will be finished anyway..”

”We expect high quality and a low costs...”

”Test is something we can take care of later...”



Intressenter och testarbete

TEST

Implementation

LineManagement

ComputerCentre

Principal SteeringCommittee

Accountants

Requirementsmanagement

ConfigurationManagement

Functionalmanagement

ProjectManagement

DBA

Directly involved stakeholders in Test & Verification activities

8



Höga krav och förväntningar

Demands from developers and other project members

Demands from business owners

TESTER

High demands and expectations

How do we solve and manage this situation ?

How do we go about ?



4 grund krav på test dokumentation ”The Mission””

A Basic Requirement

I can UpdateI can Trace I can RedoI can Prove

Customer

is a clear and concise documentation

The missionof documentation

I can Prove that I can find the right info. I can change and update all documents I can redo this thru the whole project and lifecycle

orderly, methodical- documentation

9



4 grund krav på test dokumentation ”The Mission””

I can ChangeI can Trace I can RedoI can Prove

Customer

Clear & ConciseTraceable Easy to changeThe mission

of documentation is:

The Basic Requirements ondocumentation

Aha! Yes!



Vital information + mervärde

Added Value

Time performanceand follow-up

Costs andexpenses

The Customer

The missionof documentation is:

I can ChangeI can Trace I can RedoI can Prove

orderly, methodical

10



Kvitto ( underlag för förbättring )

X (Use Case Realisation Doc.)

Component/Packagespecification

ID:007-C/P-S

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC

B (Test Case Resultat/s

ID:007-C/P-TC-S---DR/FR

Defect report/Fault report

Nr 1

C (Receipt)

Test & Change Status Verification

Nr 1

ID:007-C/P-TC-S-DR/FR

TC-SV

C (Receipt)


Nr 1


TC-SV

TIME Delivery Status

What is ready ?What is undergoing tests? What is under development ?

Basic foundation for project follow-up and control

Cost = spent time on labor

=

HistoryWho ?When ?



Kvitto ( nyttoeffekter )



ID:007-C/P-S

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC




Nr 1

C (Receipt)


Nr 1


TC-SV

C (Receipt)


Nr 1


TC-SV

Foundation for time & cost estimation

Receipt on cost / delivered componentReceipt on our efficiency

Foundation for future improvements

Cost data

Customers receipt confirming the performed test efforts

Priority foundationsUsed resources

The Receipt and its benefits

TID

TEST LEDER

Foundation for re-planning and priority states

PROJECT STATUS

11



Kap II: ------------ ”Att jobba enligt samma modell” (Bakgrund

Traditional IT organization

Volvo IT !

Software development model developed during the 80:thThe AU-model (Administration Development Model)

Operation and administration of large systems

Good test organization nevertheless in same point person dependent.

A common way of working was missing.



Recept för framtidens succé

Iterative ProcessPoor/Bad Good /excellent

ProjectManagement

Most likelyto succeed

Most likelyto fail

CHAOS Report by The Standish Group, a study of 23.000+ IT projects since 1994

Prescription for future success !

Good /excellent

12



Bakgrund - Varför valde vi en ny process-metod ?

Why did we choose a new method ?

• Need for an integrated system development environment

• Out of date and development model (AU-model) at Volvo developed in the middle of the (1980) eighties

• Out of time• Usage not coherent at Volvo IT

• CHAOS Report from The Standish Group:

• “Only 28% of all software projects have been successfuldue to time, cost and functionality.

• “45% of all delivered functions ware never used



§

• Homogeneous view at the test discipline

• Homogeneous view on quality goals- Higher quality in production systems

• Independent position in projects- Access to a central lab- The best people (spearhead competence) members at one ”Skill Center”

• Less complex test environment

• Less amount of different test tools- Genuine knowledge

• Homogeneous knowledge on complex test tools- All tools with the exception of tools used for Unit testing are handled outside the projects

Expected positive effects within TEST

13



Förväntade positiva effekter på Volvo IT

- Rational Unified Process (RUP)

Most likelyto fail

Expected and positive effects for Volvo IT

• increased number of successful projects • Shorter development time• Higher delivery precision• Better product adaptation to real needs• Reduced labor costs• Better product maintenance

ProjektManagement- Project

ControlModel(PCM)

Iterative Process

Good /excellent

Good /excellent

Poor/Bad



Kap III: Ämne :-------- ”Erfarenheter med att jobba med RUP med avseende på TEST” + RUP-processen och svagheter inom Test

RUP / TEST

+ -

Our experiences when working with RUP with reference on the TEST discipline

Positive and negative experiences

14



Info 2000 - 2002

RUP 2000 [TEST] RUP 2001 [Test]

RUP 2002 [Test]

Historical experience

RUP 2003 [Test]



Anpassningar av RUP

Our adaptations

RUP - VOLVO IT

+

TemplatesMethodsGuidelinesToolsPractical experiences+

15



Test Plan improvement/adaptation for RUP 2001 (Decision maker)

Test Templates

Testing Types

Data and Database Integrity Testing Test Objective:

Technique:

Completion Criteria: All database access methods and processes function as designed anwithout any data corruption.

Special Considerations:

Test type decision template

Status Description Annotations

Decision status Status Test environment Consequences of a “No Go” decision on test type

Justification Decision maker

(Responsible for risk) [Name, date and project status/role]

Clear decisions

Clear risk takingExample:



Våra ambitioner ---------(Målsättning Vår framtid !)

Our ambitions

Where do we want to go ?

16



Vad vill vi uppnå

What do we want to achieve ? ”Ambitions”

A controlled system development process

Why ?

We know what we are doing ! We know were are !

We know why we are doing specific tasks !What know what will come next !

We can trace and follow -up !

Therefore we have better prerequisites to succeed !

Clear documentation requirements is a way of achieving better results !



Fem steg till bättre utveckling

Initial level

Repeatable level

Defined level

Managed level

Optimizing level

1.

2.

3.

4.

5.

SPICE / CMM

17



Fem steg till bättre utveckling (Definitioner)

1.

2.

3.

4.

5.

The repeated level: has basic project handling routines in place for the control of cost, time plans and functionality.

The initial level: is characterized by chaos. Success here i basedon individual achievement and hero culture.

The defined level: have the development process documented and all projectsthat are handled by the main organization follows the established model.

VOLVO IT

The Managed level: here the organization performs detailed measurementson the development processes and productivity. All programs and productsare defined in quantified terms.

The Optimizing level: has an incorporated continuous process improvement based on quantified measurements that are continuously brought back to the development process frompilot projects and new techniques.



Vad vill vi uppnå

Team WorkI test and

verify !

I design !

18



Samma utgångspunkt Strategi

Project leader

StrategyCustomer

TesterTest Designer

Tactics

Operative functions

Test leader

DeveloperDesigner

Architect

VerifiesDesigns

Decides

Carries out

Documentation levels within a project organization (Large projects)

Realizes

Verifies



Viktig ”Överlämnande”

Important !

A formalized delivery of project Information.

Is it easy for my counterpart's to understand my documentation ?

19



Avslutning Avslutning --------------------------(Tack)(Tack)--------------------------------------

Thank You

VOLVO INFORMATION TECHNOLOGYEnd of Part 1



Avslutning (Frågor II Extra Avslutning (Frågor II Extra del:)del:)

End of part IQuestions

?


20



AvslutningAvslutning-------------------------- (SLUT)(SLUT)--------------------------------------

VOLVO INFORMATION TECHNOLOGYPart 2

How we introduce quality based testing to new projects



4 grund dokument

I can UpdateI can Trace I can RedoI can Prove

Customer perspective



ID:007-C/P-S

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC

B (Test Case Resultat/s)



Nr 1

C (Receipt)


Nr 1


TC-SV

Basic Project Documentation

21



Specificera på komponent nivå



ID:007-C/P-S



ID:007-C/P-S

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC




Nr 1

C (Receipt)


Nr 1


TC-SV

Specify on component level

Clearly defied relations between physical components & design documents

All nödvändig information om en specifikkomponent finns samlad i ett och endast ett dokument

Planad time

All necessary information on a specific componentis collected into one document that can be usedand understood by any designer that will be ableto build the actual component



Felrapport, underlag för verifiering



ID:007-C/P-S

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC




Nr 1

C (Receipt)


Nr 1


TC-SV

B (Test Case Resultat/s)



Nr 1

Work order to designerControlled follow-up and history

Test certificate / evidence = Quality guarantee

Analysis documentVerification of work results

22



Spårbarhet direkt till implementerad komponent



ID:007-C/P-S

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC




Nr 1

C (Receipt)


Nr 1


TC-SV

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC

Direct traceability to an implementedor executable component

.exe


ID:007-C/P-S


Direct traceability to a corresponding test case



Tydlig koppling mot funktionalitet



ID:007-C/P-S



ID:007-C/P-S

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC




Nr 1

C (Receipt)


Nr 1


TC-SV

FUNCTION 1 [ name ] = Service = Business valueFUNCTION n+ [ name ]

GUIScenarioUser CaseFunctionsDB-tablesValidation rules

Planed moment of delivery

Clearly defined relations towards functional requirements

23



Kvitto ( Utformning )



ID:007-C/P-S

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC




Nr 1

C (Receipt)


Nr 1


TC-SV

C (Receipt)


Nr 1


TC-SV

Test & Change Status verification

Test Run 1Test Start.……………..Test Ready…………… Name Sign.......

Change Start……………Change Ready…….. Name Sign.......

Test Run 2Test Start.……………..Test Ready…………… Name Sign.......

Change Start……… …Change Ready…….. Name Sign.......

Test Run (approved by CCB)Test Start.……………..Test Ready…………… Name Sign.......


___________________________________________________Test Case Comments (Notes)

____________________________________________________

Deploy! Component ready.________________________________Tester Project leader (Test Leader)Date.....Sign....... Sign......

Test Case number(ID)………Test Type: Functional

Who ?

TEST performerDeveloper

TEST LEADER

Example: Simple Receipt



Kvitto Ex: original

Example: Simple Receipt

Test Start.……………..Test Ready…………… Name Sign.......


___________________________________________________

Test Case Comments (Notes)

____________________________________________________

Deploy! Component ready.

________________________________

Tester Project leader (Test Leader)

Date.....

Sign....... Sign......Test & Change Status Verificationdocument

24



Test på specificerad leverans



ID:007-C/P-S

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC




Nr 1

C (Receipt)


Nr 1


TC-SV

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC

.exeOn preplanned time

- baseline

Tests are performed on executable components



A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC



ID:007-C/P-S

CR (Change Request)

Change Request

Nr 1

ID:007-C/P-S--CRQ

.exe




Nr 1

C (Receipt)


Nr 1


TC-SV

Ändringar görs alltid med full Spårbarhet

Changes are always done with full traceability

25



Ändringar görs alltid med full Spårbarhet

RUP-exempel

Changes should be distinct and methodically traceable



Changes should always be distinct and methodically traceable

A (Test Case)

Test Case

Nr 1

ID:007-C/P-S--TC



ID:007-C/P-S

CR (Change Request)

Change Request

Nr 1

ID:007-C/P-S--CRQ

.exe

Ändringar ska vara tydliga och metodiskt spårbara

26



Avslutning Avslutning --------------------------(Tack(Tack II )II )--------------------------------------

Thank You



Avslutning (Frågor II Extra Avslutning (Frågor II Extra del:)del:)

Questions?


27



Kontakt Sida (Visit kort)

Jacek JaniczkoMethod SpecialistTest & Configuration Management

Mail: [email protected]: + 46 31 – 322 13 25


Business Consultant & Business Analyst, Coach and mentor within change management



Kontakt Sida (Volvo IT)

Volvo Information Technology ABSE-405 08 GöteborgSweden Phone +46 31 66 70 00

www.it.volvo.com


28



presentation euroforum ibc copenhagen 6 nov 2003 ver handouts [2,2]

Documents

volvo busses

volvo penta

volvo aero

volvo construction equipment

volvo companies sweden

requirement work

developed adaptations

vrlds karta