Template Version: @(#)onepager.txt 1.35 07/11/07 SMI
Copyright 2007 Sun Microsystems

1. Introduction
   1.1. Project/Component Working Name:
	Drools

   1.2. Name of Document Author/Supplier:
	Rick Matthews

   1.3. Date of This Document:
	12/02/2008
	
	1.3.1. Date this project was conceived:
		10/2007

   1.4. Name of Major Document Customer(s)/Consumer(s):
	1.4.1. The PAC or CPT you expect to review your project:
		Solaris PAC
	1.4.2. The ARC(s) you expect to review your project:
		LSARC
	1.4.3. The Director/VP who is "Sponsoring" this project:
		Karen Jourdenais
	1.4.4. The name of your business unit:
		SDASH

   1.5. Email Aliases:
    	1.5.1. Responsible Manager: greg.matthews@sun.com
    	1.5.2. Responsible Engineer: rick.matthews@sun.com
    	1.5.3. Marketing Manager: margaret.hamburger@sun.com
	1.5.4. Interest List:

2. Project Summary
   2.1. Project Description:
	Drools is an open-source rules engine being proposed for use in
	several projects, including ADM (PSARC/2007/210). There are a significant
	number of dependancies which need to be integrated into Open Solaris
	to support Drools. In addition, this case and it's dependencies are
	being provided for familiarity to developers, currently using various
	Linux distributions, moving to OpenSolaris.

   2.2. Risks and Assumptions:
	Several projects including ADM need a rules engine for storage 
	policy management. Drools was selected for its flexibility, and
	its proposed use in another project.

	Risks would involve re-working the storage policy infrastructure in
	several projects, including ADM.

	The large number of dependencies is a source of Risk due to the
	various licenses and source provence.

3. Business Summary
	Drools is a commonly accepted business rules management system
	within the open source comminity.

	Drools is a proposed important component for ADM.
	See PSARC/2007/210 for ADM business justification.

   3.1. Problem Area:
	Storage and Data policy within HSMs, archive systems and other storage
	related products are defined to control movement, lifecycle and
	other desired actions on data. A consistent language and implementation
	of this policy is desired by consumers of these multiple products.

   3.2. Market/Requester:
	Open Source familiarity and ADM.

   3.3. Business Justification:
	In addition to the ADM business justification, there is a need to provide
	familiarity to Linux developers moving to OpenSolaris.

   3.4. Competitive Analysis:
	Drools is an open source implementation of JSR94, there are various
	commercial license versions as well.

   3.5. Opportunity Window/Exposure:
	

   3.6. How will you know when you are done?:
	When Drools delivers the required functionality to ADM.

4. Technical Description:
    4.1. Details:
	Drools is an open source business rules management system being consumed
	by ADM. 

    4.2. Bug/RFE Number(s):
    
    4.3. In Scope:
	The primary purpose of this project is consumption of Drools
	by ADM and other storage products.

    4.4. Out of Scope:
    
    4.5. Interfaces:
	The JSR94 standard interface is the primary exported interface that
	Drools implements
	
    
    4.6. Doc Impact:
	New man pages will be provided
    
    4.7. Admin/Config Impact:
	Drools is a Java library used by other programs that provide
	their own configuration.
    
    4.8. HA Impact:
	N/A
    
    4.9. I18N/L10N Impact:
	N/A
    
    4.10. Packaging & Delivery:
	Drools will only bundle dependencies that have no broad usefulness
	outside of the rules engine context. All other dependencies under
	this umbrella will have separate packages for generalized use.
    
    4.11. Security Impact:
	Drools is a Java library that, by itself, makes no security 
	decisions and does not use communication protocols. Security
	of the using applications is out of scope.
    
    4.12. Dependencies:
	See case materials for complete list of dependencies.

5. Reference Documents:
	See case materials for a list of reference cases.

6. Resources and Schedule:
   6.1. Projected Availability:
	Due to the scope of included dependencies, the schedule is still in flux.

   6.2. Cost of Effort:
	Due to the scope of included dependencies, the cost is still in flux.

   6.3. Cost of Capital Resources:
	N/A

   6.5. ARC review type:
	Standard

   6.6. ARC Exposure:
	open