  |
|
Instructions for Request for Deviation/Waiver Form
The Request for Deviation/Waiver Form is used to request a deviation from or waiver to a requirement, standard, or process. All available information on the request should be fully and accurately documented or referenced on the form. Forms are available from the Software Configuration Management (SCM) Manager, and are in the SCM Plan (SCMP).
Please type text or check boxes only in the shaded areas. These shaded areas can be accessed by pressing the TAB key, or placing the cursor on the appropriate area and pressing the left mouse button. The shaded areas marked for text will expand or contract to fit the amount of text that is typed. There is no limit (other than size of page) to the number of words that can be typed in the shaded text areas.
Header Section:
[1] Deviation/Waiver Number: Unique Request For Deviation/Waiver number.
[2] System/CSCI Name: System or CSCI to which the request applies.
[3] Requester’s Name: Person submitting the request.
[4] Date of Request: Date the request is submitted.
Section A (Deviation/Waiver Identification):
[1] Describe the Deviation/Waiver: Requirements, standards, or processes the request involves. Additional documents or files may be referenced here.
[2] Describe rationale for this request: Why request should be granted. Will time or money be saved by granting the request? Will the software product quality be improved by granting the request?
Section B (Analysis):
[1] Analyzed By: Individual responsible for doing the analysis and the requested completion date (Req. Comp. Date). The individual analyzing the request enters the date the analysis was complete in the Comp Date field.
[2] Impact on Software Products: Software products to be affected by approval of the request, and explain the impact to each product.
[3] Impact on software activities: Planned activities to be affected by request approval, and the impact to each activity.
[4] Impact on Schedule: If granting the request affects the software development schedule, explain the impact in staff hours.
[5] System Level Impacts: Identify and explain impacts to system-level products, activities, or schedules.
Section C (Resolution)
[1] Action Taken: Action to be taken by checking the appropriate box.
[2] SCB Decision: SCB decision. Check the appropriate box.
[3] SCB/Project Software Manager Comments: If the request is denied by the Project Software Manager without submittal to the SCB, the reason is documented. The reasons for the SCB approval or denial is documented. Any dissenting SCB members also are allowed to document the reason for their dissenting viewpoint here.
[4] Reviewed by: The Project Software Manager signs and dates the request.