Virtual Satellite 4 - CORE

Virtual Satellite is a DLR open source software for model based systems engineering (MBSE).

Project Status

Status for Development build.

Status for Integration build.

Status for Master build.

Purpose

Virtual Satellite 4 is the new evolution of MBSE. With a customizable data model it can be tailored to the various needs of individual engineering tasks and project requirements. Rather than the historic approach of trying to create the data model and system engineering language that can handle all possible tasks, the new approach focuses on necessities leading to simple and easy to use applications. The data model of a Virtual Satellite 4 application can be extended by a concept. Such a concept is a set of data model extensions plus functionality to provide corresponding user interfaces and further functionality.

Requirements

Virtual Satellite is based on Java / Eclipse and provides an installable feature with plug-ins for your personal eclipse IDE. The following infrastructure is required:

• Java Development Kit (JDK) 8 - 64 bit
• Windows 7 or Linux Computer - 64 bit

Quickstart for users

If you just want to use Virtual Satellite feel free to download it from the Releases section here on GitHub. A manual is provided as PDF in the upcoming distributions from version 4.10.x onwards. The latest changes on the manual is written in ascii doc and can be found here: de.dlr.sc.virsat.docs.feature/src/docs/VirSat_Core_User_Manual.adoc

Quickstart for developers

1. Open your Eclipse and switch to the Git Perspective.
2. Clone this repository.
3. Import all projects and working-sets via the ProjectSet file in de.dlr.sc.virsat/projectSet
4. Execute the Virtual Satellite build from de.dlr.sc.virsat/launchers
5. Inspect the build artifacts for the p2 repository in de.dlr.sc.virsat.p2updatesite/target

Travis CI and Releases

Tarvis CI is set-up to start a build job for every branch and every new commit to the repository. It executes all relevant tests such as jUnit, SWTBot, Checkstyle, SpotBugs, etc. Making a successful pull-request into development requires all tests to pass.

Starting a Travis CI job on development or integration deploys all relevant artifacts.

For creating a new release, create a tag starting with Release_ on the master branch. All artifacts are automatically deployed.

Provided Features

• Basic modeling concepts such as product structures, mass budgeting, visualization, etc.
• Core engines such as Calculcation Engine, UI Engine, etc.
• Xtext based Concept IDE Tools for creating new concepts, including code generators

Downloads and Deployment

Deployments are done using GitHub Releases as well as sourceforge:

Contribution

We are happy to receive your contributions. Nevertheless in such a big project there is a lot to respect and to obey. One thing to respect are legal requirements such as authorship rights and privacy protection. Therefore, before we can accept your contributions we need you to sign our Contributor License Agreement (CLA). The CLA is provided in English language only:

Contributor License Agreement CLA

Before you sign it and send it to us, you have to read the privacy policy as well. The privacy policy is available in English and German (Deutsch) language:

To contribute to this project follow the given steps:

Declaration of consent data processing and privacy policy

Einverständniserklärung Datenverarbeitung und Datenschutz

If you agree to the CLA and privacy policy, please fill out the CLA and send it back to us. The detailed process of how to submit the documents is described in the documents themself.

Once you are an authorized committer feel free to contribute. We will not activate your account within our organization. Therefore use Pull-Requests to contribute:

1. Create your own fork of the project.
2. Apply your changes.
3. Make sure you own all relevant rights to make this contribution.
4. Make sure you are obeying legal requirements.
5. Create a pull-request of your change to our development branch.

To increase chance that we accept your pull-request, make sure all tests are working. The best indicator is the Travis CI job. Next we will review your pull-request, give comments and maybe accept it.

License

Copyright 2019 German Aerospace Center (DLR)

The German Aerospace Center (DLR) makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the Eclipse Public License Version 2.0 ("EPL"). A copy of the EPL is available at https://www.eclipse.org/legal/epl-2.0. For purposes of the EPL, "Program" will mean the Content.

If you did not receive this Content directly from German Aerospace Center (DLR), the Content is being redistributed by another party ("Redistributor") and different terms and conditions may apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise indicated below, the terms and conditions of the EPL still apply to this content.

DLR trade mark and copyrighted material other than S/W

The DLR trade mark (as the word mark DLR or as combination DLR with the DLR Logo) is a registered and protected trade mark and may not be used without DLR´s prior written permission.

Copyrighted content other than the S/W provided under the indicated Eclipse License Conditions such as images, photographs, videos and texts which are indicated as being under DLR´s copyright through copyright notice (i.g. © DLR 2020) are provided for use under the Terms of use as provided for on DLRs webpage https://www.dlr.de.

Third Party Licenses

Third party licenses are named in the plug-ins where used in the respective aboutfiles folders. At runtime third party licenses can be viewed in the usual Eclipse About dialog. Also check out the Notice file.