© 2000 D EMO D AY 2000 Page 1 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology Leïla Charfi, Luigi Logrippo & group.

Slides:

Advertisements

Similar presentations

Fraunhofer FOKUS Competence Center MOTION FOKUS VIEW ON MODEL-BASED TEST DESCRIPTION LANGUAGES (TDLS) Alain-G. Vouffo Feudjio.

Advertisements

International Telecommunication Union © ITU-T Study Group 17 Integrated Application of URN Daniel Amyot University of Ottawa, Canada

Tool support for Distributed Object Technology

Friday, April 17, 2015 Requirements Specifications Interaction Analysis Bill Mitchell Software and Systems Research Labs Motorola UK Research Labs Bill.

Network Protocols Dr. Eng Amr T. Abdel-Hamid NETW 703 Winter 2006 Finite State Machines (FSMs)

Daniel Amyot, PhD student, University of Ottawa Scenarios As First-Class Entities Functional Entities Mapping Scenarios on Functional Entities Network.

Hydra (A General Framework for Formalizing UML with Formal Languages for Embedded Systems*) *from the Ph.D. thesis of William E. McUmber Software Engineering.

August Moscow meeting1August Moscow meeting1August Moscow meeting11 Deductive tools in insertion modeling verification A.Letichevsky.

Alternate Software Development Methodologies

Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,

Automata Based Programming Anatoly Shalyto, Fedor Tsarev Saint-Petersburg State University of Information Technologies, Mechanics and Optics.

Software Testing and Quality Assurance

Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 5, Analysis: Dynamic Modeling.

Requirements Analysis Concepts & Principles

1 SWE Introduction to Software Engineering Lecture 5.

Systems Engineering Project: System Validation and Verification Using SDL Ron Henry ENSE 623 November 30, 2004.

Chapter 1 Software Engineering. Homework ► Read Section 2.2 (pages 79-98) ► Answer questions: ► 7, 8, 11, 12, & 13 on page 134. ► Answer on paper, hand.

Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.

L ECTURE 2 S OFTWARE P ROCESSES 1. O BJECTIVES To describe outline process models for requirements engineering, software development, testing and evolution.

[ §4 : 1 ] 4. Requirements Processes II Overview 4.1Fundamentals 4.2Elicitation 4.3Specification 4.4Verification 4.5Validation Software Requirements Specification.

©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.

RESEARCH REPORT PREPARATION AND PRESENTATION. 2 RESEARCH REPORT A research report is: – a written document or oral presentation based on a written document.

