Software Engineering: Introduction to Software Engineering Topics

- Introduction to Software Engineering

**Mathematical Foundation

**Computing Foundation

**Engineering Foundation

**Software Engineering Process

**Software Engineering Models and Methods

Software Verification and Validation in Airborne Systems in DO-178C

In the ever-evolving world of aviation, where safety is paramount, the role of software in airborne systems cannot be overstated. Ensuring that the software in aircraft and related equipment operates with absolute reliability and safety is a monumental challenge. It is precisely this challenge that the DO-178C standard, also known as “Software Considerations in Airborne Systems and Equipment Certification,” seeks to address. Representing the latest evolution in a series of standards, DO-178C provides a comprehensive framework for the development, certification, and maintenance of safety-critical software in the aerospace industry

Software development process in DO-178C

The software development process in DO-178C is a crucial component of the standard, as it provides a systematic approach to developing safety-critical software for use in airborne systems. The process follows a structured and rigorous methodology to ensure the airworthiness and safety of the software. Here are the key steps and activities involved in the software development process of DO-178C:

1. Planning (Software Development Plan – SDP):

The process begins with the creation of a Software Development Plan (SDP). The SDP outlines the overall approach to software development, including objectives, criticality levels, and development and verification strategies. It defines the scope of the software development effort and serves as a roadmap for the project.

2. Requirements Analysis (Software Requirements – SRD):

In this phase, software engineers analyze and establish software requirements based on system-level requirements and safety objectives. These requirements are documented in the Software Requirements Data (SRD) and serve as the foundation for subsequent design and development activities.

3. High-Level Design (Software Design Description – SDD):

The high-level design phase involves creating a Software Design Description (SDD) that defines the overall architecture and structure of the software. It identifies software components, interfaces, and data flows. The SDD ensures that the software design aligns with the specified requirements.

4. Low-Level Design (Software Design Description – SDD):

Building upon the high-level design, software engineers create detailed Low-Level Design (LLD) documentation. The LLD specifies how each software component is implemented, including algorithms, data structures, and coding standards.

5. Implementation (Source Code):

In this phase, developers write the actual source code for the software. The code must adhere to the Low-Level Design (LLD) documentation and coding standards. Comprehensive documentation of the code is essential for traceability.

6. Verification and Testing:

Verification activities include unit testing, integration testing, and system testing. These tests are designed to verify that the software components operate as intended and meet their specified requirements. Test cases are developed based on the Software Verification Plan (SVP).

7. Traceability:

Throughout the development process, traceability ensures that every requirement, design element, and line of code is traceable back to specific software and system requirements. This ensures consistency and alignment with higher-level objectives.

8. Documentation:

Comprehensive documentation is a fundamental requirement in DO-178C. Each phase of development, including requirements, design, code, and testing, requires detailed documentation. This documentation is essential for certification and auditing purposes.

9. Configuration Management:

Software Configuration Management (SCM) processes are employed to control and manage changes to software configuration items (SCIs) throughout the development lifecycle. This ensures version control and traceability of changes.

10. Change Control:

Changes to software requirements, design, or code must be carefully controlled and documented. The impact of changes on safety and certification objectives is assessed, and appropriate actions are taken to maintain airworthiness.

11. Tool Qualification:

If software development tools are used, they must undergo a tool qualification process to ensure their reliability and suitability for the development process.

12. Safety Assessment:

A safety assessment is performed to evaluate the software’s safety-critical aspects, including potential hazards, risk mitigation measures, and safety objectives. This assessment informs safety certification efforts.

13. Certification:

The final step in the process is the certification of the software by the appropriate certification authority (CA), such as the Federal Aviation Administration (FAA) in the United States or the European Union Aviation Safety Agency (EASA) in Europe. The CA reviews all documentation, test results, and safety assessments to determine if the software is airworthy and safe for use in airborne systems.

Verification and Validation in DO-178C

Verification and validation (V&V) are critical processes in DO-178C (Software Considerations in Airborne Systems and Equipment Certification) that ensure the safety and airworthiness of software used in airborne systems, including aircraft and related equipment. These processes are designed to confirm that the software performs its intended functions correctly and reliably. Here’s an explanation of verification and validation in DO-178C:

Verification:

Verification in DO-178C focuses on confirming that the software has been correctly developed. It involves checking whether the software has been designed, coded, and integrated in accordance with the specified requirements and standards. The primary goal of verification is to ensure that each software component meets its intended functionality, is free from defects, and operates as expected. Key aspects of verification in DO-178C include:

1. Unit Testing: Developers perform unit testing to validate individual software components (such as modules or functions) in isolation. This ensures that each component operates correctly and conforms to the design and requirements.

