Results 11 - 20
of
31
Best Practices for Component-Based Development and Model-Driven Architecture -- Version 1.0
, 2003
"... Although component-based development provides the concepts and mechanisms to manage complexity in large software development efforts, most teams in practice still have to come to grips with the basics. Inexperienced teams perceive the introduction of additional interfaces and rigorously enforced s ..."
Abstract
-
Cited by 5 (5 self)
- Add to MetaCart
(Show Context)
Although component-based development provides the concepts and mechanisms to manage complexity in large software development efforts, most teams in practice still have to come to grips with the basics. Inexperienced teams perceive the introduction of additional interfaces and rigorously enforced subsystem boundaries as avoidable overhead. Especially when a system started out small, and initially a less rigorous approach to system design seemed to work, resistance to change is to be expected. A model-driven approach to component specification and generative techniques can help to simplify the process for componentbased development, and at the same time can enforce standardised implementation of design patterns and ensure adherence to architectural guidelines. This paper summarises lessons from several projects where a model-driven approach and component based development was implemented to address productivity problems. The important issues are surprisingly non-technical and require paying careful attention to team structure and project organisation.
Using XML to implement Abstraction for Model Checking
- In Proc. of ACM Symposium on Applied Computing
, 2002
"... Model Checking has become one of the most powerful meth-ods for automatic verification of software systems. How-ever it is widely accepted that this technique is only usable when the behavior of the system to be analyzed is given by small models, in order to avoid the state explosion problem. The pa ..."
Abstract
-
Cited by 5 (5 self)
- Add to MetaCart
(Show Context)
Model Checking has become one of the most powerful meth-ods for automatic verification of software systems. How-ever it is widely accepted that this technique is only usable when the behavior of the system to be analyzed is given by small models, in order to avoid the state explosion problem. The paper presents oSPIN, an XML-based tool for obtaining abstract versions from a given model written in PHOMELA, which can be verified with the model checker SPIN. This tool follows the theoretical basis presented in [9].
Two-Level Grammar as the Formalism for Middleware Generation in Internet Component Broker Organizations
- Proceedings of GCSE/SAIG Young Researchers Workshop, held in conjunction with the First ACM SIGPLAN Conference on Generative Programming and Component Engineering
, 2002
"... During the software production of any business domain, we will encounter components coming from different component models. Realizing the interoperability among heterogeneous component models at technology domain level is one of the fundamental difficulties of achieving product line constructions at ..."
Abstract
-
Cited by 4 (4 self)
- Add to MetaCart
(Show Context)
During the software production of any business domain, we will encounter components coming from different component models. Realizing the interoperability among heterogeneous component models at technology domain level is one of the fundamental difficulties of achieving product line constructions at business domain level. Our research of automatic glue and wrapper code generation to compose the components adhering to different component models follows the idea of Generative Programming (GP) [Cza00]. The Generative Domain Model (GDM) for glue/wrapper code production consists of two levels: 1) metaspecifications for heterogeneous components from the component level, 2) on the system level, there are component model domain-specific Knowledge Bases (ds-KBs) together with their associated middleware 1 code generators. Two-Level Grammar is the formalism for both the component and system level specifications, thus is the key technology to automate middleware code generation. 1. Introduction and Architectural
A Review of Frame Technology
, 2003
"... Frame Technology was introduced during the early 1980's as an approach to providing significant levels of improvement in software productivity through adaptive reuse. However, despite the claims of order of magnitude improvements and reuse levels of 90%, this technology does not appear to have ..."
Abstract
-
Cited by 2 (0 self)
- Add to MetaCart
Frame Technology was introduced during the early 1980's as an approach to providing significant levels of improvement in software productivity through adaptive reuse. However, despite the claims of order of magnitude improvements and reuse levels of 90%, this technology does not appear to have acquired a corresponding level of popularity, appearing to loose out to the more recent technologies of generative programming and aspect oriented programming. Our interest frame technology stems from our work on the meta-modelling of feature models to support the expression of product line architectures in the UML using a meta-modelling research tool. Whist the tool provides direct support for templates, we sought an approach that would approximate to customisable templates, allowing us to generate specific configurations in response to user choices by severing unused features. Frame Technology appears to offer a potential solution and we present a summary of our investigation of this technology. Finally, we propose future directions of study based around a meta-modelling approach.
Transforming Business Process Models: Enabling Programming at a Higher Level
"... Two practical paradigms are presented, which facilitate domain concepts to be directly used to model business operations: the first paradigm is based on the business artifacts and their life cycle; the second paradigm is based on the business tasks and their sequencing. Transformation is an effectiv ..."
Abstract
-
Cited by 2 (1 self)
- Add to MetaCart
(Show Context)
Two practical paradigms are presented, which facilitate domain concepts to be directly used to model business operations: the first paradigm is based on the business artifacts and their life cycle; the second paradigm is based on the business tasks and their sequencing. Transformation is an effective way to bridge the gap between business level analysis and IT solutions. We present algorithms that transform business process models based on these two paradigms into IT solutions of web service platform. The specific problems we addressed in this transformation are: 1) how to generate the implementation code of an optimal size; 2) how to preserve the natural structure of business process models in the generated code. 1.
AUTOMATIC CODE GENERATION FOR RECURRING CODE PATTERNS IN WEB BASED APPLICATIONS AND INCREASING EFFICIENCY OF DATA ACCESS CODE
"... Today, a lot of web applications and web sites are data driven. These web applications have all the static and dynamic data stored in relational databases. The aim of this thesis is to generate automatic code for data access located in relational databases in minimum time. ..."
Abstract
- Add to MetaCart
Today, a lot of web applications and web sites are data driven. These web applications have all the static and dynamic data stored in relational databases. The aim of this thesis is to generate automatic code for data access located in relational databases in minimum time.
Malaysian Software Engineering Conference (MySEC’05) A Test Specification Code Translator Using Ontology and XML/XSLT Technologies
"... Testing equipment from different vendors utilise different syntax for their test specifications, but writing specifications for the same tests on different platforms is labour-consuming and error-prone. We present a prototype system for the automatic translation of test specifications between platfo ..."
Abstract
- Add to MetaCart
(Show Context)
Testing equipment from different vendors utilise different syntax for their test specifications, but writing specifications for the same tests on different platforms is labour-consuming and error-prone. We present a prototype system for the automatic translation of test specifications between platform-specific languages, the framework of which is reusable for similar scenarios or software projects. We first design a generic representation scheme for test specifications. To perform a translation from a source language S to a target language T, a context free language parser module reverse-engineers test specifications in language S to a platform-independent equivalent in the generic syntax, marked up with XML. An XML/XSLT-driven generator module then transforms the platform-independent test specifications to language T syntax. In addition, we encapsulate knowledge about the tester domain in an ontology to facilitate the translation process. We also found ontologies to be helpful tools for requirements gathering, analysis and design.
Practicalities of Implementing Component-Based Development and Model-Driven Architecture
"... Abstract. Although component-based development provides the concepts and mechanisms to manage complexity in large software development efforts, most teams in practice still have to come to grips with the basics. Inexperienced teams perceive the introduction of additional interfaces and rigorously en ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract. Although component-based development provides the concepts and mechanisms to manage complexity in large software development efforts, most teams in practice still have to come to grips with the basics. Inexperienced teams perceive the introduction of additional interfaces and rigorously enforced subsystem boundaries as avoidable overhead. Especially when a system started out small, and initially a less rigorous approach to system design seemed to work, resistance to change is to be expected. A model-driven approach to component specification and generative techniques can help to simplify the process for component-based development, and at the same time can enforce standardized implementation of design patterns and ensure adherence to architectural guidelines. This paper summarizes lessons from several projects where a modeldriven approach and component based development was implemented to address productivity problems. The important issues are surprisingly nontechnical and require paying careful attention to team structure and project organization. 1
2 Adaptive and Reflective
"... Middleware platforms and related services form a vital cog in the construction of robust distributed systems. Middleware facilitates the development of large software systems by relieving the burden on the applications developer of writing a number of complex infrastructure services needed by the sy ..."
Abstract
- Add to MetaCart
(Show Context)
Middleware platforms and related services form a vital cog in the construction of robust distributed systems. Middleware facilitates the development of large software systems by relieving the burden on the applications developer of writing a number of complex infrastructure services needed by the system; these services include persistence, distribution,
