Role: Rule Architect
The Rule Architect is responsible for defining and maintaining the structure of the rule-based application
Extends: Architect
Role Sets: Agile Rules Roles
Relationships

Build Rule Project StructureDefine Business Rule TeamDefine Domain Object Model ChangesDefine Rule Change Management ProcessDefine Rule Governance ActorsDefine Rule Life CycleDefine Rule SetDefine Rule Set Life CycleDesign Object Model for Rule Engine ProcessingDevelop Business Rule Application ArchitectureSynchronize Data ModelArchitecture NotebookRule_Architect
Additionally Performs
Modifies
Main Description

A Rule Architect helps the team to: 

  • work together in an agile fashion,
  • jointly own the solution, and to
  • interface well with other parts of the organisation.

The Rule Architect defines the structure and organisation of the rule-based system. Outside of the standard activities, skills, roles and responsibilities of a software architect, his role extends to:

  • Selecting the technology to ensure performance of the rule execution and usability of the BRMS platform
  • Designing the infrastructure necessary for editing rules, and producing one or several Rule Sets
  • Building the structure of rule projects, the dependencies on the executable domain object model.
  • Defining the decision services part of a SOA. Those services use Rule Sets.
  • Ensuring that the overall deployment organization of the rules makes sense from an application segmentation perspective
  • Ensuring optimization of rule execution
  • Establishing traceability for rules within the technical architecture
  • Ensuring rule reuse
  • Designing the structure of the rule repository (defining the required metadata customizations and possibly implementing the structure)
  • Developing the processes around repository management, rule life-cycle, rule set life-cycle, rule governance
  • Coordinating with application developers on system design, implementation and testing
  • Acting as a liaison between business and IT
Staffing
SkillsDeep knowledge of BRMS products, software engineering process, UML, application integration, JEE, .Net, data to object mapping
Assignment Approaches

This person in this role should be engaged in the project from start to finish.

For smaller projects, a single person may act as both Architect and Project Manager. However, it is better to have these roles performed by different people to ensure that the pressures one role doesn't cause neglect of the other role. The Architect and Project Manager must work together closely.

Key Considerations
This role places emphasis on the core principle Focus on the architecture early to minimize risks and organize development.
More Information
Concepts

This program and the accompanying materials are made available under the
Eclipse Public License v1.0 which accompanies this distribution.

OpenUP Copyright.

OpenUP/ABRD Copyright