By the end of this chapter, you should:  Understand the properties of an engineering requirement and know how to develop well-formed requirements that.

Slides:



Advertisements
Similar presentations
By: Edith Leticia Cerda
Advertisements

Developing a tool to monitor and help prevent concussions Instrumented Football Helmet Development Team Joseph Jackson (ME) Adam McCauley (ECE) Shawn Kachnowski.
GFX Abstract The existing technology used to create guitar sound effects is often prohibitively expensive to the amateur guitarist. The object of this.
LR NYU Fall 2007 Business Operations New Product Development Process.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
Organizational Influences and Life Cycle
EE496A Senior Design Project I Dr. Jane Dong Electrical and Computer Engineering.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
By the end of this chapter, you should:  Have an understanding of the types of projects electrical and computer engineers undertake.  Understand and.
Engineering Requirements
Team of engineers who build a system need:  An abstraction of the system  An unambiguous communication medium  A way to describe the subsystems ◦ Inputs.
 Design creates a new artifact (system, component or process) to meet a given need.  Broad Classifications ◦ Creative Designs – the first PDAs ◦ Variant.
System Testing There are several steps in testing the system: –Function testing –Performance testing –Acceptance testing –Installation testing.
Requirements/Systems analyst
Requirements Engineering
Software Project Management Lecture # 8. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
1 Rev: 02/12/2007 MSE-415: B. Hawrylo MSE-415: Product Design Lecture #3 Chapter 4 Identifying Customer Needs.
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
Guidelines for the Development and Maintenance of RTF- Approved Measure Savings Estimates December 7, 2010 Regional Technical Forum Presented by: Michael.
Business Analysis and Essential Competencies
Requirements 101 CS3300 Fall 2015.
 Explain the role of a system analyst.  Identify the important parts of SRS document.  Identify the important problems that an organization would face.
Creating a Shared Vision Model. What is a Shared Vision Model? A “Shared Vision” model is a collective view of a water resources system developed by managers.
To come up with a practicum project that full filled the 411 requirements Create a fun project that would get kids interested in science and engineering.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
Approaching a Problem Where do we start? How do we proceed?
The Need Specification. References  Adapted from:  Design for Electrical and Computer Engineers, first edition, by Ralph M. Ford and Chris S. Coulston.
The Need Specification. References  Adapted from:  Design for Electrical and Computer Engineers, first edition, by Ralph M. Ford and Chris S. Coulston.
Lecture 7: Requirements Engineering
Human Factors Issues Chapter 9. Human Factors = ergonomics WWII based – military significance… … a necessary part of medical device design…
Requirements Collection By Dr. Gabriel. Requirements A requirement is any function, constraint, or property that the system must provide, meet, or satisfy.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Project Selection And Needs Identification
Senior Design II proposal A step-by-Step review. What is Senior Design?  Senior Design is a sequence of two courses during two consecutive semesters.
Headphone Amplifier, Equalizer, and Sound Stage Abstract Some portable media devices, such as mp3 players, have insufficient power to drive top-of-the-line.
Develop Project Charter
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
CT1404 Lecture 2 Requirement Engineering 1 1. Today's Lecture Definition of a Software Requirement Definition of Software Requirements Management Characteristics.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
SECON Team Zulu IEEE SoutheastCon Hardware Competition 2010.
Human Factors Issues Chapter 8. What is Human Factors? Application of the scientific knowledge of human capabilities and limitations to the design of.
Improving Readability with Style and Design
Smart Home Technologies
Approach Design Definition with Synthesis and Analysis of Alternative Solutions Leading to a Decision.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Concept Development and End Product Description. Concept Generation.
Concept Development and End Product Description. Concept Generation.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
Wheels: Go Forward Speakers: Say “Hello” OSCAR: Go Forward Say “Hello” Remote Control PC.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
ISO 9001:2015 Subject: Quality Management System Clause 8 - Operation
System Development Life Cycle (SDLC). Activities Common to Software Projects Planning : Principles Principle #1. Understand the scope of the project.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
Information Technology Project Management, Seventh Edition.
Assumptions Limitations
Chapter 4 Requirements Engineering (1/3)
Project Learning in Capstone Design
Requirement Engineering
AIM: To control the movement of a manual wheelchair by means of human voice for paralyzed patients.
Human Factors Issues Chapter 8 Paul King.
Project Learning in Capstone Design
UNIT II.
Engineering cycle.
By the end of this chapter, you should:
The Need Specification
Presentation transcript:

By the end of this chapter, you should:  Understand the properties of an engineering requirement and know how to develop well-formed requirements that meet the properties.  Be familiar with engineering requirements that are commonly specified in electrical and computer systems.  Understand the properties of the complete requirements specification, as well as knowing the steps to develop one.  Be able to conduct advanced requirements analysis to identify tradeoffs. 2

3

Marketing Requirement Engineering Requirement Requirements Specification 4

3.2 Engineering Requirements 5

1) Abstract 2) Verifiable 6

3) Unambiguous 4) Traceable 7

Does the following requirement meet the four desirable properties? (abstract, verifiable, unambiguous, traceable) “The robot must have an average forward speed of 0.5 feet/sec, a top speed of at least one foot/sec, and the ability to accelerate from standstill to the average speed in under one second.” 8

