TOTEM ( Testing-Object OrienTed systEms) Test Methodology Darrel K. Farro Master Business...

University Utrecht / MBI Class 2012-2013

1

S

TOTEM(Testing-Object OrienTed

systEms)

Test MethodologyDarrel K. Farro

Master Business Informatics

Agenda

Authors Dr. Lionel C. Brand Dr. Yvan Labiche

TOTEM test methodology: definition & purpose

Origins

Main phases

Related literature

PDD explanation

Example Use case sequential constraint Directed graph Derives dependency sequences

QuestionsUniversity Utrecht / MBI Class

2012-20132

AuthorsDr. Lionel C. Brand


3

• University of Paris VI, France• In 1986, Dr. Brand received his B.Sc in

Geophysics and Computer Systems Engineering;

• In 1988, Dr. Brand received his M.Sc for the same course

• University of Paris, XI, France• In 1994, Dr. Brand received his Ph.D degree in

Computer Science (with high honor)

Dr. Lionel C. BrandLeader of the Certus software V&V center and Professorat the University of Oslo

• Dr. Brand have founded SQUALL;• Dr. Brand (not by himself) had over 135

publications in:• Peer-reviewed journal and conferences;• Book chapters and Technical reports

AuthorsDr. Yvan Labiche


4

Dr. Yvan LabicheAssociate professor at DSCE at Carlton University

• Blaise Pascal University, France• In 1995, Dr. Yvan Labiche received his M.Sc of

fundamental computer science and production systems;

• LAAS/CNRS in Toulouse, France• In 2000, Dr. Yvan Labiche received his Ph.D in

Software Engineering

• Dr. Yvan Labiche and Dr. Lionel C. Brand have written over 60 journals and conferences together;

Definition & Purpose

TOTEM test methodology is according to Briand and Labiche (2001, p.14) a “system test methodology, as far as deriving test requirements is concerned.”


5

• Support the derivation of test requirements• Determines the design of the system• System engineers can

• Test plan• Evaluate the size of a task• Plan the appropriate resources• Allows walkthroughs• Allow early decision making prior to implementing a

function/ use case

Origins

System testing Complex system Consists of many

functionalities Consists of many roles Each role has its own goal The sequence of the

functionalities


6

(Idoughia, Kerkara & Kolski, 2007)

Main phases


7

TestRequiremen

ts&

Sequences

Class diagra

ms

Activity diagra

ms

Sequence

diagrams

State diagram

sGenerate code for Oracles

Derive

Deriv

e

Derive

Derive

Embedding into

executable test drivers

1

2

3

Variant sequenc

es

Deriv

e

Related literatures

Fusion Object-oriented methodology (Sendall & Strohmeier, 1999)

OMT BOOCH CRC

Shlaer-Mellor methodology (Shlaer & Mellor, 1996)

Main focus is the implementation of architectural componentsinto a software system

Coad-Yourdon methodology (Burleson, 2011)

Data flow diagrams Define structure & attributes for the classes and their

relationship


8

Integrated into one single framework

Related literaturePositioning of TOTEM test methodology


9

TOTEM

1. Fushion object-

oriented

2. Shlaer-mellor

3. Coad-Yourdon’

s

1. TOTEM does cover requirements capture and testing by using its artifacts e.g., ‘Sequence diagram’

2. TOTEM does test the system by using for example its artifact called ‘Use case sequential diagram’ and ‘Directed graph’.

3. TOTEM’s artifacts inlcudes all Coad Youdon’s artifacts

Process-Delivery DiagramHigh-level overview


10

Consists of 8 activities

Process-Delivery DiagramLow-level overview


11

TOTEM test methodologyExample


12Use Case sequential constraintDirected graph

TOTEM test methodologyContinued


13

Seq 1: A(user_id) . B(user_id)

Seq 2: A(user_id) . C(user_id, d_id) . D(user_id, d_id)

Seq 3: A(user_id) . C(user_id, d_id) . E(user_id, income)

Parametrized Use Case sequences

- A(user_id).B(user_id)- C(user_id, d_id).D(user_id, d_id)- (A(user_id)||C(user_id, d_id)).E(user_id,

d_id)

Parameter Instances(Symbolic values)

- User(1): user_id- Department(1): d_id- Income(1): income

References

Briand, L., & Labiche, Y. (2001). A UML-Based Approach to System Testing. Computer Science , 1(1), 194-208. doi:10.1007/s10270-002-0004-8

Burleson, D. (2011). Object-Oriented Analysis Models - Rumbaugh, Booch, Coad-Yourdon, and Shlaer-Mellor Method. Retrieved February 17, 2012, from dba-oracle: http://www.dba-oracle.com/

Idoughia, D., Kerkara, M. & Kolski, C.. (2007). Towards new web services based supervisory systems in complex industrial organizations: Basic principles and case study, Retrieved April 11, 2012, from: http://ars.sciencedirect.com/content/image/1-s2.0-S0166361509001596-gr21.jpg

Sendall, S., & Strohmeier , A. (1999). UML-Based Fusion Analysis. 1723, pp. 278-291. Colorado: Springer Berlin / Heidelberg. doi:10.1007/3-540-46852-8_20

Shlaer, S., & Mellor, J. S. (1996). The shlaer-mellor method. California: Project Technology.

Strohmeier, A. (2000, October 19). Fusion/UML Overview. Retrieved February 17, 2012, from EPFL | IC: http://diwww.epfl.ch/researchlgl/teaching/software_engineering00_01/documentation/introduction/overview_fusion-UML.pdf University Utrecht / MBI Class

2012-201314

Questions?


15

TOTEM ( Testing-Object OrienTed systEms) Test Methodology Darrel K. Farro Master Business...

Documents

Transcript of TOTEM ( Testing-Object OrienTed systEms) Test Methodology Darrel K. Farro Master Business...