Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
72:tailoring [2018/06/15 17:44] – [Manage tailoring] bkkr | 72:tailoring [2018/06/25 18:37] – [Manage tailoring] bkkr |
---|
| |
(not in the software yet, for now, just talk about it and give background) | (not in the software yet, for now, just talk about it and give background) |
| |
We use tailoring to incorporate requirements of project- or program-specific instances in a process. | |
| |
=== Tailoring === | === Tailoring === |
| |
There is no "Ultimate" process that all processses can follow successfully. All of the processes follow the same [[:general:metamodel|]], but they have small variations. Tailoring a process filters out the process activities, work products, roles, etc. for a specific project. For example, a "Safety Manager" role will have different work products based on the level of safety integrity needed, so the information for all other levels is not relevant for a specific project. Tailoring this process allows the safety manager to only see the components that are applicable to the specific project. | We use tailoring to incorporate requirements of project- or program-specific instances in a process. The specific requirements are tailored in/out of a process depending on the specifications of that process. The user viewing the tailored process will only see the relevant information for their project, not the tailored out information. |
| |
| Project- or program-specific processes can be created through module inheritance. Specific requirements of the specific processes can be incorporated by a tailoring mechanism. |
| |
TBD | TBD |
| |
| |