Ieee 1012

IEEE's 1012 Standard for independent software and hardware verification and validation (IV&V) is under attack in U.S. federal criminal court. As software spreads through the criminal legal system ...

IEC/IEEE 82079-1:2019 Preparation of information for use (instructions for use) of products: Part 1: ... IEEE 1012-2016 IEEE Standard for System, Software, and Hardware Verification and Validation Author: IEEE (06-02-2020) IEEE 1016-2009 IEEE standard for Information Technology-Systems Design-Software Design Descriptions Author: IEEE (05-12-2011)IEEE 1012 focuses on the verification and validation of the software entire lifecycle, and gives the minimum set of tasks and V&V requirements for each software V&V phase, which is suitable for the identification of software with complete development documents and data. EPRI NP-5652 provides an evaluation and acceptance method for commercial ...IEEE 1012-2016. IEEE Standard for System, Software, and Hardware Verification and Validation . Add to cart ISO 15382:2015. Radiological protection - Procedures for monitoring the dose to the lens of the eye, the skin and the extremit ... Add to cart Document History.(IEEE 1012-2004, 3.1.35) Source (1) ISO/IEC/IEEE. 2015. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15288:2015 …is based in part on IEEE Standard 1012 (“IEEE 1012-2016 - IEEE Standard for System, Software, and Hardware Verification and Validation” 2016) and ISO 16730-1 (“ISO 16730-1:2015E - Fire Safety Engineering — Procedures and Requirements for Verification and Validation of Calculation Methods” 2015).IEEE 1012-2016, IEEE Standard for System, Software, and Hardware Verification and Validation [19] IEEE 2675-2021, IEEE Standard for DevOps: Building Reliable and Secure Systems Including Application Build, Package and Deployment: IEEE notices and abstract.

Title: IEEE Standard For Software Verification and Validation - IEEE Standard F or Software Verification and Validation - IEEE Std. 1012-1998 AuthorISO/IEC/IEEE 15026 (all parts) uses concepts and terms consistent with ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and generally consistent with the ISO/IEC 25000 series, but the potential users of ISO/IEC/IEEE 15026 (all parts) need to understand the differences from concepts and terms to which they may be accustomed. This document attempts to ...IEEE 1012‐2004 • SRR/SDR IV&V findings • Mostly Requirements • Some Findings on – Architecture – Verification – CONOPS IEEE 1012-2004 Standard for Software Verification and Validation SLS Artif act #1 SLS Artif act #2 SLS Artif act #3 IV&V Pre-Rid & RID References 1. Overview 2. Referenced documents 3. Definitions 4. Software ... IEEE 1012‐2004 • SRR/SDR IV&V findings • Mostly Requirements • Some Findings on – Architecture – Verification – CONOPS IEEE 1012-2004 Standard for Software Verification and Validation SLS Artif act #1 SLS Artif act #2 SLS Artif act #3 IV&V Pre-Rid & RID References 1. Overview 2. Referenced documents 3. Definitions 4. Software ...The IEEE Std. 1012-2004 adopts software integrity level (SIL) system, SIL 4 being the highest and SIL 1 the lowest. The minimum V&V tasks are determined by SIL. The SIL is a range of values that represent characteristics that define the importance of the software such as software complexity, criticality, and safety level.CWE™ is a community-developed list of software and hardware weakness types. It serves as a common language, a measuring stick for security tools, and as a baseline for weakness identification, mitigation, and prevention efforts. This list demonstrates the currently most common and impactful software weaknesses.He is a Senior Staff Systems Engineer with Northrop Grumman. He has been the Chair of the IEEE 1012 Working Group since 2018, after serving as Secretary from 2007 to 2018. Dr. Addy has been the Chair of the IEEE Computer Society Software and Systems Engineering Standards Committee since 2019, having served on the Executive Committee since 2013.

