ISO/IEC/IEEE 29148
E20661
ISO/IEC/IEEE 29148 is an international standard that defines best practices and processes for engineering and managing system and software requirements.
All labels observed (5)
How this entity was disambiguated
This entity first appeared as the object of triple T166337 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: ISO/IEC/IEEE 29148 Context triple: [IEEE 830, supersededBy, ISO/IEC/IEEE 29148]
-
A.
IEEE 1532
IEEE 1532 is an extension of the JTAG boundary-scan standard that defines in-system programming and configuration procedures for programmable devices such as FPGAs and CPLDs.
-
B.
IEEE 1028 (Software Reviews and Audits)
IEEE 1028 (Software Reviews and Audits) is an IEEE Computer Society standard that defines processes and procedures for conducting formal software reviews and audits throughout the software lifecycle.
-
C.
ISO 21500
ISO 21500 is an international standard that provides high-level guidance and principles for effective project management applicable to organizations of all types and sizes.
-
D.
IEEE 1012 (Software Verification and Validation)
IEEE 1012 (Software Verification and Validation) is an IEEE standard that defines processes and requirements for systematically verifying and validating software and system products throughout their life cycle.
-
E.
IEEE 830 (Software Requirements Specification standard)
IEEE 830 (Software Requirements Specification standard) is a widely recognized IEEE guideline that defines the recommended structure and content for documenting software requirements in a clear, complete, and verifiable manner.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: ISO/IEC/IEEE 29148 Target entity description: ISO/IEC/IEEE 29148 is an international standard that defines best practices and processes for engineering and managing system and software requirements.
-
A.
IEEE 1532
IEEE 1532 is an extension of the JTAG boundary-scan standard that defines in-system programming and configuration procedures for programmable devices such as FPGAs and CPLDs.
-
B.
IEEE 1028 (Software Reviews and Audits)
IEEE 1028 (Software Reviews and Audits) is an IEEE Computer Society standard that defines processes and procedures for conducting formal software reviews and audits throughout the software lifecycle.
-
C.
ISO 21500
ISO 21500 is an international standard that provides high-level guidance and principles for effective project management applicable to organizations of all types and sizes.
-
D.
IEEE 1012 (Software Verification and Validation)
IEEE 1012 (Software Verification and Validation) is an IEEE standard that defines processes and requirements for systematically verifying and validating software and system products throughout their life cycle.
-
E.
IEEE 830 (Software Requirements Specification standard)
IEEE 830 (Software Requirements Specification standard) is a widely recognized IEEE guideline that defines the recommended structure and content for documenting software requirements in a clear, complete, and verifiable manner.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
international standard
ⓘ
systems and software engineering standard ⓘ |
| appliesTo |
life cycle processes
ⓘ
software engineering ⓘ systems engineering ⓘ |
| covers |
analysis of requirements
ⓘ
elicitation of requirements ⓘ management of requirements changes ⓘ specification of requirements ⓘ validation of requirements ⓘ |
| defines |
best practices for software requirements
ⓘ
best practices for system requirements ⓘ requirements engineering processes ⓘ requirements management processes ⓘ |
| focusesOn |
engineering of requirements
ⓘ
management of requirements ⓘ |
| fullName |
ISO/IEC/IEEE 29148
self-linksurface differs
ⓘ
surface form:
ISO/IEC/IEEE 29148 Systems and software engineering — Life cycle processes — Requirements engineering
|
| governingBody |
Institute of Electrical and Electronics Engineers
ⓘ
International Electrotechnical Commission ⓘ International Organization for Standardization ⓘ |
| intendedAudience |
project managers
ⓘ
requirements engineers ⓘ software engineers ⓘ systems engineers ⓘ |
| objective |
improve completeness of requirements
ⓘ
improve consistency of requirements ⓘ improve correctness of requirements ⓘ support communication among stakeholders ⓘ |
| provides |
requirements engineering guidance
ⓘ
requirements management guidance ⓘ requirements quality criteria ⓘ requirements specification guidelines ⓘ |
| relatedTo |
ISO/IEC 12207
ⓘ
surface form:
ISO/IEC/IEEE 12207
ISO/IEC 15288 ⓘ
surface form:
ISO/IEC/IEEE 15288
|
| replaces |
IEEE 830 (Software Requirements Specification standard)
ⓘ
surface form:
IEEE 830
|
| scope |
life cycle requirements processes
ⓘ
software requirements ⓘ stakeholder requirements ⓘ system requirements ⓘ |
| standardFamily |
International Electrotechnical Commission
ⓘ
surface form:
IEC
Institute of Electrical and Electronics Engineers ⓘ
surface form:
IEEE
International Organization for Standardization ⓘ
surface form:
ISO
|
| subjectArea |
requirements engineering
ⓘ
requirements management ⓘ systems and software engineering ⓘ |
| usedFor |
assessing quality of requirements
ⓘ
developing requirements specifications ⓘ establishing organizational requirements processes ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: ISO/IEC/IEEE 29148 Description of subject: ISO/IEC/IEEE 29148 is an international standard that defines best practices and processes for engineering and managing system and software requirements.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.