IV.O.12 Operations Phase - Business Information and Must provide the ability to clone Technical Architecture - rules, modify them and then Rules Engine & Rules implement them as new separate Management rules. IV.O.12 Operations Phase - Business Information and Technical Architecture - Must test, validate and receive Rules Engine & Rules State approval for rule changes Management prior to implementation. IV.O.12 Operations Phase - Must provide the capability for Business Information and users to receive push Technical Architecture - notifications/alerts based on Rules Engine & Rules parameters (rules Management and/or rules groups). Must provide the capability to track IV.O.12 Operations Phase - and report rule usage, exception Business Information and usage, and when a rules fail to Technical Architecture - work as designed, and provide Rules Engine & Rules recommendations to resolve rule Management failure. Must provide the capability for a multi-level rule review and approval process that will validate logic errors, conflicts, redundancy IV.O.12 Operations Phase - and incompleteness across Business Information and business rules to identify any Technical Architecture - conflicts in business rules as they Rules Engine & Rules are being developed, tested, and Management implemented. IV.O.12 Operations Phase - Must provide version control Business Information and including the ability to revert to a Technical Architecture - prior version of the rules if there Rules Engine & Rules are unwanted or unexpected Management consequences of a rule change.
IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the ability to clone rules, modify them and then implement them as new separate rules. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must test, validate and receive State approval for rule changes prior to implementation. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the capability for users to receive push notifications/alerts based on parameters (rules and/or rules groups). IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the capability to track and report rule usage, exception usage, and when a rules fail to work as designed, and provide recommendations to resolve rule failure. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the capability for a multi-level rule review and approval process that will validate logic errors, conflicts, redundancy and incompleteness across business rules to identify any conflicts in business rules as they are being developed, tested, and implemented. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide version control including the ability to revert to a prior version of the rules if there are unwanted or unexpected consequences of a rule change.
4%20Attachment%20B%20-%20Business%20and%20Technical%20Requirements%20Matrix.docx