Requirement Traceability Matrix or RTM captures all requirements proposed by the client or

software development team and their traceability in a single document delivered at the

conclusion of the life-cycle. In other words, it is a document that maps and traces user
requirement with test cases

A test strategy is an outline that describes the testing approach of the software development

cycle. It is created to inform project managers, testers, and developers about some key issues
of the testing process. 

BRD- Business Requirement Document The Business/Client/other Stakeholders provide a

requirement. ... But, has to be break wherever it requires and taken as multiple
requirements. FRD- Functional Requirement Document: The Process to reach the expectancy
of the BRD is an FRD. A functional specification (also, functional spec, specs, functional
specifications document (FSD), functional requirements specification) in systems
engineering and software development is a document that specifies the functions that a system or
component must perform (often part of a requirements specification)

Sanity testing is the subset of regression testing and it is performed when we do not have

enough time for doing testing. Sanity testing is the surface level testing where QA engineer
verifies that all the menus, functions, commands available in the product and project are
working fine.

Regression testing is a type of software testing that ensures that previously developed and

tested software still performs the same way after it is changed or interfaced with other software.
Changes may include software enhancements, patches, configuration changes, etc.

Types of testing

 Unit Testing.
 Integration Testing.
 Functional Testing.
 System Testing.
 Stress Testing.
 Performance Testing.
 Usability Testing.
 Acceptance Testing.

Level of Testing -There are generally four recognized levels of tests: unit/component

testing,integration testing, system testing, and acceptance testing.

Defect life cycle, also known as Bug Life cycle is the journey of a defect cycle, which
a defect goes through during its lifetime. It varies from organization to organization and also
from project to project as it is governed by the software testing process and also depends upon
the tools used.
 The V-model is an SDLC model where execution of processes happens in a sequential manner
in a V-shape. It is also known as Verification and Validationmodel. The V-Model is an extension
of the waterfall model and is based on the association of a testing phase for each
corresponding development stage.

Smoke Testing, also known as “Build Verification Testing”, is a type of softwaretesting that

comprises of a non-exhaustive set of tests that aim at ensuring that the most important
functions work. The results of this testing is used to decide if a build is stable enough to
proceed with further testing.

Types of Software developing life cycles (SDLC)

 Waterfall Model.
 V-Shaped Model.
 Evolutionary Prototyping Model.
 Spiral Method (SDM)
 Iterative and Incremental Method.
 Agile development.

There are following six phases in every Software development life cycle model:

 Requirement gathering and analysis.

 Design.
 Implementation or coding.
 Testing.
 Deployment.
 Maintenance.

RAD model is Rapid Application Development model. It is a type of incrementalmodel. In RAD

model the components or functions are developed in parallel as if they were mini projects. The
developments are time boxed, delivered and then assembled into a working prototype.

Software development lifecycle methodologies

 Agile - In the Agile model, “fast failure” is a good thing. The approach
produces ongoing release cycles, each featuring small, incremental changes
from the previous release. At each iteration, the product is tested.
 Lean - The seven Lean principles (in this order) are: eliminate waste,
amplify learning, decide as late possible, deliver as fast as possible, empower
the team, build integrity in, and see the whole.
 Waterfall - It’s also a very straightforward approach: finish one phase,
then move on to the next. No going back. Each stage relies on information
from the previous stage and has its own project plan.
 Iterative - The Iterative model is repetition incarnate. Instead of starting
with fully known requirements, project teams implement a set of software
requirements, then test, evaluate and pinpoint further requirements. A new
version of the software is produced with each phase, or iteration. Rinse and
repeat until the complete system is ready.
 Spiral - One of the most flexible SDLC methodologies, the Spiral model
takes a cue from the Iterative model and its repetition; the project passes
through four phases (planning, risk analysis, engineering and evaluation) over
and over in a “spiral” until completed, allowing for multiple rounds of
refinement.
 DevOps - In a DevOps model, Developers and Operations teams work
together closely — and sometimes as one team — to accelerate innovation
and the deployment of higher-quality and more reliable software products and
functionalities. Updates to products are small but frequent. Discipline,
continuous feedback and process improvement, and automation of manual
development processes are all hallmarks of the DevOps model.

The four core values of  agile software development as stated by the Agile Manifesto
emphasize:

 Individuals and interactions over processes and tools.

 Working software over comprehensive documentation.

 Customer collaboration over contract negotiation.

 Responding to change over following a plan.

The 12 principles laid down in the Agile Manifesto have been adapted for managing a
variety of business and IT-related projects, including business intelligence (BI).  They
include:

1. Satisfying 'customers' through early and continuous delivery of valuable work.

2. Breaking big work down into smaller components that can be completed
quickly.

3. Recognizing that the best work emerges from self-organizing teams.

4. Providing motivated individuals with the environment and support they need
and trust them to get the job done.

5. Creating processes that promote sustainable efforts.

6. Maintaining a constant pace for completed work.

7. Welcoming changing requirements, even late in a project.

8. Assembling the project team and business owners on a daily basis throughout
the project.

9. At regular intervals, having the team reflect upon how to become more
effective, then tuning and adjusting behavior accordingly.

10. Measuring progress by the amount of completed work.

11. Continually seeking excellence.

12. Harnessing change for competitive advantage.

Joint Application Development (JAD) is a development methodology system originally used for

designing a computer-based system, but can be applied to any development process. It
involves continuous interaction with the users and different designers of the system in
development.

A systems analyst is a person who uses analysis and design techniques to solve business
problems using information technology. Systems analysts may serve as change agents who
identify the organizational improvements needed, design systems to implement those changes,
and train and motivate others to use the systems.

