.
Application Express
Application Accelerator
Application Profiler
Application Explorer
Implementation Only
Framework and Implementation
Framework Only
To provide a custom framework name
To create a division reuse layer
To specify business objectives
To create an organization
Use Case Explorer
Use Application Express
Add it manually
Use Application Accelerator
Define parent/child relationships for Case Types
Reuse Data Types from an extended framework
Define a Data Type in the enterprise or application layer
Define initial stages for Case Types
Property
Application
Class
Activity
Rules in all lower numbered versions of that ruleset
Rules in the ruleset versions defined as prerequisites for that ruleset version
Rules in the rulesets specified in the application rule
Rules in the ruleset versions defined as prerequisites for the prerequsites of this ruleset
Specified through the Access Group, Organization, and Division
Specified in the Application rule
Used when running rules
Used when developing rules
Only the highest version of ruleset should be unlocked
All application rulesets should have the same version number
Once locked, a ruleset version should not later be unlocked
All development should occur in the highest version
Refactor on import
Lock and Roll
Skim a Ruleset
Copy/merge a Ruleset
All rules in the branch RuleSet must be checked in
All merge conflicts must be resolved
A higher version of the base RuleSet must be available on the system
The branch RuleSets must be locked
Discuss conflict with the individual who modified base rule if changes are complex
Use the automatic merge functionality for minor base rule changes
It is recommended to merge rules into a new (higher) base RuleSet version
Ignore conflicts in other branched RuleSets since changes might not be final
Always merge all available branches into the base RuleSet at the same time
Create a new RuleSet version in the target base RuleSet for the branch
Lock the target base RuleSet version after the merge
Lock the branch RuleSet before the merge
A branch is a container for RuleSets with rules that are undergoing change and development
A branched RuleSet must belong to a branch
Branches are defined on the application
A branch RuleSet can be branched from another branch RuleSet
Several development teams work on different enhancements in a RuleSet simultaneously that will go into production at the same time
Several development teams work on different enhancements in the same RuleSet simultaneously and it is not known ahead which enhancements will go into production first
All development teams simultaneously work on the same enhancement in a RuleSet and it is not known ahead when the enhancement will go into production
The only development team work on an enhancement in a RuleSet and it is not known ahead when the enhancement will go into production
True
False
The rule that is chosen by the system has an Availability of “Withdrawn”
The user does not have appropriate privilege to access the rule that is chosen by the system.
The rule that is chosen by the system is in a RuleSet that is not in the application’s RuleSet stack.
The rule that is chosen by the system is not in the class inheritance path for the given context.
The rule that is chosen by the system has an Availability of “Blocked”
The rule that is chosen by the system has warning messages shown to the designer when the rule was last saved.
I, no erorr raised
F, error raised
D, error raised
E, error raised
E, no error raised
D, no error raised
C, no error raised
B, no error raised
G, no error raised
B, error raised
C, error raised
F, no error raised
H, error raised
H, no error raised
I, error raised
A, error raised
G, error raised
A, no error raised
D, no error raised
F, error raised
I, error raised
B, error raised
G, error raised
G, no error raised
H, no error raised
F, no error raised
D, error raised
E, error raised
H, error raised
B, no error raised
E, no error raised
I, no error raised
C, error raised
A, error raised
C, no error raised
A, no error raised
Implementation
Framework
Division
Organization
In the organization – so they can be reused
In the implementation – to be the most specific
In the division – so the division retains ownership of the work.
In the framework – so they can be easily maintained
True
False
Two, in: MyCo-FW-LoanApp-Work, MyCo-DivE-LoanAppDivE-Work
Five, in: MyCo-DivA-, MyCo-DivB-, MyCo-DivC-, MyCo-DivD-, MyCo-DivE-
Six, in: MyCo-FW-LoanApp-Work, MyCo-DivA-LoanAppDivA-Work, MyCo-DivB-LoanAppDivB-Work, MyCo-DivC-LoanAppDivC-Work, MyCo-DivD-LoanAppDivD-Work, MyCo-DivE-LoanAppDivE-Work
Six, in: MyCo-FW-LoanApp-Work, MyCo-DivA-, MyCo-DivB-, MyCo-DivC-, MyCo-DivD-, MyCo-DivE-
Two, in: MyCo-FW-LoanApp-Work, MyCo-DivE-
Five, in each of the implementation classes: MyCo-DivA-LoanAppDivA-Work, MyCo-DivB-LoanAppDivB-Work, MyCo-DivC-LoanAppDivC-Work, MyCo-DivD-LoanAppDivD-Work, MyCo-DivE-LoanAppDivE-Work
Five, in: MyCo-DivA-LoanAppDivA-Work, MyCo-DivB-LoanAppDivB-Work, MyCo-DivC-LoanAppDivC-Work, MyCo-DivD-LoanAppDivD-Work, MyCo-DivE-LoanAppDivE-Work
Five, in: MyCo-DivA-, MyCo-DivB-, MyCo-DivC-, MyCo-DivD-, MyCo-DivE-
Six, in: MyCo-FW-LoanApp-Work, MyCo-DivA-LoanAppDivA-Work, MyCo-DivB-LoanAppDivB-Work, MyCo-DivC-LoanAppDivC-Work, MyCo-DivD-LoanAppDivD-Work, MyCo-DivE-LoanAppDivE-Work
Six, in: MyCo-FW-LoanApp-Work, MyCo-DivA-, MyCo-DivB-, MyCo-DivC-, MyCo-DivD-, MyCo-DivE-
4
2
1
Circumstancing cannot be used to address this requirement
3