By Topic

Software Specification and Design, 1996., Proceedings of the 8th International Workshop on

Date 22-23 March 1996

Filter Results

Displaying Results 1 - 25 of 28
  • 8th International Workshop on Software Specification and Design

    Publication Year: 1996
    Request permission for commercial reuse | PDF file iconPDF (164 KB)
    Freely Available from IEEE
  • Author index

    Publication Year: 1996
    Request permission for commercial reuse | PDF file iconPDF (42 KB)
    Freely Available from IEEE
  • Specification and verification of real-time properties using LOTOS and SQTL

    Publication Year: 1996, Page(s):75 - 84
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (796 KB)

    We present a new approach to the formal specification of distributed real-time systems using the formal description technique LOTOS together with a real-time temporal logic SQTL. This approach characterized by a separation of concerns, aims to construct abstractly a model from the a functional specification according to real-time constraints. The functional behaviour is described in LOTOS without ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Industrial software architecture with Gestalt

    Publication Year: 1996, Page(s):176 - 180
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (401 KB)

    The architecture of a software system specifies, among other things, its decomposition into parts and the communication between those parts. The structure of this decomposition and interconnection is separable from the protocols (types and sequencing) of communication. A language for specifying this structure and a toolset for checking consistency between structure specifications and code would pr... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A survey of architecture description languages

    Publication Year: 1996, Page(s):16 - 25
    Cited by:  Papers (60)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (862 KB)

    Architecture description languages (ADLs) are emerging as viable tools for formally representing the architectures of systems. While growing in number, they vary widely in terms of the abstractions they support and analysis capabilities they provide. Further, many languages not originally designed as ADLs serve reasonably well at representing and analyzing software architectures. This paper summar... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software package requirements and procurement

    Publication Year: 1996, Page(s):141 - 145
    Cited by:  Papers (15)  |  Patents (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (474 KB)

    The paper outlines the problems of specifying requirements and deploying these requirements in the procurement of software packages. Despite the fact that software construction de novo is the exception rather than the rule, little or no support for the task of formulating requirements to support assessment and selection among existing software packages has been developed. We analyse the problems a... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A comedy of errors: the London Ambulance Service case study

    Publication Year: 1996, Page(s):2 - 4
    Cited by:  Papers (35)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (259 KB)

    This paper provides an introduction to the IWSSD-8 (8th International Workshop on Software Specification and Design) case study-the “Report of the Inquiry Into the London Ambulance Service”. The paper gives an overview of the case study and provides a brief summary. It considers how the case study can be used to orient discussion at the workshop and provide a bridge between the various... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Truth vs. knowledge: the difference between what a component does and what we know it does

    Publication Year: 1996, Page(s):181 - 185
    Cited by:  Papers (16)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (427 KB)

    Conventional doctrine holds that specifications are sufficient, complete, static, and homogeneous. For system level specifications, especially for software architectures, conventional doctrine often fails to hold. This can happen when properties other than functionality are critical, when not all properties of interest can be identified in advance, or when the specifications are expensive to creat... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A mathematical toolbox for the software architect

    Publication Year: 1996, Page(s):46 - 55
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (876 KB)

    It is suggested that category theory provides the right level of mathematical abstraction to address languages for describing software architectures. Contrarily to most other formalisations of SA concepts, category theory does not promote any particular formalism for component and connector description but provides instead the very semantics of the concepts that are related to the gross modularisa... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Learning from inconsistency

    Publication Year: 1996, Page(s):136 - 140
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (501 KB)

    The paper argues that inconsistencies that occur during the development of a software specification offer an excellent way of learning more about the development process. We base this argument on our work on inconsistency management. Much attention has been devoted recently to the need to allow inconsistencies to occur during software development, to facilitate flexible development strategies, esp... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Tool specification with GTSL

    Publication Year: 1996, Page(s):26 - 35
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (934 KB)

    The definition of software development methods encompasses the definition of syntax and static semantics of formal languages. These languages determine documents to be produced during the application of a method. Developers demand language-based tools that provide document production support, check the syntax and static semantics of documents, and thus implement methods. Method integration must de... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A computational mechanism for parallel problem decomposition during requirements engineering

    Publication Year: 1996, Page(s):159 - 163
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (488 KB)

    The earliest phases of requirements engineering capture large amounts of diverse facts about the problem domain. These facts must be structured according to useful decompositions of that problem domain. Existing goal oriented decompositions methods do not address issues specific to such decomposition. The paper outlines a tentative model of parallel problem domain decomposition, and describes a co... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Relating CHAM descriptions of software architectures

    Publication Year: 1996, Page(s):66 - 74
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (616 KB)

    We propose an approach to compare descriptions of software architectures based on the CHAM formalism. The need to compare descriptions of the same system at different level of abstraction often arises typically when the software practice uses a stepwise refinement approach. Differently from other approaches presented in the literature, our framework allows for expressing correct refinement both of... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Design decision trees

    Publication Year: 1996, Page(s):172 - 175
    Cited by:  Papers (8)  |  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (416 KB)

    The paper proposes a formalism to be used as a systematic approach to incrementally document, refine, organise and reuse the architectural knowledge for software design. The formalism is a hierarchical organisation of design patterns into a design decision tree (DDT) that is a partial ordering of design decisions put in the context of the problem requirements and the constraints imposed by earlier... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Requirements elicitation driven by interviews: the use of viewpoints

    Publication Year: 1996, Page(s):85 - 94
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (761 KB)

    Requirements elicitation in the context of organizational information systems is a very hard task, being very dependent on the experience and cleverness of the team performing the elicitation. In such a context the use of interviews is common and seen as the major technique for obtaining the requirements from the actors in the organization. We have been working with the idea of a general interview... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A case study in architectural modeling: the AEGIS system

    Publication Year: 1996, Page(s):6 - 15
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (912 KB)

    Software architecture is receiving increasingly attention as a critical design level for software systems. However the current practice of architectural description is largely informal and ad hoc, with the consequence that architectural documents serve as a poor communication mechanism, are difficult to analyze, and may have very little relationship to the implemented system. In an attempt to addr... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Formalising system structure

    Publication Year: 1996, Page(s):95 - 104
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (752 KB)

    Darwin is a language designed for configuring distributed systems. A system is modelled as a decompositional hierarchy of components with interfaces. Connections are represented as bindings between interfaces. Darwin programs define component types. Configurations of a system are obtained by instantiating these types. Configurations have to comply with a number of constraints on the system structu... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A “coming and going” approach to specification construction: a scenario

    Publication Year: 1996, Page(s):155 - 158
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (280 KB)

    The construction of a specification, or a program is rarely done in one single step and in a linear way. “Coming and Going” among the different components of the specification are often performed, i.e., the specification needs to be frequently revisited. The paper illustrates this approach on the production cell case study by means of a scenario of development. It shows what could be a... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • How modeling methods affect the process of architectural design decisions: a comparative study

    Publication Year: 1996, Page(s):125 - 134
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (851 KB)

    A number of modeling methods have been proposed and practiced for the analysis process of software development. As many modeling methods cover the design process as well, it would be natural to ask how those methods affect the critical decisions made during the transition phase from the analysis to the architectural design, but there is little research tackling this problem. The reasons might be t... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A framework for heterogeneous concurrency control policies in distributed applications

    Publication Year: 1996, Page(s):105 - 114
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (855 KB)

    Several concurrency control policies for distributed systems have been proposed both by theorists and practitioners. We present an abstract framework for concurrency control policies for the serial model. This framework supports a wide range of policies and permits the integration of different policies within the same application. It is shown how the framework is instantiated for several policies:... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Supporting the selection of software requirements

    Publication Year: 1996, Page(s):146 - 149
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (470 KB)

    The choice of candidate requirements for implementation is a primary determinant of customer satisfaction. It is argued that a set of requirements should be chosen which reflects both the importance and the estimated cost of each candidate requirement. A contribution-based method is proposed which determines importance and estimates cost and industrial experience in applying this method is reporte... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Towards a formal specification method for graphical user interfaces using modularized graph grammars

    Publication Year: 1996, Page(s):56 - 65
    Cited by:  Papers (2)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (822 KB)

    Well designed graphical user interfaces offer a high potential to increase the productivity of human users. The necessary condition for such a good performance is that the user interface represents the semantics of the underlying application in a clear and comprehensible way. This means, especially, that not only syntactical layout but also semantic consistency conditions between the various inter... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Visual presentation of software specifications and designs

    Publication Year: 1996, Page(s):115 - 124
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1120 KB)

    Formal methods hold the promise for high dependability in the design of critical software. However, software engineers who employ formal methods need to communicate their design decisions to users, customers, managers, and colleagues who may not be in a position to acquire a full understanding of the formal notation being used. Visualizations derived from formal specifications and designs must be ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Concern-driven design for a specification language supporting component-based software engineering

    Publication Year: 1996, Page(s):150 - 154
    Cited by:  Papers (1)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (439 KB)

    The paper concerns an approach to software development which is referred to as Component Based Software Engineering (CBSE). The approach is based on the principle of extensive use of preexisting, standard or customizable components in building new systems. CBSE has received considerable attention recently since it promises to bring to software development the engineering discipline that has been l... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • ACME/PRIME: requirements acquisition for process-driven systems

    Publication Year: 1996, Page(s):36 - 45
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1306 KB)

    The paper discusses a requirements gathering methodology and tool support for a class of systems we term service oriented systems. The requirements acquisition methodology that our tools support is, not surprisingly, a process centered methodology, since the processes of the system map to the services provided by our organization. The ACME/PRIME tool to support this methodology is built upon a con... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.