Describe a feature of a piece of software and then describe the attributes of that feature that should be tested to assess the quality of the feature and finally the values that should be tested. This is similar to the equivalence class approach described in Chapter 10. If the feature is n ot well-known and/or some of the values might not be clear, add comments make things clear. Two examples are below: Example 1: Consider the feature of an ATM where a person wants to withdraw cash. Attribute Values Comments Network connection Online, Offline If the connection is offline, then a message should be displayed on the screen saying that the machine is unavailable. Card condition Card is read, Card can't be read PIN Valid, Invalid Withdraw Amount Account has enough money, Account doesn't have enough money ATM Cash on hand Withdraw amount <= cash on hand, Withdraw amount > cash on hand. Example 2: A player comes to bat in an online baseball game. Attribute Values Pitch Strike, Ball, Pitch hits batter Response to pitch Swing, Don't swing Result of swing Miss, Hit-foul, Hit-fair play Result of foul ball Caught, Not caught Result of hit into field of play Caught, Not caught Result of hit into field of play that is not caught Single, Double, Triple, Homerun, Thrown or tagged out