2. Integration Testing: Integration testing involves verifying the interactions between software components and their interfaces. It ensures that integrated components work together seamlessly and meet their specified functions.

3. System Testing: System testing evaluates the entire software system in its operational environment. It assesses the system’s behavior under various conditions and scenarios, including both normal and abnormal situations.

4. Requirements Traceability: Verification activities should be traceable to the software requirements. This means that each test case or verification activity should be linked back to specific software requirements, ensuring that all requirements are verified.

5. Structural Coverage Analysis: DO-178C mandates structural coverage analysis, which assesses the completeness of testing by measuring code coverage (e.g., statement coverage, branch coverage). High levels of code coverage are required for critical software.

6. Code Reviews and Inspections: Formal code reviews and inspections are conducted to identify defects and ensure that coding standards and guidelines are followed.

7. Documentation: Comprehensive documentation of verification activities, test cases, results, and traceability is essential for demonstrating compliance with DO-178C requirements.

Validation:

Validation in DO-178C focuses on confirming that the software meets its intended functionality and performance objectives within the context of the entire aircraft system. It ensures that the software operates correctly when integrated into the aircraft and interacts with other system components. Key aspects of validation in DO-178C include:

1. System Integration Testing: Validation activities involve testing the software within the aircraft’s integrated environment, considering the interaction between software and hardware components, as well as external factors.

2. Real-World Scenarios: Validation testing includes real-world scenarios, such as flight simulations, to assess the software’s behavior under actual operating conditions.

3. Safety Assessment: A safety assessment is performed as part of the validation process to evaluate potential hazards and risks associated with the software. Mitigation measures are identified and implemented to ensure safety.

4. Environmental Testing: Validation may include environmental testing to assess how the software performs under extreme conditions, such as temperature variations, electromagnetic interference, and vibration.

5. Performance Testing: Validation verifies that the software meets its performance requirements, such as response times, throughput, and data accuracy.

6. User Acceptance Testing: In some cases, user acceptance testing involves feedback from pilots, operators, or other end-users to validate that the software meets their needs and expectations.

Both verification and validation are essential for ensuring that software in airborne systems is safe, reliable, and compliant with DO-178C standards. These processes contribute to the overall airworthiness of the aircraft and help mitigate risks associated with software failures in critical aviation applications.

This Blog Part taken from Visure Blog "DO-178C Risk Management for Airborne Systems and Equipment"

Safety-critical systems

A safety-critical system or safety-involved system is one whose failure may cause death or injury to people, harm to the environment, or substantial economic loss. such as aviation, railway, and automotive, such systems are typically subject to a rigorous safety assessment process.

Examples of safety-critical systems

• Aerospace, Spaceflight Systems
• Defense Systems
• Aviation, Airborne  Systems
• Automotive, Vehicles Systems
• Railways Systems
• Energy,  Nuclear, Oil and Gas Production Systems
• Medical Devices, Life support  Systems
• Manufacturing, Industry Infrastructure, machinery Systems

Some of Standards for safety-critical systems used as reference in Software Quality Engineering and Testing:

• IEC 61508: Functional Safety of Electrical/Electronic/Programmable Electronic Safety-related Systems
• DO-178C: Software Considerations in Airborne Systems and Equipment Certification
• ISO 26262: Road vehicles — Functional safety
• IEC 62279: Railway applications - Communication, signalling and processing systems - Software for railway control and protection systems
• IEC 61513: Nuclear power plants - Instrumentation and control Systems important to safety
• IEC 62304: Medical device software — Software life cycle processes
• IEC 61511: Safety instrumented systems for the process industry sector
• IEC 62061: Safety of machinery - Functional safety of safety-related control systems

Software Engineering: Software Testing and Quality Engineering Topics

- Software Testing

 **Software Testing Fundamentals

 **Test Levels

 **Test Techniques

 **Test Process

 **Test-Related Measures

- Software Quality

**Software Quality Fundamentals

**Software Quality Management Process

**Software Quality Assurance Process

Computer Minors/Specializations

Each of the following Specializations contains one or more professional Specializations/Tracks inside, For example Software Engineering include software development, business analysis, software quality engineering and so on.

Computer Minors/Specializations: 

* Software Engineering

* Computer Networks

* Data Science

        * Information&Cyber Security

        * AI and Machine Learning

* Robotics

* Embedded Systems

* Cloud Computing

* Internet of Things(IoT)

* Computer Support

* Computer Research

* Computer Hardware

* Graphic Design

Software Engineering Certifications

Software Engineering Certifications in the areas of Software Development, Software Testing and Quality Engineering: 

C++ Institute

        * CPA – C++ Certified Associate Programmer Certification

        * CPP – C++ Certified Professional Programmer Certification

