Scribd
Upload
50 views

Structure & Content of Software Engineering Standards-1

The document discusses the structure and content of software engineering standards. It describes how standards establish technical requirements and guidelines for software development processes. Standards cover the entire software lifecycle, including processes for description, verification, and validation. IEEE standards are categorized into conceptual, prescriptive, and guidance standards. Conceptual standards provide principles and approaches, prescriptive standards establish requirements for developers, and guidance standards apply to implementing prescriptive standards. The purpose of standards is to promote common processes, traceability, and software quality.

Uploaded by

Rehan Ejaz
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
50 views

Structure & Content of Software Engineering Standards-1

The document discusses the structure and content of software engineering standards. It describes how standards establish technical requirements and guidelines for software development processes. Standards cover the entire software lifecycle, including processes for description, verification, and validation. IEEE standards are categorized into conceptual, prescriptive, and guidance standards. Conceptual standards provide principles and approaches, prescriptive standards establish requirements for developers, and guidance standards apply to implementing prescriptive standards. The purpose of standards is to promote common processes, traceability, and software quality.

Uploaded by

Rehan Ejaz
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

STRUCTURE & CONTENT OF

SOFTWARE ENGINEERING
STANDARDS

BY REHAN AHMAD AND SYED IJTABA AHSAN NAQVI


STANDARDS IN SOFTWARE ENGINEERING

• Standard - A standard is a technical publication created to ensure the reliability of the
materials, products, methods, and/or services.
• They establish the technical requirements, specifications, guidelines, characteristics,
and/or procedures designed.
CONTENT OF SOFTWARE ENGINEERING
STANDARDS
• Content engineering is the practice of organizing the shape, structure, and application
of content.
• The standard’s contents reflect the processes that appear throughout the software’s life
cycle:
• Description of the primary life cycle processes
• Definitions of supporting life cycle processes
• Definitions of organizational life cycle processes
• V&V activities include verification and validation IEEE 1012
CLASSES OF IEEE STANDARDS

• IEEE standards may be allocated to three main classes:


• Conceptual Standards
• Prescriptive Standards of Conformance
• Guidance Standards
CONCEPTUAL STANDARDS

• Guiding principles and overall approach are as follow


• IEEE 610.12 – Glossary of Software Engineering Terminology
• IEEE 1061 – Software Quality Metrics Methodology
• IEEE 1320.2 – Conceptual Modeling Language, Syntax and Semantics for IDEF1X97
• IEEE/EIA 12207.0 – Information Technology Software Life Cycle Processes.
PRESCRIPTIVE STANDARDS OF CONFORMANCE

• These standards address the requirements to which a software developer must conform.
A major portion of the standards collection belongs to this class. Examples:
• IEEE 828 – Software Configuration Plans
• IEEE 829 – Software Test Documentation
• IEEE 1012 – Software Verification and Validation
• IEEE 1028 – Software Reviews
GUIDANCE STANDARDS

• These apply mainly to implementation of Class B (Non-Serious Injury is Possible) standard


conformance requirements. Examples:
• IEEE 1233 : Guide for Developing System Requirement Specifications
• IEEE/EIA 12207.1– Guide, Information Technology , Software Life Cycle Processes – Life Cycle
Data
PURPOSE OF IEEE STANDARDS

• To establish an internationally recognized model of common software life cycle processes


that can be referenced by the software industry worldwide.
• To promote understanding among business parties by processes, activities and tasks.
• Establish a common framework for traceability activities and tasks for all software life
cycle processes
•  Define software integrity levels and the appropriate tasks (Standards for Verification and
Validation)
PURPOSE OF IEEE CONTENT

• Purpose The purposes of IEEE 1012-1998 are:


• To establish a common framework for V&V activities and tasks for all software life cycle
processes, eliminating defects from software artifacts across the software lifecycle.
• To define Verification and validation requirements, including their inputs and outputs
• To define software integrity levels , risk ,security levels, desired performance ,reliability.
CONCLUSION

• Standards form the fundamental building blocks for product development by establishing


consistent protocols that can be universally understood and adopted in software
development industry. This helps fuel compatibility and interoperability and simplifies
product development, and speeds time-to-market. Standards enable each member of a
software team to work anywhere in the source code without needing to recognize and
adopt a different programming style

You might also like