Final Presentation

T 3

200711453 류진렬

200711477 황진수

200711428 박기성

201360220 황 민

200312489 유현덕

1

Software Verification

CTIP

- Our Team Activities & Result

- What we’ve learned?

System Testing

- Our Team Activities & Result

- What we’ve learned?

Static Analysis

- Our Team Activities &Result

- What we’ve learned?

Contents

2

CTIP

3

Our Team Activities & Result

4

CTIP Environments

Final Presentation CTIP

Code Quality Management

Sonar

Clover

JDepend

Eclipse

PMD

Build / Deploy Management

Source Code Version Management

SVN

CruiseControl

Ant

CheckOut

Developer

Communicate Issues

Mantis

CheckIn / CheckOut Feedback

Execute

Static Analysis

Our Team Activities & Result

5

New Millenium Hall Room.#605

Mantis & AMPSetup

->(Web Server) http://kucse13.iptime.org/mantisbt/

Set up SVN Server -> Source Code Version Management

Svn://203.252.182.163/repository

Set up CruiseControl(Ant) -> (Automated Build and Report)

http://203.252.182.163/CruiseControl

Server setting for CTIP

• Problems

1. Have no experiences and knowledge of Server setting (CTIP)

-> Fail to use Subclipse (connect SVN with eclipse)

2. The Server PC shut down frequently

Final Presentation CTIP

Our Team Activities & Result

6

Mantis

• Report failed test cases after System Testing

Final Presentation CTIP

Our Team Activities & Result

7

Mantis

• Static Analysis Report • About New release point • About Server PC status • And so far..

Final Presentation CTIP

Our Team Activities & Result

8

SVN

Location : repository/trunk/modling/ Revision : 134

Final Presentation CTIP

Our Team Activities & Result

9

SVN

Location : repository/trunk/modling/ Revision : 134 Location : repository/tags/ Release : 2

Final Presentation CTIP

What We’ve learned?

10

CTIP

- The process about large scale project.

- Importance of Periodic(Automated) integration & testing

- Usefulness of source code version Management System

Final Presentation CTIP

System Testing

11

12

System Testing – Combinatorial Testing

Category Partitioning -> Test Cases

Our Team Activities & Result

Final Presentation System Testing

Choosing Category

Identify Representative

Value

Generate Test Case

Specification

Misunderstood the meaning of Single Constraints

What We’ve learned?

13

System Testing

- Better Category partitioning, better detection of error.

- Impossible to find all errors

- Tester’s knowledge and experience are important.

- Requirements Spec need to be verifiable for System Testing

(also validate)

Final Presentation System Testing

Static Analysis

14

15

System Testing & Static Analysis

Our Team Activities & Result

Code coverage, Cyclomatic Complexity, Copy & Paste Detection, Rule based code check, and so far.

Even if we have fine test cases, It is very hard to achieve 100% code coverage.

Line numbers in each class

Comments, Duplication, Complexity

Rule Based Code Check

Final Presentation Static Analysis

What We’ve learned?

16

Static Analysis

- Choose proper Static Analysis Tools with target program.

- Understand the meaning of metrics from Static Analysis tools.

- Analyze the code status and advise the developer for the

better program

- Even if it achieve 100% code coverage, it is not meaning of

“NO ERRORS”

Final Presentation Static Analysis