Oracle Certifications

        * OCP Java SE Programmer

        * Jave EE Application Developer

Python Institute

        * PCAP: Certified Associate Python Programmer (PCAP)

        * PCPP: Certified Professional Python Programmer (PCPP)

Microsoft Certifications

* MC: Azure Fundamentals

* MCA: Azure Developer Associate

        * MCE: Azure Solutions Architect Expert

* MCE: DevOps Engineer Expert

Amazon Certifications

* AWS Cloud Practitioner

* AWS Developer Associate

        * AWS Solutions Architect Professional

* AWS DevOps Engineer Professional

Google Certifications

* Foundational Cloud Digital Leader

* Professional Cloud Developer

        * Professional Cloud Architect

        * Professional Cloud DevOps Engineer

ISTQB Certifications

* CTFL: Certified Tester Foundation Level

        * CTAL-TA: Certified Tester Advanced Level Test Analyst

* CTAL-TAA: Certified Tester Advanced Level Technical Test Analyst

* CTAL-TAE: Certified Tester Advanced Level Test Automation Engineering

American Society for Quality (ASQ)

        * Software Quality Engineer (CSQE)

CompTIA Certifications

* CompTIA ITF+: IT Fundamentals

* CompTIA A+: Foundational IT Skills

Foundational C# with Microsoft

Course 01: Write Your First Code Using C#

learning to write your first code using C#. Develop a strong foundation as you explore the fundamentals and syntax of the language, setting the stage for your programming adventures.

• Write Your First C# Code
• Store and Retrieve Data Using Literal and Variable Values in C#
• Perform Basic String Formatting in C#
• Perform Basic Operations on Numbers in C#
• Guided Project - Calculate and Print Student Grades
• Guided Project - Calculate Final GPA

Course 02: Create and Run Simple C# Console Applications

Master the art of creating and running simple C# console applications. Dive into the world of console-based programming, where you will gain hands-on experience executing your code and seeing it in action.

• Install and Configure Visual Studio Code
• Call Methods From the .NET Class Library Using C#
• Add Decision Logic to Your Code Using if, else, and else if statements in C#
• Store and Iterate Through Sequences of Data Using Arrays and the foreach Statement in C#
• Create Readable Code with Conventions, Whitespace, and Comments in C#
• Guided Project - Develop foreach and if-elseif-else Structures to Process Array Data in C#
• Challenge Project - Develop foreach and if-elseif-else Structures to Process Array Data in C#

Course 03: Add Logic to C# Console Applications

Unlock the power of logic in C# console applications. Learn how to add logic and decision-making capabilities to your code, enabling your applications to make dynamic choices and respond intelligently to different scenarios.

• Evaluate Boolean Expressions to Make Decisions in C#
• Control Variable Scope and Logic Using Code Blocks in C#
• Branch the Flow of Code Using the switch-case Construct in C#
• Iterate Through a Code Block Using the for Statement in C#
• Add Looping Logic to Your Code Using the do-while and while Statements in C#
• Guided Project - Develop Conditional Branching and Looping Structures in C#
• Challenge Project - Develop Branching and Looping Structures in C#

Course 04: Work with Variable Data in C# Console Applications

Discover the versatility of variable data in C# console applications. Harness the ability to store and manipulate different types of data, such as numbers and text, as you delve into the essential concepts of variables and data handling.

• Choose the Correct Data Type in Your C# Code
• Convert Data Types Using Casting and Conversion Techniques in C#
• Perform Operations on Arrays Using Helper Methods in C#
• Format Alphanumeric Data for Presentation in C#
• Modify the Content of Strings Using Built-In String Data Type Methods in C#
• Guided Project - Work with Variable Data in C#
• Challenge Project - Work with Variable Data in C#

Course 05: Create Methods in C# Console Applications

Take your C# console applications to the next level by mastering the art of creating methods. Learn how to organize and modularize your code, making it more manageable, reusable, and efficient.

• Write Your First C# Method
• Create C# Methods with Parameters
• Create C# Methods that Return Values
• Guided Project - Plan a Petting Zoo Visit
• Challenge Project - Create a Mini-Game

Course 06: Debug C# Console Applications

Sharpen your troubleshooting skills as you dive into the world of debugging C# console applications. Gain the ability to identify and fix issues in your code, ensuring your applications run smoothly and deliver the desired results.

• Review the Principles of Code Debugging and Exception Handling
• Implement the Visual Studio Code Debugging Tools for C#
• Implement Exception Handling in C# Console Applications
• Create and Throw Exceptions in C# Console Applications
• Guided Project - Debug and Handle Exceptions in a C# Console Application Using Visual Studio Code
• Challenge Project - Debug a C# Console Application Using Visual Studio Code