PART A

(PART A : TO BE REFFERED BY STUDENTS)

Software Testing

A.1 Aim:
 To implement requirement testing for your project

A.2 Prerequisite:
Basic knowledge of Project topic

A.3 Outcome:

After successful completion of this experiment students will be able to

(a) To implement testing to further understand user requirements.

Theory :

Requirements testing also includes help in gathering and analysis of user data and their domain. This
procedure is required to research UI usability, creation of profiles, finalizing documentation and, on the
whole, facilitates design process.

This procedure helps improve requirements quality and reduce the number of tests necessary to meet
these requirements.

First of all, our QA team gathers and analyzes requirements to find out what technology will be used to
build the project, who this project is designed for and the project goal.

We also discover missing requirements to make sure the information we gathered is consistent, clear and
covers every aspect of software under development.

Then we create test cases on the basis of the requirement measurements and perform them to make sure
that the system under test operates in accordance with the set requirements.

For example, you’d like to have system response time of 2 seconds – that is your requirement
measurement. All of such requirement measurements are passed through tests and then evaluated.

We also take part in review meetings, and in case any new requirements appear or any changes are made
to the set requirements, we track them in an issue tracking system.
Finally, when all requirements are tested and the client is satisfied with the results and signs the
requirements document, we freeze the requirements for design phase.

A.4. Procedure:

Steps:

This type of testing covers testing of requirements specification that describes:

 project functionality
 user interface
 software and hardware interfaces
 performance criteria
 implementation issues and risks
 security and system correctness criteria

Following steps to be followed

Step 1:
 Discover Missing Requirement
 Check If the Requirements Are Related to The Project Goal

Step 2:
 Structure: What is it?

 Function: What does it do?

 Data: What does it process?

 Platform: What does it depend upon?

 Operations: How will it be used?

Step 3 :
Checklist for each requirement
1. User story describes one part of the functionality.

2. User story has all the necessary information and doesn’t refer to other stories.

3. All entities and objects of the user story are clear and defined in this story.
 4. The customer and programmer can co-create details during development.

5. User story captures the essence, not the details.

6. All items in the story are useful to the system user.

7. The functionality described in the story is user-friendly.

8. Tasks in a story have enough information to be estimated.

9. User story should be easily estimated or sized, so it can be properly prioritized.

10. User story can be fully implemented in one schedule (including testing).

11. User story isn’t too big to plan/task.

12. Acceptance criteria are accurate and unambiguous.

(PART - B)

(TO BE COMPLETED BY STUDENTS)

(Students must submit the soft copy as per following segments within two hours of the practical. The soft
copy must be uploaded on the MS Team at given link or emailed to the concerned lab in charge faculties
at the end of the practical in case there is no MS Team access available)

Roll.No. : Name:
Sem/Year : Batch:
Date of Experiment : Date of Submission:
Faculty

B.1: Input and Output:

 Write the answers of questions given in Part A

B.2: Learning’s:

(Students are expected to comment on the output obtained with clear observations and learning for each
task/ sub part assigned)
B.3: Conclusion:

(Students must write the conclusion as per the attainment of individual outcome listed above and
learning/observation noted in section B.2)