why software testers can read maps

27
why software testers read MAPS jayapradeep jiothis

Upload: jayapradeep

Post on 25-May-2015

399 views

Category:

Technology


2 download

DESCRIPTION

A presentation made at H-IT(High Impat Trandformation Seminar of Perpetua IT Consulting a Kochi , on Skills for a software tester

TRANSCRIPT

Page 1: Why software testers can read Maps

why software testers readMAPS

jayapradeep jiothis

Page 2: Why software testers can read Maps

agenda

• the plot

• the twists

• cool stories

• the climax

Page 3: Why software testers can read Maps

about perpetua

• Knowledge services firm providing consulting & training services on Software Testing , QA , Project Management and BFSI

• To provide high end education through web , mobile , e learning ,e tutoring and television

• IP licensing of high end knowledge content• Pioneering educational tourism

• Vision to be among the top three knowledge services providers in our segment in South East Asia by 2012.

• Mission : democratise and make knowledge jargon free

Page 4: Why software testers can read Maps
Page 5: Why software testers can read Maps

Software Testing

it SUCKS

Page 6: Why software testers can read Maps

so what is software testing

• Something that people do when they have free time at s/w companies

• Punishment post when you don’t perform in your development job

• Find BUGS in software

• Third rate citizens who belong to united states of imbeciles who need passports to be admitted to an IT company

Page 7: Why software testers can read Maps

so what is software testing : redux

• Activity which manages risk for a business

• Management consulting for a project

• Guides and Navigators for any software project

• Statistical and mathematical activity par excellence

Page 8: Why software testers can read Maps
Page 9: Why software testers can read Maps

the market

Page 10: Why software testers can read Maps

$100bnglobal testing market

Avendus

Page 11: Why software testers can read Maps

$13 bnoutsourced market

gartner

Page 12: Why software testers can read Maps

hey are we notsupposed to talk MAPS ?

Page 13: Why software testers can read Maps

A map is a visual representation of an area

maps

Page 14: Why software testers can read Maps

software requirements = maps

• Requirement is the map (blueprint) of the software to be build.

• Represented through various written documents like SRD , SRS , Design Docs ...

• Users(navigators , sailors ??) inlcude customer , developers , architects , BA’s, software testers

• They don’t read the maps well and we have bad software , failed projects

Page 15: Why software testers can read Maps

idea one

“ No force in the world can stop and idea whose time has come” - Victor Hugo

IDEA + TIME

Page 16: Why software testers can read Maps
Page 17: Why software testers can read Maps

sample req:

Page 18: Why software testers can read Maps

sample req:The mobile application would be able to read ISP emails and governed by single login user friendly interface.

Page 19: Why software testers can read Maps

sample req:The mobile application would be able to read ISP emails and governed by single login user friendly interface.

Upon 3 incorrect attempts the system shall lock out the user.

Page 20: Why software testers can read Maps

mapis a

linear representation

Page 21: Why software testers can read Maps

mapis not the

“Territory”

Page 22: Why software testers can read Maps

mapshide morethan they

reveal

Page 23: Why software testers can read Maps
Page 24: Why software testers can read Maps

morevisual

=more

clarity

Page 25: Why software testers can read Maps

goodnavigators

readmapsbetter

Page 26: Why software testers can read Maps

StopStartContinue