Support for Systems, Software and Requirement Tools
With its expandable set of engineering tool connectors, SECollab provides the ability to read design data from widely used systems, software, requirement and change management tools - IBM, PTC, The Mathworks, Siemens Polarion, Mega, No Magic, Atlassian, Microsoft... Designs gathered on the SECollab platform are graphically rendered and become fully navigable directly in the web browser, stored in a common graph data repository, and fully accessible through OSLC REST API’s.
Reviewers are able to view and browse designs without the need for a tool license, and without having to be trained on how to use each individual application.
SECollab enables a robust configuration management solution across the set of disconnected engineering tools to manage evolutions of each design artifact in relation to the overall project. Instead of manually mapping and communicating individual artifact versions, SECollab provides a common baseline linking together the individual design artifact versions.
SECollab exposes the individual elements of each design artifact and requirement document to enable full traceability across the entire set of engineering artifacts. By using your semantics to describe the information coming from the engineering tools, any design or requirement element can be linked to any other element whether or not it is originated in the same application.
Lightweight/Formal Review Processes
Technical reviews of CONOPS, requirements, architectures, system designs, and other engineering milestones are both a necessity and a pain. Traditional reviews are expensive, time consuming, slow to provide feedback, and prone to opinion-based assessment.
However, when done properly, technical reviews are extremely valuable. A common software design review metric indicates that 50-70% errors can be found through technical reviews.
Expand and formalize your design review process by providing web access to all the design documents to your reviewers. The team can review a set of artifacts at once, to ensure consistency across the team and across deliverables. The project owner is able to assign review tasks to the appropriate team member, indicate the intention of the review, and formally follow the comments and progress of each reviewer.