Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
77:releasenotes [2021/07/13 10:28] – emr | 77:releasenotes [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 11: | Line 11: | ||
So if you want to benefit from a stream of new features every few months, feel free to upgrade to version 7.7. You need to be prepared to upgrade to version 7.8 within 3 months after it is released though. | So if you want to benefit from a stream of new features every few months, feel free to upgrade to version 7.7. You need to be prepared to upgrade to version 7.8 within 3 months after it is released though. | ||
- | If you want to upgrade your system less frequently, we suggest to stay on version 7.6 an benefit from its Long Term Support. | + | If you want to upgrade your system less frequently, we suggest to stay on version 7.6 and benefit from its Long Term Support. |
===== Association Grouping* ===== | ===== Association Grouping* ===== | ||
Line 45: | Line 45: | ||
Before version 7.7, interfaces were shown between process versions with the same name. This capability has been removed. | Before version 7.7, interfaces were shown between process versions with the same name. This capability has been removed. | ||
- | ===== Scheduled | + | ===== Scheduled |
Some process changes should be made effective at a specific date, e.g. at the first day of a month. With Stages 7.7, the release automations can be configured so reviewers and/or approvers can set a specific date and time when the process will be released and marked as valid. | Some process changes should be made effective at a specific date, e.g. at the first day of a month. With Stages 7.7, the release automations can be configured so reviewers and/or approvers can set a specific date and time when the process will be released and marked as valid. | ||
Line 55: | Line 55: | ||
[[https:// | [[https:// | ||
- | ===== Value streams | + | ===== Value Streams |
- | The value stream mapping capabilities that have been introduced in previous releases are now available in each new Stages | + | Value streams are a method to manage cross-functional and cross-organizational activities and provide macro views of a process landscape. |
+ | |||
+ | The value stream mapping capabilities that have been introduced in previous | ||
[[https:// | [[https:// | ||
Line 63: | Line 65: | ||
If you have a customized metamodel version, please contact your respective product consultants for more info. | If you have a customized metamodel version, please contact your respective product consultants for more info. | ||
- | ===== Compliance | + | ===== Compliance |
A new report has been added that can be run from a reference model workspace to provide an overview of all mappings and coverage across all workspaces where that reference model has been mapped. | A new report has been added that can be run from a reference model workspace to provide an overview of all mappings and coverage across all workspaces where that reference model has been mapped. | ||
Line 71: | Line 73: | ||
As the report shows both the coverage and the number of mappings for a particular standard requirement, | As the report shows both the coverage and the number of mappings for a particular standard requirement, | ||
- | If you are upgrading from a previous version, you can download the report here. | + | If you are upgrading from a previous version, you can [[: |
===== Process Feedback in Codebeamer ===== | ===== Process Feedback in Codebeamer ===== | ||
Line 111: | Line 113: | ||
</ | </ | ||
- | ===== Support for feedback issue collectors | + | ===== Support for Feedback Issue Collectors |
We added the new [[: | We added the new [[: | ||
Line 127: | Line 129: | ||
* The access to PDF exports can now be controlled via its own security domain. While upgrading to version 7.7, all users with process read permissions are automatically given this new permission. | * The access to PDF exports can now be controlled via its own security domain. While upgrading to version 7.7, all users with process read permissions are automatically given this new permission. | ||
* The Y scales in the user activity statistics under '' | * The Y scales in the user activity statistics under '' | ||
+ | * The " | ||
+ | |||
+ | ===== End of Life for CMMI in Stages ===== | ||
+ | |||
+ | CMMI (Capability Maturity Model Integration) has been one of the first quality models for software development. For over 30 years, numerous organizations matured their software development practices with the help of CMMI and many other standards and quality models have been inspired by it. Starting with CMMI V1.2, the standard has been available as a reference model in Stages, culminating with the release of CMMI V2.0 a few years ago. | ||
+ | |||
+ | In recent years, the relevance of CMMI in the industry has diminished and other standards like Automotive SPICE have taken its place. Therefore, we have decided to not support CMMI model versions beyond the current version 2.0. CMMI V2.0 will be the last version available as a reference model for Stages. Consequently, | ||
+ | |||
+ | Method Park has been a proud supporter of CMMI for over 15 years and we thank everyone in the CMMI community for their inspiration, | ||
+ | |||
+ | ===== How to Upgrade to Version 7.7 ===== | ||
+ | |||
+ | Please [[stages-support@methodpark.com? | ||
===== Notes ===== | ===== Notes ===== |