Академический Документы
Профессиональный Документы
Культура Документы
Name : Date :
10. This uses the internal structure of the program to derive the
test cases
Page 1
13. The objective of this is to verify stability of unchanged
functionalities of the software
C. Identify at least three scenarios that need to be tested to address each requirement
stated. Define any assumptions made, if necessary.
a. Generate one reminder notice for each customer who has an outstanding
balance due and who has not paid within the last 30 days.
Page 2
b. The 30-day period is counted from the day when the customer’s last payment
was received or from the day when the customer was last sent a bill or a
reminder notice.
D. Indicate in the blank provided – “T”, if the requirement is completely testable, and “F”, if
the requirement is flawed. If “F”, identify what the flaw is in the particular requirement,
and list all possible questions that will help clarify the user requirements.
a. The wording of the reminder notice must comply with all pertinent
legal and local regulations.
Page 3
c. The reminder notices must be mailed in purple 7” x 12” envelopes.
Page 4
f. If the bill was never sent to the customer and a reminder notice has been
generated, ensure that the account officer reviews and approves it
before it is sent out.
Page 5