By Topic

Engineering of Computer Based Systems, 2000. (ECBS 2000) Proceedings. Seventh IEEE International Conference and Workshopon the

Date 3-7 April 2000

Filter Results

Displaying Results 1 - 25 of 51
  • Proceedings Seventh IEEE International Conference and Workshop on the Engineering of Computer Based Systems (ECBS 2000)

    Save to Project icon | Request Permissions | PDF file iconPDF (244 KB)  
    Freely Available from IEEE
  • IEEE/IFIP Joint Workshop on Formal Specifications of Computer-Based Systems

    Page(s): 382
    Save to Project icon | Request Permissions | PDF file iconPDF (11 KB)  
    Freely Available from IEEE
  • Author index

    Page(s): 398
    Save to Project icon | Request Permissions | PDF file iconPDF (6 KB)  
    Freely Available from IEEE
  • A component-based architecture for software communication systems

    Page(s): 36 - 44
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (124 KB)  

    We examine the usefulness of component-based software-engineering for the implementation of software communication systems. We present an architecture that allows to divide protocol software into fully de-coupled components that can be plugged together using visual builder tools to rapidly prototype flexible, robust, and application-tailored communication protocols. We show the feasibility of component-based protocol engineering by demonstrating how a simple transport protocol was realized. A discussion about advantages and impacts concludes this paper View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Formal parameters synthesis for track segments of a subway mesh

    Page(s): 263 - 271
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (144 KB)  

    The aim of this work is to apply formal specification techniques to model real-time distributed systems arising from real-world applications. The formal models discussed here are based on the notion of hybrid automata. The target system is the maneuvering yard of a subway mesh. Semi-automatic tools are used in the analysis and verification of the models here developed. The models are also used to synthesize some important parameters of the system wider consideration. All results were obtained on a typical 350 MHz desktop PC, with 320 MB of main memory View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Support for representation of functional behaviour specifications in AP-233

    Page(s): 351 - 358
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (40 KB)  

    This paper discusses the topic of functional behaviour representations from a data exchange point of view. The motivation comes from our work with developing a standard information model for systems engineering data exchange-ISO 10303-233. In this setting it is not sufficient that the exchanged model displays the same behaviour as the original one. When possible, the structure of the original specification shall be maintained. The paper reviews behaviour formalisms identified as being relevant to systems engineering and discusses different options for supporting the behaviour formalisms in the IS010303-233 systems engineering data exchange information model. The structure of the functional behaviour part of the current version of the information model is also outlined View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • On the design of ORBIT

    Page(s): 110 - 118
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (108 KB)  

    Design of highly complex systems relies on effective utilization of multiple tools. The tools vary with the aspect of the design the user is currently interested in. Also, the approaches used to verify the correctness of the design are different for different domains. Because of the importance of verifying the correctness of the design, there is considerable interest in utilizing the different approaches and tools in a complementary manner to provide higher degrees of assurance. Unfortunately, due to constraints on the model representations and incompatibilities among the various tools, heterogeneous design and analysis is not feasible. The ORBIT project was envisaged to address this problem. ORBIT is an heterogeneous, component-based design and analysis environment. This paper presents the original requirements of this environment, details the various design decisions taken towards satisfying the requirements, and presents an overview of the implementation. In particular it discusses the generic framework used (GRAVITY), the integration of simulation and formal verification within the design process, automatic generation of proof obligations for checking designs, verification of constraints in the designs and work on re-usability using persistent storage View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • SAABNet: Managing qualitative knowledge in software architecture assessment

    Page(s): 45 - 53
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (84 KB)  

    Quantitative techniques have traditionally been used to assess software architectures. We have found that early in development process there is often insufficient quantitative information to perform such assessments. So far the only way to make qualitative assessments about an architecture, is to use qualitative assessment techniques such as peer reviews. The problem with this type of assessment is that they depend on the techniques knowledge of the expert designers who use them. In this paper we introduce a technique, SAABNet (Software Architecture Assessment Belief Network), that provides support to make qualitative assessments of software architectures View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Issues in defining, analyzing, refining, and specifying system dependability requirements

    Page(s): 334 - 340
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (116 KB)  

    Requirements specification has long been acknowledged as an area for further research in the development of systems, particularly for those that are computer based. In addition, an IEEE White Paper by Tripp and Keane indicates that current practice regarding system dependability is in large part based on “tricks of the trade ”, and that there is a need to codify “best practices ”. This paper attempts to codify the practice for specifying dependability requirements, by classifying and describing the process and product requirements needed for such specification View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Design tool integration: an exercise in semantic interoperability

    Page(s): 272 - 278
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (72 KB)  

    The integration of software tools used in an engineering process is a problem that arises frequently in large-scale engineering projects. Traditional approaches are insufficient for complex engineering tools and processes. The solution must also account for the evolution of the system, as tools and processes change over time. This paper shows a new approach to the problem, describes the supporting infrastructure, and discusses the background model-integrated generation technology View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Systematic derivation of operational scenarios using ECSAM

    Page(s): 359 - 366
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (296 KB)  

    ECSAM is a method for modeling, analysis, and derivation of requirements of embedded computer systems and their software. Previous ECSAM papers described its application in the conceptual modeling of system internals, providing white box models. The current paper extends the use of ECSAM to the systematic derivation of the system's external specifications taking into consideration the behavior of the environmental systems. The application of the method described in the paper results in a black box external model, which can serve as a basis for the development of operational specifications of the system in terms of system modes and its behavioral processes. The resulting external and internal system models are inherently consistent. The external specifications are translatable into use cases and operational scenarios, which can successively be transformed into operational and test requirements. The approach is demonstrated on a simplified Home Alarm System (HAS). The approach can be automated using CAS2E tools, to systematically generate operational and test requirements from a system's black box external model View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Designing a model-based interaction planner with dialogue analysis

    Page(s): 82 - 90
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (60 KB)  

    We present an approach to computer-based training that takes advantage of two techniques related to modelling. Dialogue modelling (DM) and model-based training (MBT) are examined here with a view to using DM to provide the models needed in MBT. Our work is motivated by the fact that certain domains are very difficult to produce models for, which makes MBT impracticable. We describe a computer-based training agent that has been developed as a result of using dialogue analysis and DM techniques. MBT is investigated as a technique that could be compatible with DM to support instruction through use of dynamic model-based explanations. Together these two techniques enable a computer-based training system to be designed that is able to support technical skills, such as controlling a power plant, and creative skills, such as design View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Enhancing architectural mismatch detection with assumptions

    Page(s): 138 - 146
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (88 KB)  

    Detecting software architecture inconsistencies is a critical issue in software design. Software systems are described in terms of components, component behavior and interaction and mismatch detection is explored through techniques based on behavior analysis. Integration problems, however, are not only caused by behavioral mismatch: components make assumptions about their environment to guarantee functional and non-functional properties. If the actual deployment environment of each component does not satisfy its assumptions, component and system properties may not hold. In this work we propose to extend the idea of architectural mismatch to include the notion of assumption. We concentrate on a subset of possible assumptions and show how software architects can benefit from using them. We also present a discussion on how architecture description languages (ADLs) can be extended to include assumptions View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Architecture-based performance analysis of the COLLINS class submarine open system extension (COSE) concept demonstrator (CD)

    Page(s): 26 - 35
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (136 KB)  

    Being able to predict the overall performance of a computer based system, prior to building it, is one of the greatest challenges facing system engineers today. The emerging discipline of system architecture, by defining a high level abstraction of the overall structure of the system, hopes to provide the foundation for this reasoning. The authors demonstrate an architecture-based performance analysis technique on the COLLINS class submarine Open System Extension (COSE) Concept Demonstrator (CD) system. The layered architectural design of the COSE CD system, together with it's normally probabilistic, repeatable and predictable nature for varying loads, makes it suitable to an architecture-based approach to performance analysis. An architectural model of the system is developed and populated and then used to predict the performance characteristics of service time, waiting time, response time and device utilisation. These predictions are then verified against theoretical performance predictions and validated against a preliminary implementation of the system View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A Java-based CSCW tool for supporting software processes

    Page(s): 368 - 374
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (2164 KB)  

    PSTOOL is designed as a tool of the supporting environment based on P-F method. The P-F method is a description methodology for supporting software processes improvements. It consists of concept model and implementation model. The mechanism of CSCW on the WWW within PSTOOL is described by the user awareness rules, client/server architecture with Java applet. An example of BugFix process on discussing subsystem is used for declaring the flexibility of P-F process's describing power View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A survey of software reuse repositories

    Page(s): 92 - 100
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (84 KB)  

    Reuse libraries are organizations of personnel, procedures, tools, and software components directed toward facilitating software component reuse to meet specific cost-effectiveness and productivity goals. The paper gives a survey of the major software reusable component repositories. This survey will be a base to develop future efficiently searchable, user-friendly, useful, and well-organized repositories View full abstract»

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

    Page(s): 56 - 61
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (144 KB)  

    Because there are different types of software (e.g., language, application, target environment, etc.), different software certification methodologies are needed. Software process improvement schemes have not taken this approach and have therefore suffered in widespread adoption as a result. Their “one approach fits all” perspective is one reason why we are now seeing more customized process improvement schemes being created (e.g., CMM-SSE and the Common Criteria are recent “newcomers” that address developing software with security requirements) and even the call to certify software professionals. This paper presents a framework for customizing certification methodologies according to: (1) the specific needs of the organization requesting assurances about the software's integrity, and (2) the pecularities of that type of software. Each methodology must mirror the nuances of the type of software it was designed for. For example, certifying that a desktop plug-in will behave appropriately requires a different set of assessment technologies than the set of technologies needed to certify that an aircraft control system will behave appropriately. The goal of creating a certification framework is to provide a more systematic way to create and compare software certification methodologies which today does not exist. And from there, we will be able to offer limited software warranties View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Multimedia systems: on the ergonomic design and evaluation of user interfaces and system structures

    Page(s): 256 - 262
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (40 KB)  

    Based on the concept of interdependence between user surface and internal system structure in multimedia systems, we derive ergonomic development criteria and consequences for the development process, and present a short example-points of information-taken from an ongoing project. Special emphasis will be given to the possible evaluation of multimedia systems with regards to their ergonomic attributes View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The use of architecture description languages to describe a distributed measurement system

    Page(s): 185 - 193
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (148 KB)  

    This paper describes and specifies architectural features of an industrial distributed measurement system, using two architectural description languages (ADLs). A discussion of the advantages and disadvantages of the ADLs is given View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A co-operative object-oriented architecture for adaptive systems

    Page(s): 120 - 128
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (80 KB)  

    Adaptive systems should be able to adapt to changes that occur in their operating environment without any external human intervention. Software architectures for such systems should be flexible enough to allow components to change their pattern of collaboration depending on the environmental changes and goals of the system, without changing the actual components themselves. This paper describes a co-operative object-oriented style that is able to represent software architectures for adaptive systems. The connectors in this style, described as co-operations, embody the description of complex interacting behaviour between the architectural components. Depending on the environmental changes, the behavioural adaptability in a co-operative object-oriented architecture is achieved by replacing the connectors. The applicability of the architectural style is demonstrated in terms of a case study of a control system that has to adjust the height of a vehicle's suspension to different road conditions View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Scenario-based software process

    Page(s): 375 - 380
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (64 KB)  

    Scenarios are becoming ubiquitous artefacts in software development. Many researchers view scenarios as the product of the collaboration among developers and users during the requirements definition stage. We believe scenarios should be used in a wider scope, covering the whole development process. In this light, scenarios would be produced at different stages and, like other artefacts, would be in constant evolution. In order to support the scenario evolutionary process and aid the migration between stages, springs the need for a scenario-based software process. Recent research evidenced that the process dimension of scenarios is seldom considered in the literature. In this paper we propose a scenario-based process framework to support the evolution of scenarios. The framework relies on a set of scenario operations/relationships described previously and incorporates configuration management techniques View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Coupling architectures for low-level fieldbusses

    Page(s): 148 - 153
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (768 KB)  

    This paper deals with hierarchical, multiple fieldbus-based architectures using four case studies that present some concepts reusable in developing the interconnections of intelligent sensors and actuators. The single-master, low-level fieldbusses considered involve (1) ASI (Actuator-Sensor-Interface), which is an example of a lowest-level industrial interconnection; (2) NBIP (Nine-Bit Inter-processor Protocol), which is an example of a special purpose link-layer protocol for microcontrollers; and (3) Bitbus, which is an example of well-established fieldbus utilized for almost 20 years in various applications. The paper begins with classification issues; particularly, coupling architectures are treated both from the viewpoint of more classical interconnections of wide-area and local-area networks, and from the viewpoint of fieldbus domain. Next part introduces the ASI and NBIP protocols while the well-known Bitbus is reviewed in applications. To offer more complex insight, implementation tools-developed particularly to support low-level fieldbus interconnecting experiments-are also mentioned. Four case studies demonstrating consequently NBIP-ASI, ASI-ASI, and two different Bitbus-NBIP hierarchical coupling structures create the kernel of the paper. Finally, brief notes about origins, results, and current targets of the project conclude the contribution View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Java-prototyping of hardware/software CBS using a behavioral OO model

    Page(s): 73 - 81
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (168 KB)  

    This paper presents a method to build software-prototypes of Computer-Based Systems (CBS) that describe and simulate parts of software and parts of hardware using a common concurrent software Behavioral Object Oriented Model (BOOM). For the hardware objects this behavioral prototyping can be viewed as a pre-stage of specification and analysis before the real physical design. The CBS prototypes are built in Java using a method called Vowels2. This method permits the development of the prototype as a concurrent application, from the user-requirements to the software programming in Java. The process of prototype description is made step by step. These steps use a subset of the UML graphical diagrams. The Java coding is deduced from these commented diagrams, using general patterns of thread-active-objects linked by customized objects: synchronous stimuli, asynchronous FIFO-queues etc. The method is illustrated by a simplified example containing parallelism synchronization: the blood-test machine View full abstract»

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

    Page(s): 299 - 307
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (80 KB)  

    System level specification and analysis has become a critical issue in designing today's ever increasingly complex systems. System level design is distinguished from other design activities by its heterogeneous nature. Specifically, systems level designers must integrate information from many different design domains in a single design decision making activity. Rosetta is a systems level specification language that addresses problems specific to systems level specification. Rosetta supports specifying heterogeneous systems by providing mechanisms for: (i) constructing architectures involving heterogeneous components and interconnections; and (ii) specifying multiple views of the same component. Specifications are written in the form of formally defined facets. Each facet extends an associated domain theory, allowing it to be defined using a vocabulary specific to that system facet. Facets are assembled through a facet algebra supporting traditional logical operators plus aggregation. This paper concentrates on system specification using Rosetta View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Forensic ECBS: A Situational Assessment

    Page(s): 390 - 392
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (24 KB)  

    First Page of the Article
    View full abstract»

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