Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887
banner image
image of Volume 1, Issue 2
Online ISSN 1751-8814 Print ISSN 1751-8806

IET Software

Volume 1, Issue 2, April 2007

Volumes & issues:

Volume 1, Issue 2

April 2007

Show / Hide details

    • Petri-nets for formal verification of MAC protocols
      • Author(s): R.J. Haines ; G.R. Clemo ; A.T.D. Munro
      • Source: IET Software, Volume 1, Issue 2, p. 39 –47
      • DOI:  10.1049/iet-sen:20060057
      • Type: Article
      • + Show details - Hide details
      • p. 39 –47 (9)
        Full or partial reconfiguration of communications devices offers both optimised performance for niche scenario-specific deployments and support for de-regulated radio spectrum management. The correctness of the protocols or protocol-enhancements being deployed in such a dynamic and autonomous manner cannot easily be determined through traditional testing techniques. Formal description techniques are a key verification technique for protocols. The Petri-net formal description technique offers the best combination of intuitive representation, tool-support and analytical capabilities. Having described key features and analytical approaches of Reference-nets (an extended Petri-net formalism), a case study is presented applying this approach to a contemporary research area: IEEE 802.11 centralised control mechanisms to support delay-sensitive streams and bursty data traffic. This case study showcases the ability both to generate performance-oriented simulation results and to determine more formal correctness properties. The simulation results allow comparison with published results and show that a packet-expiration mechanism places greater demands on the contention-free resource allocation, while the mathematical analysis of the model reveals it to be free of deadlock and k-bounded with respect to resources. The work demonstrates the potential that the Petri-net formal method has for analysing process and protocol models to support reconfigurable devices.
        Add to favourites
        Export citations
      Scientific programming with Java classes supported with a scripting interpreter
      • Author(s): S. Papadimitriou
      • Source: IET Software, Volume 1, Issue 2, p. 48 –56
      • DOI:  10.1049/iet-sen:20060048
      • Type: Article
      • + Show details - Hide details
      • p. 48 –56 (9)
        jLab environment provides a Matlab/Scilab like scripting language that is executed by an interpreter, implemented in the Java language. This language supports all the basic programming constructs and an extensive set of built in mathematical routines that cover all the basic numerical analysis tasks. Moreover, the toolboxes of jLab can be easily implemented in Java and the corresponding classes can be dynamically integrated to the system. The efficiency of the Java compiled code can be directly utilised for any computationally intensive operations. Since jLab is coded in pure Java, the build from source process is much cleaner, faster, platform independent and less error prone than the similar C/C++/Fortran-based open source environments (e.g. Scilab and Octave). Neuro-Fuzzy algorithms can require enormous computation resources and at the same time an expressive programming environment. The potentiality of jLab is demonstrated by describing the implementation of a Support Vector Machine toolkit and by comparing its performance with a C/C++ and a Matlab version and across different computing platforms (i.e. Linux, Sun/Solaris and Windows XP).
        Add to favourites
        Export citations
      Survey of component-based software development
      • Author(s): S. Mahmood ; R. Lai ; Y.S. Kim
      • Source: IET Software, Volume 1, Issue 2, p. 57 –66
      • DOI:  10.1049/iet-sen:20060045
      • Type: Article
      • + Show details - Hide details
      • p. 57 –66 (10)
        Because of the extensive uses of components, the Component-Based Software Engineering (CBSE) process is quite different from that of the traditional waterfall approach. CBSE not only requires focus on system specification and development, but also requires additional consideration for overall system context, individual components properties and component acquisition and integration process. The term component-based software development (CBD) can be referred to as the process for building a system using components. CBD life cycle consists of a set of phases, namely, identifying and selecting components based on stakeholder requirements, integrating and assembling the selected components and updating the system as components evolve over time with newer versions. This work presents an indicative literature survey of techniques proposed for different phases of the CBD life cycle. The aim of this survey is to help provide a better understanding of different CBD techniques for each of these areas.
        Add to favourites
        Export citations

Most viewed content for this Journal

Article
content/journals/iet-sen
Journal
5
Loading

Most cited content for this Journal

Print this page
This is a required field
Please enter a valid email address