Conference Paper

Using SDL to Model an Object-Oriented Real-Time Software Architectural Design.

Telcordia Technol., Morristown, NJ
DOI: 10.1109/ISORC.2000.839542 Conference: 3rd International Symposium on Object-Oriented Real-Time Distributed Computing (ISORC 2000), 15-17 March 2000, Newport Beach, CA, USA
Source: DBLP

ABSTRACT Specification and Description Language (SDL) is a formal
object-oriented language for modelling real-time interactive systems. It
is an International Telecommunication Union (ITU) standard. A software
architecture is the structure of a program including a set of
inter-communication components. These components are often independently
executable super objects. We use the architecture design to answer
questions such as how the super objects fit together and how to reuse
them. We investigate the feasibility and benefits of using SDL to
represent the dynamic aspect of the software architectures. It includes
a methodology and an accompanying tool, Workflow-to-SDL-Transformation
(W2S), for deriving software architectures in SDL from an originally
informal use case flow definition. The focus of the research is in the
telecom domain, many of which are real-time interactive systems. We
applied our method to a partial telecom system. The experimental results
are collected and presented. Our result shows the feasibility and
benefits of representing the dynamic software architecture in SDL

  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: A model of commumcations protocols based on finite-state machines is investigated. The problem addressed is how to ensure certain generally desirable properties, which make protocols "well- formed," that is, specify a response to those and only those events that can actually occur. It is determined to what extent the problem is solvable, and one approach to solving it ts described.
    Journal of the ACM 04/1983; 30:323-342. · 2.94 Impact Factor
  • [Show abstract] [Hide abstract]
    ABSTRACT: Failures of a software system are detected by a supervisor, a separate unit which observes the inputs and outputs of the system and reports its failures in real-time. The supervisor determines whether a failure has occurred by comparing the observed and the specified behavior. The specification of behavior is assumed to be expressed in a formalism based on communicating extended finite state machines (specifically, ITU-T SDL). The supervisor must tolerate legal behavioral alternatives resulting from nondeterminisms in the specification. The computational costs of considering such alternatives can be fairly high. The paper presents the Conditional-Belief (CB) theory that reduces the cost of consideration of alternatives by using conditional-beliefs to represent sets of legal behavioral alternatives. The paper reviews belief-based supervision, introduces the CB theory, and outlines an algorithm for conversion of a class of SDL specification to a CB supervisor model. It describes a demonstration system developed to evaluate CB supervision, and summarizes failure detection and computational cost results for the supervisor of the control program of a small telephone exchange
    Software Reliability Engineering, 1996. Proceedings., Seventh International Symposium on; 01/1996
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: The 4 + 1 View Model describes software architecture using five concurrent views, each of which addresses a specific set of concerns: The logical view describes the design's object model, the process view describes the design's concurrency and synchronization aspects; the physical view describes the mapping of the software onto the hardware and shows the system's distributed aspects, and the development view describes the software's static organization in the development environment. Software designers can organize the description of their architectural decisions around these four views and then illustrate them with a few selected use cases, or scenarios, which constitute a fifth view. The architecture is partially evolved from these scenarios.The 4+1 View Model allows various stakeholders to find what they need in the software architecture. System engineers can approach it first from the physical view, then the process view; end users, customers, and data specialists can approach it from the logical view; and project managers and software-configuration staff members can approach it from the development view.
    IEEE Software 11/1995; 12(6):45-50. · 1.23 Impact Factor