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 2 years ago
International Telecommunication Union © ITU-T Study Group 17 Integrated Application of URN Daniel Amyot University of Ottawa, Canada ITU-T Workshop on the Integrated Application of Formal Languages Geneva, September 13, 2003
© ITU-T Study Group 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 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 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 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 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 (c) Service and SDF in SCP Three Alternative Solutions
© ITU-T Study Group 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 UCMNav and Scenario Definitions
© ITU-T Study Group Two Resulting MSCs
© ITU-T Study Group 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 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 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 UCMNav and UCMExporter o UCMNav 2 generates scenarios (in XML) from traversals o UCMExporter takes these as input and generates: MSC (Z.120, textual form) UML sequence diagrams (in XMI) TTCN-3 o
© ITU-T Study Group 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
© ITU-T Study Group 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 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 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 For More Information… o User Requirements Notation URN Focus Group o Papers UCM Virtual Library
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.
UCM Path Traversal Daniel Amyot SG17, Geneva, March 5 th, 2002 UCM Scenarios and Path Traversal.
Use Case Maps Daniel Amyot, Gunter Mussbacher Introduction to Use Case Maps.
Agent Based Software Development Michael Luck, Ronald Ashri and Mark dInverno Chapter 4: Methodologies and Modeling Languages.
Embedded System, A Brief Introduction Presented by Subash Chandra Nayak 01EC3010, IIT Kharagpur.
International Telecommunication Union © ITU-T Study Group 17 Use of ITU-T Formal Languages Amardeo Sarma NEC Europe Ltd.
The Language ITU-T Amardeo Sarma Co-Chairman, ITU-T Study Group 17.
Ch:8 Design Concepts S.W Design should have following quality attribute: –Functionality –Usability –Reliability –Performance –Supportability (extensibility,
International Technology Alliance In Network & Information Sciences International Technology Alliance In Network & Information Sciences 1 Policy Specification,
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 10 Practical Database Design Methodology and Use of UML Diagrams.
DATABASE SYSTEM CONCEPTS AND ARCHITECTURE CHAPTER 2 1.
® IBM Software Group © 2008 IBM Corporation Dr Tariq Aslam Business Alignment Using Enterprise Architecture Productivity, Governance, Innovation.
Copyright 1999, 2003 G.v. Bochmann CN-FM ch.2 1 Course Notes on Formal Methods for the Development of Distributed Real-Time Applications Gregor v. Bochmann.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Distributed Systems Architectures.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Topics covered l Functional and non-functional requirements l User requirements.
1 © NOKIA ITU workshop.ppt/ C. Willcock, July 2004 Use of ITU-T languages in Nokia Colin Willcock Nokia Research Center ITU-T Workshop Geneva, July 2004.
Language Specification using Metamodelling Joachim Fischer Humboldt University Berlin LAB Workshop Geneva
Chapter 7 – Design and Implementation 1Chapter 7 Design and implementation Note: These are a modified version of Ch 7 slides available from the authors.
Chapter 4 Operations and Transactions The Strategic Management of Information Systems.
16 November 2002 Use and needs of description techniques in Study Group 4 Knut Johannessen Rapporteur Q.12/4, Telenor, Norway.
Copyright 2011 John Wiley & Sons, Inc Business Data Communications and Networking 11th Edition Jerry Fitzgerald and Alan Dennis John Wiley & Sons, Inc.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps Unit - II.
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java L6 (Adapted For ISE 2005/6 By Ananda Amatya, University.
How to align IT/SOA on the basis of Changing Strategies and Capabilities ? TOGAF 9 and ArchiMate 2 on a short Case Study to drive SOA (Excerpts from the.
Chapter 4 Requirements Engineering Slide 1 Chapter 4 Requirements Engineering.
COMET Approach for UML Overview Chapter 6 Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Chapter 6 Architectural Design Slide 1 Chapter 6 Architectural Design.
7 February An Overview of the Systems Modeling (SysML) Specification Shana L. Lloyd Julie A. Street The Aerospace Corporation Systems Modeling Language.
© 2016 SlidePlayer.com Inc. All rights reserved.