Overview requirements, and more Targets, requirements and ...

[Pages:4]Target, specifications, requirements, and more

Dr. Elise Fear Electrical and Computer Engineering

fear@enel.ucalgary.ca

Overview

? Our experiences with targets, specifications and requirements in ENGG 251 (up to the IMPACT project)

? Working towards definitions of targets, requirements and specs (what and why?)

? Application to the IMPACT project

? Project target ? List of users ? User needs ? Specifications

Targets, requirements and specs

? Several projects so far this term, including

? Leave No Trace ? Perpetual Motion Machine ? DFX ? Dr. Walker's lecture

? What were you aiming to do? ? What were the constraints/rules? ? What did Dr. Walker say about requirements?

Why bother?

? Make sure that your team is solving an appropriate problem.

? Make sure that you have familiarized yourself with the problem domain (translate user needs into reasonable design requirements).

? Define the "problem box."

Example

? Traffic engineers building western extension to Glenmore Trail

? Target: to build a safe and cost effective western extension to Glenmore Trail

? safe ? cost effective

Sub-targets

? What does safe mean? What does cost effective mean?

Example

? User needs: safety = number of accidents; cost = $$ per km

? Specifications:

? Safety: speed limit (110 km/h vs. 90 km/h); width of lanes; use of dividers

? Cost: with wider lanes, cost of materials increases

? Which is more important?

1

Target

? What is the main goal or objective of your project?

? Example: microwave breast cancer detection project

? Target: to develop a clinical system to assist radiologists in diagnosing malignant tumours in the breast

Target

? What is the target for the IMPACT project?

? What is your team trying to do? ? Who is your client?

Requirements

? Translate user needs into design requirements ? May want to think in terms of specs:

? convergent: technical specifications

- physical (how big?) ? operational (what is the function? not how, but what?) ? codes, regulations, standards

? divergent: user preferences, designer preferences

? Likely an iterative process

Requirements: users

? Who are the users of your design?

? Example: microwave breast cancer detection project

? Radiologists ? Women (patients) ? Technicians ? Health care planners

Requirements: user needs

? Example: Microwave breast cancer detection project user needs

? Detect and localize malignant tumours of 5 mm diameter and smaller

? Does not detect non-cancerous lesions ? Provide images with resolution of 1 cm

? Cost less than mammography ? Less painful than mammography ? Satisfy ANSI safety standard

Requirements: user analysis

? Who are the users of the IMPACT project? ? What are the needs of each user? Or, another way: ? What are you trying to do for the user?

(e.g. design a safe mat) ? What does that mean? (absorb impact of

typical skater at typical speed)

2

Translating requirements to specifications

? Example: breast cancer detection

? The system shall have a bandwidth of 5 GHz with upper frequency of 10 GHz.

? The system shall not deposit energy in the patient that is greater than 1.6 W/kg averaged over 1 g of tissue.

? The system shall not be larger than a standard patient bed.

? The system shall include sensors that do not contact the patient.

Standards and more

? Codes ? Standards (MIL specs or ANSI standards) ? Laws (occupational health and safety) ? Contracts and obligations (e.g. deadlines)

? Patents

Standards and IMPACT

? ISU communication 1019 ? What is required? (Look for words like

"must" and "shall", but watch out for "minimum") ? What is optional ("should")? ? Suggestion: translate ISU specs into meaningful specs for your project

Reviewing specifications

? Are your requirements specific enough? ? Are your requirements comprehensible? ? Can you meet the requirements? Can you

measure/evaluate whether you have met them? ? Does a requirement or specification matter in the

end? ? Have you considered standards and legalities? ? Remember specs are somewhat flexible ?modify

with more info, delete if one ends up not being relevant

IMPACT specifications

? Translate your user needs into specifications.

? You may wish to consider prioritizing (which are the most important? Do the important specs lead to criteria for evaluating the final design? e.g. cost vs. effectiveness)

Summary

target

familiarization

specifications

3

Requirements for today

? Coach stamp in your logbook:

? Target ? List of users ? User needs ? Specs

? Sign out and in with coach if you are going to the Oval

4

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download