Glossary all terms 3.1 / Glossary all terms 3.1: S

Власник перекладу встановив такі правила доступу, що ви не можете переглядати чужі варіанти перекладів тут.
Оригінал англійською Переклад українською

S.M.A.R.T. goal methodology (SMART)
A methodology whereby objectives are defined very specifically rather than generically. SMART is an acronym derived from the attributes of the objective to be defined: Specific, Measurable, Attainable, Relevant and Timely.

#1


safety

#2

safety critical system
A system whose failure or malfunction may result in death or serious injury to people, or loss or severe damage to equipment, or environmental harm.

#3

safety testing
Testing to determine the safety of a software product.

#4

salting
See Also: hashing
A cryptographic technique that adds random data (salt) to the user data prior to hashing.

#5

scalability
Ref: After Gerrard
The capability of the software product to be upgraded to accommodate increased loads.

#6

scalability testing
Testing to determine the scalability of the software product.

#7

scorecard
See Also: balanced scorecard, dashboard
A representation of summarized performance measurements representing progress towards the implementation of long-term goals. A scorecard provides static measurements of performance over or at the end of a defined interval.

#8

scribe

#9

script kiddie
See Also: hacker
A person who executes security attacks that have been created by other hackers rather than creating own ones.

#10

scripted testing
Test execution carried out by following a previously documented sequence of tests.

#11

scripting language

#12

scrum
See Also: Agile software development
An iterative incremental framework for managing projects commonly used with Agile software development.

#13

security

#14

security attack
Ref: after NIST.IR.7298
An attempt to gain unauthorized access to a system or component, resources, information, or an attempt to
compromise system integrity.

#15

security audit
An audit evaluating an organization's security processes and infrastructure.

#16

security policy
A high-level document describing the principles, approach and major objectives of the organization regarding security.

#17

security procedure
A set of steps required to implement the security policy and the steps to be taken in response to a security incident

#18

security testing

#19

security testing tool

#20

security tool

#21

security vulnerability
A weakness in the system that could allow for a successful security attack.

#22

session-based test management
A method for measuring and managing session-based testing, e.g., exploratory testing.

#23

session-based testing
An approach to testing in which test activities are planned as uninterrupted sessions of test design and execution, often used in conjunction with exploratory testing.

#24

severity

#25

short-circuiting
A programming language/interpreter technique for evaluating compound conditions in which a condition on one side of a logical operator may not be evaluated if the condition on the other side is sufficient to determine the final outcome.

#26

simulation

#27

simulator

#28

site acceptance testing

#29

smoke test
See Also: build, verification test, intake test
Synonyms: confidence test , sanity test
A subset of all defined/planned test cases that cover the main functionality of a component or system, to ascertaining that the most crucial functions of a program work, but not bothering with finer details.

#30

social engineering
Ref: NIST.IR.7298
An attempt to trick someone into revealing information (e.g., a password) that can be used to attack systems or networks.

#31

software

#32

software integrity level

#33

software lifecycle

#34

software process improvement (SPI)
Ref: After CMMI
A program of activities designed to improve the performance and maturity of the organization's software processes and the results of such a program.

#35

software quality
Ref: After ISO 9126 See Also: quality
The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs.

#36

Software Usability Measurement Inventory (SUMI)
Ref: Kirakowski93
A questionnaire-based usability test technique for measuring software quality from the end user's point of view.

#37

specification

#38

specified input
An input for which the specification predicts a result.

#39

SQL injection
A security attack inserting malicious SQL statements into an entry field for execution.

#40

stability

#41

staged representation
See Also: CMMI
A model structure wherein attaining the goals of a set of process areas establishes a maturity level; each level builds a foundation for subsequent levels.

#42

standard

#43

standard-compliant test strategy
A test strategy whereby the test team follows a standard. Standards followed may be valid e.g., for a country (legislation standards), a business domain (domain standards), or internally (organizational standards).

#44

standard-compliant testing

#45

state diagram
Ref: IEEE 610
A diagram that depicts the states that a component or system can assume, and shows the events or circumstances that cause and/or result from a change from one state to another.

#46

state table

#47

state transition

#48

state transition testing

#49

statement

#50

Наступна сторінка →

Хвилинку...