Overview
What is Team for Capella?
Team for Capella is an add-on for Eclipse Capella that enables multiple team members to collaborate on editing Capella models simultaneously. It is designed to streamline the collaboration process and prevent conflicts that may arise from concurrent updates. This collaborative tool is suitable for companies...
Pricing
Basic
$6,000
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Product Details
- About
- Tech Details
What is Team for Capella?
Team for Capella is an add-on for Eclipse Capella that enables multiple team members to collaborate on editing Capella models simultaneously. It is designed to streamline the collaboration process and prevent conflicts that may arise from concurrent updates. This collaborative tool is suitable for companies of all sizes, including small teams and large organizations. It caters to a variety of professions and industries, such as systems engineers, enterprise architects, software developers, and the aerospace and automotive sectors.
Key Features
Simultaneous collaboration: Team for Capella allows multiple users to work together on the same model by automatically locking and indicating any object being edited to other users, ensuring smooth collaboration without conflicts.
Instant updating: Modifications made by one user on a model element are automatically and instantly propagated across all users' views, eliminating the need for manual refreshes and ensuring everyone works with the most up-to-date model elements.
Explicit locking: Users can explicitly lock a set of model elements when they require an extended period to work on them. The lock is released on-demand by the owner, giving users control over access to specific model elements.
Storage on a shared server: Team for Capella operates on a shared server, allowing authorized team members to access and collaborate on models. The server can be administered to manage system status, connected users, and models stored on one or several databases.
Sharing a local project: Users can export their modeling projects from their local environment to the remote repository, enabling seamless sharing with other team members.
Retrieving a remote project: Projects installed on the shared server can be manually imported into the user's environment or automatically saved to a backup server, ensuring easy access and retrieval of remote projects.
Change history: Team for Capella provides a comprehensive history of commits, allowing users to track changes made on shared models. Users can compare versions, view differences, and identify impacted model elements and diagrams.
Secured access: Data stored in the repositories is protected by user authentication using LDAP. SSL encryption ensures secure exchanges between clients and databases. Access rights can be defined based on user profiles, enhancing data security.
Flexible licensing mode: Team for Capella offers a floating licensing model, allowing for flexible deployment. Licenses can be shared among multiple users over time, and a remote desktop mechanism is supported for low network bandwidth situations. Large organizations can deploy multiple Team for Capella servers simultaneously to meet their specific needs.
Team for Capella Features
- Supported: Real Time Editing
Team for Capella Technical Details
Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
---|---|
Operating Systems | Web-Based, Windows, Linux |
Comparisons
Compare with
Reviews
Community Insights
- Pros
- Cons
Intuitive Interface: Several users have praised the intuitive interface of Team for Capella, making it easy to navigate and use. They have found it particularly beneficial for new users who are unfamiliar with systems modeling.
Efficient Collaboration: Many reviewers appreciate the collaborative aspect of the software, mentioning that it is easy to set up Capella models for multiple team members to access. This feature has facilitated efficient teamwork in creating system designs.
Effective File Management: Users have commended the auto fine-grained lock-out check-out functionality of Team for Capella, which ensures efficient management of model-file access and prevents conflicts when multiple users are working on the same project. This feature has been highly valued by those using the software for prolonged multi-user capella file access.
Cumbersome Jenkins Setup Process: Several users have found the process of setting up a Jenkins server for beginners to be laborious and delicate. They have expressed frustration with the complexity involved in getting started, which has resulted in wasted time and effort.
Lack of Client Tools for Repository Removal: Some users have mentioned that there is a lack of client tools on the Capella side, specifically for removing a repository. Instead, they are required to create an archive from a local version, which they find inconvenient and time-consuming.
Confusing Implementation of Jenkins for Version Backup: Users have reported that the implementation of Jenkins for version backup is not intuitive. This has caused confusion among some users who struggle to understand how to effectively use this feature, resulting in additional difficulties during their modeling projects.