Requirements Flashcards

Question

What is the right situation to use benchmarking/reverse engineering?

Answer 1

▪Concept development to detail design phase ▪Need of approaches to achieve design goals

Answer 2

Crucial question of Reverse Engineering: “How was the design problem solved?” 1.Define the attributes for comparison/questions to be answered. 2.Select reverse engineering object (e. g. competitor product or process). 3.Disassemble the object in your mind or physically . 4.Analyze the object and the chosen solutions regarding the present problem and questions. 5.Apply the gained knowledge to solve the problem. Notes: ▪ Danger of getting stuck in established solutions rather than innovative approaches ▪ Time and cost-intensive approach, especially for complex products ▪ Consider patent protection

Answer 3

▪ The goal of storytelling is shared understanding. ▪ Storytelling enables the design engineer to imagine unknown situations and assume the customer’s/user’s perspective. →non-obvious requirements, e.g., related to customer needs, are easier to identify. ▪ Indirect way to express requirements. Ideally it is supplemented by explicit requirement formulation.

Answer 4

-Characters → Personas -Plot → Story board -Narrative point of view → User stories

Answer 5

A persona is a fictitious character that helps to imagine someone’s perspective who could be involved in a use-case

Answer 6

A storyboard is a series of sketches of real-life situations, depicting users carrying out several activities by using the device in a certain context. ▪ Rough sketch (not too many details to encourage creativity of reader). ▪ Written from the user’s perspective.

Answer 7

-To provide a common visual language that people from different backgrounds can read and understand. -Readers can experience the visualized interactions by empathizing with the user or the situation (subjective perspective).

Answer 8

A user story is told from the perspective of the user or customer for which the system is developed. It describes a functionality which provides users or customers with a capability to achieve their goals in order to satisfy their needs and therefore, deliver value. ▪ Usually kept short and simple: “As a , I want so that ”. ▪ I-perspective important to assume the user’s perspective.

Answer 9

▪Vague idea of the desired product ▪Use cases, characters, motives & known needs ▪Possibly team of experts

Answer 10

▪ Improved understanding of relevant needs and user’s perspective ▪ Implicit or explicit formulation of requirements

Answer 11

▪Typically within planning and concept development phase ▪Need to view the system through the user´s eyes ▪Need for requirements

Answer 12

1.Define Personas 2.Sketch a customer journey (e.g., by a storyboard), including: ▪ User as a (more detailed) persona ▪ Context (surroundings,…) ▪ Timing ▪ Interactions between product and user ▪ Emotions and feelings of users (expressions) 3.Write down the user stories ▪ As a , I want so that 4.Use for: ▪ Discussion and confirmation of your view ▪ Detailed requirement definition

Answer 13

▪ Customer journeys ▪ Scenarios ▪ Interviews ▪ Kano Model

Answer 14

-Social -Environmental -Economic

Answer 15

-By 2030, substantially increase the number of youth and adults who have relevant skills -By 2030, ensure equal access for all to affordable and quality education -By 2030, ensure complete free, equitable and quality education for all

Answer 16

-By 2025, prevent and significantly reduce marine pollution of all kinds -Minimize and address the impacts of ocean acidification, including through enhanced scientific cooperation -By 2020, sustainably manage and protect marine and coastal ecosystems

Answer 17

-Develop quality, reliable, sustainable and resilient infrastructure -By 2030, significantly raise industry’s share of employment and gross domestic product -Enhance scientific research, upgrade the technological capabilities of industrial sectors in all countries

Answer 18

▪ Components of the atmosphere that influence the heat permeability ▪ Comparability through CO2 equivalent

Answer 19

“refers to the situation that may occur if, for reasons of costs related to climate policies, businesses were to transfer production to other countries with laxer emission constraints."

Answer 20

SCOPE 1: Direct emissions from controlled sources SCOPE 2: Indirect emissions from purchased energy (only upstream) SCOPE 3: Indirect emissions from the upstream and downstream value chain

Answer 21

