What is the context for the paradigm in a methodology

In a general context, the term “paradigm” refers to a framework or model that shapes how we perceive and understand the world around us. It is a set of beliefs, values, assumptions, regulations, standards and practices that form the basis for how we approach and interpret various aspects of a ‘field of knowledge’. In our case the field of software testing.

The concept of paradigm was popularized by philosopher and historian of science, Thomas Kuhn, in his influential book “The Structure of Scientific Revolutions” published in 1962. Kuhn used the term to describe the fundamental shifts in scientific thinking and methodologies that occur when a new scientific theory or model replaces the prevailing one. He argued that scientific progress is not always a steady accumulation of knowledge but involves disruptive changes called “paradigm shifts” that redefine the scientific landscape.

In this context, Bona Iiqniso is using the ‘paradigm’ of several sources, creating its own paradigm. It provides a shared framework for software testing practitioners to understand, communicate, and advance knowledge.

Paradigm can be anything that relates to software testing and that influences Bona Iqiniso. This is a bit too abstract and may make it unclear whether something is part of the core of the Bona Iqiniso methodology (life cycle, qualitative and/or quantitative techniques, methods) or merely an influencer (paradigm).

That is why Bona Iqiniso uses the following guide to determine this.

• Foundation: Bona Iqiniso uses this artifact as a source, or reference, to have a link with commonly accepted ideas. E.g. the ISO 29119 standard gives us a foundation for software testing but misses practicality. Bona Iqiniso uses bits and pieces from this standard to explain what to do, how to do it, why and where. This is part of the Bona Iqiniso paradigm.
  • Standards
  • Regulations
  • White papers
  • Presentations
  • Websites
  • Blogs
  • (e)Books
• Support: Bona Iqiniso uses this artifact to help implement a practical, hands-on approach to software testing. E.g. reference models help to describe the context of a software testing practice. Templates help to visualize the concept. Guidelines help the implementation and checklists help both the implementation and verification.
  • Templates
  • Guidelines
  • Checklists
  • Taxonomies
  • reference models (see also qualitative techniques – context)
  • Metrics/Controls/Indicators (see also quantitative techniques – context)
  • …
• Core: Bona Iqiniso describes software testing methods, but will use paradigm documents to detail these methods. Don’t forget that Bona Iqiniso is supporting organizations in doing software testing, but does not dictate. E.g. Every method needs to be captured in a policy document. Bona Iqiniso will create this document in the paradigm section because organizations will have to customize this document to fit their organization.
  • Policy
  • Strategy
  • Stakeholders (roles & responsibilities)
  • …