Does the following requirement meet the four desirable properties? (abstract, unambiguous, verifiable, traceable) “The robot must employ IR sensors to sense its external environment and navigate autonomously with a battery life of one hour.” 9

 IMPORTANT – Your requirements for your project must also be REALISTIC.  => You need to demonstrate that the target you have selected is technically feasible.  How are you going to do this? 10

 Constraint = design decision imposed by the environment or a stakeholder that impacts or limits the design. (see the original overview diagram).  Example contraint: The system must use a PIC18F52 microcontroller to implement processing functions. 11

 A standard is what?  Question is, what standards are relevant to your project and how do you use them?  Different levels of usage ◦ User ◦ Implementation ◦ Developer  Types: safety, testing, reliability, communication, data, documentation, design, … 12

 Structured workshops and brainstorming  Interviews and surveys  Observation of processes and devices in use  Benchmarking and market analysis  Prototyping and simulation  Research survey 13

 Need to know what type of requirement to select for a given system.  These are but EXAMPLES – you must determine the correct ones for your system!  Hint: don’t just try to copy and paste them. 14

Performance  The system should detect 90% of all human faces in an image.  The amplifier will have a total harmonic distortion less than 1%. Reliability & Availability  The system will have a reliability of 95% in five years.  The system will be operational from 4AM to 10PM, 365 days a year. 15

Energy  The system will operate for a minimum of three hours without needing Environmental  The system should be able to operate in the temperature range of 0°C to 75°C.  The system must be waterproof and operate while submersed in water.  to be recharged. Many more examples in the book. 16

3.3 The Requirements Specification 17

Definition 18

 Normalized/Orthogonal  Complete Set 19

 Consistent  Bounded 20

Validation = 21

 Ask the customer if the requirements meet their needs.  Usually done in teams.  For each engineering requirement ◦ Traceable? ◦ Verifiable? ◦ Realistic & technical feasible?  For the complete Requirements Specification ◦ Orthogonal? ◦ Complete? ◦ Consistent? 22

Marketing Requirement s Engineering RequirementsJustification 1, 2, 41.The total harmonic distortion should be <0.1%. Based upon competitive benchmarking and existing amplifier technology. Class A, B, and AB amplifiers are able to obtain this level of THD. 1–41.Should be able to sustain an output power that averages  35 watts with a peak value of  70 watts. This power range provides more than adequate sound throughout the automobile compartment. It is a sustainable output power for projected amplifier complexity. 2, 41.Should have an efficiency (  ) >40 %. Achievable with several different classes of power amplifiers. 31.Average installation time for the power and audio connections should not exceed 5 minutes. Past trials using standard audio and power jacks demonstrate that this is a reasonable installation time. 23

1–41.The dimensions should not exceed 6” x 8”x 3”. Fits under a typical car seat. Prior models and estimates show that all components should fit within this package size. 1–41.Production cost should not exceed $100. This is based upon competitive market analysis and previous system designs. Marketing Requirements 1.The system should have excellent sound quality. 2.The system should have high output power. 3.The system should be easy to install. 4.The system should have low cost. 24

25 Marketing Requirements Engineering RequirementsJustification 4, 61.System will implement nine voice command functions ( menu, play/pause, previous, next, up, down, left, right and select) and respond appropriately according to each command. These are the basic nine commands that are used to control an iPod and will provide all functionality needed. 1, 3, 4, 71.The time to respond to voice commands and provide audio feedback should not exceed 3 seconds. The system needs to provide convenient use by responding to the user inputs within a short time period. Based on research it was determined that the response time for the iPod is less than 1 second and an average voice recognition system requires 2 seconds to recognize commands. 4, 61.The accuracy of the system in accepting voice commands will be between 95% and 98%. Research demonstrates that this is a typical accuracy of voice recognition chips. Speaker independent systems can achieve 95% and speaker-dependent up to 98%.

26 5, 61.The system should be able to operate from a 12 V source and will draw a maximum of 150 mA. The automobile provides 12V DC. A current draw budget estimate was developed with potential components and 150mA was an upper limit of current estimated. 5, 6, 71.The dimensions of the prototype should not exceed 6” x 4” x 1.5”. This system must be able to fit in a car compartment, somewhere between the seats. Estimate is based upon a size budget calculation using typical parts. Marketing Requirements 1.Should not minimize or slow down the functional quality of the iPod. 2.User should be able to search for songs and artists and receive feedback on selection. 3.System should provide clear understandable speech. 4.System should be able to understand voice commands from user. 5.Should be able to fit and operate in an automobile. 6.Should be easy to use. 7.Should be portable.

3.5 Advanced Requirements Analysis 27

THD Output Power , Efficiency Install Time Dimensions Cost ) Sound Quality+ 2) High Power+ 3) Install Ease+ 4) Cost- 28

THD Output Power , Efficiency Install Time Dimensions Cost THD- Output Power+ , Efficiency+ Install Time- Dimensions- Cost- 29

Apex AudioMonster AmpsOur Design THD0.05%0.15%0.1% Power30W50W35W Efficiency70%30%40% Cost$250$120$100 30

A complete requirements document will contain:  Needs, Objectives, and Background (See Chapter 2).  Requirements. ◦ marketing requirements ◦ engineering requirements  Should be abstract, verifiable, and traceable  Some maybe constraints  Some may be standards ◦ Advanced analysis  Engineering-marketing tradeoffs  Engineering-engineering tradeoffs  Benchmarks 31

 Properties of engineering requirements  Examples of engineering requirements  Properties of the Requirements Specification  Advanced Requirements Analysis ◦ Tradeoff matrices ◦ Benchmarks 32