In the Analysis subset, scoping a process with Design subset type, Delete protection and default expansion includes these objects at these protections:
|
Object Included by the Scoped Process |
Protection |
Considerations |
|
|---|---|---|---|
|
Scoped process |
Modify |
The scoped process, requested at Delete protection, is downgraded to Modify, but all the child and grandchild processes are included with Delete protection. To delete the scoped process, scope its parent also at Modify protection. |
|
|
Parent, grandparent processes |
Access |
|
|
|
Child, grandchild processes |
Delete |
|
|
|
Dependencies for child processes |
Delete |
|
|
|
Process information views |
Delete |
The only way to delete a view for a process is to have Delete protection on the process. If you request Delete protection for the process and receive a protection downgrade, CA Gen still lets you delete as many views as possible. |
|
|
Process expected effects |
Delete |
|
|
|
Entity type in PAD view |
Access |
|
|
|
Entity type in expected effects |
Access |
|
|
|
PAD (if elementary) |
Delete |
To include the Process Action Diagram (PAD) in the subset, specify default expansion, which includes the fully expanded action blocks of the scoped process and its subordinates and the views of USEd action blocks. |
|
|
Action block USEd by PAD |
Delete |
All Common Action Blocks (CABs) USEd by a PAD are included with Delete protection only if you obtain full expansion of the process. If action blocks are shared among project members, add the action blocks to the subset definition with Access protection (Action diagrams are a separate scoping object.) If anyone has an action block with Delete, no one else can USE that action block in a PAD. The full expansion option ensures that the CABs USEd by the CABs are also included. |
|
|
Copyright © 2013 CA.
All rights reserved.
|
|