management

Stakeholder

Forming part of the value/risk story: Anyone who has a vested interest in the success (or failure) of the project

Expectations & Oracles

Expectations are mental models of how software works or delivers value; built from references which can be used as oracles to evaluate and identify problems

Left vs Right

Continuous, parallel testing in throughout the software DevOps lifecycle

Idea & Artefact

Software starts with an idea which is communicated and refined through artefacts tested with heuristics and imaginations

Risk Mapping & Threat Modelling

Risk assessment framework via value, scope, assets, categories, risks, threats, vulnerabilities then prioritise document, manage, monitor, retrospect

Capability

Ability to complete tasks in reasonable and expected ways, possibly in multiple different ways (flexibility).

Performance

Ability to complete tasks in reasonable time and with reasonable responsiveness

Usability

Ability to complete those tasks reasonably easily, simply and intuitively.

Accessibility

Ability to complete those tasks reasonably well as accessibility-needs users

Security

Ability to reasonably guard against completing or altering tasks as unauthorised users or prevent authorised users from doing so

Reliability

Ability to complete tasks reasonable accurately and when needed

Security (Project)

Ability for teams to guard against information confidentiality, integrity, availability issues

References

Ideas or artefacts that form the basis of expectations and utilised as comparison oracles

Auth

Authentication vs Authorisation: Confirming users are who they say they are and assigning what users can do and access

MAC/DAC/RBAC

For authentication and authorisation, logical access control can be mandatory, discretionary or role-based

MFA

Authentication via multiple method types of knowledge, possession (token) and inherence (biometric) where needed

Process

Process are repeatable tasks to achieve something modellable as flow diagrams

Metrics

Assigning numbers to test processes including information or motivation; value vs cost; execution, reporting and setup; dysfunction and construct validity

Assurance vs Control

Proactive vs reactive approaches to putting good things in and taking bad things out of testing processes to assure and control testing quality

Servant

Leadership through selfless empowerment, growth, improvement, moral/values led, action, responsibility

Motivation

Measurement management via theory X external vs delegation management via theory Y internal, plus values and relationships

Mentor

Process where seniors help/assist/teach/advise/guide juniors/interns/apprentices to onboard, upskill, achieve goal, get promoted informally/ad-hoc or part of a programme

1:1

(One-to-one) Regular, private, non-status update, tester-driven agenda meetings to build human connections, trust and rapport with manager

Environment

Foster trust, support, happy, fulfilled working conditions for teams

Values

A strong set based on strong moral and integral principles to lead by, and to facilitate in teams

Moral

Guides core values, direction and decisions towards a greater good with sacrifice, subordination, worthy cause, justification and relationships

Skills

Skills, knowledge, abilities that form the role and responsibilities of testers

Institution

Build a model team of shared purpose, support, fulfilment, growth, nobility through shared goals/concepts, discipline, service, structure, trustees

First/Action

Show the way, invite followers and lead by example, also consult with team, show patience, speak last but make decision, take first step and accept responsibility for failure

Concurrency

Ability to complete tasks reasonably simultaneously with similar or other tasks