JReality

high_level

chart semantics

Principles -- Evolution

• Originator Closes (OC) Principle: Only the originator can authorize closure (of a CR or BR)
  Change requests (CRs) and bug reports (BRs) may only be closed by those who open them. This helps ensure needs in the field are not ignored or glossed over.

Analyze & Track Change Requests

When the customer user staff identifies ways in which the application may potentially be improved to enhance its effectiveness in automating the Customer Enterprise Process Model, they fill out a change request for each suggested change and submit them to the maintainers. The maintainers log, analyze, and track the change requests. In concert with customer management, the change requests are prioritized. Those with the highest priority are scheduled for implementation, usually starting with the Requirements task since most change requests from users will concern changes to the requirements. After the initiating users verify the change has been implemented satisfactorily, the change request is closed.

Analyze & Track Bug Reports

If the result of the analysis is that a bug has been found, the maintainers fix the bug by repeating the development process starting at a task appropriate to the nature of the bug, and concluding with a new version of the application delivered to the users. Only after the initiating users verify the bug has been corrected is the bug report closed.

If the result of the analysis is that the problem is a user error or otherwise not a bug, the initiating users are notified of the true nature of the problem, and the bug report is closed.