Defining the Fluid framework

Anthony Jones*, Dan Cornford

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

In this position paper we present the developing Fluid framework, which we believe offers considerable advantages in maintaining software stability in dynamic or evolving application settings. The Fluid framework facilitates the development of component software via the selection, composition and configuration of components. Fluid's composition language incorporates a high-level type system supporting object-oriented principles such as type description, type inheritance, and type instantiation. Object-oriented relationships are represented via the dynamic composition of component instances. This representation allows the software structure, as specified by type and instance descriptions, to change dynamically at runtime as existing types are modified and new types and instances are introduced. We therefore move from static software structure descriptions to more dynamic representations, while maintaining the expressiveness of object-oriented semantics. We show how the Fluid framework relates to existing, largely component based, software frameworks and conclude with suggestions for future enhancements. © 2007 IEEE.

Original languageEnglish
Title of host publicationIEEE International Conference on Information Reuse and Integration, 2007. IRI 2007
Pages695-700
Number of pages6
DOIs
Publication statusPublished - 2007
Event2007 IEEE International Conference on Information Reuse and Integration, IEEE IRI-2007 - Las Vegas, NV, United Kingdom
Duration: 13 Aug 200715 Aug 2007

Conference

Conference2007 IEEE International Conference on Information Reuse and Integration, IEEE IRI-2007
CountryUnited Kingdom
CityLas Vegas, NV
Period13/08/0715/08/07

Fingerprint

Fluids
Chemical analysis
Semantics
Software
Object-oriented

Bibliographical note

The Second IEEE International Workshop Towards Stable and Adaptable Software Architectures, 13-15 August 2007, Las Vegas (US). © 2007 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.

Keywords

  • object-oriented languages
  • object-oriented programming
  • fluid framework
  • component software
  • object-oriented principle
  • software dynamic representation
  • software stability
  • static software structure description

Cite this

Jones, A., & Cornford, D. (2007). Defining the Fluid framework. In IEEE International Conference on Information Reuse and Integration, 2007. IRI 2007 (pp. 695-700). [4296701] https://doi.org/10.1109/IRI.2007.4296701
Jones, Anthony ; Cornford, Dan. / Defining the Fluid framework. IEEE International Conference on Information Reuse and Integration, 2007. IRI 2007. 2007. pp. 695-700
@inproceedings{940536139f5c46b284cb72a9d3c988ce,
title = "Defining the Fluid framework",
abstract = "In this position paper we present the developing Fluid framework, which we believe offers considerable advantages in maintaining software stability in dynamic or evolving application settings. The Fluid framework facilitates the development of component software via the selection, composition and configuration of components. Fluid's composition language incorporates a high-level type system supporting object-oriented principles such as type description, type inheritance, and type instantiation. Object-oriented relationships are represented via the dynamic composition of component instances. This representation allows the software structure, as specified by type and instance descriptions, to change dynamically at runtime as existing types are modified and new types and instances are introduced. We therefore move from static software structure descriptions to more dynamic representations, while maintaining the expressiveness of object-oriented semantics. We show how the Fluid framework relates to existing, largely component based, software frameworks and conclude with suggestions for future enhancements. {\circledC} 2007 IEEE.",
keywords = "object-oriented languages, object-oriented programming, fluid framework, component software, object-oriented principle, software dynamic representation, software stability, static software structure description",
author = "Anthony Jones and Dan Cornford",
note = "The Second IEEE International Workshop Towards Stable and Adaptable Software Architectures, 13-15 August 2007, Las Vegas (US). {\circledC} 2007 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.",
year = "2007",
doi = "10.1109/IRI.2007.4296701",
language = "English",
isbn = "1424414997",
pages = "695--700",
booktitle = "IEEE International Conference on Information Reuse and Integration, 2007. IRI 2007",

}

Jones, A & Cornford, D 2007, Defining the Fluid framework. in IEEE International Conference on Information Reuse and Integration, 2007. IRI 2007., 4296701, pp. 695-700, 2007 IEEE International Conference on Information Reuse and Integration, IEEE IRI-2007, Las Vegas, NV, United Kingdom, 13/08/07. https://doi.org/10.1109/IRI.2007.4296701

Defining the Fluid framework. / Jones, Anthony; Cornford, Dan.

IEEE International Conference on Information Reuse and Integration, 2007. IRI 2007. 2007. p. 695-700 4296701.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

TY - GEN

T1 - Defining the Fluid framework

AU - Jones, Anthony

AU - Cornford, Dan

N1 - The Second IEEE International Workshop Towards Stable and Adaptable Software Architectures, 13-15 August 2007, Las Vegas (US). © 2007 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.

PY - 2007

Y1 - 2007

N2 - In this position paper we present the developing Fluid framework, which we believe offers considerable advantages in maintaining software stability in dynamic or evolving application settings. The Fluid framework facilitates the development of component software via the selection, composition and configuration of components. Fluid's composition language incorporates a high-level type system supporting object-oriented principles such as type description, type inheritance, and type instantiation. Object-oriented relationships are represented via the dynamic composition of component instances. This representation allows the software structure, as specified by type and instance descriptions, to change dynamically at runtime as existing types are modified and new types and instances are introduced. We therefore move from static software structure descriptions to more dynamic representations, while maintaining the expressiveness of object-oriented semantics. We show how the Fluid framework relates to existing, largely component based, software frameworks and conclude with suggestions for future enhancements. © 2007 IEEE.

AB - In this position paper we present the developing Fluid framework, which we believe offers considerable advantages in maintaining software stability in dynamic or evolving application settings. The Fluid framework facilitates the development of component software via the selection, composition and configuration of components. Fluid's composition language incorporates a high-level type system supporting object-oriented principles such as type description, type inheritance, and type instantiation. Object-oriented relationships are represented via the dynamic composition of component instances. This representation allows the software structure, as specified by type and instance descriptions, to change dynamically at runtime as existing types are modified and new types and instances are introduced. We therefore move from static software structure descriptions to more dynamic representations, while maintaining the expressiveness of object-oriented semantics. We show how the Fluid framework relates to existing, largely component based, software frameworks and conclude with suggestions for future enhancements. © 2007 IEEE.

KW - object-oriented languages

KW - object-oriented programming

KW - fluid framework

KW - component software

KW - object-oriented principle

KW - software dynamic representation

KW - software stability

KW - static software structure description

UR - http://www.scopus.com/inward/record.url?scp=47949125522&partnerID=8YFLogxK

UR - http://ieeexplore.ieee.org/document/4296701/?arnumber=4296701

U2 - 10.1109/IRI.2007.4296701

DO - 10.1109/IRI.2007.4296701

M3 - Conference contribution

SN - 1424414997

SN - 9781424414994

SP - 695

EP - 700

BT - IEEE International Conference on Information Reuse and Integration, 2007. IRI 2007

ER -

Jones A, Cornford D. Defining the Fluid framework. In IEEE International Conference on Information Reuse and Integration, 2007. IRI 2007. 2007. p. 695-700. 4296701 https://doi.org/10.1109/IRI.2007.4296701