| At line 5 removed 4 lines. |
| This information is |
| Sun Proprietary/Confidential: Internal Use Only: Engineering Need-to-Know |
| Copyright 2006 Sun Microsystems |
| At line 22 removed 11 lines. |
| 1.4. Name of Major Document Customer(s)/Consumer(s): |
| 1.4.1. The PAC or CPT you expect to review your project: |
| // This should match the spelling used in PLCtool, as this will be |
| // used to cross-reference the information |
| 1.4.2. The ARC(s) you expect to review your project: |
| // Leave blank if you don't have any preference |
| // This item is advisory only |
| 1.4.3. The Director/VP who is "Sponsoring" this project: |
| // John.Doe@Sun.Com |
| 1.4.4. The name of your business unit: |
| // SSG, Software, ... |
| At line 34 removed 6 lines. |
| 1.5. Email Aliases: |
| 1.5.1. Responsible Manager: |
| 1.5.2. Responsible Engineer: afung@dev.java.net |
| 1.5.3. Marketing Manager: |
| 1.5.4. Interest List: |
| At line 82 removed 25 lines. |
| 3.3. Business Justification: |
| // Why is it important or valuable to do this project? |
| // Include monetary estimate and precision. |
| 3.4. Competitive Analysis: |
| // Who are the current and anticipated players in this market? |
| // How/why will we succeed when competing with them? |
| 3.5. Opportunity Window/Exposure: |
| // Time-to-market window, if any, and precision. |
| 3.6. How will you know when you are done?: |
| // What will you measure to determine that the project is complete? |
| // |
| // This section is for explicit measurable customer CTQs that apply |
| // to this specific feature proposal, not to the product as a whole. |
| // |
| // We *expect* every development team to meet their Feature, |
| // Performance and Security and Testing goals, as well as getting |
| // all required ARC and PAC review approvals, so don't put that |
| // sort of metric here. |