Software Engineering Standards Reference
Software engineering standards provide established best practices for development, quality assurance, and project management. Use this skill to properly reference standards and find the appropriate standard for your needs.
When to Use
- Citing standards in documentation or specifications
- Establishing organizational development processes
- Creating quality assurance plans
- Developing project management frameworks
- Writing requirements, design, or test documentation
Standard Naming Convention
Use this format when referencing IEEE, ISO, EIA, or IEC standards:
[Organization] Std [Number]-[Year], [Title]
Components:
- Organization: IEEE, ISO, EIA, IEC, or combination (e.g., IEEE/EIA)
- Number: Unique standard identifier (e.g., 830, 12207)
- Year: Year the standard was adopted (e.g., 1998, 2002)
- Title: Full descriptive title of the standard
Examples:
IEEE Std 830-1998, Recommended Practice for Software Requirements SpecificationsIEEE/EIA Std 12207-1997, Information Technology—Software Life Cycle ProcessesISO/IEC Std 12207, Information Technology—Software Life Cycle Processes
Top-Level Lifecycle Standard
ISO/IEC 12207 (Information Technology—Software Life Cycle Processes)
- Purpose: Defines the lifecycle framework for developing and managing software projects
- US Adoption: IEEE/EIA Std 12207
- Scope: Top-level standard covering the entire software development and management lifecycle
Finding the Right Standard
Standards are organized by domain and purpose. Consult the reference lists in references/standards-lists.md for:
- Development standards: Requirements, design, configuration management, user documentation, maintenance
- Quality assurance standards: QA plans, reviews, unit testing, test documentation, quality metrics
- Management standards: Project management, lifecycle processes, productivity metrics, acquisition, risk management
Usage Guidelines
- Identify your domain: Determine whether you need development, QA, or management standards
- Find the specific standard: Use the categorized lists to locate the standard matching your activity
- Apply the naming convention: Reference standards using the proper format
- Check for updates: Verify you are using the current version of the standard
1---2name: software-engineering-standards-reference3description: Use this skill when you need to reference, cite, or apply software engineering standards. This skill provides the IEEE/ISO standard naming convention and categorized lists of standards for software development, quality assurance, and project management.4---5
6# Software Engineering Standards Reference
7
8Software engineering standards provide established best practices for development, quality assurance, and project management. Use this skill to properly reference standards and find the appropriate standard for your needs.
9
10## When to Use
11
12- Citing standards in documentation or specifications
13- Establishing organizational development processes
14- Creating quality assurance plans
15- Developing project management frameworks
16- Writing requirements, design, or test documentation
17
18## Standard Naming Convention
19
20Use this format when referencing IEEE, ISO, EIA, or IEC standards:
21
22```
23[Organization] Std [Number]-[Year], [Title]
24```
25
26**Components**:
27- **Organization**: IEEE, ISO, EIA, IEC, or combination (e.g., IEEE/EIA)
28- **Number**: Unique standard identifier (e.g., 830, 12207)
29- **Year**: Year the standard was adopted (e.g., 1998, 2002)
30- **Title**: Full descriptive title of the standard
31
32**Examples**:
33- `IEEE Std 830-1998, Recommended Practice for Software Requirements Specifications`
34- `IEEE/EIA Std 12207-1997, Information Technology—Software Life Cycle Processes`
35- `ISO/IEC Std 12207, Information Technology—Software Life Cycle Processes`
36
37## Top-Level Lifecycle Standard
38
39**ISO/IEC 12207** (Information Technology—Software Life Cycle Processes)
40
41- **Purpose**: Defines the lifecycle framework for developing and managing software projects
42- **US Adoption**: IEEE/EIA Std 12207
43- **Scope**: Top-level standard covering the entire software development and management lifecycle
44
45## Finding the Right Standard
46
47Standards are organized by domain and purpose. Consult the reference lists in `references/standards-lists.md` for:
48
49- **Development standards**: Requirements, design, configuration management, user documentation, maintenance
50- **Quality assurance standards**: QA plans, reviews, unit testing, test documentation, quality metrics
51- **Management standards**: Project management, lifecycle processes, productivity metrics, acquisition, risk management
52
53## Usage Guidelines
54
551. **Identify your domain**: Determine whether you need development, QA, or management standards
562. **Find the specific standard**: Use the categorized lists to locate the standard matching your activity
573. **Apply the naming convention**: Reference standards using the proper format
584. **Check for updates**: Verify you are using the current version of the standard
majiayu000