Requirements – Short Review

Slides:



Advertisements
Similar presentations
Design Constraints For Engineering Projects
Advertisements

Testing Medical Devices A Brief Overview © 2005 Max Cortner. Copying and distribution of this document is permitted in any medium, provided this notice.
Chapter 2Test Specification Process. n Device Specification Sheet – Purpose n Design Specification – Determine functionality of design n Test List Generation.
LP33 Series UPS kVA 400Vac/CE
Mr. Harethe El Ouadhane IEC member for IEC MT14. |Infrastructure Business | Germany | Test Engineer & Expert (Internal Arc, Making, Breaking.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
PURPOSE OF DFMEA (DESIGN FAILURE MODE EFFECTS ANALYSIS)
WBS & AO Controls Jason Chin, Don Gavel, Erik Johansson, Mark Reinig Design Meeting (Team meeting #10) Sept 17 th, 2007.
Software Requirements
ES305: Virtual Tools in Engineering Design: The Eng. Design Process James Carroll, Associate Professor Electrical and Computer Engineering.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Unit 3a Industrial Control Systems
1 Lecture 5.3: SEF Ch 4 Requirements Analysis Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
From Research Prototype to Production
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
Chapter 9 Testing the System Shari L. Pfleeger Joann M. Atlee
Design Documentation Clint Kehres, Brian Krouse, Jenn Shafner.
Defining Design Goals and Design Requirements © 2013 Project Lead The Way, Inc.Engineering Design and Development.
Smart Home Technologies
Plasma Sense Amplifier
Failure Modes and Effects Analysis (FMEA)
Workshop on Accreditation of Bodies Certifying Medical Devices Kiev, November 2014.
Design Process Design process is a collection of procedures and habits that help teams design better products.
Wireless Home Control Team # 2
Typical Business >$100M Sales
Home Theater Pre-AMP Team #4 Title Christopher Merkl Negar Farzinnia
User Manual Product Specifications
Efficient Engineering teams fully specify before they design !!
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
World Health Organization
Detailed Block Design Presentation 3 (P3)
Project Plan, Task Checklist, Estimates Project Prototyping
Welcome ! Capstone Design Lab is a new 4 credit course specifically aimed to give you industry design exposure in a design team atmosphere The course.
Welcome ! Capstone Design Lab is a newer 4 credit course specifically aimed to give you industry design exposure in a design team atmosphere The course.
Team #2: Staff Adam Wozniak Barry Gentz Brad LaCount Sean Murphy
Team #6: Transistor/Diode Curve Tracer
Requirements – Essential To Robust Product Design
Raechel Huebner Ruthanne Sherer
Safety Standards & Block-Block Interface Definitions
September 9, 2013 Quiz summary Team Meetings Honors Course
Project Statement ..
Project Definition and Selection Process
Team 4: Staff Shawn Bentley Chris Mueller Erick Janke Nic Langlois
No Lab Assignment for Next Week Mandatory Attendance
TEAM 2 Remote Control Car.
Presentation Practices
Requirements – Essential To Robust Product Design
Product Life Cycles and Sustainability
Presentation Practices
OVERVIEW Impact of Modelling and simulation in Mechatronics system
Business Processes Organization and Roles
Chapter 18 Maintaining Information Systems
Presentation Practices
Block Diagram Transmitter Receiver × 2 Transmitter Power Supply ADC
Project Plan, Task Checklist, Estimates Project Prototyping
Capstone Design Project
Team #: Staff Name 1 Name 2 Name 3 Name 4 Name 5 Name 6
Introduction to System Analysis and Design
Open Book, Open Note 3-4 Multipart Questions
Efficient Engineering teams fully specify before they design !!
Presentation P2 System Design Preliminary Detailed Design
Object oriented system development life cycle
No Lab Assignment for Next Week Mandatory Attendance
Power Block Implementation
IEEE SC-2 International Standard Review
Direct Attached Storage and Introduction to SCSI
GE 6757 TOTAL QUALITY MANAGEMENT
J1879 Robustness Validation Hand Book A Joint SAE, ZVEI, JSAE, AEC Automotive Electronics Robustness Validation Plan Robustness Diagram Trends and Challenges.
FPGA Vinyl to Digital Converter (VDC)
Design Constraints For Engineering Projects
Presentation transcript:

Requirements – Short Review User Level Product Level Block Levels Definition: “Statements of desired product performances and features used to define and quantify a product design” User Level: Special list or labels which state the intended application and/or purpose of the product (Labeling) Product Level: Quantitatively state all features, performances, and interfaces described in “Eng Terms” Block Level: State all features, performances and interfaces describing the block in “Engineering Terms” User Level >>> Validation Product & Block Level>>>Verification Effective Engineering means full specification before design !!

Requirements Imply Proof of Satisfaction Requirements Imply Proof of Satisfaction ! Implied Product Design Integrity ! Many Gov’t Agencies mandate that ALL product requirements should be user validated and/or engineering verified (tested or justified). A requirement which cannot be verified or validated should NOT be stated unless objective evidence can be compiled to prove its satisfaction Requirement Categorization Used in this Course: Standard: Common to ALL Project Teams Performance: Unique to Project and Technology, For Differentiating

Design Blocks Complex products require that the design be broken into logical design elements (termed blocks in this course) A minimum of 1 Design Block per team member is required for ALL projects Blocks form the basis of standardized design elements in this course. Product Level Requirements can either be allocated or just associated to all design blocks. The Project System Design entails defining ALL Block Performance Reqs incl Interfaces and Functions

Allocation and Association to Design Blocks ALL Product Level Requirements Must be allocated or associated to each Design Block within the project to complete a System Design Phase Allocated: % of total budgeted to applicable design blocks plus margin. For example: Product Cost, Power Consumption, Mass …. Associated: Used when allocation is not applicable. For example: Country(s) of Market, Annual Volume, Safety Standards ….

Types of Verification Inspection, Existence (Mostly Std Requirements) User Manual (UM) Product Labeling Business Case BOM’s, Asm Dwgs and other Eng Dwgs Engineering Analysis (Mix of Std and Perf Requirements) Analog Worst Case DFM Analysis Digital Worst Case DFM Analysis Circuit Simulations Lab Testing (Mix of Std and Perf Requirements) Bench testing circuit performances Mechanical Measurements Integration with other design blocks, compatible equipment HALT and Other Stress Tests for Reliability Safety and EMC Testing

Verification Evidence Verification Plan* Numbered List or Numbered Table of ALL requirements Corresponding List or Table of Verification Types Location or Pointer to Verification Evidence File(s) or Doc(s) Detailed Test Plan and Test Results Document Use for All Simulation and Lab Test Verifications Written with sufficient detail, a 2nd party could perform the testing Must describe all inputs, permutations, configurations, and expected output limits Test Results may be in a separate document in case multiple verifications will be conducted. Sims, Scope Traces, Digital Photos * Summary of Verification Plan (PPT Slides) List Key Requirements and Verification Types Employed List Any Requirements which were Unverifiable Summarize Detailed Test Plan for Key Performance Requirements Show % of Requirements Verified (Coverage)

Product Level - Standard Requirements Standard Requirements are those requirements which are universal and can be applied to nearly all products and hence final projects Standard Requirements may or may not be differentiating depending upon project goals but MUST be part of the minimum description of the product Standard Reqs Are Common to Nearly ALL Projects

Documented Business Case & Product Labeling PL - Std Reqs: Market & Business Case Requirement Verification Evidence Market Size Average List Price Market Geography Market Demography Intended Application Material Cost Manufacturing Cost Annual Volume Business Case User Manual, Env, Power Reqs Labeling, User Manual Overall BOM Spreadsheet $ Mfg Process Diags Documented Business Case & Product Labeling

Analysis and Specific Lab Testing PL - Std Reqs: Env & Safety Requirement Verification Evidence Min Oper Temp Range Min Oper Humidity Range Min Oper Alt or Press Range Min Storage Temp Range Min Storage Humidity Range Min Storage Alt or Press Range Max Storage Duration Primary EMC Standards Primary Safety Standards Eng Analysis, Lab Test EMC Certification Tests Safety Tests Analysis and Specific Lab Testing

PL - Std Reqs: Power Interfaces Requirement Verification Evidence Energy Source List Source Connection List Min Oper Voltage Range Max Power Consumption Max Energy Consumption Block Diags, Schematics, Lab Test User Manual (UM) UM, Labels, Lab Test, Sims Eng Analysis, Sims & Lab Test

Variety of Evidence for Verification PL - Std Reqs: Mechanical Requirement Verification Evidence Max Volume Shipping Container Size Max Mass Elec I/F Connector(s) Max # of PC Bds Max PCB Circuit Area Max Shock Mech Dwgs, Asm Dwg, UM Mech Dwgs, Measurement Eng Analysis, Lab Test BOM, Asm Dwgs Top Level Asm Dwg, BOM Bd Layout Dwgs Variety of Evidence for Verification

PL - Std Reqs: Mfg & Life Cycle Requirement Verification Evidence Max Parts Count Max Unique Parts Count Parts/Mat $ Allocation Asm/Test $ Allocation Product Life, Reliability Full Warranty Period Product Disposition Production Life Support Service Strategy Composite BOM Composite BOM, Quotations Quotations, Cycle Time Eng Analysis, Lab Tests UM, Analysis of R(1 period) UM, Labeling Obsolescence Analysis Product designs should consider full “life cycle” from Mfg process to Disposal

Product Level - Performance Requirements Performance Requirements are those requirements which are specific to a product and project Performance Requirements differentiate the product from all other similar products Performance Requirements should describe …. Signal Interfaces Mechanical Interfaces Features, Options Modes of Operation Performance Parameters User Controls User Displays and Outputs

Requirement Verification Evidence PL – Perf Reqs: Power Input(s) Requirement Verification Evidence AC Power Freq Range(s) AC Power EMC Stds Battery Chemistry Battery Std Size Battery Capacity Eng Analysis, Lab Test Lab Test Mfg Data Sheet Mfg Data Sheet, Lab Test

Nearly All will be Eng Analysis and/or Lab Test Verifications PL – Perf Reqs: Electrical Functions (Must be Defined if Applicable) Requirement Definition Voltage or Current Gain Ranges Input – Output SNR Frequency Response Linearity and THD Delay in uSec or mSec Computation or Algorithm Compute Speeds in Ops/Sec Input – Output Delay Analog Functions Digital Functions Nearly All will be Eng Analysis and/or Lab Test Verifications

Every Signal Needs to be Defined in Detail PL – Perf Reqs: Electrical Interfaces (For each signal “grouping”) Electrical Signal Req Definition Signal Type Signal Direction Standard Definition Basic Analog Characteristics Detailed Analog Characteristics Analog, Digital, or Power Input, Output, Bidirectional RS170 Video, RS232, USB, Custom, etc Voltage Range, Frequency or Bandwidth Range Impedance or Current Range Offset Voltages, Currents Error Voltages, Currents Max Noise Other Analog Characteristics Every Signal Needs to be Defined in Detail

Other Verifications: Societal (#7) Societal Aspects are those concerned with accessibility, ergonomy, and diversity including cultural, gender, and age Questions to Answer as part of project design and presentation: Does the product depend on a certain class of user age, intelligence, strength, height, weight, skill, gender, language, etc. Would common handicaps (vision, hearing, limbs, etc) prevent your product from being utilized or make your product unsafe? Does your design require the use of any country specific infrastructures (ie; phone, cable, power, network, etc) What countries is the target market and what languages will the product labeling support? Does the product require special skills or tools to operate or maintain Would the product potentially offend or exclude a cultural group? Accessibility and Ergonomics: Key to products that require user interaction related to overall user height, size, strength, mobility, vision, hearing, touch, etc.

Other Verifications: Safety (#8) This aspect includes Environmental, Health and Safety (EHS) Questions to Answer as part of project design: What industry is the product intended to serve? (home, automotive, factory, medical, aerospace, telecom, computer, educational, etc) What hazard would result from a single point failure of a component? What safety features have been designed into the product to prevent injury in the case of failure or accidental misuse Does continuous use of your product present any long term user hazards? Has the environment been adequately specified for all modes? (operating environment, shipping/storage environment, indoor vs outdoor use, dry versus wet, cleaning and maintenance, etc) What hazardous materials are utilized in the product? (eg. Nickel Cadmium, Mercury or Lead Acid batteries, Lead based solders, etc) What components are recyclable? Through what process? What warning labeling will be required on the product, user manual? What safety standards will the product be designed and tested to?

Other Verifications: Legal, Ethical (#9) Pretext: Most products must be designed in accordance with the laws of the countries in which they are sold. This includes providing an operation and service manual in the language of the country sold. Key Questions to Answer: Does your product design include an operator manual? Does the operator manual or product labeling indicate specific applications or uses? What product labeling is required in the industry in which the product pertains? Does the product include labeling of user interface? Manufacturer, Date, Serial, etc? What languages would the product labeling and information need to be published in? How long would you be required to provide support parts for the product? What liabilities may be encountered if the product malfunctions?

Other Verifications: Manufacturability (#10) Manufacturability: Measure of the ability to mass produce a product design within known, established, economic and commonly available processes at a high yield. Key Questions to Answer as part of project design and presentation: Does your design utilize common place assembly industries? Are you relying on any custom processes? What % of hand assembly is required versus automated or robotic? What is the expected overall yield of your product in DPM? What measurements, adjustments, calibrations or tweaks are required during the manufacturing process? Could your product design be mass produced outside the US? Outside North America? In China, India or other lower overhead areas? Is there any processes involved in mfg which may be hazardous?

Other Verifications: Sustainability (#10) Sustainability: Measure of the ability to continue a product in mass production and/or continue to service a product even after production has ceased. Key Questions to Answer as part of project design and presentation: How would your product be serviced? Are there any user replaceable parts? What skills, tools, are required to service it? What special instructions/warnings need to be included with the product with regard to service How long will it likely remain in production? Are there any parts likely to go obsolete? Technologies that would take its place (eg; 74LSXX replaced by 74FXX device) What parts are unique with no potential substitutes? What is the oldest standard component used in the design? Newest standard component?