| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:RoleDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-utBebAOL0zjzOcCgAB-7VQ" |
| name="brms_architect,_s7UjMPjqEduTuLQpeq3SiA" guid="-utBebAOL0zjzOcCgAB-7VQ" authors="Jerome Boyer" |
| changeDate="2007-12-13T18:43:37.875-0800" version="1.0.0"> |
| <mainDescription><a id="XE_rule_architect" name="XE_rule_architect"></a> 
 |
| <p>
 |
| A Rule Architect&nbsp;helps the team to:&nbsp;
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| work together in an agile fashion,
 |
| </li>
 |
| <li>
 |
| jointly own the solution, and to
 |
| </li>
 |
| <li>
 |
| interface well with other parts of the organisation.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| 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:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Selecting the&nbsp;technology to ensure performance of the rule execution
 |
| and usability of the BRMS platform</span>
 |
| </li>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Designing the <a id="1094990" name="1094990">infrastructure necessary for
 |
| editing rules, and producing one or several Rule Sets</a></span>
 |
| </li>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Building the structure of rule projects, the dependencies on the
 |
| executable domain object model.</span>
 |
| </li>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Defining the decision services part of a SOA. Those services use Rule
 |
| Sets.</span>
 |
| </li>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Ensuring that the overall deployment organization of the rules makes sense
 |
| from an application segmentation perspective</span>
 |
| </li>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Ensuring optimization of rule execution</span>
 |
| </li>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Establishing traceability for rules within the technical
 |
| architecture</span>
 |
| </li>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Ensuring rule reuse</span>
 |
| </li>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Designing the structure of the rule repository (defining the required
 |
| metadata customizations and possibly implementing the structure)</span>
 |
| </li>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Developing the processes around repository management, rule life-cycle,
 |
| rule set life-cycle, rule governance</span>
 |
| </li>
 |
| <li>
 |
| <span style="mso-bidi-font-size: 10.0pt">Coordinating with application developers on system design, implementation
 |
| and testing</span>
 |
| </li>
 |
| <li>
 |
| <span
 |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Acting
 |
| as a liaison between business and IT</span>
 |
| </li>
 |
| </ul></mainDescription> |
| <skills><span lang="EN-GB"
 |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12.0pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; mso-fareast-language: EN-US; mso-bidi-language: HE">Deep
 |
| knowledge of BRMS products, software engineering process, UML, application integration, JEE, .Net, data to
 |
| object&nbsp;mapping</span></skills> |
| </org.eclipse.epf.uma:RoleDescription> |
