ISO/IEC 29110-5-1-1:2025 システムおよびソフトウェア エンジニアリング — 非常に小規模なエンティティ (VSE) のライフ サイクル プロファイル — Part 5-1-1:汎用エントリ プロファイルのソフトウェア エンジニアリング ガイドライン | ページ 6

3.1

agreement

mutual acknowledgment of terms and conditions under which a working relationship is conducted

[SOURCE:ISO/IEC/IEEE 12207:2017, 3.1.5]

3.2

baseline

formally approved version of a configuration item, regardless of media, formally designated and fixed at a specific time during the configuration item’s life cycle

[SOURCE:ISO/IEC/IEEE 12207:2017, 3.1.11]

3.3

defect

imperfection or deficiency in a work product (3.14) where that work product does not meet its requirements (3.8) or specifications and needs to be either repaired or replaced

[SOURCE:IEEE 1044:2009]

3.4

Entry profile

profile (3.5) targeted at start-up VSEs (i.e. VSEs who started their operation fewer than three years ago) and/or at VSEs working on a single small project (3.6) (e.g. project size of less than 6 person-months)

[SOURCE:ISO/IEC 29110-1-2:2024, 3.40]

3.5

profile

subset of appropriate standards’ processes and their outcomes, activities and tasks combined to accomplish a particular function

Note 1 to entry: The base standards used to develop profiles for VSEs are ISO/IEC/IEEE 12207, ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 15289.

[SOURCE:ISO/IEC 29110-1-2:2024, 3.70]

3.6

project

endeavour with defined start and finish dates undertaken to create a product or service in accordance with specified resources and requirements (3.8)

Note 1 to entry: A project is sometimes viewed as a unique process comprising coordinated and controlled activities and composed of activities from the Technical Management processes and Technical processes defined in this document.

[SOURCE:ISO/IEC/IEEE 12207:2017, 3.1.37]

3.7

report

information item that describes the results of activities such as investigations, observations, assessments, or tests

[SOURCE:ISO/IEC/IEEE 15289:2019, 3.1.22]

3.8

requirement

statement that translates or expresses a need and its associated constraints and conditions

Note 1 to entry: A constraint is an externally imposed limitation on the software, its design, or implementation or on the process used to develop or modify a software.

Note 2 to entry: A condition is a measurable qualitative or quantitative attribute that is stipulated for a requirement and that indicates a circumstance or event under which a requirement applies.

[SOURCE:ISO/IEC/IEEE 12207:2017, 3.1.44, modified — Notes to entry have been added.]

3.9

small and medium enterprise

SME

enterprise with less than 250 persons employed

[SOURCE:ISO/IEC 29110-1-2:2024, 3.92]

3.10

software product

set of computer programs, procedures, and possibly associated documentation and data

[SOURCE:ISO/IEC/IEEE 12207:2017, 3.1.45, modified — Note 1 to entry has been removed.]

3.11

task

requirement (3.8) , recommendation, or permissible action intended to contribute to the achievement of one or more outcomes of a process

[SOURCE:ISO/IEC/IEEE 12207:2017, 3.1.66]

3.12

validation

confirmation, through the provision of objective evidence, that the requirements (3.8) for a specific intended use or application have been fulfilled

Note 1 to entry: A system is able to accomplish its intended use, goals, and objectives (i.e. meet stakeholder requirements) in the intended operational environment. The right system was built.

Note 2 to entry: In a life cycle context, validation involves the set of activities for gaining confidence that a system is able to accomplish its intended use, goals, and objectives in an environment like the operational environment.

[SOURCE:ISO/IEC/IEEE 12207:2017, 3.1.71]

3.13

verification

confirmation, through the provision of objective evidence, that specified requirements (3.8) have been fulfilled

Note 1 to entry: Verification is a set of activities that compares a system or system element against the required characteristics. This includes, but is not limited to specified requirements, design, descriptions, and the system itself. The system was built right.

[SOURCE:ISO 9000:2015, 3.8.12, modified — Notes 1 to 3 to entry have been replaced by a new note 1 to entry.]

3.14

work product

artefact produced by a process

Note 1 to entry: A subset of the work products can be baselined to be used as the basis of further work, and some will form the set of project deliverables.

[SOURCE:ISO/IEC 20246:2017, 3.20]