Latest Activity In Study Groups

Join Your Study Groups

VU Past Papers, MCQs and More

We non-commercial site working hard since 2009 to facilitate learning Read More. We can't keep up without your support. Donate.

 

Please carefully read the following instructions before attempting assignment.

INSTRUCTIONS

It should be clear that your assignment would not get any credit if:

  • The assignment is submitted after the due date.
  • The submitted assignment does not open or file is corrupt.
  • Strict action will be taken if submitted solution is copied from any other student or from the internet.

You should concern the recommended books to clarify your concepts as handouts are not sufficient.

You are supposed to submit your assignment in .doc or docx format.

Any other formats like scanned images, PDF, zip, rar, ppt and bmp etc. will not be accepted.

 

Topics Covered:

·         Use Case Analysis Based Testing

 

NOTE

No assignment will be accepted after the due date via email in any case (whether it is the case of load shedding or Internet issues etc.). Hence refrain from uploading assignment in the last hour of deadline. It is recommended to upload solution file well before its closing date.

If you find any confusion in the assignment (Question statement), please consult with your Instructor before the deadline. After the deadline no queries will be entertained in this regard.

For any query, feel free to email at CS608@vu.edu.pk

 

 

Scenario:                                                                                                     

Consider the following High-level Use Case Model of an E-Store System (Figure-1) along with the description of the Login / Registration Use Case.

 

USE CASE DIAGRAM (HIGH LEVEL)

Explore Catalog

Maintain Account

Maintain Database

Maintain

Shopping

Cart

Process Returns

Customer

Administrator

Customer Support

Process Help

Request

System View

Credit

Institution

Shipping

Service

Manage

Financing

Financing

Department

Loginn

includes>>

includes>>

includes>>

 

                     Figure 1: High Level Use Case Diagram

USE CASE UC1: Login/Registration

Description

This use case describes how users gain access to the e-Store system through the login/registration (account creation) process.

Primary Actors

Users (Customers, Administrators)

Stakeholders and Interests

  1. User: wants to gain access to the system for any number of reasons (e.g., maintain personal account, check order status, purchase items, administer system, etc.).
  2. Marvel Electronics Owner: wants to ensure security of system.
  3. Pre-Condition: the user is on the "Sign In" screen.
  4. Post-Condition: the user is either logged in or failed to log in and is appropriately notified.

 

Basic Flow (Returning User, Valid Username/Password)

  1. The user browses to the "Sign In" page.
  2. The user enters his/her username and password in the returning user section of the "Sign In" screen.
  3. The system validates the username and password (successfully) and displays the user's account information page.

 

Extensions (Alternative Flows):

  1. The user browses to the "Sign In" page.
  2. The user enters his/her username and password.
  3. The system determines that the username or password is invalid and informs the user to try again.

 

Returning User, Forgotten Username or Password

  1. The user has forgotten his/her username, password, or both, and clicks the "Forgot Username/Password?" link
  2. The system resets the users account and sends an e-mail notification with the new information
  3. The user utilizes the new username/password information to log in following the basic flow

 

New User

  1. The user browses to the "Sign In" page.
  2. The user chooses the "New User" link on the "Sign In" page.
  3. The user enters his/her account information and chooses a username and password
  4. The system validates the information entered
  5. The system sends the user an e-mail invitation
  6. The user must confirm their new account by clicking the link in the e-mail
  7. The user is logged in and his/her account information page is displayed.

 

System Administrator

System administrators follow the basic flow for this use case when logging in to the system.

Special Requirements

  • After three consecutive unsuccessful login attempts, the user's account will be locked and must be reset by a system administrator.
  • Users may not login from multiple different computers simultaneously. If this condition is detected, the user will be notified with appropriate warning/error messages.

 

 

Question:                                                                                                                              (Marks 20)

You are required to develop all the possible Test Cases for the above mentioned Use Case (Login / Registration).

Format of your answer must be as per the following pattern:

TC ID

Use Case ID

Scenario ID

Inputs

Expected Output

Pre-Condition

Post Condition

Pass/Fail Criteria

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Note:

Your solution must be uploaded on or before 5th June, 2021

Views: 678

Attachments:

Replies to This Discussion

Stay touched with this discussion, Solution idea will be uploaded as soon as possible in replies here before the due date.

Any IDEA Solution?

Any Thing...!

RSS

© 2021   Created by + M.Tariq Malik.   Powered by

Promote Us  |  Report an Issue  |  Privacy Policy  |  Terms of Service