UCM-Based Generation of Test Goals Daniel Amyot, University of Ottawa (with Michael Weiss and Luigi Logrippo) RDA Project (funded.

An Introduction to MBT  what, why and when 张坚

Requirements Expression and Modelling

Requirements Analysis

Automatic Generation of Web Interfaces From User Interaction Diagrams Filipe Bianchi Damiani Patrícia Vilain Federal University of Santa Catarina (UFSC)

Chapter 2: Software Process Omar Meqdadi SE 2730 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.

Storyboarding 1. Purpose of Storyboarding  To gain an early reaction from users on the concepts proposed for the application.  They are an effective.

S CHOOL OF I NFORMATION T ECHNOLOGY AND E NGINEERING U NIVERSITY OF O TTAWA, C ANADA Daniel Amyot Q18/17 (URN) Rapporteur User Requirements.

1 Presentation and tool by Jason Kealey University of Ottawa CSI5180 Automatic conversion of Use Cases to Use Case Maps.

GENERATION OF PROTOCOLS FOR TELEPHONY FEATURES FROM SCENARIO REQUIREMENTS By Luigi Logrippo University of Ottawa School of Information Technology and.

Framework for the Development and Testing of Dependable and Safety-Critical Systems IKTA 065/ Supported by the Information and Communication.

TSERGPCS Workshop-98 UNIVERSITE D’OTTAWA UNIVERSITY OF OTTAWA SITE p 1 Prototyping and Validation of the General Packet Radio Service: A Data Service of.

1 Recent work in the area: Requirement-Driven Development of Distributed Applications Gregor v. Bochmann School of Information Technology and Engineering.

1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Methodologies of the SDLC Traditional Approach to SDLC Object-Oriented Approach to SDLC CASE Tools.

Institute for Telematics University of Lübeck, Germany M. Ebner, M. Schmitt, J. Grabowski Test Generation with Autolink and TestComposer.

S CHOOL OF I NFORMATION T ECHNOLOGY AND E NGINEERING U NIVERSITY OF O TTAWA Feature Description and Feature Interaction Analysis with Use Case Maps and.

Fall 2010 CS4310 Requirements Engineering A Brief Review of UML & OO Dr. Guoqiang Hu Department of Computer Science UTEP 1.

Requirements Specification. Welcome to Software Engineering: “Requirements Specification” “Requirements Specification”  Verb?  Noun?  “Specification”

1 Representing New Voice Services and Their Features Ken Turner University of Stirling 11th June 2003.

Deliverable 10. Deliverable #10 Class Design and Implementation #1 due 9 April Executive Summary and Statement of Work Iteration Plan (Updated) for remaining.

1 Overview of the project: Requirement-Driven Development of Distributed Applications School of Information Technology and Engineering (SITE) University.

Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.

Requirements Validation

Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher(2009) with material from Amyot User Requirements Notation (URN)

© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.

Generating Software Documentation in Use Case Maps from Filtered Execution Traces Edna Braun, Daniel Amyot, Timothy Lethbridge University of Ottawa, Canada.

Software Engineering Lecture 11: System Analysis.

4 th SDL and MSC Workshop SAM’04 Ottawa 1st-4th June 2004 Alkiviadis Yiannakoulias NTUA

S CHOOL OF I NFORMATION T ECHNOLOGY AND E NGINEERING U NIVERSITY OF O TTAWA, C ANADA Daniel Amyot Q18/17 (URN) Rapporteur User Requirements.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.

©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.

MICON 2000 F ormal methods for design methodology by Luigi Logrippo with D. Amyot, R. Chan, L. Charfi, N. Gorse, J.Sincennes, R. Plesa,... S CHOOL OF I.

Dynamic Models - Page L M.E. Fayad Lesson 30: Dynamic Models Object- Oriented Modeling & Application s.

21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.

Requirement Analysis SOFTWARE ENGINEERING. What are Requirements? Expression of desired behavior Deals with objects or entities, the states they can be.

Daniel Amyot, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: Jo Atlee, Dan Berry (both University of Waterloo);

Miguel Garzón, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: Jo Atlee, Dan Berry (both University of.

Copyright 1999 G.v. Bochmann ELG 7186C ch.1 1 Course Notes ELG 7186C Formal Methods for the Development of Real-Time System Applications Gregor v. Bochmann.

Aspect-oriented Code Generation Approaches Abid Mehmood & Dayang N. A. Jawawi Department of Software Engineering Faculty of Computer Science and Information.

UNIVERSITÉ D’OTTAWA UNIVERSITY OF OTTAWA IWTCS ‘ Fast Functional Test Generation Using an SDL Model Robert L. Probert Alan W. Williams School of.

Chapter 5 System modeling

Description of WIN Incoming Call Screening Service using Use Case Maps

Software Design Mr. Manoj Kumar Kar.

Participants and Collaborators

Model Based Testing Venkata Ramana Bandari, Expert Software Engineer

Decentralized Model-Based Testing of Distributed Systems

Engineering Quality Software

Chapter 7 Software Testing.

Presentation transcript:

© 2000 D EMO D AY 2000 Page 1 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology Leïla Charfi, Luigi Logrippo & group (with RL Probert & group) School of Information Technology and Engineering University of Ottawa Participants “Fast Spec-to-Test” Project University of Ottawa Mitel Corporation

© 2000 D EMO D AY 2000 Page 2 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology Objectives u The Problem: Obtaining tests that cover the requirements u Automatic functional test generation – by developing automatic test purpose generation from requirements Use Case Maps (UCM)  LOTOS u Proposition of a design methodology with automatic test suite generation: u UCM at requirements stage u LOTOS at design & prototyping stage u Automatic LOTOS test purpose generation from UCM u Automatic test suite generation from LOTOS

© 2000 D EMO D AY 2000 Page 3 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology Design Methodology for Telecommunication Systems Use Case Maps Requirements stage LOTOS specification Design stage LOTOS scenarios verification, validation and test suite generation Test suites Mapping UCM to LOTOS statements (1) (2) (3) (4) Implementation stage Test suite execution on Implementation MSCs lotos2msc msc2lotos Input for possible SDL specification,...

© 2000 D EMO D AY 2000 Page 4 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology Use Case Maps (UCM) u Semi-formal notation, used at requirement stage u Visual representation of system’s behavior u Derived from informal requirements or use cases start point responsibility end point Example of map: simple call establishment component stub offHookdial onHook phoneA phoneB switch checkIfIdle offHook [Idle] [busy] or_fork disconnection checkCalleesStatus

© 2000 D EMO D AY 2000 Page 5 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology LOTOS – Formal Description Technique – Design of telecommunication systems – Validation tools: interactive simulation (step-by-step execution), validation using test conformance on the specification u LOLA u XELUDO u CEASAR – Test generation tools u UCM2LotosTests: LOTOS scenario generation from UCM u TGV: test suite generation from LOTOS scenarios u TorX: test generation and execution of test suites Language Of Temporal Ordering Specification

© 2000 D EMO D AY 2000 Page 6 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology UCM to LOTOS mapping (1) UCM elements LOTOS elements map, componentprocess stub start-point responsibilityaction end-point or-forkchoice operator [] and-forkparallel composition

© 2000 D EMO D AY 2000 Page 7 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology UCM2LOTOSTests (1) (2) Process Calle_Busy[ user_to_phone, phone_to_user] :exit Test generation algorithm generates 2 scenarios UCM to LOTOS scenario transformation offHook dial onHook dial checkIfIdle offHook dial offHook [busy] [Idle] disconnection user_to_phone !A !phoneA !offHook; phone_to_user !phoneA !A !dialTone; user_to_phone !A !phoneA !dial !B; phone_to_user !phoneA !A! busyTone; user_to_phone !A !phoneA !onHook; endProc user_to_phone !A !phoneA !offHook; phone_to_user !phoneA !A !dialTone; user_to_phone !A !phoneA !dial !B; phone_to_user !phoneB !B ! ringTone; user_to_phone !B !phoneB ! offHook; ( user_to_phone !A !phoneA !onHook; phone_to_user !phoneB !B !disconnectTone; user_to_phone !B !phoneB !onHook; [] user_to_phone !A !phoneA !onHook; phone_to_user !phoneB !B !disconnectTone; user_to_phone !B !phoneB !onHook) endProc Process Calle_Idle [ user_to_phone, phone_to_user]: exit checkCalleesStatus checkIfIdle [Idle] [busy] checkCalleesStatus phoneA phoneB switch phoneAphoneB switch Aim: covering the UCM with test cases

© 2000 D EMO D AY 2000 Page 8 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology Test Purpose (MSC format) Message Sequence Chart offHook dialTone dial[B] ring userAdebA Test purpose: - Abstract description of a subset of the specification - Tests the functional behavior of the specification against its expected behavior debB userB ringTone offHook answer onHook disconnection onHook

© 2000 D EMO D AY 2000 Page 9 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology Test suite generation with TGV (3) (4) Test purpose Test suite generated from LOTOS using TGV 0 1 user_to_phone !A !offHook phone_to_user !A !dialTone 2 user_to_phone !A !dial !B 3 phone_to_user !B !ringingOn 4 phone_to_user !B !ringBackTone 5 user_to_phone !B !offHook 6 phone_to_user !A !ringBackToneOff 7 user_to_phone !B !onHook 8 phone_to_user !A !disconnectTone 9 user_to_phone !A !onHook 10 TGV 0 1 user_to_phone !A !offHook; INPUT phone_to_user !A !dialTone; OUTPUT 3 user_to_phone !A !dial !B; INPUT 5 phone_to_user !B !ringingOn; OUTPUT 7 phone_to_user !B !ringBackTone; OUTPUT 8 user_to_phone !B !offHook; INPUT 9 phone_to_user !A !ringBackToneOff; OUTPUT 11 user_to_phone !A !onHook 11 phone_to_user !B !disconnectTone 12 user_to_phone !B !onHook user_to_phone !B !offHook (INCONCLUSIVE) user_to_phone !B !onHook; INPUT 13 phone_to_user !A !disconnectTone; OUTPUT 15 user_to_phone !A !onHook; INPUT(PASS) 17 user_to_phone !A !onHook; INPUT 14 phone_to_user !B !disconnectTone; OUTPUT 16 user_to_phone !B !onHook; INPUT(PASS) user_to_phone !B !onHook (INCONCLUSIVE) 12 user_to_phone !A !offHook (INCONCLUSIVE) 10 18

© 2000 D EMO D AY 2000 Page 10 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology Conformance relation used by TGV The Implementation can have more inputs The Specification can have more outputs I: implementation, S: specification I ioconf S  traces(S), O(I after  )  O(S after  ) I1I1 I2I2 I 2 not ioconf S switch? checkIfIdle phone2! idle phone2! busy switch? checkForward I 1 ioconf S switch? checkIfIdle phone2! idle phone2! busy switch !indefinedUsr switch? checkIfIdle phone2! idle phone2! busy S

© 2000 D EMO D AY 2000 Page 11 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology Success to date and Lessons Learned u Use of UCM to formalize requirements:  Automatic test generation with full coverage of the UCM (implying full coverage of the requirements)  Easy derivation of a prototype using the UCM to LOTOS mapping

© 2000 D EMO D AY 2000 Page 12 Automatic Generation of Conformance Test Cases from Use Case Maps Strategic Technology Key Issues u How to design UCMs so as to facilitate requirement documentation and obtention of meaningful test case u Automating as much as possible UCM to LOTOS translation u More experience is needed...