IEEE标准的种类以及软件工程包含的标准

最新推荐文章于 2023-09-04 11:11:40 发布
最新推荐文章于 2023-09-04 11:11:40 发布
阅读量7k 收藏 2
点赞数
分类专栏： 软件工程方法 文章标签： classification validation library generation application basic
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/teamlet/article/details/2210949
版权

一、IEEE标准的种类列表

▲ Aerospace and Electronic Systems
▲ Antennas and Propagation
▲ Automatic Meter Reading and Energy Management
▲ Bus Architecture
▲ Cement Industry
▲ Circuits and Systems
▲ Color Book Series
▲ Communication
▲ Computer Simulation
▲ Design Automation
▲ Dielectrics and Electrical Insulation
▲ Electric Machinery
▲ Electrical Insulation
▲ Electro-Magnetic Compatibility
▲ Electron Devices
▲ Graphic Symbols, Designations and Units
▲ Industrial and Commercial Facilities
▲ Instrumentation and Measurement
▲ Insulated Conductors
▲ Insulation Coordination
▲ Intelligent Transportation
▲ LAN/MAN (802)
▲ Medical Devices
▲ Nuclear Engineering
▲ Petroleum and Chemical
▲ Pole Line Hardware
▲ Portable Applications (POSIX)
▲ Power Electronics
▲ Power Generation
▲ Power Systems Communications
▲ Power, Distribution and Regulating Transformers
▲ Protective Relaying
▲ Reliability
▲ Roadway Lighting
▲ Software Engineering
▲ Static Power Converter
▲ Storage Systems
▲ Substations
▲ Surge Protective Devices
▲ Switchgear
▲ Test Technology
▲ Test and Diagnosis for Electric Systems
▲ Transmission and Distribution
▲ Ultrasonics, Ferroelectrics, and Frequency Control
▲ Vehicular Technology 

二、 软件工程类别

▲ IEEE Std 1012-1998 IEEE Standard for Software Verification and Validation
▲ IEEE Std 1012-1998 aSupplement to IEEE Standard for Software Verification and Validation: Content Map to IEEE/EIA 12207.1-1997
▲ IEEE Std 1016-1998 IEEE Recommended Practice for Software Design Descriptions
▲ IEEE Std 1028-1997 IEEE Standard for Software Reviews
▲ IEEE Std 1044.1-1995 IEEE Guide to Classification for Software Anomalies
▲ IEEE Std 1058-1998 IEEE Standard for Software Project Management Plans
▲ IEEE Std 1061-1998 IEEE Standard for a Software Quality Metrics Methodology
▲ IEEE Std 1062, 1998 and 1062-1993 and 1062-1998 aIEEE Recommended Practice for Software Acquisition
▲ IEEE Std 1220-1998 IEEE Standard for Application and Management of the Systems Engineering Process
▲ IEEE/EIA 12207.0-1996 IEEE/EIA Standard Industry Implementation of International Standard ISO/IEC12207:1995 and (ISO/IEC 12207) Standard for Information Technology—Software life cycle processes
▲ IEEE Std 12207.1-1997 IEEEsol;EIA Guide for Information Technology Software life cycle processes—Life cycle data
▲ IEEE/EIA12207.2-1997 IEEE/EIA Guide Software life cycle processes—Implementation considerations
▲ IEEE Std 1233, 1998 and 1233-1996 aIEEE Guide for Developing System Requirements Specifications
▲ IEEE Std 1320.1-1998 IEEE Standard for Functional Modeling Language—Syntax and Semantics for IDEF0
▲ IEEE Std 1320.2-1998 IEEE Standard for Conceptual Modeling Language Syntax and Semantics for IDEF1X97(IDEFobject)
▲ IEEE Std 1348-1995 IEEE Recommended Practice for the Adoption of Computer-Aided Software Engineering (CASE) Tools
▲ IEEE Std 1362-1998 IEEE Guide for Information Technology—System Definition—Concept of Operations (ConOps) Document
▲ IEEE Std 1420.1-1995 IEEE Standard for Information Technology—Software Reuse— Data Model for Reuse Library Interoperability: Basic Interoperability Data Model (BIDM)
▲ IEEE Std 1420.1b-1999 IEEE Trial-Use Supplement to IEEE Standard for Information Technology—Software Reuse—Data Model for Reuse Library Interoperability:Intellectual Property Rights Framework
▲ IEEE Std 1471-2000 IEEE Recommended Practice for Architectural Description of Software-Intensive Systems
▲ IEEE Std 1540-2001 IEEE Standard for Software Life Cycle Processes—Risk Management
▲ IEEE Std 730-1998 IEEE Standard for Software Quality Assurance Plans
▲ IEEE Std 730.1-1995 IEEE Guide for Software Quality Assurance Planning
▲ IEEE Std 828-1998 IEEE Standard for Software Configuration Management Plans
▲ IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications

