1 / 19

Integrated Application of URN

Integrated Application of URN. Daniel Amyot University of Ottawa, Canada damyot@site.uottawa.ca ITU-T Workshop on the Integrated Application of Formal Languages Geneva, September 13, 2003. URN. User Requirements Notation

adila
Download Presentation

Integrated Application of URN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integrated Application of URN Daniel Amyot University of Ottawa, Canada damyot@site.uottawa.ca ITU-T Workshop on the Integrated Application of Formal Languages Geneva, September 13, 2003 © ITU-T Study Group 17

  2. URN • 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 • URN = GRL + UCM • Combines goals and scenarios • Graphical notations • Reusable patterns • Applicable to various domains (e.g. telecom services, distributed or reactive systems), in industry and SDOs © ITU-T Study Group 17 2003

  3. GRL (URN) • 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

  4. UCM (URN) • 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

  5. Integrating GRL and UCM • Traceability between: • Goals/tasks and UCMs (or UCM scenario definitions) • Tasks and UCM responsibilities • Different granularity • Requirements management • Others… • 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? • Refinements of alternative solutions • From GRL (identification) to UCM (evaluation) © ITU-T Study Group 17 2003

  6. Example GRL Model (Wireless Service) High Performance Minimum MobSC Load HighEvolveability High Throughput Low Cost Less need for new hardware MinimumChanges to Infrastructure MaximumHardwareUtilisation MinimumMessageExchange Impact is vendor-specific Servicein MobSC Servicein SCP Determine SDF Location SDF in SCP SDF in SN © ITU-T Study Group 17 2003

  7. Three Alternative Solutions (a) Service in MobSC (b) Service in MobSC, SDF in SN (c) Service and SDF in SCP © ITU-T Study Group 17 2003

  8. Integrating UCM and MSC • 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

  9. UCMNav and Scenario Definitions © ITU-T Study Group 17 2003

  10. Two Resulting MSCs © ITU-T Study Group 17 2003

  11. MSC2SDL UCMExporter UCM SDL MSC Integrating UCM and SDL • Generating MSC enables the synthesis of SDL specifications • Early prototyping and requirements analysis • Some results already available • Presented at the 11th SDL Forum, 2003 © ITU-T Study Group 17 2003

  12. Integrating UCM and UML • Similar transformations from UCM to: • UML sequence diagrams • UML activity diagrams • These can be used to further synthesize state diagrams © ITU-T Study Group 17 2003

  13. Integrating UCM and TTCN-3 • 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

  14. UCMNav and UCMExporter • UCMNav 2 generates scenarios (in XML) from traversals • http://www.UseCaseMaps.org/tools/uvmnav • UCMExporter takes these as input and generates: • MSC (Z.120, textual form) • UML sequence diagrams (in XMI) • TTCN-3 • http://ucmexporter.sourceforge.net/ © ITU-T Study Group 17 2003

  15. Integrating UCM and LQN • Quantitative performance analysis with Layered Queuing Networks • Transformation from complete UCM model to an LQN model • Supported by UCMNav • Enables: • Analytic evaluations (LQNS) • Simulations (LQSim) • http://www.LayeredQueuing.org © ITU-T Study Group 17 2003

  16. T2 UCMs and Performance • Device Characteristics • Processors, disks, DSP, external services… • Speed factors • Arrival • Characteristics • Exponential, or • Deterministic, or • Uniform, or • Erlang, or • Other • Population size Timestamp • Response Time • Requirement • From T1 to T2 • Name • Response time • Percentage TaxPayer Security E_Accountant T1 CheckBio Continue Ready Access Rejected • Components • Allocated responsibilities • Processor assignment • Responsibilities • Data access modes • Device demand parameters • Mean CPU load (time) • Mean operations on other devices • OR Forks • Relative weights (probability) Can generate Layered Queuing Networks (LQN) automatically! © ITU-T Study Group 17 2003

  17. From Goals to Design, Performance, and Test Artifacts • 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

  18. Still To Be Explored… • Integrated use of URN and • eODL • object interfaces • Deployments • ASN.1 • Interface/message definitions • Other requirements • URN can’t express everything… © ITU-T Study Group 17 2003

  19. For More Information… • User Requirements Notation • URN Focus Group • http://www.UseCaseMaps.org/urn/ • Papers • UCM Virtual Library • http://www.UseCaseMaps.org/pub/ © ITU-T Study Group 17 2003

More Related