LKSG (Lieferkettensorgfaltspflichtengesetz): The Supply Chain Act mandates industries to comply with human rights regulations throughout their supply chain, including their supply partners. Applies for companies with at least 1000 employees in Germany CSRD: The Corporate Sustainability Reporting Directive makes industries report how their operations affect the environment and people. Applies for companies with more than 250 employees and net sales of more than 50 million euros.

Answer 22

▪ Databases: ecoinvent, ProBas, GaBi, … ▪ Assessment Software: OpenLCA(freeware), Sphera, …

Answer 23

▪ is a cap-and-trade system that sets a limit on total greenhouse gas emissions ▪ for high-emission industries ▪ allowing companies to buy and sell emission allowances to incentivize reductions ▪ Focuses on Scope 1 emissions

Answer 24

-Sustainability goals can be in conflict -Sustainability goals can also synergize -Most goals are difficult to reach as agreed -Indicators help to direct effort and to allocate responsibility, however, they are often ambiguous

Answer 25

Benefits ▪ Simple structure ▪ Supports a comprehensive view ▪ Helps to organize top-level or abstract information without getting lost in detail ▪ Helps to treat VUCA by adopting a long-term view ▪ Serves as some structure for team discussion ▪ Supports decisions and the definition of concrete steps to be taken Limitations ▪ No algorithm, i.e., results are produced by qualitative reasoning. ▪ Output depends on subjective assessment of priorities or relative importance

Answer 26

The what-not-how principle says that one should focus on what goals to accomplish rather than on how to achieve it.

Answer 27

A solution-neutral requirement is formulated according to the what-not-how principle. ▪ It is useful to: − Minimize fixation on existing or suggested solutions and stay open-minded for alternative solutions − Prevent early stage-design process from evolving into details ▪ It is often not applied because: − requirements are difficult to idtentify − feasibility is not assessable − engineers tend to think in solutions and details

Answer 28

−Formulated with “shall” or “should” −Singular → only one requirement included in statement −Clear & unambiguous → readily understandable −Verifiable → objective assessment „satisfied“ or „violated“ is possible, quantitative requirements are typically easier to verify −Feasible → can be satisfied within physical laws, state of the art technologies, and other project constraints −Solution-neutral → should be closer to the problem than the solution −Not unnecessarily restrictive → allow for many or a large range of solutions to avoid over-engineering −Free of hidden assumptions → shall not include assumptions about technical feasibility

Answer 29

−Non-redundant → each requirement specified only once −Consistent → terms used are consistent −Complete → form a sufficient condition for satisfying superior requirements or reaching the overall design goal; include seemingly obvious aspects −Without unnecessary conflicts → not in obvious conflict with other requirements or itself

Answer 30

▪ A requirement list is a structured collection of all the needs, expectations, and constraints that a product, system, or project must fulfill. ▪ It is one of the most fundamental documents in engineering design, product development, and project management - serving as the bridge between what stakeholders want and what designers or engineers will create. ▪ They are structured to support clarity and traceability.

Answer 31

Experienced designers often provide useful information that are not requirements, however, declared as such. You may include them by labelling them appropriately

Answer 32

▪ Boundary conditions They define the setting for the verification of other requirements. Example: The operation temperature shall be between -20°C and +50°C. ▪ Manufacturability restrictions They ensure manufacturability but they are not related to customer-relevant properties or top-level requirements. Example: The overhang angle shall not exceed 45° (in the context of additive manufacturing). ▪ Observations They describe properties of successful predecessor products. May not be related to top-level requirements. Example: The cell phone has a physical keyboard. ▪ Design space definitions Specify ranges of design variables that are plausible to the experienced designer. Example: The radius of the profile shall be between 5 and 10 mm.

Answer 33

Design goals or superior requirements for you

Answer 34

Structured, complete list of requirements for your stakeholders

Answer 35

▪Established in early stages for definition of design goal and formulation of component requirements ▪ In later stages for component design and verification ▪To establish an agreement between stakeholders

Answer 36

