Lecture

Software Engineering: Best Practices

Graph Chat

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.

In course

ME-213: Programmation pour ingénieur

Mettre en pratique les bases de la programmation vues au semestre précédent. Développer un logiciel structuré. Méthode de debug d'un logiciel. Introduction à la programmation scientifique. Introduction à l'instrumentation virtuelle. ...

Description

This lecture covers tools and best practices for software writing, debugging, testing, and managing code. It discusses the software lifecycle, error management, testing strategies, and the importance of documentation and good coding practices.

Instructor

Christophe Salzmann

Expertise Real-time Internet ServicesReal-time controlQuality of Service and Bandwidth adaptationLabVIEW Education PhD | Remote experimentation, Network 2005 – 2005 EPFL Directed by Denis Gillet MS. Degree | Computer Science 1999 – 1999 University of Florida Directed by Prof. H. Latchman Teaching & PhD Past EPFL PhD Students as codirector Damien Perritaz, Evgeny Bogdanov, Wissam Halimi Courses Control systems + TP ME

Official source

Ontological neighbourhood

Computer engineering

Software development: Software development process

Related concepts (32)

Software testing

Software testing is the act of examining the artifacts and the behavior of the software under test by validation and verification. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not necessarily limited to: analyzing the product requirements for completeness and correctness in various contexts like industry perspective, business perspective, feasibility and viability of implementation, usability, performance, security, infrastructure considerations, etc.

System testing

System testing is testing conducted on a complete integrated system to evaluate the system's compliance with its specified requirements. System testing takes, as its input, all of the integrated components that have passed integration testing. The purpose of integration testing is to detect any inconsistencies between the units that are integrated together (called assemblages). System testing seeks to detect defects both within the "inter-assemblages" and also within the system as a whole.

Coding conventions

Coding conventions are a set of guidelines for a specific programming language that recommend programming style, practices, and methods for each aspect of a program written in that language. These conventions usually cover file organization, indentation, comments, declarations, statements, white space, naming conventions, programming practices, , , architectural best practices, etc. These are guidelines for software structural quality.

Agile software development

In software development, agile practices (sometimes written "Agile") include requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/end user(s), Popularized in the 2001 Manifesto for Agile Software Development, these values and principles were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban.

Software quality

In the context of software engineering, software quality refers to two related but distinct notions: Software's functional quality reflects how well it complies with or conforms to a given design, based on functional requirements or specifications. That attribute can also be described as the fitness for purpose of a piece of software or how it compares to competitors in the marketplace as a worthwhile product. It is the degree to which the correct software was produced.

Related lectures (64)

Automated Testing: Fuzzing and Sanitization

Explores fuzzing, bug oracles, code reviews, and automated testing techniques, emphasizing the importance of sanitization in detecting faults.

Software Engineering: Development Steps and Error Management

Covers the essential aspects of software engineering, focusing on understanding the steps of program development and error management.

Software Quality: Managing Defects and Testing Strategies

Explores managing defects, testing strategies, and challenges in software quality, with real-world examples and case studies.

Software Development: Life Cycle & Methodologies

Explores the software development life cycle, methodologies, tech choices, agile practices, and common tech industry terms.

Programming Bugs: Understanding, Fixing, and Preventing