Lecture

Requirements Definition

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

ENG-421: Fundamentals in systems engineering

Introduction to systems engineering using the classical V-model. Topics include stakeholder analysis, requirements definition, concept selection, design definition and optimization, system integration and verification and validation. This class is part of ...

Description

This lecture covers the fundamentals of requirements definition in systems engineering, focusing on the importance of clear and concise requirements for successful system design. It discusses the challenges of requirements definition, the hierarchy of requirements, and the impact of poor requirements through examples like the Mars Climate Orbiter incident. The lecture also delves into good and bad requirements examples, the evolution of requirements since the 1970s, and the methodology for requirements allocation. It emphasizes the need for verifiable, clear, and feasible requirements, and the importance of proper verification and validation processes. The session concludes with insights on requirements volatility and the significance of the System Requirements Review (SRR) in ensuring high-level requirements are well-defined and approved.

Instructor

Volker Gass

After completing his master’s degree in Microtechnology at the Federal Institute of Technology in Lausanne in 1989 he worked as a Project Manager at Mecanex SA, a Swiss High-Tech company active in the field of Aerospace Mechanisms. While working at Mecanex he completed a PhD in Science in the field of applied Micro-Systems Technologies at the University of Neuchâtel, Switzerland in 1994. In 1995, Volker Gass participated in the Management Buy Out of Mecanex SA. In 2000, Mecanex was acquired by the Swiss Defence and Technology group RUAG . He was appointed to lead Customer Relations and Business Development of the newly formed Systems & Space Division at RUAG Aerospace in 2004. In the same year he was appointed member of the Swiss Academy of Engineering Sciences for his contribution in the field of High-Technology Space applications. From November 2006 to June 2007, Volker Gass successfully graduated RUAG’s Top Leadership Course, and held the position of General Manager, Sales & Marketing in the Space Division of RUAG in Switzerland as well as Member of the Board of Directors (President) of Mecanex USA Inc., Berlin, CT, until December 2009.In 2008 he successfully led the acquisition of SAAB Space and its subsidiary Austrian Aerospace. From January to June 2009 Volker Gass led the business team in the successful acquisition of Oerlikon Space. From mid-2009 to September 2011 he was responsible for Special Projects in the Marketing & Sales Organization of RUAG Space Switzerland. Since October 2011, Dr. Volker Gass is nominated Director of the Swiss Space Center at the Ecole Politechnique Fédérale de Lausanne. In March 2012, he is awarded the title of Adjunct Professor at the School of Engineering (STI) of the EPFL. From January 2014 to December 2017, he was nominated member of ESA’s Human Spaceflight and Exploration Science Advisory Committee (HESAC) and from spring 2015 to December 2018, observer at ESA’s Earth Science Advisory Committee (ESAC).As of January 1, 2021, The Swiss Space Center is renamed "Space Innovation"

Official source

Ontological neighbourhood

Systems science and engineering

Systems thinking: Systems engineering

Related concepts (32)

Requirements analysis

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements. Requirements analysis is critical to the success or failure of a systems or software project.cite book |editor1= Alain Abran |editor2=James W.

Requirement

In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder.

Requirements traceability

Requirements traceability is a sub-discipline of requirements management within software development and systems engineering. Traceability as a general term is defined by the IEEE Systems and Software Engineering Vocabulary as (1) the degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or primary-subordinate relationship to one another; (2) the identification and documentation of derivation paths (upward) and allocation or flowdown paths (downward) of work products in the work product hierarchy; (3) the degree to which each element in a software development product establishes its reason for existing; and (4) discernible association among two or more logical entities, such as requirements, system elements, verifications, or tasks.

Business requirements

Business requirements, also known as stakeholder requirements specifications (StRS), describe the characteristics of a proposed system from the viewpoint of the system's end user like a CONOPS. Products, systems, software, and processes are ways of how to deliver, satisfy, or meet business requirements. Consequently, business requirements are often discussed in the context of developing or procuring software or other systems. Three main reasons for such discussions: A common practice is to refer to objectives, or expected benefits, as 'business requirements.

Requirements engineering

Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering. The first use of the term requirements engineering was probably in 1964 in the conference paper "Maintenance, Maintainability, and System Requirements Engineering", but it did not come into general use until the late 1990s with the publication of an IEEE Computer Society tutorial in March 1997 and the establishment of a conference series on requirements engineering that has evolved into the International Requirements Engineering Conference.

Related lectures (64)

An Introduction to Systems Engineering: Requirements, Architecture, and Concept Generation

Covers the 'V-Model' of Systems Engineering, emphasizing good requirements, system architecture, concept generation, and concept selection.

Systems Engineering: Requirements, Architecture, and Standards

Explores the history, definitions, and challenges of Systems Engineering, emphasizing the importance of requirements in system design and architecture.

Introduction to Design Reviews

Covers the objective, steps, and stakeholders in design reviews, emphasizing the importance of risk analysis and verification.

Systems Engineering: Introduction and Stakeholders

Introduces Systems Engineering, emphasizing stakeholder analysis and clear requirement definition for project success.

Scenarios and Requirements