1. Consolidate your design goal and requirements for you. 2. Deduce / derive / break down requirements for your stakeholders by, e.g., storytelling, benchmarking, QFD, checklist for requirement clarification, solution spaces, reverse abstraction (see following chapters). 3. Compile the requirement list, structured, e.g., by the responsible unit, function, type (geometry, material, …), importance 4. Label what are requirements (R) and what are non-requirements, like e.g., boundary conditions (BC), manufacturability constraints (MC), observations (O) and design space definitions (DS) 5. Update and revise requirements throughout the product development project Consider: ▪ Single requirements: Shall/should, singular, clear & unambiguous, verifiable, feasible, solution-neutral, not unnecessarily restrictive, free of hidden assumptions ▪ Sets: Non-redundant, consistent, complete, without unnecessary conflicts ▪ Traceability: origin and purpose provided ▪ Proliferation: Do you really need it?

Answer 37

P is a necessary condition for Q when Q cannot be true unless P is true. Or: Q being true implies that P is true.

Answer 38

P is a sufficient condition for Q when Q is always true whenever P is true. Or: P being true implies that Q is true.

Answer 39

An INUS condition is an Insufficient but Necessary part of an Unnecessary but Sufficient condition.

Answer 40

A cause is a set of INUS conditions which are (as a set) sufficient for its associated effect to occur

Answer 41

−single-factor thinking, i.e. confusing INUS condition and cause → considering only one element of a cause. Example: Recall the Munich subway doors from LEC 02 „doors reliably close“ is caused by (1) doors of type A AND (2) there is no snow and temperature below 0“. Only when (2) is considered, it becomes clear, that doors of type A do not work. − mono-causal thinking, i.e. assuming that there is only one cause for an effect. „when this works, it is the only way it works“, e.g., „vehicles with engine combustion“ is the only cause for economically viable mobility product

Answer 42

▪ Remember completeness of requirements: the set of requirements should be sufficient for reaching the design goal → requirements should be formulated as INUS conditions

Answer 43

▪ Quality function deployment is a method to derive technical requirements from customer preference (assumed requirements, expectations, needs). ▪ The customer’s view is represented by customer perceived attributes, short customer attributes, that may be difficult to measure. ▪ The engineering view is represented by technical attributes that can be measured and subjected to quantitative requirements. Synonyms: engineering characteristics, or metrics ▪ House of Quality (HoQ) = documentation scheme with the roof for the correlation matrix

Answer 44

▪ Product management ▪ Marketing ▪ Controlling ▪ R&D, engineering design ▪ Quality Management ▪ Production ▪ Purchasing / (After) sales ▪ Moderator ‒ Moderates the team ‒ Asks the right questions ‒ Structures the discussion ‒ Supports consensus building ‒ Documents the results

Answer 45

▪Understanding of customers‘ needs and expectations ▪Optional: data about own and competitors' products ▪ Interdisciplinary team of experts (development, marketing, procurement, controlling, product management …)

Answer 46

▪List of important technical attributes ▪Approximate description of the relation between customer value and technical attributes ▪Requirements on technical attributes ▪Document for decision support and effective interdisciplinary communication

Answer 47

▪Typically in early design stages, but can be applied in all phases of product development ▪Need for technical requirements ▪Applicable to products and processes

Answer 48

1. Collect customer attributes and customer importance values. 2. Customer competitive assessment: Compare own and competitors´products based on customer attributes. 3. Collect the technical attributes of the product that are relevant to satisfy the customer requirements and define the directions of improvement. 4. a) Establish relationship matrix: Evaluate how a technical attribute is related to a customer requirement (0-1-3-9). b) Calculate importance values of technical attributes. c) Estimate the technical difficulty of implementation d) Derive priorities of technical attributes for development. 5. Establish correlation matrix: Evaluate the type of relation between the technical attributes (--, -, o, +, ++) 6. a) Conduct technical competitive assessment (benchmarking) with competitors and own products based on technical attributes. b) Plausibility check of the benchmark (2,6a). 7. Estimate target values for technical product attributes 8. Analyze results.

Requirements Flashcards

(72 cards)