ObjectWeb Consortium
Search ObjectWeb Mail Archive: 

Advanced Search - Powered by Google


Mail Archive Home | architecture List | December 2003 Index

<--  Date Index  --> <--  Thread Index  -->

RE: [architecture] General considerations on objectweb development process


Pascal,

Thanks for this proposal, I am in favor of pushing for more formalism
since OSMOSE provides us some resources to do so and it will help the
community at large.

Thanks,
Christophe


-----Original Message-----
From: pascal.llorens@xxxxxxxxxxxxxxxxxx
[mailto:pascal.llorens@xxxxxxxxxxxxxxxxxx]
Sent: jeudi 4 décembre 2003 15:06
To: architecture@xxxxxxxxxxxxx
Subject: [architecture] General considerations on objectweb development
process



Hi,

Concerning OSMOSE ITEA European project which is a support
to Objectweb platforms (Jonas, OpenCCM and Oscar) it appears
at the current stage of the project a problem in the global process:

It seems necessary to open discussions and/or get details for objectweb
participants on the current Objectweb process to conduct framework
developments.
OSMOSE includes about 20 partners collaborating on framework developments.
The project is started since some months and obviously, a problem arises to
integrate homogenously the interest of each partner in common frameworks.

The feeling is that each partner is conducting works following its own
interests,
which is natural taken into account that they invest money themselves for
the community.
While each partner is willing to start modelling keeping in mind its own
objectives,
their considerations are often strongly linked to a targeted platform and
worse to a specific programming language.

Consequently, all objectives become a mess, and it is nearly
impossible to start an homogenous work that will be fruitful for the
community in the large. To meet the expectations of each partner, we propose
to
introduce and perform a specification phase between the current phase
(requirements gathering) and the modelling process:

this phase will address a global analysis and take into account
the objective of everyone. It is not intended to propose a heavy process but

just to draw the global architecture of each framework describing the
following items:

- Introduce the framework and the synthesis of the objective
- Identify the framework components (not software component meaning)
- Define the aims of each those components
- Define the data flow between the components
- Identify the internal components interfaces
- Identify the external components interfaces
- Identify the constraints

Here identification and definition must be at the system/functional level
 and not at the API or programming level.

Thanks in advance to the objectweb college of architects for an early reply
and feebback on these considerations.

Regards

--
Pascal Llorens
THALES COMMUNICATIONS FRANCE
SC2 - Software Core for Computer-based systems
1-5, Avenue Carnot / BC4
91883 Massy CEDEX
Tel 01 69 75 31 83
Fax 01 69 75 31 79
mailto:pascal.llorens@xxxxxxxxxxxxxxxxxx






<--  Date Index  --> <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.