Home>IEC Standards>IEC 61713:2000 pdf download

IEC 61713:2000 pdf download

IEC 61713:2000 pdf download.Software dependability through the software life-cycle processes -Application guide.
3 Definitions
For the purpose of this International Standard, the terms and definitions of IEC 60050(191).
ISOIIEC 12207 and ISO 8402 apply together with the following.
3.1
dependability
collective term used to describe the availability performance and its influencing factors:
reliability performance, maintainability performance and maintenance support performance.
[1EV 191-02-03)
NOTE Software dependability will be descritied in ernie at sotteale reliability, eoltwsre maintainabilily and software maintenance support.
3.2
dependability function
term used to describe an individual aspect of the software dependability requirement specification. The dependability function can describe reliability, maintainability or maintenance support- related dependability requirements
3.3
maintenance release
product release which is carried out for corrective maintenance rather than to provide enhanced functionality
3.4
software reliability
probability that no fault in any software element of a system will be activated in a given time interval in the operation of the system under given conditions
3.5
software maintainability
ease with which a detected fault in a software element of a system can be corrected
3.6
software maintenance support
ability of an organization, under given conditions, to provide upon demand the resources required to maintain a software element of a system, under a given maintenance policy
NOTE The given conditions are related to the sollware element itself and to the COndet,ons under which his used and maintained
To assist understanding of this standard, the following definitions of terms used in ISOIEC 12207 are repeated here.
3.7
acquirer
organization that acquires or procures a system. software product or software service from a supplier
NOTE The acquirer could be one 01 Itt. lollomng: buyer, customer, owner, user, purchaser.
3.8
acquisition
process of obtaining a system, software product or software service
3.9
agreement
definition of terms and conditions under which a working relahonship will be conducted
3.10
audit
conducted by an authorized person for the purpose of providing an independent assessment of software products and processes in order to assess compliance with requirements
3.11
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
3.12
configuration item
entity within a configuration that satisfies an end-use function and that can be uniquely identified at a given reference point
3.13
contract
binding agreement between two parties, especially enforceable by law, or a similar internal agreement wholly within an organization, for the supply of software service or for the supply. development, production, operation, or maintenance of a software product
3.14
developer
organization that performs development activities (including requirements analysis, design, testing through acceptance) during the software life.cycle process
3.15
evaluation
systematic determination of the extent to whch an entity meets its specified criteria
3.16
firmware
combination of a hardware device and computer instructions or computer data that reside as read-only software on the hardware device The software cannot be readily modified under program control
3.17
life-cycl, model
framework containing the processes, activities, and tasks involved In the development. operation, and maintenance of a software product, spanning the life of the system from the definition of its requirements to the termination of its use
3.18
maintainer
organization that performs maintenance activities
3.19
monitoring
examination of the status of the activities of a supplier and of their results by the acquirer or a third party
3.20
non-deliverable item
hardware or software product that Is not required to be delivered under the contract but may be employed in the development of a software product
3.21
ofl-the-shelf product
product that is already developed and available, usable either as is or with modification
3.22
operator
organization that operates the system
3.23
process
set of timely ordered and interrelated activities, which translorm inputs into outputs NOTE The term activities covers use of resources,
3.24
qualification
process of demonstrating whether an entity is capable of fulfilling specified requirements
3.25
qualification requirement
set of criteria or conditions that have to be met in order to qualify a software product as complying with its specifications and being ready for use in its target environment.

Related Standards