Videos · Features in a minute · Collaboration
Impact Before a Change Is Applied
See what a change touches before anyone approves it
A change request in Holarch shows what each proposed change would touch before anyone approves it: the items it affects directly, and the items one step further to check, such as the tests that verify a requirement. When a change touches a baselined requirement, the approval lists what needs re-review against the approved text. Applying the request is one undo step, and its History keeps the impact as it was when the change went in. The example is the CubeSat EO-1 demo project.
In more depth: the tutorial Baseline, Change, Impact.
Features: Collaboration · Help: Change Requests
Shows Holarch 2.29. Plays from holarch.app; see the Privacy Policy.
← Previous highlight · Next highlight →
Related videos
- Holarch: One Change, Connected 2:36Overviews
- Links to Review After a Change 1:09Features in a minute
- Tutorial 3: Trace Requirements 3:03Hands-on tutorials
- Training 2.2: Tracing Needs to Requirements 2:07Training course
- CubeSat 08: Traceability 3:29Worked example: CubeSat EO-1