We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byLeslie Keith
Modified over 4 years ago
International Telecommunication Union © ITU-T Study Group 17 Integrated Application of URN Daniel Amyot University of Ottawa, Canada email@example.com ITU-T Workshop on the Integrated Application of Formal Languages Geneva, September 13, 2003
© ITU-T Study Group 17 2003 URN o User Requirements Notation Allows engineers to specify or discover requirements for a proposed system or an evolving system, and review such requirements for correctness and completeness Helps bridging the gap between informal and formal concepts, and between requirements models and design models o URN = GRL + UCM Combines goals and scenarios Graphical notations Reusable patterns o Applicable to various domains (e.g. telecom services, distributed or reactive systems), in industry and SDOs
© ITU-T Study Group 17 2003 GRL (URN) o Goal-oriented Requirement Language For incomplete, tentative, (non-functional) requirements Capture goals, objectives, contributions, alternatives, and rationales Supports goal analysis and qualitative evaluations
© ITU-T Study Group 17 2003 UCM (URN) o Use Case Maps Causal sequences of responsibilities, allocated to components For operational requirements, as scenarios Support validation, performance analysis, and evaluation of architectural alternatives
© ITU-T Study Group 17 2003 Integrating GRL and UCM o Traceability between: Goals/tasks and UCMs (or UCM scenario definitions) Tasks and UCM responsibilities Different granularity Requirements management Others… o Underspecification and overspecification Discovery of new goals and scenarios Removal of unnecessary goals and scenarios Examples: Why is a UCM scenario without any link to a GRL goal? Why is a GRL goal without any link to a UCM scenario? o Refinements of alternative solutions From GRL (identification) to UCM (evaluation)
© ITU-T Study Group 17 2003 Minimum MobSC Load Minimum Message Exchange Service in SCP Service in MobSC SDF in SCPSDF in SN Determine SDF Location Impact is vendor-specific High Evolveability High Performance High Throughput Maximum Hardware Utilisation Minimum Changes to Infrastructure Low Cost Less need for new hardware Example GRL Model (Wireless Service)
© ITU-T Study Group 17 2003 (c) Service and SDF in SCP Three Alternative Solutions
© ITU-T Study Group 17 2003 Integrating UCM and MSC o Automated transformation from UCM to MSC Traversal of UCMs based on Scenario Definitions Enables scenario highlight on UCMs Paths visited can be transformed to MSCs Enables the generation of more detailed design scenarios
© ITU-T Study Group 17 2003 UCMNav and Scenario Definitions
© ITU-T Study Group 17 2003 Two Resulting MSCs
© ITU-T Study Group 17 2003 Integrating UCM and SDL o Generating MSC enables the synthesis of SDL specifications Early prototyping and requirements analysis Some results already available Presented at the 11 th SDL Forum, 2003 UCM UCM Exporter MSC SDL MSC2SDL
© ITU-T Study Group 17 2003 Integrating UCM and UML o Similar transformations from UCM to: UML sequence diagrams UML activity diagrams o These can be used to further synthesize state diagrams
© ITU-T Study Group 17 2003 Integrating UCM and TTCN-3 o UCM scenarios can be used as test goals Structured UCM scenarios converted to test suite Coverage of operational requirements Another transformation: TTCN-3
© ITU-T Study Group 17 2003 UCMNav and UCMExporter o UCMNav 2 generates scenarios (in XML) from traversals http://www.UseCaseMaps.org/tools/uvmnav o UCMExporter takes these as input and generates: MSC (Z.120, textual form) UML sequence diagrams (in XMI) TTCN-3 o http://ucmexporter.sourceforge.net/
© ITU-T Study Group 17 2003 Integrating UCM and LQN o Quantitative performance analysis with Layered Queuing Networks o Transformation from complete UCM model to an LQN model Supported by UCMNav o Enables: Analytic evaluations (LQNS) Simulations (LQSim) o http://www.LayeredQueuing.org
© ITU-T Study Group 17 2003 UCMs and Performance Response Time Requirement From T1 to T2 Name Response time Percentage SecurityE_Accountant Ready Continue CheckBio TaxPayer Access T1 Timestamp T2 Device Characteristics Processors, disks, DSP, external services… Speed factors Rejected Arrival Characteristics Exponential, or Deterministic, or Uniform, or Erlang, or Other Population size Responsibilities Data access modes Device demand parameters Mean CPU load (time) Mean operations on other devices OR Forks Relative weights (probability) Components Allocated responsibilities Processor assignment Can generate Layered Queuing Networks (LQN) automatically!
© ITU-T Study Group 17 2003 From Goals to Design, Performance, and Test Artifacts o Initial traceability from GRL goals to UCMs leads (transitively) to traceability between goals and: Design scenarios (MSC, UML SD) Internal behaviour (SDL) Test (TTCN-3) Performance evalutions (LQN)
© ITU-T Study Group 17 2003 Still To Be Explored… o Integrated use of URN and eODL object interfaces Deployments ASN.1 Interface/message definitions Other requirements URN cant express everything…
© ITU-T Study Group 17 2003 For More Information… o User Requirements Notation URN Focus Group http://www.UseCaseMaps.org/urn/ o Papers UCM Virtual Library http://www.UseCaseMaps.org/pub/
Cultural Heritage in REGional NETworks REGNET T2.4: Business Process Re-engineering.
Embedded System, A Brief Introduction
INTERVAL Next Previous 13/02/ Timed extensions to SDL Analysis requirements –Assumptions on moments and duration Semantics with controllable time.
INTERVAL Project Copyright 2000 by the INTERVAL Consortium Last revised 24 October 2000 ETSI-MTS Meeting, Sophia Consortium Objectives Technical.
System and Software Engineering Research 1 Motorola 2003 Integrated Application of MSC Clive Jervis Rapporteur Q15 Motorola UK Research Labs.
Use Case Maps Daniel Amyot, Gunter Mussbacher Introduction to Use Case Maps.
UCM Path Traversal Daniel Amyot SG17, Geneva, March 5 th, 2002 UCM Scenarios and Path Traversal.
1 GRL Introduction Lin Liu University of Toronto April 2001.
Language Specification using Metamodelling Joachim Fischer Humboldt University Berlin LAB Workshop Geneva
Use of ITU-T languages in Nokia
S CHOOL OF I NFORMATION T ECHNOLOGY AND E NGINEERING U NIVERSITY OF O TTAWA, C ANADA Daniel Amyot Q18/17 (URN) Rapporteur Time and.
ITU-T Workshop on Security Seoul (Korea), May 2002 Telecommunication network reliability Dr. Chidung LAC.
International Telecommunication Union © ITU-T Study Group 17 Use of ITU-T Formal Languages Amardeo Sarma NEC Europe Ltd.
Object-Oriented Software Engineering Visual OO Analysis and Design
Testing Workflow Purpose
User Requirements Notation URN Daniel Amyot October 2002 Requirements Engineering & User Requirements.
Based on Powerpoint slides by Gunter Mussbacher, Gregor v. Bochmann User Requirements Notation (URN) SEG3101 (Fall 2010)
Tool support for Distributed Object Technology
Daniel Amyot, PhD student, University of Ottawa Scenarios As First-Class Entities Functional Entities Mapping Scenarios on Functional Entities Network.
By Philippe Kruchten Rational Software
© 2018 SlidePlayer.com Inc. All rights reserved.