==============================-begin-acr============================== ACR Apple/IBM/Motorola CHRP Board Confidential ----------------------------------------------------------------------- Severity: <n> Creation: <ccyy/mm/dd> Status: <s> Status attained: <ccyy/mm/dd> Urgent <?> Resolution: <r> Resolution: <ccyy/mm/dd> Document changed: <ccyy/mm/dd> Book affected: <Book short name> Version: <n.mm> Sections and pages: p. <i(-j)> Section(s) <section number(s)> |p. <p(-q)> Section(s) <section number(s)| |Additional book, version and section references ...| Summary: <a few lines summarizing the requested change> Submitter: <Coordinator> Date accepted: <ccyy/mm/dd> Company: <company> |Requester: <original requester>| Assigned to: <Cognizant architect> |Impact on hardware:<brief description>| |Impact on software:<brief description>| |Impact on OF: <brief description> |Impact on RTAAS: <brief description> |Impact on validation suite:<brief description> |Effective: <Immediately, Optional, or ccyy/mm/dd> Keywords: <list of keywords> ----------------------------------------------------------------------- <explanation of why the requested change is needed> <specific changes to make in the Books> ===============================-end acr-=============================== Notes: Replace fields delimited by less than and greater than symbols with the requested information. For example, the string "<ccyy/mm/dd>" which denotes a date field should be replaced with an appropriate date, "1997/03/31". Lines delimited with bars "|" are optional. Give the required information without the delimiting bars or remove the line. When the CHRP Board Coordinator submits the ACR to the CHRP Board the ACR should have all the fields which are the responsibility of the originator completed including the proposed wording changes. However, the ACR could be originated within the company without completely specifying the resolution. The resolution and affected pages would be developed by architects within the company to the point that agreement with this approach is reached within the company. Then the ACR is submitted. The CHRP Board Secretary assigns the ACR number and replaces the "<nnnnn>" field with this number. If the originator determines this ACR is not Apple/IBM/Motorola CHRP Board Confidential, then the originator should replace the field, "<?>" with "No". Otherwise the originator should replace the string "<?>" with "Yes". The criteria for determining confidentiality is described in Section 2.5.1, "Confidentiality". The originator should replace the phrase "<title>" with the title for the ACR. The originator should replace "<s>" with the severity code. The severity code is defined as follows: 1 Major importance (e.g., may require substantial changes to hardware or software, or may affect hardware or software compatibility) 2 Moderate importance (e.g., may affect performance, cost, or usability, of hardware or software) 3 Minor importance (e.g., requests clarification of an ambiguity or inconsistency in the architecture documents) 4 Error (e.g., typos, minor corrections, minor clarifications) in the document. Many of these can be handled by means of the simplified process for correcting documentation errors described in Section 2.2.2, "Documentation Error Correction Process," and Section 2.2.3, "Trivial Documentation Error Correction Process," instead of by means of a change request. The originator should update the "Creation:" field by replacing "<ccyy/mm/dd>" with the creation date. The Cognizant Architect maintains the "Status:" field by replacing the phrase "<s>" with one of the status codes. The status codes are as follows: N New - the request has been accepted as a ACR V Votable - the ACR has been sent as ACR Correspondence at least two weeks before for normal or one week for urgent ACRs. P Pending - an ACR has been approved through the CHRP Board, but the associated changes have not yet been made in the CHRP architecture documents. C Closed - for an ACR that is approved, notice of the approval has been sent as ACR Correspondence and the associated changes have been distributed in a Change Notice and made in the source for the CHRP architecture documents. Note that these updated documents may not be published at the point of closing the ACR. - for an ACR that is rejected or withdrawn, notice of the rejection or withdrawal has been sent as ACR Correspondence. The Cognizant Architect maintains the "Status attained:" field by replacing the string "<ccyy/mm/dd>" with the date this status was attained. The originator should document the urgency of this ACR in the "Urgent:" field by replacing the string "<?>" with "Yes" if the ACR is urgent. The Cognizant Architect maintains the "Resolution:" field by replacing the string "<r>" with the resolution code and the string "<ccyy/mm/dd>" with the date that resolution was attained. These resolution codes only apply to ACRs with status P or C. The resolution code is one of the following: A Approved - ACR approved through the CHRP Board R Rejected - ACR rejected through the CHRP Board W Withdrawn - ACR withdrawn by the submitting Coordinator. The Cognizant Architect maintains the "Document changed" field by replacing the field "<ccyy/mm/dd>" with the date the changes were published in an updated CHRP architecture document or the last document if more than one was changed. This date is the date of the publication of the document not the preparation of Change Notice information and source files updates. The originator should list the affected book and its version number by replacing the field "< Book short name>" with the name of the affected book and replacing "<n.mm>" with the version number of that book. The originator gives the affected page number(s), and section number(s) by replacing the string "<i (-j)>" and "<section number(s)>" with the page ranges and sections which are to be changed. If more than one line is needed for page numbers and section numbers then the originator should replace the string "<i (-j)>" and "<section number(s)>" on a second or additional line with the page ranges and sections which are to be changed. Remove the bars, "|" from this lines. If only one line is needed, then delete the optional line. If additional books are affected, the originator would replace the optional line, "Additional book, version and section references" with the book short name, version number, page number(s), and section number(s) using the format for the first book. If this change requires changes in other standards outside the control of the CHRP Board, then they should be listed as other books. Otherwise delete this line. The originator summarizes the change request by replacing the field "<a few lines summarizing the requested change>" with a summary of the change. The originator should list the submitter and company by replacing the field "<Coordinator>" with the name of the submitting CHRP Board Coordinator, and the field "<company>" with the company name of the submitter. If the originator wishes to identify the originator of the request, then the originator does so by replacing the field "<original requester>" with the name of the original requester and removing the bars on this line. Otherwise remove this line. The CHRP Board Secretary should record the acceptance date of the request by replacing the field "<ccyy/mm/dd>" with the date the CHRP Board Chairperson accepted the request. The CHRP Board Secretary should record the Cognizant Architect to whom this ACR is assigned by replacing the field "<Cognizant architect>" with the name of the Cognizant Architect. Repeat this line if more than one Cognizant Architect has been assigned. The originator should briefly describe any impact on hardware, software, Open Firmware, and RTAS. This information will help reviewers decide what ACRs are applicable. The originator inserts this description by replacing the field "<brief description>" with a description of the impact. Remove the bars on the line. Otherwise remove any of these lines. If this change modifies or adds requirements which the PowerPC Hardware Test Program must validate, then the originator should describe this impact. Otherwise remove the line. The originator should document the time frame in which these requirements become effective for CHRP systems. More than one line may be needed if different requirements have different time frames. The entries for this field should be: Immediately Use for changes to requirements for capabilities not currently being implemented, requiring little implementation time, and any corrections to explanation and other supporting information. Optional Use for requirements that are new or complex to implement but are also optional. ccyy/mm/dd Show an effective date for any requirements or interpretation changes which effect products currently being developed and have an implementation lead time. A nominal value would be 18 months from the date of creation of the ACR. ACRs which are more strategic or simpler might have effective dates nearer to the creation date. The originator should list a few keywords by replacing the field "<list of keywords>" with a list of keywords separated by commas. The originator should describe the reason for the change by replacing the field "<explanation of why the requested change is needed>" with one of more lines of rationale. The originator should describe the specific change language by replacing the field "<specific changes to make in the Books>". This description should clearly define the changes and deletions of existing words as well as the insertion of new words. If these notes are part of the ASCII file, the originator should delete them before submitting the request.