Difference between revisions of "Transition requirement"
(Created page with "A transition requirement is a requirement that defines characteristics that a solution must have in order to transition from the current state to the desired future st...") |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
#Transition requirements are temporary. | #Transition requirements are temporary. | ||
#Transition requirements place an emphasis on change management processes. | #Transition requirements place an emphasis on change management processes. | ||
| + | |||
| + | ==Definitions== | ||
| + | According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | ||
| + | :[[Transition requirement]]. A requirement that describes the capabilities the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature. | ||
| + | |||
| + | [[Category: Business Analysis]][[Category: Articles]] | ||
| + | |||
| + | ==Draft descriptions== | ||
| + | The transition requirements are the requirements needed to implement the software application successfully. | ||
| + | |||
| + | Transition requirements refer to the requirements to enable successful implementation of a project. As per BABOK, | ||
| + | |||
| + | Describe the capabilities that the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature. | ||
| + | |||
| + | Transition requirements are short period requirements. Once these requirements are completed, these no longer exist. | ||
| + | Example of transition requirements | ||
| + | |||
| + | Examples of transition requirements are as follows: | ||
| + | |||
| + | The users must be trained to be able to use the system effectively | ||
| + | Previous years data must be migrated to the new system to generate comparative report | ||
| + | |||
| + | Transition requirements define the solution capabilities required to transition from the current to the future state and are no longer needed once the transition is complete. | ||
| + | |||
| + | Transition requirements : describe the capabilities that the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature. 7 Transition requirements address topics such as data conversion, training, and business continuity. | ||
Latest revision as of 09:52, 7 July 2020
A transition requirement is a requirement that defines characteristics that a solution must have in order to transition from the current state to the desired future state. These are characteristics that will not be needed once the transition is completed. Two key points:
- Transition requirements are temporary.
- Transition requirements place an emphasis on change management processes.
Definitions
According to the BABOK Guide (3rd edition),
- Transition requirement. A requirement that describes the capabilities the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature.
Draft descriptions
The transition requirements are the requirements needed to implement the software application successfully.
Transition requirements refer to the requirements to enable successful implementation of a project. As per BABOK,
Describe the capabilities that the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature.
Transition requirements are short period requirements. Once these requirements are completed, these no longer exist. Example of transition requirements
Examples of transition requirements are as follows:
The users must be trained to be able to use the system effectively Previous years data must be migrated to the new system to generate comparative report
Transition requirements define the solution capabilities required to transition from the current to the future state and are no longer needed once the transition is complete.
Transition requirements : describe the capabilities that the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature. 7 Transition requirements address topics such as data conversion, training, and business continuity.
