1 / 10

Telephony System Requirements Specification Using TeleLogic TAU: A Practical Guide

This tutorial, based on Qiang Chen’s work, teaches how to develop a requirements specification for a telephony system using TeleLogic TAU 4.5. It covers key concepts such as entity relationship diagrams, SOON notation, finite state machines (FSM), and message sequence charts (MSC). Participants will learn about iterative requirements gathering and the importance of accurate specification. The guide emphasizes various modeling approaches and offers practical examples for drawing MSCs, ultimately aiming to enhance clarity and accuracy in telecommunication system design.

adonia
Télécharger la présentation

Telephony System Requirements Specification Using TeleLogic TAU: A Practical Guide

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. Lab 1 Telephony SystemBased on Qiang Chen’s tutorial with minor modifications

  2. Outline • Objective • Important Concepts • Telephony System • Software TeleLogic TAU 4.5

  3. Objectives • Learn how to write requirement specification with the Telephony System example • Get familiar with different description approaches including entity relation diagram, SOON notation, FSM, MSC • Use TeleLogic TAU to draw MSC

  4. Domain Analysis • Why? (http://bdn.borland.com/article/borcon/files/2114/paper/2114.html) The most serious problems have to do with the requirements for the system. • Objective: getting the right requirements & getting the requirements right; • An iterative process; • Elements included:- statement of purpose- dictionary- description from a conceptual modeling viewpoint- diagrams (eg: use case diagrams)

  5. Diagrams • Diagrams from the STATIC view: - Entity Relation Diagram- SOON Diagram • Diagrams from the DYNAMIC view:- Finite State Machine (FSM)- Message Sequence Chart (MSC)

  6. Entity Relation Diagram • Entities (squares); • Relationships (diamonds); • Attributes (lines); • Focus on the structure of data; • Do not describe the behaviors of the system.

  7. SOON Diagram • SISU Object-Oriented Notation; • To describe structures where SDL is not appropriate; • Less formal and does not enforce SDL semantics; • Consists of frame, body, environment, entity instances, connection, relation, reference, reference definition, etc.

  8. Finite State Machine • Describe the possible states one entity will go through; • The states transition is triggered by actions; • Defined by: • a finite set of inputs, I: • a finite set of outputs, O; • a finite set of states, S; • a next state function, FS: S x I --> S; • an output function, FO: S x I --> O*; • a designated initial state, Initial.

  9. Message Sequence Chart • describe the typical interaction sequences (protocols) for each use cases; • consist of:- frame- name- instance- signal- timeline- end

  10. Draw MSC Use TeleLogic TAU • Demo

More Related