1012-1998 IEEE Standard for Software Verification and Validation. Software verification and validation (V&V) processes, which determine whether development products of a given activity conform to the requirements of that activity, and whether the software satisfies its intended use and user needs, are described. This determination may include ...Verification and validation (V&V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&V life cycle process requirements are specified for different integrity levels. The scope of V&V processes encompasses systems, software, and hardware, and it ...Mar 2, 2018 · The main body of the ISO/IEC/IEEE 12207-2008 Standard and the IEEE 1012-2012 are dedicated to a description of the processes, activities, and tasks of the software life cycle. The IEEE Standard 1012-2012 is a process that defines all SQA activities throughout the entire software life cycle as V&V activities. IEEE 829-2008 또는 829 Standard for Software and System Test Documentation 은 소프트웨어 시험을 위한 '8가지 정의된 단계'를 규정한 IEEE 표준이다. 하부표준은 다음 8가지이다. 이 글은 표준에 관한 토막글 입니다. 여러분의 지식으로 알차게 문서를 완성해 갑시다.

Climate and vegetation.

IEEE 1008: unit testing ; IEEE 1012: software verification and validation ; IEEE 1028: software inspections ; IEEE 1044: classification of software anomalies; there is a plethora of directly and indirectly related documents and …Intellect applies an Independent Verification and Validation approach based on the IEEE 1012-2016, IEEE Standard for System, Software, and Hardware Verification ...Both IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997 place requirements on plans for verification of soft- ware and validation of software. The purpose of this annex is ... testing strategy. One is the level of software integrity required. IEEE 1012-2004 (IEEE 2004b) defines four integrity levels ranging from level four, where if the software does not run correctly there may be significant consequences (loss of life, equipment, or money) to level one where the consequences of failure are minor. IEEE 1012 serves as a time-tested, widely accepted, and universally applicable process for ensuring that AI systems meet the required standards for their intended use. Policymakers can adopt this ...Standards. IEEE Guide for Software Verification and Validation Plans. Guidance in preparing Software Verification and Validation Plans (SVVPs) that comply with IEEE Std 1012-1986 are provided. IEEE Std 1012-1986 specifies the required content for an SVVP. This guide recommends approaches to Verification and Validation (V & V) planning.

7. IEEE Std 1012-1998 (IEEE, 1998) berkaitan dengan proses untuk menentukan apakah suatu produk perangkat lunak sesuai dengan spesifikasi persyaratan (verifikasi) dan apakah itu memenuhi tujuan digunakan (validasi). Standar ini mengadopsi berbagai aplikasi, seperti yang dituntut oleh berbagai verifikasi dan validasi (V & V) metode yang tersedia untuk …The purpose of this standard is to: - Establish a common framework of the V&V processes, activities, and tasks in support of all system, software, and hardware life cycle processes. - Define the V&V tasks, required inputs, and required outputs in each life cycle process. - Identify the minimum V&V tasks corresponding to a four-level integrity ...Both IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997 place requirements on plans for verification of soft- ware and validation of software. The purpose of this annex is ...IEEE Std. 1012-2004와 IEEE Std. 1012-2012의 목차 비교> 2) 무결성 등급에 기반한 V&V 조직의 역할 설정 무결성의 수준은 사용자에 대한 시스템의 중요성에 따라 복잡성, 중요도, 위험, 안전 수준, 보안 수준, 원하는 성능, 안전성 또는 기타 시스템 고유의 특성을 정량화 하여 ...Integrity Level (SIL)’ defined in IEEE 1012: Standard for Software Verification and Validation. Part 4 of IEC 61508 defines Safety Integrity as the likelihood of a safety related system satisfactorily performing the specified safety functions under all the stated conditions within a stated period of time; and a Safety Integrity Level (SIL) as ...IEEE standard 1012 [33] focuses on verification & validation (V&V) processes and applies to systems, software, and hardware being developed, maintained, or reused (e.g., Commercial Off-the-Shelf (COTS) components). V&V processes include the analysis, evaluation, review, inspection, assessment, and testing of products. 1012-2016/Cor 1-2017 IEEE Draft Standard for System, Software and Hardware Verification and Validation - Corrigendum 1. Verification and validation (V&V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs.Verification and validation (V&V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&V life cycle process requirements are specified for different integrity levels. The scope of V&V processes encompasses systems, software, and hardware, and it ...IEEE Std 1012-1986 was a product standard that defined the contents of the Software Verification and Vali-dation Plan (SVVP). This revision of the standard, IEEE Std 1012-1998, is a process standard that defines the verification and validation processes in terms of specific activities and related tasks. IEEE Std 1012-1998 Background to IEEE 829. IEEE 829-2008, also known as the 829 Standard for Software and System Test Documentation, was an IEEE standard that specified the form of a set of documents for use in eight defined stages of software testing and system testing, each stage potentially producing its own separate type of document.Both IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997 place requirements on plans for verification of soft- ware and validation of software. The purpose of this annex is ...

CWE™ is a community-developed list of software and hardware weakness types. It serves as a common language, a measuring stick for security tools, and as a baseline for weakness identification, mitigation, and prevention efforts. This list demonstrates the currently most common and impactful software weaknesses.

IV&V is mentioned in DO-178B, ISO/IEC 12207 and formalized in IEEE 1012. At ESA [ edit ] Initially in 2004-2005, a European consortium led by the European Space Agency , and composed by DNV , Critical Software SA , Terma and CODA SciSys plc created the first version of a guide devoted to ISVV, called "ESA Guide for Independent Verification and ...Verification and Validation (V and V) include the analysis, evaluation, review, inspection, assessment, and testing of products. Especially testing is an important method to verify and validate software. Software V and V testing covers test planning to execution. ISupersedes IEEE DRAFT 1012. (06/2005) Supersedes IEEE 1012A. (03/2006) 2016 version includes COR 1 2017. (10/2017) Document Type: Standard: ISBN: Pages: Published: Publisher: Institute of Electrical & Electronics Engineers : Status: Superseded: Superseded By: IEEE 1012 : 2016 ; Supersedes: IEEE DRAFT 1012 : 0 ; IEEE 1012A : 1998 ; IEEE 1012 : 2004... IEEE 29119 SRS – Software requirements specification • IEEE 29148 V&V – Software verification and validation • IEEE 1012 SDD – Software design description • ...IEEE 1012‐2004 • SRR/SDR IV&V findings • Mostly Requirements • Some Findings on – Architecture – Verification – CONOPS IEEE 1012-2004 Standard for Software Verification and Validation SLS Artif act #1 SLS Artif act #2 SLS Artif act #3 IV&V Pre-Rid & RID References 1. Overview 2. Referenced documents 3. Definitions 4. Software ...Mar 31, 2020 · IEEE 1012-2016 Estándar para la Verificación y Validación de Sistema,Software y Hardware Presentado por Yoana Caro Taborda Juan Carlos Calle García Daniel Fernando Areiza Agudelo Dairo Arley García Vergara ¿ Cuál es la diferencia entre Verificación y Validación? The main body of the ISO/IEC/IEEE 12207-2008 Standard and the IEEE 1012-2012 are dedicated to a description of the processes, activities, and tasks of the software life cycle. The IEEE Standard 1012-2012 is a process that defines all SQA activities throughout the entire software life cycle as V&V activities. The standard requires the ...Title: IEEE Standard For Software Verification and Validation - IEEE Standard F or Software Verification and Validation - IEEE Std. 1012-1998 AuthorIEEE 1012‐2004 • SRR/SDR IV&V findings • Mostly Requirements • Some Findings on – Architecture – Verification – CONOPS IEEE 1012-2004 Standard for Software Verification and Validation SLS Artif act #1 SLS Artif act #2 SLS Artif act #3 IV&V Pre-Rid & RID References 1. Overview 2. Referenced documents 3. Definitions 4. Software ...

Jason seber conductor.

Who is playing basketball.

ieee ieee 1012-2004 1.168 ip-65001.10 ieee ieee 1016-1987 ip-52003 ieee ieee 1016-1998 ip-65001.10 ieee ieee 1023-1988 ieee ieee 1028 imc-1252 app bDownload the latest drivers, firmware, and software for your HP LaserJet 1012 Printer.This is HP's official website that will help automatically detect and ...ABOUT. 23-26 OCT 2023 | Grenoble, France. 29 OCT. 2023 IEEE/ACM International Conference on Computer Aided Design (ICCAD) CALL FOR PAPERS. ABOUT. 29 OCT-2 NOV 2023 | San Francisco, California, USA. 2023 62nd IEEE Conference on Decision and Control (CDC) REGISTER.IEEE Standard for Software Verification and Validation – Content Map to IEEE 12207.1. The relationship between the two sets of requirements on plans for verification and validation of software, found in IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997, is explained so that users may produce documents that comply with both standards. Sponsor ...IEEE does not warrant or represent the accuracy or content of the material contained in its standards, and expressly disclaims all warranties (express, implied and statutory) not included in this or any other document relating to the standard, including, but not limited to, the warranties of: merchantability; fitnessMicrosoft Excel was designed around the IEEE 754 specification to determine how it stores and calculates floating-point numbers. IEEE is the Institute of Electrical and Electronics Engineers, an international body that, among other things, determines standards for computer software and hardware. The 754 specification is a very widely adopted ...1012-1998 - IEEE Standard for Software Verification and Validation. Abstract: Software verification and validation (V&V) processes, which determine whether development products of a given activity conform to the requirements of that activity, and whether the software satisfies its intended use and user needs, are described. This determination ... - IEEE Std 1012-2004, IEEE Standard for Software V&V, The Institute of Electrical and. Electronics Engineers, 2005, ISBN 0-7381-4641-2. - IEEE Std 1016-1998, ...1012-2016/Cor 1-2017 IEEE Draft Standard for System, Software and Hardware Verification and Validation - Corrigendum 1. Verification and validation (V&V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. ….

1012-2004 - IEEE Standard for Software Verification and Validation. null | IEEE Xplore 1012-2004 - IEEE Standard for Software Verification and Validation | IEEE Xplore IEEE websites place cookies on your device to give you the best user experience. ... IEEE Std. 1012- 2012 (which will be referred to as “IEEE 1012” for the remainder of this SLP). While the focus of. IEEE 1012 is V&V and not specifically IV&V ...IEEE 730 Institute of Electrical and Electronics Engineers (IEEE) Standard for Software Quality Assurance Processes IEEE 828 IEEE Standard for Configuration Management in Systems and Software Engineering. IEEE 982.1 IEEE Standard Measures of the Software Aspects of Dependability IEEE 1012 IEEE Standard for System, Software, and HardwareIEEE 1012-2012 IEEE Standard for Software Verification and Validation [2] ISO/IEC 12207, Systems and software engineering — Software life cycle processes [3] ISO/IEC/IEEE 29119-1, Software and systems engineering — Software testing — …IEEE 1012‐2004 • SRR/SDR IV&V findings • Mostly Requirements • Some Findings on – Architecture – Verification – CONOPS IEEE 1012-2004 Standard for Software Verification and Validation SLS Artif act #1 SLS Artif act #2 SLS Artif act #3 IV&V Pre-Rid & RID References 1. Overview 2. Referenced documents 3. Definitions 4. Software ...See other industries within the Manufacturing sector: Aerospace Product and Parts Manufacturing , Agriculture, Construction, and Mining Machinery Manufacturing , Alumina and Aluminum Production and Processing , Animal Food Manufacturing , Animal Slaughtering and Processing , Apparel Accessories and Other Apparel Manufacturing , Apparel Knitting Mills , Architectural and Structural Metals ...IEEE 1012-2016 This verification and validation (V&V) standard is a process standard that addresses all system, software, and hardware life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups.preclude using IEEE 1012 for V&V. IEEE 1012's recurring criticality analyses have no value for nuclear SR systems. State in the VVP that the system-of-interest is integrity level 4 throughout the project and, therefore, criticality analyses will not be repeated. IEEE 1012's security analyses are redundant to those performed to satisfy otherIEEE Std 1012- 201 6/Cor1 -2017) Authorized licensed use limited to: University of New Hampshire. Downloaded on April 08,2019 at 17:05:38 UTC from IEEE Xplore. Restrictions apply. IEEE Std 1012™-2016 (Revision of IEEE Std 1012-2012/ Incorporates IEEE Std 1012-2016/Cor1-2017) Ieee 1012, 13 Jun 2018 ... 3Institute of Electrical and Electronics Engineers, IEEE Standard for System and Software Verification and Validation,. IEEE Std. 1012-2012 (New ..., IEEE 1012 serves as a time-tested, widely accepted, and universally applicable process for ensuring that AI systems meet the required standards for their intended use. Policymakers can adopt this ..., IEEE 1012. IEEE Standard for Software Verification and Validation Plan 1986. 13. IEEE 828. IEEE Standard for Software Configuration Management Plans. 1983. 14. IEEE 1042. IEEE Guide to Software ..., Background to IEEE 829. IEEE 829-2008, also known as the 829 Standard for Software and System Test Documentation, was an IEEE standard that specified the form of a set of documents for use in eight defined stages of software testing and system testing, each stage potentially producing its own separate type of document., IEEE 1012 [1] describes the SDLC phase activities for software independent verification and validation (IV & V) for nuclear power plant in truly general and conceptual manner, which requires the upward and/or downward tailoring on its interpretation for practical IV & V. , IEEE 1012-1986 IEEE 1012-1998 Standard for Software Verification and Validation plans Standard for Software Verification and Validation 10 Recent Review Experience • Vendor LTR Submittal – Unendorsed Standards were used to qualify the safety system. DO – 254 (FAA standard) was used instead of IEEE 7-4.3.2 – License amendment ..., See other industries within the Manufacturing sector: Aerospace Product and Parts Manufacturing , Agriculture, Construction, and Mining Machinery Manufacturing , Alumina and Aluminum Production and Processing , Animal Food Manufacturing , Animal Slaughtering and Processing , Apparel Accessories and Other Apparel Manufacturing , Apparel Knitting Mills , Architectural and Structural Metals ..., IEEE 1012 standard [33]. Verification is addressed using . formal approaches with in software e ngineering in academia . but not widely used by practitioners, esp ecially in the ., 20 Agu 2021 ... Foundational standard ISO/IEC/IEEE 12207:2017, Software life cycle processes, and the widely used IEEE 1012, System, Software and Hardware ..., 2 Nov 2019 ... IEEE 1012- 2012 System and Software Verification & Validation; 확인과 검증(V&V)에 관한 표준., May 17, 2023 · (ieee 1012-2004, 3.1.36) (3b) Process of providing objective evidence that the software and its associated products comply with requirements for all life cycle activities during each life cycle process, satisfy standards, practices, and conventions during life cycle processes, and successfully complete each life cycle activity and satisfy all ... , Purpose: The purpose of this standard is to: - Establish a common framework of the V&V processes, activities, and tasks in support of all system, software, and hardware life …, 29 Sep 2017 ... This verification and validation (V&V) standard is a process standard that addresses all system, software, and hardware life cycle processes ..., (ieee 1012-2004, 3.1.36) (3b) Process of providing objective evidence that the software and its associated products comply with requirements for all life cycle activities during each life cycle process, satisfy standards, practices, and conventions during life cycle processes, and successfully complete each life cycle activity and satisfy all ..., The standard from IEEE Std 1012-2004 is recommended by regulatory guide 1.168 in 2013 about verification, validation, reviews, and audits for digital computer software used in safety systems of NPP. In despite of IEEE 1012 had the latest revision in IEEE Std 1012-2012, but in the traceability, The main body of the ISO/IEC/IEEE 12207‐2008 Standard and the IEEE 1012‐2012 are dedicated to a description of the processes, activities, and tasks of the software life cycle. The IEEE Standard 1012‐2012 is a process that defines all SQA activities throughout the entire software life cycle as V&V activities. , Again, IEEE 1012-2016 is a standard with a large scope. However, whether it's system, software, or hardware, or commonly a combination of these processes, the IEEE 1012-2016 V&V standard helps provide achievable goals for specific products. Remember "V&V reporting occurs throughout the system, software, or hardware life cycle.", Purpose: The purpose of this standard is to: - Establish a common framework of the V&V processes, activities, and tasks in support of all system, software, and hardware life …, The work described in this presentation is based on IEEE Standard 1012, which is developed by the IEEE P1012 Working Groupthat is chartered by the Software & Systems Engineering Standards Committee (C/S2ESC) of the IEEE Computer Society. The Working Group has voluntary participation by members of the systems and software engineering communities., Apr 6, 2022 · After the creation and application of the VVP for SAREL software, based on the IEEE 1012-2016/Cor 1-2017 standard, several V&V artifacts were obtained as a result. Compliance with the criteria that were evaluated in the software is evidenced, in addition a final report was created describing the results obtained. , Supersedes IEEE DRAFT 1012. (06/2005) Supersedes IEEE 1012A. (03/2006) 2016 version includes COR 1 2017. (10/2017) Document Type: Standard: ISBN: Pages: Published: Publisher: Institute of Electrical & Electronics Engineers : Status: Superseded: Superseded By: IEEE 1012 : 2016 ; Supersedes: IEEE DRAFT 1012 : 0 ; IEEE 1012A : 1998 ; IEEE 1012 : 2004, IEEE 1012 or the ESA’s standar d. They measure their robots against EN1525 (safety of industrial. driverless trucks and their systems), JIS D6802 (a Japanese standard on automatic guided vehicle., definitions may be found in IEEE Standard 1012-2012, or in NIST-SP 800-53A. Acquirer The acquirer is the entity or individual who specifies the requirements and accepts the resulting software products. The acquirer is usually NASA or an organization within the Agency but can also refer to the Prime contractor – subcontractor relationship …, 1012-2016 IEEE Standard for System, Software, and Hardware Verification and Validation. Verification and validation (V&V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs., IEEE 1394, commonly known as FireWire, is a standard connection type for many electronic devices such as digital video cameras, printers and scanners, external hard drives , and other peripherals. The terms IEEE 1394 and FireWire usually refer to the types of cables, ports, and connectors used to connect these types of external devices to ..., ieee ieee 1012-2004 1.168 ip-65001.10 ieee ieee 1016-1987 ip-52003 ieee ieee 1016-1998 ip-65001.10 ieee ieee 1023-1988 ieee ieee 1028 imc-1252 app b ieee ieee 1028-1988 ip-52003 ieee ieee 1028-1997 1.168,1.168 ip-65001.10 ieee ieee 1028-1997, ieee ieee 1028-2008 1.168 ieee ieee 1042-198, ANSI/IEEE 1012 provides uniform and minimum requirements for the format and content of software verification and validation plans. It defines minimum tasks, inputs, and outputs for critical software (software whose failure could have an impact on safety or could cause large financial or social losses) and, Within the next decades, robots will need to be able to execute a large variety of tasks autonomously in a large variety of environments. To relax the resulting programming effort, a knowledge-enabled approach to robot programming can be adopted to organize information in re-usable knowledge pieces., 1.168 was issued in 2004 and it endorsed IEEE 1012-1998. The current revision of RG 1.168 issued in 2013 endorses IEEE 1012-2004. Since that latest US NRC endorsement in 2013, IEEE 1012-2004 has been the industry benchmark for software verification and validation (V&V) activities. While draft version IEEE 1012-2016 is the latest , IEEE Std 1012-2004 IEEE Standard for Software Verification and Validation. Software verification and validation (V&V) processes determine whether the development products of a given activity conform to the requirements of that activity and whether the software satisfies its intended use and user needs. Software V&V life cycle process ..., Both IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997 place requirements on plans for verification of soft- ware and validation of software. The purpose of this annex is ..., IEEE develops its standards through an accredited consensus development process, which brings together volunteers representing varied viewpoints and interests to achieve the final product. IEEE Standards are documents developed by volunteers with scientific, academic, and industry-based expertise in technical working groups., IEEE Std 1012-1986 was a product standard that defined the contents of the Software Verification and Vali-dation Plan (SVVP). This revision of the standard, IEEE Std 1012-1998, is a process standard that defines the verification and validation processes in terms of specific activities and related tasks. IEEE Std 1012-1998