Browse Prior Art Database

Distributed Software Solution Generation and Language Disclosure Number: IPCOM000192682D
Original Publication Date: 2010-Jan-28
Included in the Prior Art Database: 2010-Jan-28
Document File: 5 page(s) / 38K

Publishing Venue



Distributed Software Solution Generation language is a proposal to enable the specification and generation of software solution patterns based on architectural descriptions, and platform characteristics. This solution proposes to take a knowledge of the functional and non functional characteristics of multiple potential software platform components, and an understanding of a desired solution architecture, and to generate a set of architectural recommendations and templates to meet the needs of that solution.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 33% of the total text.

Page 1 of 5

Distributed Software Solution Generation and Language

Distributed software solutions, such as those implied by SOA-based implementations, are implemented across a range of technical platforms, each with varying non-functional criteria (performance, scalability, quality of service...) and varying best practices and technical patterns. This makes the design and development of these solutions heavily dependent on the experiences and personal biases of individual software architects. Further, these software architects often operate within only a subset of the software platforms that could be considered for a given solution, and have difficulty assessing the relative strengths and weaknesses of various platforms. All of this means that arriving at a formalized assessment of how a given software solution can be best deployed across a heterogeneous range of software platforms is a difficult and subjective process.

Distributed Software Solution Generation is a proposal to formalize this process through the encoding of the characteristics of software platforms (through a language) such that architectural specifications specified in an existing Architectural Description Language (ADL) may be evaluated against these characteristics. The outcomes of these evaluations may then be used to generate template solution specifications that capture the optimal distribution of a software system over the available platforms, taking highest advantage of the encoded characteristics of those platforms. These encoded characteristics include a range of technical and non-technical characteristics as detailed in section 2 below. "Platform" in this case can include any element of the infrastructure being evaluated from the hardware platform, through the OS, middleware to any application solutions being integrated within the architecture being expressed through an ADL.

Note that an Architectural Description Language (ADL) is an existing and well recognized concept - and is quite


[This page contains 1 picture or other non-text object]

Page 2 of 5

distinct from this proposal. The intent of an ADL is the specification of the key characteristics of a proposed architecture. This proposal takes this specification and a newly proposed platform metadata description (business and technical metadata) and automates the reasoning required to make solution recommendations based on these inputs.

This proposal consists of two main components:

1. The specification of a Software Platform Metalanguage the encodes characteristics of software platforms such that evaluations of those platform for the implementation of components of a software architecture can be formalized. The encoded metrics that are proposed include, but are not limited to:

Flexibility metrics (late v early binding / degree of externalization / ability to update flow logic at runtime...) Per...