1997
DOI: 10.1016/s0169-7552(96)00110-9
|View full text |Cite
|
Sign up to set email alerts
|

Structural models for specifying telephone systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

1998
1998
2007
2007

Publication Types

Select...
6
1
1

Relationship

2
6

Authors

Journals

citations
Cited by 11 publications
(6 citation statements)
references
References 21 publications
(7 reference statements)
0
5
0
Order By: Relevance
“…We use the algebraic specification language LOTOS [BoBr87] [LoFH92] for feature specification [FaLS97]. LOTOS semantics are based on the concept of labeled transition systems (LTSs).…”
Section: Basic Concepts and Notationmentioning
confidence: 99%
See 1 more Smart Citation
“…We use the algebraic specification language LOTOS [BoBr87] [LoFH92] for feature specification [FaLS97]. LOTOS semantics are based on the concept of labeled transition systems (LTSs).…”
Section: Basic Concepts and Notationmentioning
confidence: 99%
“…Figure 2 (a) shows the POTS (Plain Old Telephone Service, denoting a basic featureless telephone system) model defined in [FaLS91] for the specification of basic call processing. The model is based on the concept of constraints which is used to structure the specification [FaLS91] [FaLS97]. A specification is expressed as a set of communicating processes representing three types of constraints: local constraints, end-to-end constraints, and global constraints: Local constraints are used to enforce the appropriate sequences of events at each user's interaction point; they are different according to whether the interaction point connects to a Caller telephone or a Called telephone.…”
Section: Specification Of Features In the Context Of A System (Step )mentioning
confidence: 99%
“…The semantics of LOTOS is based on algebraic concepts and it can be used to describe systems at several levels of abstraction and in several ways, some of which may describe the constraints that determine the system behavior rather than the system architecture [30] [29] [11]. This is an advantage because of various reasons: the language can be used in several phases of the software development cycle (from requirements to implementation [29] [1]); it provides flexibility to address a variety of applications; and it lends itself to many design and validation techniques.…”
Section: Motivationmentioning
confidence: 99%
“…In papers that present LOTOS specifications, structural diagrams are often used [20] [11]. This is useful in order to describe the components of a system and their external interaction points (the gates) but is not useful during the specification validation phase, neither to understand traces, nor to help in the exploration of alternative behaviors in a step-bystep approach.…”
Section: Motivationmentioning
confidence: 99%
“…It provides simplicity and comprehensibility in specifying complicated communication among multiple concurrent processes such as mutual exclusion and dynamic job assignment, which are frequently used in recent communication protocols. In addition, multi-way synchronization enables the constraint oriented specification style [5,13] where each functional unit of a system is designed as an independent module and then appropriate constraints (described as processes) are specified among those modules so that they work cooperatively. This technique is useful, for example, when we frequently need to modify constraints among modules and/or modify internal structure of each functional unit.…”
Section: Introductionmentioning
confidence: 99%