Waterfall is a structured software development methodology, and often times can be quite rigid,
whereas the Agile methodology is known for its flexibility. ... One of the major differences
between Agile and Waterfall development methodology is their individual approach towards
quality and testing

Difference between Verification and Validation. The distinction between the two terms is

largely to do with the role of specifications. Validation is the process of checking whether the
specification captures the customer's needs. ... Verification is the process of checking that the
software meets the specification

The SDLC has five phases: The Planning phase, the Analysis phase, the Design phase,
the Implementation phase and the Maintenance Planning of the SDLC.

A software development life cycle (SDLC) model is a conceptual framework describing

all activities in a software development project from planning to maintenance. This
process is associated with several models, each including a variety of tasks and
activities. The development team selects the best suitable model. The different models
are:

 Waterfall model: Developers state the requirements, analyze them, determine a

solution and frame a software architecture, interface representation, and
algorithmic details. Then they develop the code, test the code, deploy the
software, and maintain it. While the waterfall method is easy to understand and
sets requirement stability, it might give a false impression of not providing much
customer participation. The main problem with this model is that the requirement
to correct errors should be known upfront and at an early stage. Otherwise, the
whole process may continue in a wrong direction, which could negatively impact
the cost of production.
 V Shaped model: Is a variation of the waterfall model. It emphasizes verification
and validation of the product. All deliverables are testable and progress is
tracked by milestones. Testing is implemented in parallel to
the development phase.
 Prototype model: A prototype is developed in the requirement phase and
evaluated by end users. Based on user feedback, developersalter the prototype
to satisfy user requirements. While this model finalizes the requirements easily,
its use in the production environment might result in quality issues, thereby
making the process of correction continue forever.
 Spiral model: Makes use of both waterfall and prototype models. It adds 4th
generation programming languages, rapid application development prototyping
and risk analysis to the waterfall model. The system requirements are designed
and a preliminary system design is created. An initial prototype is designed and
tested. Based on the evaluation of test results, a second prototype is created.
Subsequent prototypes are constructed to ensure customer satisfaction. The
system is created based on the final prototype. The final system is evaluated and
tested. Though this model reduces risk to a large extent, it may not meet the
budget and is applied differently for each application.
 Iterative and incremental SDLC model: Specifies and implements a part of the
software, which is then reviewed and further requirements added and
implemented in groups. Every release delivers an operational product presenting
the customers with important functionalities first, lowering initial delivery costs.
The risk of changing requirements is greatly reduced and customers are allowed
to respond to each build. In spite of its strengths, this model requires good
 planning and early definition of the complete and fully functional system. It also
requires well-defined module interfaces.
 Agile development model: Is used for time-critical applications in organizations
employing disciplined methods. It speeds up the life cycle phases and has
reduced scope.
 Magic box model: Is a Web application development model. It is the fastest way
to finish the project with the least bugs as it provides the chance to alter the code
and database structures.

Scrum is not a methodology. It simply provides structure, discipline and a framework

for Agile development. The whole project is made up of a series of Sprints or Sprint Cycles (1 to
n) where each Sprint is of the same duration.

Severity of a defect is related to how severe a bug is. Usually the severity is defined in terms of
financial loss, damage to environment, company's reputation and loss of life. Priority of a defect
is related to how quickly a bug should be fixed and deployed to live servers.

Kanban is one of the Lean tools designed to reduce the idle time in a production
process. The main idea behind the Kanban system is to deliver what the process
needs exactly when it needs it.

In Japanese, the word "Kan" means "visual" and "ban" means "card," so Kanban
refers to visual cards. Lean uses visual cards as a signaling system that triggers
an action to supply the process with its needs either from an external supplier or
from a warehouse.

6 rules of Kanban provided by Toyota:

1. Customer (downstream) processes withdraw items in the precise amounts specified by the
Kanban.
2. Supplier (upstream) produces items in the precise amounts and sequences specified by the
Kanban.
3. No items are made or moved without a Kanban.
4. A Kanban should accompany each item, every time.
5. Defects and incorrect amounts are never sent to the next downstream process.
6. The number of Kanbans is reduced carefully to lower inventories and to reveal problems.

Implementing 5S lean manufacturing training has a number of other benefits,

these include:

 Increased Productivity. Every organization works towards achieving increased

productivity, after all, productivity increases the overall return on investment. ...
 Improved Safety. ...
 Reduction in Waste. ...
 Worker Commitment

5S in Kaizen stands for sort, set in order, shine, standardize and sustain.

KAIZEN BENEFITS. These continual small improvements add up to major benefits. They result
in improved productivity, improved quality, better safety, faster delivery, lower costs, and
greater customer satisfaction

Poka-yoke [poka joke] is a Japanese term that means "mistake-proofing" or "inadvertent error

prevention". The key word in the second translation, often omitted, is "inadvertent". ... A poka-
yoke is any mechanism in a lean manufacturing process that helps an equipment operator
avoid (yokeru) mistakes (poka).

A core definition of total quality management (TQM) describes a management approach to

long–term success through customer satisfaction. In a TQM effort, all members of an
organization participate in improving processes, products, services, and the culture in which
they work.

The ISO 9000:2015 and ISO 9001:2015 standards are based on seven quality
management principles that senior management can apply for organizational
improvement:

 Customer focus.
 Leadership.
 Engagement of people.
 Process approach.
 Improvement.
 Evidence-based decision-making.
 Relationship management.

Introduction to HP Application Lifecycle Management/Quality Center: HP ALM formerly known

as Quality Center is a Test Management tool to manage entire Quality Assurance and testing
process for an organization. Before being called HPQuality center it used to be Mercury Test
Director