ASTA2007講演資料「Using Mind Map forSoftware Testing Activities」

168 Views

October 10, 07

スライド概要

2007年10月10日に「ASTA 2007 Software Testing Conference」での講演資料です。
https://www.aster.or.jp/activities/asta/asta_07.html

profile-image

クオリティアーツ代表/NaITE代表/ASTER理事/AFFORDD運営委員/Bizreach Software Quality Enabler、等。世の中に品質の技術で貢献するために活動中。 https://quality-arts.com/ https://naite.swquality.jp/ https://www.aster.or.jp/ https://affordd.jp/

シェア

埋め込む »CMSなどでJSが使えない場合

関連スライド

各ページのテキスト
1.

Using Mind Map for Software Testing Activities ASTA 2007 Software Testing Conference October 10, 2007 Mikio Suzuki(TIS) & Akira Ikeda (Hitachi Information & Communication Engineering)

2.

Akira Ikeda’s self introduction • Akira Ikeda • Hitachi Information & Communication Engineering Ltd. • After I join the company… – design embedded system – QA department – Today, company wide as consult • promoting testing and its design technology • Other… – promoting testing technology to Japan wide • ASTER、JSQC、TEF、S-Open、etc… – writing book and essay (in Japan)

3.

Mikio Suzuki’s self introduction • Name: Mikio Suzuki • Work: TIS Corporation – Developed Enterprise system, such as credit company system, web site for publisher – Today, consultant group in TIS – Member of JSTQB technical committee • writing book and essay (in Japan)

4.

What is Mind Map?

5.

Mind Map invoke what?

6.

Unconscious Thinking

7.

And

8.

Creativities

9.

Testing Activities require creativities?

11.

We use Mind Map for

12.

Creating test cases (and other testing activities)

13.

We see awful output!

15.

We teach you

16.

How to use Mind Map for Testing Activities

17.

Introduction Mind Map in the world Mind Map is methodology to invoke ideas

18.

Session Style • This session includes: – Presentation – Demonstration Movie

19.

Agenda 1. Overview using Mind Map for software testing 2. Abstract of Mind Map 3. Benefits when using Mind Map 4. Processes when using Mind Map 5. Group session &Review by Mind Map 6. Future Expansion 7. Appendix

20.

Agenda 1. Overview using Mind Map for software testing 2. Abstract of Mind Map 3. Benefits when using Mind Map 4. Processes when using Mind Map 5. Group session &Review by Mind Map 6. Future Expansion 7. Appendix

21.

1.1 Why do we need to use Mind Map for testing? ・・・ • Beginner testers face difficulty to create test cases and other materials for testing. Help!!! Mind Map can be solution to create test cases for beginner testers.

22.

1.2 Comparison between beginner testers and expert testers thinking … Beginner Specification Just copies from the specification Test cases !!! Expert Specification Think and covert from the specification to test cases Test cases !! Beginner Specification Think and covert from the specification to test cases Test cases

23.

1.2 Then, we can say • “Beginner testers plus Mind Map nearly equals to Expert testers!” ≒ + Beginner testers Mind Map Expert testers

24.

Agenda 1. Overview using Mind Map for software testing 2. Abstract of Mind Map 3. Benefits when using Mind Map 4. Processes when using Mind Map 5. Group session &Review by Mind Map 6. Future Expansion 7. Appendix

25.

2.1 Mind Map, in general ※Ref : Wikipedia • A mind map is a diagram used to represent words, ideas, tasks or other items linked to and arranged around a central key word or idea. • It is used to generate, visualize, structure and classify ideas, and as an aid in study, organization, problem solving, decision making, and writing.

26.

2.2 Mind Map Guidelines ※Ref : Wikipedia 1. Start in the center with an image of the topic, using at least 3 colors. 2. Use images, symbols, codes, and dimensions throughout your Mind Map. 3. Select key words and print using upper or lower case letters. 4. Each word/image must be alone and sitting on its own line.

27.

2.2 Mind Map Guidelines ※Ref : Wikipedia 5. The lines must be connected, starting from the central image. The central lines are thicker, organic and flowing, becoming thinner as they radiate out from the centre. 6. Make the lines the same length as the word/image. 7. Use colors – your own code – throughout the Mind Map.

28.

2.2 Mind Map Guidelines ※Ref : Wikipedia 8. Develop your own personal style of Mind Mapping. 9. Use emphasis and show associations in your Mind Map. 10. Keep the Mind Map clear by using radial hierarchy, numerical order or outlines to embrace your branches

29.

Agenda 1. Overview using Mind Map for software testing 2. Abstract of Mind Map 3. Benefits when using Mind Map 4. Processes when using Mind Map 5. Group session &Review by Mind Map 6. Future Expansion 7. Appendix

30.

3.1 Benefits of Mind Map for adopting software testing • 1.Three problems of beginner testers • 2.Mind Map can get rid of your problems • 3.Other benefits when using Mind Map

