Project Page - Array Services


Rob Bradshaw, rdb@engr.sgi.com

1. Identification:

1.1 Project Code name:

1.2 Product name (if known):

1.3 Engineering manager:

1.4 Marketing manager:

1.5 Project software architects/lead designers:

1.6 Who outside the project is familiar with the project's technical details?

1.7 What parts of the source tree contain the results of this project?

Currently:

This would be changed to:

1.8 What sub-projects contribute to this project?

2. Goals:

2.1 What problem (or problems) is this project solving and for whom?

2.2 What specific features or functions are being created?

2.3 What user documentation will be produced?

2.4 What are the quantitative performance and resource usage goals for the product?

2.5 What tests are planned to measure performance?

2.6 What other functionality will regress in performance due to these changes?

2.7 What are this project's goals for reliability, testability, robustness, maintainability?

2.8 What tests are planned to assure functionality and reliability.

2.9 What problems are NOT going to be addressed by this project that someone might expect to be addressed?

2.10 What is the target market user expertise?

3. Dependencies:

3.1 What will be required of the customer to use this product (investment, training, reconfiguration, etc.)?

3.2 Which projects depend on the results of this project?

3.3 Which projects does this project depend upon?

3.4 Which platforms will be supported and which will not?

4. Schedule:

4.1 Provide a schedule with the following milestones:

  (following assumes Array 2.0 array services ships with ficus)

       done       Design Complete
       done       Coding Complete
       done       Integration Complete
       done       System Test Complete
       done       Alpha Test Cycle
       done       Early Customer Access Cycle
       done       Beta Test Cycle
       done       Manufacturing
       done       Release
       done       First Customer Ship

4.2 What are the major risks to achieving all goals while meeting this schedule?

4.3 Are you on schedule?

5. Documents:

5.1 How can I obtain the documents that describe the functionality, performance, architecture, interfaces, design of this product?

5.2 How can I obtain the documents that represent the Test Plan and Documentation Plan for this product?

6. Contracts and Licenses

6.1 What contracts exist for third party software and what is the approval cycle?

6.2 Are there any built in assumptions in the contract regarding distribution methods and quantities?

6.3 What is the royalty structure?

6.4 How are customers under support contract to be managed?

6.5 What are the contract start and stop dates?

7. Miscellaneous:

7.1 Anything else you think people should know about the project?

8.0 Software Release Request (pointer)

n/a