New and noteworthy
SECollab now allows you to implement your very own Traceability model. This comes through a
set of 3 features: the resource types, the queries, and the report templates / reports.
- Resource Types: you can now create custom types to make your resources more specific.
With this, you can say that all resources having DOORS as their tool and a custom doors
property set to SYSTEM are "SystemRequirement". Other resources where the tool is doors
and the same custom doors property is set to SOFTWARE would be another resource type labelled
"SoftwareRequirement". This will allow you to create traceability within your data using
custom links, such as a link "systemToSoftware" that would track how system requirements are
translated to software requirements.
- Queries: queries will help you track how your traceability is done throughout your data.
For that, you may create a query to see SystemRequirement artifacts linked to
- Report templates and reports: Report templates allow you to build a reporting view based
on a given query. This reporting is a full featured report: you can create chapters, down
to any number of levels, and each chapter can be just an introductory chapter (not linked to
a specific query), or serve a display purpose (by being linked to a query and an available
display style). Reports are an application of a given template on a set of Designs. This
allows for one template to evolve, and let all your reports be automatically updated.
Now that you have such features on resource types, queries and report templates,
you may want to share those across your projects and configurations. That's what the
Project template feature is all about. It's still very new, and we plan for quite some
enhancements around that feature, but it's already working good: just create your administration
data in one configuration, create and download a template, then it's up to you to deploy that
template on any configuration and project you want to share that in.
User management: LDAP, archiving
SECollab lets you provide LDAP parameters to authenticate against the LDAP server instead of directly using SECollab.
This frees you of the pain involved by creating all users "by hand". Just register any number of users you might want
directly from the LDAP server, make them members of any projects they belong to, and you're good to go.
This release fixes an issue that prevented publishing a Capella design directly to the server and forced publishing to a file.
The list of known issues can be found on the known issues page.
This version requires going through a migration. To start this migration:
back up your data
- if running on the Jazz platform, proceed with the backup of Jazz' data and indexes as per the tool documentation
- while your application server is shut down, copy (or zip) the workspace folder that is used by SECollab
start the migration process
- start your application server
- head to https://secollab.acme.com/secollab/setup in your browser
- connect using administrator credentials
- read and be careful to understand the implications of starting the migration
- agree to the migration notice
- start the migration
- once the migration is done, head over to https://secollab.acme.com/secollab/