Score A+
1. 3 questions to ask when planning user views 1. What field does the
user
need to work with?
2. How will the user
enter the value of the
field?
3. Can the user
modify the field
value?
2. Business Rule Related to the business
processes in the
specific application. Is
usually as- sociated with
a specific use case or
step in a process, and
identifies the system
behavior at that step
ex. First Name should
not be longer than 20
charac- ters
3. Change Control Related to the needs of
making modifications
in the application and
sys- tem, and
managing those
changes.
Ex. System shall
support two-digit
version numbers
1/
50
, PEGA CPBA Exam Solved Correctly To
Score A+
4. Enterprise Standard Identifies an
enterprise- or industry-
wide standard to
which the application
or system must
adhere.
2/
50
, PEGA CPBA Exam Solved Correctly To
Score A+
5. Functional Identifies what the
system
has to do. Typically used to
identify a function that
will be used in the
ap- plication, such as a
data transformation or
calcula- tion, rather
than describ- ing
system behavior.
Ex. Remaining budget must
be calculated to two
decimal points
6. Non-functional Identifies qualities the
overall system must have,
typically related to how
the system performs.
Ex. System needs to have 2-
3 seconds screen to
screen interaction
7. Characteristics of Good Requirements Written in business
terms Clear and
concise Consistent
Verifiable Atomic
8. Characteristics of Good Specifications Written in business
terms Complete and
unambigu- ous
No change of ownership
3/
50
, PEGA CPBA Exam Solved Correctly To
Score A+
Can be implemented
and
4/
50