Course intended for:

  • business analysts, who are or will be responsible for defining of business rules using JBoss Drools and Drools Guvnor technologies

  • programmers or architects, willing to get familiar with the issues of modeling using business rules from the perspective of a business analyst.

Course objective:

The training is aimed at getting the participants ready to model problems using business rules without a – typical for programmers – knowledge of the technical details of functioning of the Drools technology. The training is focused on issues associated with engineering of requirements and management of change in the context of business rules. Moreover, strong emphasis is put on development of the ability to communicate with the programmers so that both sides are able to understand their mutual needs and properly integrate their works.

Course strengths:

After the training, the participants will have the following skills:

  1. Development of business rules in Drools language using the Test-Driven Development methodology,

  2. Proficient use of the Drools Guvnor tool,

  3. Management of rules and change of rules,

  4. Identification of roles in the rule lifecycle,

  5. Understand the architecture of rule engine based systems and the role of Drools Guvnor in this architecture,

  6. Cooperation with programmers to build an effective system together.

Requirements:

The training does not require preliminary knowledge of the technologies discussed; in particular, knowledge of any programming language is not required.

Course parameters:

3 x 8h in the following proportion: 80% workshops, discussions; 20% - lectures.

Course curriculum

  1. What is business modeling?

  2. Introduction to business rule modeling.

    1. What is a rule engine?

    2. What is a rule?

  3. A review of rule engines.

  4. Basic principles of rule modeling.

    1. Java and Declared types.

    2. Drools language.

    3. The order of performance of rules.

  5. Drools Guvnor.

    1. Introduction

      1. Working Sets.

      2. Editor of resources.

      3. packages

      4. versioning.

    2. Development of rules using a graphic editor.

    3. Own DSL language.

    4. Decision-making tables using a spreadsheet.

    5. Decision-making tables using an editor.

    6. Business rule templates.

    7. QA.

      1. Test-Driven Development in Guvnor.

      2. Test scenario development.

      3. Audit log.

      4. Analysis of results.

    8. Packages.

      1. Package management

      2. Categories

      3. Development of packages

      4. Snapshots.

      5. Publication.

  6. Architecture of systems using Drools rule engines and the role of Drools Guvnor in this architecture.

  7. The lifecycle of rules and roles involved.

    1. Objective and scope (including specification of the business context, identification of threats, identification of business and technological limitations).

    2. Discovery – creation of a domain model, specification of facts, identification of roles, rule sources and their valuation.

    3. Design

    4. Implementation

    5. testing

    6. Management of change and estimation of impact of change

    7. Roles in the process

    8. Rule Maturity Model.

  8. How to cooperate with programmers?

    1. The technical plane and the business plane

    2. Use of shared concepts

    3. What to expect of programmers to properly integrate our works.

    4. What the programmers expect of us to properly integrate their works.

  9. Summary.

Any questions?

* Required.


Contact
Phone +48 22 2035600
Fax +48 22 2035601
Email