Product Development R. Fries

Slides:



Advertisements
Similar presentations
Medical Device Software Development
Advertisements

Prescriptive Process models
Chapter 2Test Specification Process. n Device Specification Sheet – Purpose n Design Specification – Determine functionality of design n Test List Generation.
1 Software Processes A Software process is a set of activities and associated results which lead to the production of a software product. Activities Common.
Ch 3: Unified Process CSCI 4320: Software Engineering.
Software Development Life Cycle
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Software Development Methods and Tools Chapter 8.
Software Quality Assurance (SQA). Recap SQA goal, attributes and metrics SQA plan Formal Technical Review (FTR) Statistical SQA – Six Sigma – Identifying.
Chapter 21: Product Issues Design of Biomedical Devices and Systems By: Paul H. King Richard C. Fries.
Unit 251 Implementation and Integration Implementation Unit Testing Integration Integration Approaches.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
©Ian Sommerville 2000 Software Engineering, 6th edition Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing.
Software Testing and Reliability Testing Real-Time Systems Aditya P. Mathur Purdue University May 19-23, Corporation Minneapolis/St Paul,
High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Hardware Development Methods and Tools Design Methodologies Component Variations Misuse Extended TRIZ.
Chapter 3 Software Processes.
Testing: Chapter 13 "You make it, I’ll break it".
TGDC Meeting, July 2011 VVSG 1.1 Reliability David Flater, Ph.D. Computer Scientist, Software and Systems Division, ITL
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 1 Integration testing l Tests complete systems or subsystems composed of integrated.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Safety-Critical Systems 6 Certification
Instructor: Peter Clarke
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
Product Development Chapter 6. Hardware & Software Techniques Block diagram the system (Visio) Redundancy  Active: failure of one parallel component.
ETHICS & LEGAL CONCERNS Ethics – principles or values that guide actions All members are responsible for their actions. Need to protect all members of.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Team Think For You. Outline  Introduction  Process  Requirements Engineering  Architecture  Detailed Design  Testing  Demo  Extensibility  Conclusions.
System Implementation Dr. Dania Bilal IS 582 Spring 2009.
System Implementation Dr. Dania Bilal IS 592 Spring 2005.
Chapter 2 – Software Processes Lecture 2 1Chapter 2 Software Processes.
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
Part I Heading text 1 Part II Heading text 2 Kristian Sandahl Part III Heading text 3 1 Requirements  Elicitation  Analysis  Specification.
Over View of CENELC Standards for Signalling Applications
1. What do you understand by software engineering? Discuss the role of engineering software development. 2. What do you understand by software requirement.
Assoc. Prof. Dr. Ahmet Turan ÖZCERİT.  System and Software  System Engineering  Software Engineering  Software Engineering Standards  Software Development.
Software Engineering Saeed Akhtar The University of Lahore.
Ch7: Software Production Process. 1 Waterfall models  Invented in the late 1950s for large air defense systems, popularized in the 1970s  Main characteristics:
Software reviews Cost impact of software defects Defect amplification model Review metrics and their use – Preparation effort (E p ), assessment effort.
Software Engineering I. Introduction to Software Engineering Software models Formal Specification using ASML (Abstract State Machines Language) Software.
Lectures 2 & 3: Software Process Models Neelam Gupta.
1 Product Development Process Requirements Definition (Chap. 3) Conceptual Design (Chap. 3 and 4) Detailed Design (Chap. 5) Manufacturing (Chap. 7) Logistics,
Roadmap to Greener Computing Henri Mikkola. Eco-Friendly Product Lifecycle Today through globalization products travel long distances before reaching.
Advanced Software Engineering Dr. Cheng
Medical Device Software Development
Integration Testing.
Integrating Quality Activities in the Project Life Cycle
Chapter 21 Software Quality Assurance
Chapter 2 The Process.
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
QUALITY IMPROVEMENT BASICS
Chapter 21 Software Quality Assurance
Chapter 10 Systems Implementation and Operation
Design for Quality Design for Quality and Safety Design Improvement
Chapter 2 – Software Processes
Process Models Coming up: Prescriptive Models.
HMI Reliability Dale Wolfe Reliability Engineer LMSSC*ATC*LMSAL
Chapter 2 The Process.
Chapter 7 Software Engineering.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 3 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 3 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Computers.
RELIABILITY Reliability is -
THE OLD WAY AND THE NEW Conventional software engineering has numerous well-established principles. Many are still valid; others are obsolete. A modern.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 3 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Definitions Cumulative time to failure (T): Mean life:
Software Testing Software Testing is a process of evaluating a system by manual or automatic means and verify that it satisfies specified requirements.
Presentation transcript:

Product Development R. Fries Chapter 6 Product Development R. Fries

Hardware & Software Techniques Block diagram the system (Visio) Consider Redundancy – active or standby Active: failure of one parallel component - the second still works Standby: failure of component – replacement MTBF =mean time between failures = 1/λ Active MTBF=3/(2λ) Standby MTBF=2/λ

Hardware/Software Cont. Consider component reliability Vendor assessment (Hx, failure, etc.) Vendor audit (check facility) Vendor evaluation (inspect incoming) Vendor qualification (on-list?) Consider component history – military & reliability groups, government info bases Consider safety (FMEA, etc.)

Hardware/Software Cont. Consider component derating Use 2 watt R in 1 watt situation, decrease failure rate >30% (T, humidity, P, V, I, friction, vibration) Usage ratio = max stress/stress rating (.5-.9) Goal is reliability! Pacemaker example

Hardware/Software Cont. Safety margin must be considered Safety margin=safety factor-1 =(mean strength/mean stress)-1 Elevator – safety margin~2 Medical devices – Fries - .5 and up. Load protection must be considered Environment must be considered (see 112) Product misuse – consider Design for variation (6 sigma?)

Software Engineering Management Planning for safety (FDA!) Planning for risk assessment Planning for method Waterfall Incremental delivery Spiral Cleanroom Code and fix, …

Software Engineering Management Choose design method Top-down Data driven OOP Language (Assembler/C++/Qbasic?etc.) Testing Requirements Hazard Analysis!!! (FDA)

Software Engineering Management Requirements traceability (FDA) Software architecture design Well defined modules (logical) Other vendor – standalone Single purpose modules Cohesion & coupling Naming Integration

Structured/Unstructured Design Techniques Computer/database assisted: Ideation International IWB TRIZ Techoptimizer Others… Example done in class, another in text

Structured/Unstructured Design Techniques Axiomatic Design Nam Suh, MIT Requirements, design parameters, process variables, customer needs = vectors Try to solve, disassociate functional requirements and design parameters Highly mathematical Acclaro Software

Structured/Unstructured Design Techniques Structured, step by step, 8 steps Pahl and Beitz Semistructured – Wilcox, Engineering Design for Electrical Engineers, Ulrich and Eppinger Product Design and Development

Structured/Unstructured Design Techniques Reverse engineering Redesign Etc.