Lecture

Soft grips for delicate sample testing in tension

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-314: Concurrent engineering project

L'étudiant apprend à appliquer les compétences acquises en travaillant dans une équipe responsable d'une portion d'un projet plus vaste. ...

Description

This lecture discusses the development of soft grips for delicate sample testing in tension, focusing on the design process and analysis. The founders of Soft Grips SA and the project supervisor are introduced. Existing solutions for sample testing, EPFL self-tightening grips, project requirements, final design, clamp mechanism, adjusting mechanism, and analysis are covered. The lecture also touches upon the commercial strategy for the developed product.

This video is available exclusively on Mediaspace for a restricted audience. Please log in to MediaSpace to access it if you have the necessary permissions.

Watch on Mediaspace

Official source

Ontological neighbourhood

Systems science and engineering

Systems thinking: Systems engineering

Related concepts (11)

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.

Software requirements specification

A software requirements specification (SRS) is a description of a software system to be developed. It is modeled after the business requirements specification (CONOPS). The software requirements specification lays out functional and non-functional requirements, and it may include a set of use cases that describe user interactions that the software must provide to the user for perfect interaction.

Requirements management

Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requirement is a capability to which a project outcome (product or service) should conform. The purpose of requirements management is to ensure that an organization documents, verifies, and meets the needs and expectations of its customers and internal or external stakeholders.

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.

Related lectures (57)

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.

Requirements Definition

Explores the fundamentals of requirements definition in systems engineering, emphasizing the importance of clear and concise requirements for successful system design.

Scenarios and Requirements

Delves into the significance of scenarios and requirements in design, emphasizing storytelling for design solutions.

Systems Engineering: Introduction and Stakeholders

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

Master Programs Overview