Proposed ARC 20 questions                                                     Oct.1, 2008
                                                                              Rick Matthews


The 20 questions outline serves several purposes. One is to present to the ARC in a
uniform manner pertinent information about any case. Many of the answers to these
questions can be direct and specific references to other case materials (although care
must be taken to keep the references current). A second purpose is to allow an ARC member
to get a concise overview of the case in an efficient manner. Another purpose is that the
20 questions should provoke thought and questions for project teams unfamiliar with the
ARC process, by asking questions about aspects of the project that need be considered.
Lastly, the 20 questions serves as a vehicle between the case owner and the project team
as an indicator of preparedness. The 20 questions, as do other ARC materials, remain as
documentation of the case plan of record.


1.  What is the proposal being presented for review?

* Give an overview of the project and its phase(s).
* Describe the exposure (OpenSolaris), scope and type of review desired (overview,
  full case, etc.)
* Indicate the release binding requested by the project team.
* What are the project's deliverables.
* How does this project align with existing or proposed ARC cases?

2.  Describe user interactions.

* Are new user interfaces being proposed, or existing interfaces being changed?
* Explain the similarities in proposed interfaces with existing OS user interfaces
  (Solaris, Linux, Windows, etc.).
* Are there any install time changes?

3.  What are the imported (consumed by the project) and exported (exposed by the project)
    interfaces or protocols and their respective stability levels?

* Is there a versioning scheme in place?
* Has the team secured interface contracts where necessary?
* Use an ARC prescribed interface table format. 


4.  Describe any dependencies on hardware (e.g. SPARC exclusive), and on other projects
    within Solaris.

5.  What are the security implications of this project? (Gary Winiger to expand).

6.  Describe means of observing project functionality and performance, by an end
    user or by a system administrator.

7.  How does the project deal with faults and interruptions? Initialization and
    restarting?

8.  How does the project interact with Solaris virtualization technologies (xVM,
    LDOMs, SunCluster, etc.)? 

9.  Is systems administration needed for your project? If so,

* How is the project administered, and what sort of review process has this user
  interface undergone?
* Is there a means of aggregating management and/or configuration with other related
  projects?
* Are there any external (to Solaris) management interfaces to consider, or being
  consumed?


10. Have you reviewed the Best Practices? Are there any exceptions this project needs?