Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Answers to Recruitment Test

Answers to Recruitment Test



|Views: 181|Likes:
Published by Irfan

More info:

Published by: Irfan on Feb 06, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





 Your company is developing the credit-card payment page for an onlineflowerShop. The payment form will contain these fields:Purchase of 12 roses for
US$ 12.95
Please input your credit card details:Name on card: _____________________ Card type: [Visa/MasterCard]Card number: _____________________ Expiry date (MM/YY): _____________________ Last 3 digits on back of Card: _____________________ 
design and usability specification
for this form.2. Write a
functional specification
for this form.3. Write a
security specification
for this form.QUALITY4. Specify your
quality requirements
for the form and payment process. TESTING5. Write a
test plan
for this form, covering unit tests, security tests,Acceptance tests, integration tests, stress tests and such other tests as youthink may be required.------------------------------------------------------------------------------------------------------------
1.a) Design of the Form:
A Design document generally describes the look and feel of the user interface. It tells aboutthe specified and intended design that is being wanted by the customers. The Design for theabove given form can be illustrated in to the following points.
D 1.1: The Upper Portion of the form displays the transaction details (E.g. Purchase of 12roses for
US$ 12.95
D1.2: The Form will be mentioning (should specify) the user to enter the Credit carddetails.
D1.3: The Body of the form should contain the following fields in the specified order:
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
D1.3.1, D1.3.3,
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].
Once [Submit] is clicked a validation will be done to verify whether all the mandatory fieldsare filled, in any case if they are not entered a message will be displayed to the user on thepage highlighting the fields to be entered.
Once the validation is passed the user will be directed to a user authentication page askingfor a transaction password if any based on the credit card type.
Meanwhile the system is expected to store and keep track of the values that were entered inthe previous page i.e. our Test Form. These details will be sent to the corresponding bank of the credit card via a payment gateway for the authorization and approval of the transactionmade by the user.
3) Security Specification:
The Security specification document contains the guidelines that need to be followed andmaintained while implementing a design and making an application. Following points come under thesecurity specification of the given Form.
SS1.1: Make sure that the ‘Card Number’ field accepts only sixteen digits andalphabets or any other special characters are not allowed.
SS1.2: When typed in the field ‘last three digits on back of card’, make sure that thenumbers are not visible and a special character asterisk appears in place of eachnumber typed in.
SS1.3: When clicked [Submit], see that the entered values are not being displayed inthe address bar of the browser. Follow a method such that these values areencrypted and sent when they move from one page to another in the application.
SS1.4: Disable the automatic cookie storage (data that might be saved in thebrowser) properties, as the Form contains confidential information that can bemisused when disclosed.
4) Quality Requirements:
Quality Requirements are nothing but the customer's expectations for quality, the internalprocess and product attributes that indicate whether the quality factors are being satisfied, and themeasures to be used to give visibility to the levels of quality being achieved.QR1.1: Using a Front-end verification technique, make the ‘Card Number’ fieldaccept only sixteen digits and rejects alphabets or any other special characters; ithelps the customers Focus on their necessary inputs alone. It narrow downs theoptions to give a wrong input, there by improving the quality of the Form. Thissaves the customer time as well.QR1.2: A similar kind of Front-end verification for the remaining fields helps inimproving the quality and robustness of the form.QR1.3: Taking proper care of the Font size and placement of all the fields of theForm in an appropriate manner also contribute to the enhancement of the Form’sQuality.

Activity (6)

You've already reviewed this. Edit your review.
1 hundred reads
EzKeezE liked this
Irfan liked this
Praveen Reddy liked this
kumar2k0 liked this
clipz liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->