31.

3.2 Three problems of beginner testers Specs ・・ ・ Cannot explain about own created test cases Problem 3 Analyzing Specs Problem 1 Don't analyze specification Creating Test cases Review Test Cases Problem 2 Test Cases Cannot use testing techniques

32.

3.3 Mind Map can get rid of your problems Analyzing Specs Creating Test cases Review Test Cases Don't analyze specification Cannot use testing techniques Cannot explain about own created test cases Any popped idea should be written Indicating process of thinking Mind Map

33.

3.4.1 Five characteristics of Mind Map Only one paper for drawing Mind Map The results of the way of thinking The rules are not so strict Mind Map Easy to learn and Low installation costs Color and illustration

34.

3.4.2 Solve the problems by using Mind Map Analyzing Specs Creating Test cases Review Test Cases Don't analyze specification Cannot use testing techniques Cannot explain about own created test cases One paper The way of thinking Color and illustration Free format Easy to learn, Low installation costs

35.

3.4.2 Solve the problems by using Mind Map

36.

3.4.3 We did test design by Mind Map and hear impression Analyzing Specs Creating Test cases Review Test Cases Don't analyze specification Cannot use testing techniques Cannot explain about own created test cases Beginner Expert "ItIt is isworth." worth Beginner Use testing techniques Beginner Expert "It Very is worth." happy

37.

3.5 Other benefits when using Mind Map • Motivate engineers • Improve communication

38.

Agenda 1. Overview using Mind Map for software testing 2. Abstract of Mind Map 3. Benefits when using Mind Map 4. Processes when using Mind Map 5. Group session &Review by Mind Map 6. Future Expansion 7. Appendix

39.

4.1 Working step Specifications Design test cases Create test cases Test cases Mind Map

40.

4.2 Drawing Mind Map Expense Sharing Calculator Total Expense Person Discount Amount Discount Percentage (Yen) (H/C) (Yen) (%) Calculate Expense for one person: (Yen) Amount Shortage: (Yen)

41.

4.2 Drawing Mind Map Item Name Type Total expense Numeric Number of Person Digits In/Out Comments 6 Input Display comma separated. Minimum total expense: zero yen. Numeric 2 Input Minimum person: One person Discount amount Numeric 2 Input Minimum discount amount: One yen. Discount percentage Numeric 2 Input Minimum discount percentage: One % Select item Radio button -- Input Select one of discount amount or percentage Default selection is amount Calculate button button -- Input Click to calculate of expense for wach person and amount shortage Expense for one person Numeric 6 Output Display comma separated Amount shortage Numeric 6 Output Display comma seperated

42.

4.4.1 Mind Map Sample • Mind Map is depend on person • Even these are written in Japanese, you may understand what differences are. AAA ・・・ Depend…? BBB ・・・

43.

4.4.2 Mind Map Sample

44.

4.4.3 Mind Map Sample

45.

4.4 Difference between list type and Mind map type test cases • Develop normal test cases – It is ok a few slides on PowerPoint – It is difficult for reviewing, isn’t it?

46.

4.5 Difference between list of test cases and Mind map test cases Test cases Date: Name: High level Middle level Low level Check input data Value of total expense NULL MINUS(-1) ZERO MAX VALUE(999999) MAX VALUE + 1 comma Special character Comma on total expense 3digits 4digits

47.

4.5 Difference between list of test cases and Mind map test cases Test cases Date: Name: High level Middle level Low level Check input data Value of the number of person NULL MINUS(-1) ZERO LOW VALUE(1) MAX VALUE(99) MAX VALUE + 1 Special character ・・・・・・・・・・・・・

48.

4.5 Difference between list of test cases and Mind map test cases Test cases Date: Name: High level Middle level Low level Calculation Discount amount Total<Discount Total=Discount Total>Discount Discount percentage ・・・・・・・・ ・・・・・・・・ Difficult to review this!! ・・・・・・・・

49.

Agenda 1. Overview using Mind Map for software testing 2. Abstract of Mind Map 3. Benefits when using Mind Map 4. Processes when using Mind Map 5. Group session &Review by Mind Map 6. Future Expansion 7. Appendix

50.

5.Group session and review • Brainstorming • reviewing

51.

Agenda 1. Overview using Mind Map for software testing 2. Abstract of Mind Map 3. Benefits when using Mind Map 4. Processes when using Mind Map 5. Group session &Review by Mind Map 6. Future Expansion 7. Appendix

52.

6. The future activities • This mind map methodology is still undergoing. • We keep improving receiving feedback comment from many people.

54.

Agenda 1. Overview using Mind Map for software testing 2. Abstract of Mind Map 3. Benefits when using Mind Map 4. Processes when using Mind Map 5. Group session &Review by Mind Map 6. Future Expansion 7. Appendix

55.

7. Appendix • • • • Analyze Plan Execute Report

56.

Analyze examples

57.

Plan example テスト観点

58.

Execute example

59.

Report example