D1.3.1 Name on CardD1.3.2 Card TypeD1.3.3 Card NumberD1.3.4 Expiry DateD1.3.5 Last 3 Digits on back of card
D1.4: Against each of the
Fields there should be a Text box.
D1.5: Against the Field
there should be two radio buttons with the options as Visaand MasterCard.
D1.6: Against the Field
there should be two dropdown boxes providing the optionsfor all the months in the first dropdown and a range of few years in the seconddropdown.
D1.7: The Form will be ending with a submit button.
1.b) Usability Specification of the Form:
The Usability Specification document gives an insight to the users specifying the differentways to use the application. It helps them understand the application and guides them whileputting the same to usage. Following are the main points that come under ‘usabilityspecification’ for the form that was provided in the test.
U1.1: The user performing the online transaction is supposed to type in the name asit appears on his/her credit card in the ‘Name on card’ field (D1.3.1) of the form
U1.2: User should select the correct ‘Card Type’ (D1.3.2) according to theVisa/MasterCard card type that is provided on the credit card.
U1.3: User should provide the sixteen-digit card number that appears on the creditcard in the ‘Card number’ (D1.3.3) field of the Form.
U1.4: User is supposed to fill in the ‘Expiry date’ (D1.3.4) with the appropriate Monthand Year that will be specified on the credit card.
U1.5: ‘Last three digits on back of the card’ (D1.3.5) field should be populated withthe last three digits that appear on the rear side of the credit card.
U1.6: The user should make sure that he/she provides all the required Fields that arementioned in the Functional specification doc with out fail.
2) Functional Specification:
The Functional specification is the documentation that describes the requested behavior of any system. The documentation typically describes what is needed by the system user as well as therequested properties of inputs and outputs. It mainly helps in finding out the navigations that happenin the system. Following is the functional specification for the Form provided in the test.
When the user is directed to the above Form, it is expected that the system is holding thevalue of the transaction amount in some variable at the back end. This value is fetched anddisplayed on top of the Form.
After providing the required details in the form, user clicks [Submit].