Following are high-level Capella key features. For a more detailed description, please refer to the dedicated page on the website.
- First, Capella defines an engineering language, that has been specified by recognized engineering experts from Thales. The resulting intuitive engineering environment allows the engineers to concentrate on the definition of their systems and software architectures instead of having to determine how to use a complex general purpose modelling language such as UML or SysML to capture their information. It also shorten the learning curve of new engineers in a project ;
- As a tool, Capella automates engineering tasks ensuring productivity and quality, avoiding engineers to perform repetitive and cumbersome modelling tasks (e.g. automated maintenance of the model out of graphical editing in compliance with the unified engineering language business rules, automatically proposing pertinent information while editing information also based on the engineering rules, producing information out of model information such as function to component allocation matrices, checking additional engineering rules wherever and whenever needed, etc.). Model information consistency is systematically and automatically maintained during the editing process and can also be evaluated a posterior by advanced checking tools ;
- It is also designed to provide a framework ensuring a seamless engineering workflow. Tooling is provided and can be completed to manage information propagation and maintenance and to manage traceability at different stages of the engineering activities: internally between engineering levels, externally from upstream and to downstream engineering phases or with specialty engineering activities and environments. Transitions is ensured in an iterative and conservative way ;
A Capella major innovation is to provide the built-in support to Viewpoints. Viewpoints, through language and tooling extensions, can be used for:
- Adding additional engineering preoccupations (e.g. Performance, Safety, Costs, etc.) to the engineering backbone for addressing speciality engineering ;
- Or specializing the engineering environment (i.e. for a Domain -e.g. ATM or Avionics-) for customisation.
- Multi-criteria analysis of the Systems and Software Architectures through a combination of Viewpoints allows effective early validation during the definition phase, i.e. before the implementation and the IVV phases, inducing significant re-engineering costs savings ;
- Finally, Capella is compatible with multi-user and configuration management services ;
- Capella provides engineering know-how and best practices capitalisation and reuse at all levels : by tooling an Arcardia process in the backbone engineering environment, but also by allowing the definition and usage of dedicated engineering viewpoints.
The project leadership certifies that the APIs in this release are "Eclipse Quality".
For now, there is no specific issue detected on the Capella solution architecture.
The role of Kitalpha is twofold:
- Providing basic components from the Kitalpha Core Technology Kit (e.g. Transposer)
- Extending Capella with Viewpoints for System co-engineering
Capella is extensible with add-ons (available in a specific Git repository)
- System to Subsystem Transition
- XML Pivot
- HTML DocGen
In a near future, Capella Studio will be provided to create Capella Viewpoints (also available in a specific Git repository)
For now, there is no specific security issue detected on the Capella solution.
All communication links regarding Capella solution are up-to-date:
- Wiki with "News" section
Website with different sections:
- Installation instructions on Getting Started page
- Community links
- Download page for Capella solution and Documentation
- Events around Capella solution (conferences, talks, etc.)
- Links to YouTube dedicated channel for Capella as well as LinkedIn page and Twitter
- Project page
- Books and sample use-case to come this year
- Bugzilla, Hudson instance, etc.
The quality is ensured through:
Capella solution UI is compliant with User Interface Guidelines.
The workbench is decomposed as shown in the Wiki figure:
- On the left, the Capella "model" project explorer
- In the center, the Overview for Arcadia phases and Diagrams editors
- Property views and Semantic browser at the bottom
- Fast linker (optional) in the bottom left-hand corner providing facilities for diagrams edition
No APIs and significant features are intended to be deprecated in a near future.
Improvements this year on Capella solution feature:
- Performance increase
- Palettes customization
- Development of extensions
User, adopter and developer/committer:
- Initiator of the Capella solution: Thales
Consortium of the 3-years Clarity project
- Improvement of the Capella solution: bug fixes, improvements (functional, non-functional), enhancements
- Training to the methodology,
- Coaching to ease the adoption
- Books being written (Reference, Encyclopedia, Exercises)
- Sustainability ensured with support, training and coaching
- External partners showing interest in Capella solution through available communication means:
- Dissemination: Publications, Talks, Conferences (EclipseCon France, Europe, NA, PolarSys Day, etc.), are referenced in the website dedicated page
- Active forum (~100 msg), mailing-list and Bugzilla
- The first documentation has been made available for download in the website
- Gerrit is enabled to accept external contributions: Changes are uploaded to Gerrit but don’t actually become a part of the project until they’ve been reviewed and accepted by a committer
- Capella is built on the Capella HIPP