Title | Due date | Budget | Progress | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
||||||||||||||||||||||||||
Efp types implemented
efp types should allow to express all informations related to efps that are transfered among tools in the "EFP toolbox".
It will express properties (simple and derived), their data types and values. |
|
||||||||||||||||||||||||||
Try to create a DSL for efp evaluation
the DSL allows to write math formulas that contains efps. The aim is to provide a DSL that is easily evaluated.
Preliminary idea: groovy language - efps-types overrides standard operators +,-,*,/ and allows to operate with intervals (or any other data types). Other math functions (sqrt, sqr, sin, cos, ...) will be created as a "category" extension of the object class (not clear yet). The language assumes definitions of epfs values like: def a = new Interval("property A", 10, 20) def b = new Interval("property B", 30, 40) def c = new OneValue("propety C", 40) a user may then write an equotion like: a + b + c - sin(a) * sqrt(c) |
|
|
|||||||||||||||||||||||||
Bundle and relationship representation
Complete representation of surface information on CoSi bundles (current CoSi Bundle Types) and their relationships (links, wirings), in the form of a Java API and UML model.
Acceptance criteria: - Simple application which reads a set of bundles from .jar files in filesystem into this API representation, outputs textual information about bundle and relationship structures. - Documentation matches implementation. |
Overdue | Sep 04, 2009 |
|
||||||||||||||||||||||||
Bundle set loaded
Complete implementation of bundle and relationship information loading into the API representation.
Acceptance criteria: A tool (at least a text UI, better a GUI) which - takes a set of bundles from a testing suite - loads them all - creates internal representation of bundles and their relationships (via provided-required features) - outputs or draws list of bundle descriptions + list of links to other bundles (outgoing, incoming) for each bundle |
Overdue | Dec 31, 2009 |
|
|
|||||||||||||||||||||||
Groovy class comparator working
We have a Groovy class representation comparator which is able to take two GClass-es, run exact type-based compatibility checks and announce the result (B1 compatible/incompatible with B2, with the "none", "spec", "gen", "mut" levels).
Acceptance criteria: - library which performs the comparison on any two GClass-es - if one of the classes is Java (not Groovy), delegates to Java class comparator |
Overdue | Mar 24, 2010 |
|
|
|||||||||||||||||||||||
Standard Java class comparator working
Implementation of bundle type-based comparator. Ported from OSGi implementation as far as possible.
Acceptance criteria: We have a library that - takes 2 JavaTypes JClass-es - performs standard "exact" type-based check - outputs overall verdict - logs detailed difference data Responsible is TPeterka. Should be virtually no work, done by JACC project. |
Overdue | Mar 24, 2010 |
|
|
|||||||||||||||||||||||
Bundle exact type-based comparator working
We have a library + basic system service/bundle which can compare two bundles A,B and decide if B is compatible with A. Includes JavaDoc and PDF documentation.
Acceptance criteria: - Set of testing bundles in which there are compatible and incompatible differences in version streams. - Framework offers a service and basic UI over it to check compatibility of two bundles. - Service informs correctly when user compares any two bundles of this set. |
Overdue | Mar 26, 2010 |
|
|
|||||||||||||||||||||||
Bundle loader
We are able to read a bundle into the BundleTypes API representation (JCosiBundle).
Acceptance criteria: A simple tool exists to demonstrate that - any bundle from a testing set is loaded - on console an output is written with simple text representation - this is done via API that is also used by comparator service in CoSi fw core |
Overdue | Apr 02, 2010 |
|
||||||||||||||||||||||||
Enhanced Java class comparator working
This performs "approximate matches" and returns similarity indication.
|
Overdue | Apr 30, 2010 |
|
|
|||||||||||||||||||||||
Bundle update compatibility checking via enhanced component lifecycle
Hookable lifecycle, lifecycle events. Type compatibility verification on "resolve", "update", service binding events. (We may want to split into two separate milestones.)
Acceptance criteria: A demonstration set of bundles is available which - has a bundle that acts as filter on bundle install and bundle update - listens to bundle lifecycle events and outputs real-time "log" of lifecycle events in the framework When updating a .groovy-only bundle, the type-based comparator kicks in to verify that the new version is compatible with the current one. If yes, update is run, if not, the current bundle is left in the state in which it was when update was called. Includes JavaDoc and PDF documentation. Acceptance criteria: - Set of testing bundles in which there are compatible and incompatible differences in version streams. - Framework spits error messages when user tries to update a bundle to incompatible version. |
Overdue | Apr 30, 2010 |
|
||||||||||||||||||||||||
Framework cleanup and corrections
Fix the different obscurities and bugs that have been found so far.
|
Overdue | Jun 30, 2010 |
|
||||||||||||||||||||||||
Enhanced EFPs implemented
Complex properties, expressions etc.
|
Overdue | Dec 31, 2010 |
|
||||||||||||||||||||||||
EFP repository implemented
The implementation provides user with possibility to load, store or update efps via an user interface. The implementation will also provides efps via efp-types to be available for other tools or participants.
|
Overdue | Apr 15, 2011 |
|
||||||||||||||||||||||||
Attachment of efps to components implemented
The tool provides a user with possibility to attach efps to components. Efps will be loaded from the repository. The user will be able to attach direct efps or functions determining provided efps from required efps.
|
Overdue | Apr 15, 2011 |
|
||||||||||||||||||||||||
EFP evaluation implemented
The implementation allows to evaluate efps in a chain of components. It goes through the graph of components and evaluates resulting efps. The resulting efps will be compared with user requirements that results in a compatibility decision.
|
Overdue | Apr 15, 2011 |
|
|
Home / Developer API / Tour / Get a Project - Solutions for Bug & Issue Tracking, Collaboration Tools, Subversion Hosting, Git Hosting
Cosi - the obsessively black-box component model in osgi style is powered by Assembla.