teamlet
关注
专栏目录
关于软件架构设计的核心思想与标准 ( IEEE 1471 2000 )
程序员光剑
04-08 9846
What Is Architecture?软件系统的架构是一个隐喻，类似于建筑物的架构。存在着一个极为重要的特质，它是人、城市、建筑或荒野的生命与精神的根本准则。这种特质客观明确，但却无法命名。( C·亚历山大《The Timeless Way of Building》)架构（Architecture）这个词来源于建筑学。IT这个行业中的词汇许多都来源于传统行业。传统行业......
IEEE软件工程标准.pdf
09-30
IEEE软件工程标准.pdf
IEEE 软件工程相关的标准名称
LongAway 的 CyberLog
09-01 3460
列表截至 2006 年中。最近在参与过程度量的东西。搜集了些资料。 Standard Number Standard Name IEEE Std 610.12-1990 (Sep 28)Reaffirmed Sept 2002
IEEE软件工程标准词汇表定义需求
qq_34859668的博客
02-06 2695
1. 用户解决问题或达到目标所需的条件或能力。 2. 系统或系统部件要满足合同、标准、规范或其它正式规定文档所需具有的条件或能力。              一种反映上面(1)或(2)所描述的条件或能力的文档说明。
IEEE-CS和ACM通过软件工程职业道德规范
05-22
IEEE发布的有关软件工程职业道德规范的文献，值得一看！
ISO/IEC/IEEEE 测试和软件质量有关的标准
最新发布
seanyang_的博客
09-04 2135
5. ISO/IEC/IEEE 15288: 系统和软件工程生命周期过程：这个标准定义了系统和软件工程的生命周期过程，包括规划、需求定义、设计、开发、测试和维护等。6. ISO/IEC/IEEE 29119: 软件和系统工程测试：这个标准是 ISO/IEC 29119 的扩展，定义了软件和系统工程测试的一套过程和方法。2. IEEE 829: 软件和系统文档标准：这个标准定义了软件和系统文档的格式、内容和组织，包括需求规格、设计文档、测试文档和用户手册等。
现行ISOIEC软件工程国际标准
04-22
在软件工程领域中，ISO/IEC制定了一系列标准以规范软件开发过程、软件产品的质量以及相关的技术和管理活动。 ISO/IEC 9126是ISO/IEC 9126软件工程产品质量国际标准的旧版，它被ISO/IEC 25010所取代。这个标准将软件...
2022年软件工程标准的定义与层次(共72张PPT).pptx
11-14
国家标准，如中国的GB/T 15538-1995，提供了软件工程标准的分类框架，指导不同类型的文档编制和管理。此外，还有针对特定领域的专业标准，如编程语言的标准和软件配置管理的规定，如GB/T 12505-90。 软件工程标准...
第章软件过程标准化与工程化ppt课件.ppt
11-13
软件工程标准定义了一套协调不同开发阶段和组件的规则和规定，旨在提高产品质量，提升技术水平，规范管理，提高效率，以及降低成本。中国的软件标准分为基础标准、开发标准、文档标准和管理标准等几大类，同时也有...
IEEE的文章的分类
04-23
IEEE的文章的分类,详细介绍了IEEE文章的分类与用途等信息
IEEE Std 1012-2012 系统、软件测试与验证标准
11-07
IEEE Standard for System and Software Verification and Validation IEEE Std 1012-2012 Front Cover -14 Title Page -12 Notice to users -9 Laws and regulations -9 Copyrights -9 Updating of IEEE documents -9 Errata -9 Patents -8 Participants -7 Introduction -5 Contents -3 Important notice 1 1. Overview 1 1.1 Scope 1 1.2 Purpose 2 1.3 Field of application 3 1.4 V&V objectives 4 1.5 Organization of the standard 4 1.6 Audience 6 1.7 Conformance 7 1.8 Disclaimer 7 2. Normative references 7 3. Definitions, abbreviations, and acronyms 7 3.1 Definitions 7 3.2 Abbreviations and acronyms 11 4. Relationships between V&V and life cycle processes 12 5. Integrity levels 15 6. V&V processes overview 17 6.1 General 17 6.2 V&V testing 18 7. Common V&V activities 19 7.1 Activity: V&V Management 19 7.2 Activity: Acquisition Support V&V 20 7.3 Activity: Supply Planning V&V 21 7.4 Activity: Project Planning V&V 21 7.5 Activity: Configuration Management V&V 21 8. System V&V activities 33 8.1 Activity: Stakeholder Requirements Definition V&V 33 The purpose of the Stakeholder Requirements Definition Process is to define the requirements for a system that can provide the services needed by users and other stakeholders in a defined environment. It identifies stakeholders, or stakeholder classes... 33 The V&V effort shall perform, as specified in Table 2b for the selected integrity level, the following Stakeholder Requirements Definition V&V tasks described in Table 1b: 33 8.2 Activity: Requirements Analysis V&V 33 8.3 Activity: Architectural Design V&V 34 8.4 Activity: Implementation V&V 35 8.5 Activity: Integration V&V 35 8.6 Activity: Transition V&V 36 8.7 Activity: Operation V&V 36 8.8 Activity: Maintenance V&V 37 8.9 Activity: Disposal V&V 38 9. Software V&V activities 68 9.1 Activity: Software Concept V&V 68 9.2 Activity: Software Requirements V&V 68 9.3 Activity: Software Design V&V 69 9.4 Activity: Software Construction V&V 69 9.5 Activity: Software Integration Test V&V 70 9.6 Activity: Software Qualification Test V&V 70 9.7 Activity: Software Acceptance Test V&V 71 9.8 Activity: Software Installation and Checkout V&V 71 9.9 Activity: Software Operation V&V 72 9.10 Activity: Software Maintenance V&V 72 9.11 Activity: Software Disposal V&V 73 10. Hardware V&V activities 110 10.1 Activity: Hardware Concept V&V 110 10.2 Activity: Hardware Requirements V&V 110 10.3 Activity: Hardware Design V&V 111 10.4 Activity: Hardware Fabrication V&V 111 10.5 Activity: Hardware Integration Test V&V 112 10.6 Activity: Hardware Qualification Test V&V 112 10.7 Activity: Hardware Acceptance Test V&V 113 10.8 Activity: Hardware Transition V&V 113 10.9 Activity: Hardware Operation V&V 114 10.10 Activity: Hardware Maintenance V&V 114 10.11 Activity: Hardware Disposal V&V 115 11. V&V reporting, administrative, and documentation requirements 147 11.1 V&V reporting requirements 147 11.2 V&V administrative requirements 150 11.3 V&V documentation requirements 150 12. V&V plan outline 151 12.1 Overview 151 12.2 VVP Section 1: Purpose 152 12.3 VVP Section 2: Referenced documents 152 12.4 VVP Section 3: Definitions 152 12.5 VVP Section 4: V&V overview 152 12.5.1 VVP Section 4.1: Organization 152 12.5.2 VVP Section 4.2: Master schedule 153 12.5.3 VVP Section 4.3: Integrity level scheme 153 12.5.4 VVP Section 4.4: Resources summary 153 12.5.5 VVP Section 4.5: Responsibilities 153 12.5.6 VVP Section 4.6: Tools, techniques, and methods 153 12.6 VVP Section 5: V&V processes 154 12.6.1 VVP Section 5.1: Common V&V Processes, Activities, and Tasks 154 12.6.2 VVP Section 5.2: System V&V Processes, Activities, and Tasks 154 12.6.3 VVP Section 5.3: Software V&V Processes, Activities, and Tasks 154 12.6.4 VVP Section 5.4: Hardware V&V Processes, Activities, and Tasks 154 12.7 VVP Section 6: V&V reporting requirements 154 12.8 VVP Section 7: V&V administrative requirements 154 12.8.1 General 154 12.8.2 VVP Section 7.1: Anomaly resolution and reporting 154 12.8.3 VVP Section 7.2: Task iteration policy 154 12.8.4 VVP Section 7.3: Deviation policy 155 12.8.5 VVP Section 7.4: Control procedures 155 12.8.6 VVP Section 7.5: Standards, practices, and conventions 155 12.9 VVP Section 8: V&V test documentation requirements 155 Annex A (informative) Mapping of IEEE 1012 V&V activities and tasks 156 A.1 Mapping of ISO/IEC 15288 V&V requirements to IEEE 1012 V&V activities and tasks 156 A.2 Mapping of IEEE 1012 V&V activities to ISO/IEC 15288 system life cycle processes and activities 158 A.3 Mapping of ISO/IEC 12207 V&V requirements to IEEE 1012 V&V activities and tasks 159 A.4 Mapping of IEEE 1012 V&V activities to IEEE 12207 software life cycle processes and activities 161 Annex B (informative) A risk-based, integrity-level scheme 163 Annex C (informative) Definition of independent V&V (IV&V) 165 C.1 Technical independence 165 C.2 Managerial independence 165 C.3 Financial independence 165 C.4 Forms of independence 165 C.4.1 Classical IV&V 166 C.4.2 Modified IV&V 166 C.4.3 Integrated IV&V 166 C.4.4 Internal IV&V 166 C.4.5 Embedded V&V 167 Annex D (informative) V&V of reuse software 168 D.1 Purpose 168 D.2 V&V of software developed in a reuse process 169 D.2.1 V&V of assets in development 169 D.2.2 V&V of reused assets 169 D.3 V&V of software developed and reused outside of a reuse process 169 Annex E (informative) V&V measures 175 E.1 Introduction 175 E.2 Measures for evaluating anomaly density 175 E.3 Measures for evaluating V&V effectiveness 176 E.4 Measures for evaluating V&V efficiency 176 Annex F (informative) Example of V&V relationships to other project responsibilities 178 Annex G (informative) Optional V&V tasks 179 Annex H (informative) Environmental factors considerations 185 H.1 Introduction 185 H.2 In the agreement processes 185 H.3 In the organizational project-enabling processes 185 H.4 In the project processes 186 H.5 In the technical processes 186 Annex I (informative) V&V of system, software, and hardware integration 188 I.1 Introduction 188 I.2 Examples of system failures caused by integration issues 188 I.2.1 Year 2000 System Integration Issue 189 I.2.2 System architecture integration issues 189 I.3 System, software, and hardware interaction issues 190 Annex J (informative) Hazard, security, and risk analyses 193 J.1 Hazard analysis 193 Annex K (informative) Example of assigning and changing the system integrity level of “supporting system functions” 198 Annex L (informative) Mapping of ISO/IEC/IEEE 15288 and IEEE 12207 process outcomes to V&V tasks 200 Annex M (informative) Bibliography 209
IEEE Std 730-1989 IEEE Standard for Software Quality Assurance Plans
10-29
IEEE Std 730-1989 IEEE Standard for Software Quality Assurance Plans
IEEE 1012-2012
09-26
最新版的IEEE1012 ，目前国内从事软件质量相对权威的标准，尤其是核电行业，审查机构的工作依据。从生命周期的角度较为详细的说明了软件质量验证和确认过程
IEEE Std 1012-2004 IEEE Standard for Software Verificiation and Validation
01-06
IEEE标准，适用与软件开发，供大家学习参考。
IEEE Std-1012 System, Software, IV&V
05-20
IEEE Std-1012 System, Software, IV&V
测试二、 测试模型
object_oriented_uy的博客
03-08 503
V模型: 需求分析: 用户需求、业务需求、需求规格说明书 概要设计: 系统架构、模块划分、模块与模块之间的接口 详细设计: 模块内部实现的逻辑和方法 编 码: 实现上面的设计 单元测试: 检测代码的开发是否符合详细设计的要求。 集成测试: 检测此前测试过的各组成部分是否能完好地结合到一起。系统测试: 检测已集成在一起的产品是否符合系统规格说明书的要求。验收...
IEEE Std 1016-1998《软件设计描述IEEE推荐实践》阅读摘要
老好人(廖海仁）的专栏
09-17 3011
Normal 0 7.8 磅 0 2 false false false MicrosoftInternetExplorer4 <object classid
软件评审讲座讲义
老吴的红茶馆
09-02 1467
软件评审讲座讲义（PDF格式的幻灯片，63K）作者：PMT 左礁来源于：http://www.pmtsolution.net/forums/pmtforum004-20020512.pdf 评审的定义Review (IEEE Std 1028-1988) is an evaluation of software element or project status to asce
IEEE浮点标准详解
热门推荐
sinat_33248998的博客
07-05 1万+
1 IEEE浮点数 1.1 格式 IEEE定义了多种浮点格式，但最常见的是三种类型：单精度、双精度、扩展双精度，分别适用于不同的计算要求。一般而言，单精度适合一般计算，双精度适合科学计算，扩展双精度适合高精度计算。一个遵循IEEE 754标准的系统必须支持单精度类型（强制类型）、最好也支持双精度类型（推荐类型），至于扩展双精度类型可以随意。   长度
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值