Task: Design Rule Packages
Set up the rule authoring and management environment so that rule implementation can take place.
Disciplines: Rule Analysis
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    		Optional:
      Outputs
        Main Description

        The results of this task consists some or all of the following artifacts in the BRMS repository:

        • Business rules authored in BRMS Guided Rule Editor
        • Technical rules authored in Eclipse DRL format
        • Java fact model or BRMS defined fact model
        • Domain specific language
        • Web based decision tables
        • Spreadsheet based decision tables
        • Ruleflows
        • Enumerations
        • Test scenarios
        Steps
        Determine the rule implementation strategy.

        Choices include:

        • DRL
        • Guided Rule Editor
        • DSL
        • Spreadsheet Decision Table
        • Web Decision Table
        Create Drools projects in Eclipse Drools IDE.
        Add Domain Object Model jars to Eclipse classpath.
        Create a <package-name>.package file in the Eclipse project.
        Specify the package name and import statements for the Java classes used as facts. Define the use of any globals in this .package file as well.
        Create rule packages within the Drools BRMS.
        Upload Domain model jars in BRMS (or create fact model in BRMS).
        If the domain model jars were uploaded to the BRMS, use the Package view to add the fact types from the domain model to the package.
        Define the use of any globals as well.
        Define (search) criteria in BRMS.
        Prototype more rules to get business user feedback.
        For technical rules authored in Eclipse Drools IDE, only place a single rule in the file.
        This will make integration with BRMS easier.
        Create several test scenarios in BRMS to test prototyped rules and get end user feedback.
        Determine the package deployment strategy and create a <package-name>deployment.properties file.
        Establish a continuous integrated build process which can execute the JUnit tests and BRMS Test Scenarios automatically.
        TestScenarios can be run authomatically by using WebDav to download the TestScenario files and then use the ScenarioRunner API.