Thanks for your interest in this project.
Kitalpha is an environment to develop and execute MBE (Model-Based Engineering) workbenches for description of systems in system, software and hardware engineering. Kitalpha provides both development and runtime services to define, use and manage architecture frameworks and viewpoints.
Kitalpha is dedicated to implement modelling frameworks and viewpoints, and this in coherence with the ISO/IEC 42010 standard for description of system architecture. In this standard, an architecture framework aggregates viewpoints. Each viewpoint describes at least one system concern, such as non-functional concerns (e.g., performance, safety, security, and cost), for involved stakeholders (e.g., safety engineer). Kitalpha extends the definition of viewpoint to also consider it as an engineering extension which comes with its own metamodels, representations (e.g., diagrams, tables, user interfaces), rules (e.g., validation, analysis, transformation), services and tools to address an engineering specialty. Consequently, an MBE workbench is the result of a flexible assembly of core viewpoints extended by new ones which are, in the context of co-engineering, appropriate and valuable for specialty engineers. The set of all the viewpoints provide a solution for the complete description of a system.
For more detailed information see the Kitalpha Overviews and Project Plan.
Information regarding source code management, builds, coding standards, and more.
The project maintains the following source code repositories
This project uses Bugzilla to track ongoing development and issues.
- Search for issues: https://bugs.eclipse.org/bugs/buglist.cgi?classification=Polarsys&list_id=19950826&product=Kitalpha&query_format=advanced
- Create a new report: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=Kitalpha
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
This project is built using Maven/Tycho.
Before your contribution can be accepted by the project team contributors must electronically sign the Eclipse Contributor Agreement (ECA).
Commits that are provided by non-committers must have a Signed-off-by field in the footer indicating that the author is aware of the terms by which the contribution has been provided to the project. The non-committer must additionally have an Eclipse Foundation account and must have a signed Eclipse Contributor Agreement (ECA) on file.
For more information, please see the Eclipse Committer Handbook: https://www.eclipse.org/projects/handbook/#resources-commit
Ask questions via the project's forum:
Contact the project developers via the project's "dev" list.