Challenge

Project 1 - V&V SW Analysis - I

 1)Test Plan:

     -> It is detailed documentation that provides information about all the necessary resources and activities that will be a part of software testing.

     -> Test plans are necessary documentation used in blackbox testing. 

Test Objectives:

     -> Evaluate the user-friendliness of the mobile phone's interface and features.

Scope of Testing:

     -> Software working for the user interface.

In-scope features:

     -> Features that fall under the user interface.

Out-of-scope features:

     -> Features that don't fall under the user interface.

Roles and Responsibility:

     -> To measure the user interface in checking all the conditions,check for any malfunctions interface.

     -> To identify malfunction of the mobile function during the user interaction.

Scheduled of Test:

     -> Start date:Day 1

     -> End date:Day 6

Assumptions:

     -> Good hardware working.

     -> Portable points also good condition.

Risks:

     -> Availability of close environment.

     -> Technical knowledge of the team python,java requirements.

Mitigation/Contingency plans:

     -> Recording of the problem with previous model upgrade in the previous structure.

     -> Analyze the testing report for the previous 3 models.

Test Methodology:

     -> We implemented the methodology is based on the requirements are,

     -> CFT condition.

     -> Error Guessing.

Test Deliverables:

     -> All the testing documents given below,

US-1:As a product owner,when long pressed the power button of the phone shall switch ON with a company logo at the center of the screen.

     -> if(power button is long pressed)

     -> printf("company logo at the center of the screen");

US-2:As a customer,when the power button is presssed my phone is switched ON and all my icons of the APPS shall be present in the grid.

     -> if(power button is pressed)

     -> Output:all my icons of the APPS shall be present in the grid.

US-3:As a product owner,when the phone is powered ON,I shall see the "call the phone" icon as the first icon at the bottom bar of my screen.

     -> if(phone is powered ON)

     -> Output:"call the phone" icon as the first icon at the bottom bar of my screen.

US-4:As a product owner,when the phone is powered ON,I shall see the "Dictionary" icon as the second icon at the bottom bar of my screen.

     -> if(phone is powered ON)

     -> Output:"Dictionary" icon as the second icon at the bottom bar of my screen.

US-5:As a product owner,when I clicked my "call the phone" icon,all the contacts shall be visible based on chronological order.

     -> if(clicked my "call the phone" icon)

     -> Output:all the contacts shall be visible based on chronological order.

US-6:As a product owner,when I clicked my "Dictionary" icon,a search bar shall appear at the middle of the screen to let me search the meanings of the words I desire.

     -> if(clicked my "Dictionary" icon)

     -> Output:search bar shall appear at the middle of the screen to let me search the meanings of the words I desire.

US-7:As a product owner,when I long pressed my "power on" button,my phone shall be switched off saying "Good-Bye" Message.

     -> if(power button is long pressed)

     -> Printf("my phone shall be switched off saying Good-Bye Message");

US-8:As a product owner,my font in the mobile shall always be "calibri(Body)" and shall be size 12.

     -> Readability

     -> Output:font "calibiri body" size 12.

US-9:As a Customer,I need my UI to be touch responsive.

     -> if(touch)

     -> Output:accurate response.

US-10:As a Customer,my mobile phone should have no hard buttons.

     -> Output:no hard buttons.

Your portfolio, next

Ship work like this
in your own course.

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.