engineering paper

profileyna0990
ProjectProcess.pdf

10/17/19

1

EE 200: Electrical Engineering Design Project Process AKA Systems Engineering

4

4

Dr. Haggerty, PE (EE)

• Guide you through o Project Process o Requirements Analysis o Prototype Development

• 14 years: Systems Engineering Aerospace and electronic systems o Numerous winning proposals

o 100s M$ in new business

• 20 years: Consulting Engineer o Broader technical

o Multiple large clients

o Multiple start-ups

• 5 Years Adjunct faculty o Teach LD, UD, and Grad

o A “go to” replacement 5

5

10/17/19

2

Dr. Haggerty, PE (EE)

• Guide you through o Project Process o Requirements Analysis o Prototype Development

• 14 years: Systems Engineering Aerospace and electronic systems o Numerous winning proposals o 100s M$ in new business

• 20 years: Consulting Engineer o Broader technical o Multiple large clients o Multiple start-ups

• 5 Years Adjunct faculty o Teach LD, UD, and Grad o A “go to” replacement 2

Elevator Pitch is Short Explanation to Catch Listeners Interest

Individual • Name • Project Role • Experience Summary

• 15𝑠 ≤ 𝑇&' ≤ 2𝑚𝑖𝑛

6• References on BeachBoard 6

Project/Product:

• Product Elevator Pitch Outline o Hook:

o Who it is for:

o What it does:

o Why it is needed:

• What would differentiate your product ? o (To help generate info for

Elevator Pitch)

7

7

10/17/19

3

They say there is no “I” in Team.

9

9

Engineering Project Process Defined in: HF Hoffman, The Engineering Capstone Course

Part 1 • Select team and project • Analyze business case and issues • Unit specifications • Parts list and purchase • Test planning • Proposal

Part 2 • Weekly status • Formal team meetings • Formal design reviews • Software design, code, and test • Hardware design, fabrication, and

integration • Software/hardware integration • Final report, presentation, and

demonstration of final product 10

10

10/17/19

4

Systems Engineering Made up of Technical and Managerial Functions

Technical • Requirements Analysis • System Architecture/Design • Performance Analysis • Interface Specification • Test

o Verification and Validation o AKA V&V

Managerial • Customer Interface • Technical Management • Information Management

Process Engineering • Logistics and Operations • Coordination

11

11

Validation Shows Product Meets User Needs Verification Shows Design Meets Requirements

14

14

10/17/19

5

15

Full V&V Systems Engineering Example: NASA Systems Engineering Handbook

15

Tailored Process Flow Guides You Through Streamlined Product Prototype Development

16

System Requirements • Specific statements • One shall per req • Independent of Design • What Not How

Acceptance Tests • For each System Req • Tests System at End

Design and Development

Requirements Analysis • Technical Objectives • Constraints Worksheet • Standards Usage

Integration and Test • Hardware Unit • Software Module • HW/SW

HW/SW Partitioning

Hardware • Req Trace • Design • Fabrication

Software • Req Trace • Design • Code

Parts List • Safety Sheet

Requirements Workbook

16

10/17/19

6

Functional Require- ments (Events) Words

Design Parameters (Idea) Words & Drawings

Analysis Experiments, Words, FEA, Equations, Spreadsheets …

References Historical documents, www…

Risk Words, Drawings, Analysis …

Counter- measures Words, Drawings, Analysis…

A list of independent functions that the design is to accomplish. Series (1,2,3…) and Parallel (4a, 4b..) FRs (Events) can be listed to create the Function Structure

Ideally independent means to accomplish each FR. AN FR CAN HAVE SEVERAL POTENTIAL DPs. The “best one” ultimately must be selected

Economic (financial or maximizing score etc), time & motion, power, stress… EACH DP’s FEASABILITY MUST BE PROVEN. Analysis can be used to create DPs!

Anything that can help develop the idea including personal contacts, articles, patents, web sites….

High, Medium, Low (explain why) risk of development assessment for each DP

Ideas or plan to mitigate each risk, including use of off-the-shelf known solutions

FRDPARRC Project Design Process: Essential Elements (Slocum, MIT)

17

17

Least Formal Method is Repeated Rapid Prototyping

Pro • Short Turn-Around Products

o More productive o Schedule too short for Systems

Engineering Overhead

Con • Bad for complex products • May never get “there”

18

One of my more lucrative consulting contracts: Bailing out a company operating this way on a very complex product

18

10/17/19

7

Increasing Levels in SEI Capability Maturity Model (CMM) = Better Process and Product

19

# Level Focus Key Process Areas

5 Optimizing Continuous Improvement

Defect Prevention Process Change Management Technology Change Management

4 Managed Product and Process Quality

Quantitative Process Management Software Quality Management

3 Defined Engineering Process

Organization Process Focus and Definition Integrated Software Management Software Product Engineering Intergroup Coordination, Training Program, and Peer Reviews

2 Repeatable Project Management

Requirements Management Software Project Planning, Tracking, and Oversight Software Subcontract Management Software Quality Assurance and Configuration Management

1 Initial Heroes None

19

Cull “Realistic Constraints” from Tech Objectives and Other Sources • Social and Ethical

o Accessibility o Aesthetics o Functionality o Usability

• Manufacturability o Constructability o Codes o Size, Weight, and Power (SWAP) o Standards

• Environmental o Environmental Standards o Sustainability o Toxic waste (Solar panels)

• Economic o Cost o Extensibility o Interoperability o Maintainability, Quality, other -ilities o Marketability o Schedule o Standards use

• Health and Safety o Ergonomics o Safety Standards

• Political o Legal Considerations o Policy and Regulations 22

ABET Requirement on Capstone Courses

22

10/17/19

8

Hawaiian Weather Station is Safe and

Effective Realistic Constraints

Nonpoisonous

All natural

Edible

Simple user I/F Not annoying

23

Coconuts are safe and edible Buckeyes are useless nuts

23

One Use of Standards is Pass-Through Compliance: Use Parts that Meet Standards

• Standards section lists the standards that apply. • For Example: Prototype uses Bluetooth

o Reference the Bluetooth spec as applicable o You are not expected to actually shell out this money o When you work for a large company: o They will provide access o Some are available for free on the Internet:

ZigBee is I think

24

24

10/17/19

9

Good System Req. Criteria Provide Checks # Criteria Check Description

1 Necessary System cannot meet intended use without req

2 Feasible Req can be accomplished within schedule and budget

3 Concise Req is stated simply

4 Unambiguous Req can be interpreted only one way

5 Correct Req is factually accurate, technically possible, and legal

6 Complete All req conditions stated and req expresses whole idea

7 Consistent Req does not conflict with another req

8 Verifiable Implementation of req in system can be proved

9 Design Independent Req does not specify an implementation

10 Nonredundent Req is not a duplicate

11 No escape clauses Req is not conditional, speculative, or general 25

25

26

From Textbook

26

10/17/19

10

Risk Matrix

5

4

3

2

1

1 2 3 4 5

Consequence

Date: _____________ Project Title: ________________

Risk #1 Title: Driver: Mitigation:

Risk #2 Title: Driver: Mitigation:

Risk #3 Title: Driver: Mitigation:

Green – Low Risk - No Action Yellow – Moderate Risk – Take Action Red – High Risk – Seek an Immediate Remedy

P ro

ba bi

lit y

Cheating Risk Matrix

High Risk

Moderate Risk

Low Risk

Project Risk Assessed Using Management Friendly Risk Matrix

29

29