Term
| Senge's 3 Simulation Lessons |
|
Definition
1. Structure Influences Behavior
2. Structure in human systems is subtle
3. Leverage often comes from new ways of thinking |
|
|
Term
| The principle behind Dym and Little's Prescriptive Model of Design |
|
Definition
| Design ---> Build ---> Test |
|
|
Term
| Five steps of Dym and Little's descriptive design process |
|
Definition
1. Problem Definition
2. Conceptual Design
3. Preliminary Design
4. Detailed Design
5. Design Communication |
|
|
Term
|
Definition
1. Engage
2. Define Stated Problem
3. Explore/Create Internal Idea of Problem
4. Plan a Solution
5. Carry Out the Plan
6. Evaluate, Check, and Look Back |
|
|
Term
| Glass-making, weaving, and Ballet Mecanique all did what |
|
Definition
| Greatly contributed to engineering |
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
|
Definition
|
|
Term
| 3 Parts of the Toulmin model of argument |
|
Definition
1. Claim
2. Data
3. Warrant |
|
|
Term
| Technique to writing a paragraph |
|
Definition
| Begin with a general statement, and work down to a specific statement |
|
|
Term
What is Hayakawa's ladder of abstraction?
What writing rule is derived from it? |
|
Definition
| Metaphor detailing abstraction process, ladder at the top of which sit all the most abstract words, with the bottom having the most specific. The rule is that technical writers should use the least abstract terms possible. |
|
|
Term
| 10 steps of Dym and Little's PREscriptive model of design |
|
Definition
1. Clarify Objectives
2. Establish User Requirements
3. Identify Constraints
4. Establish Functions
5. Establish Design Specifications
6. Generate Design Alternatives
7. Model/Analyze Alternatives
8. Test/Evaluate Alternatives
9. Refine and Optimize Chosen Alternative
10. Document Design |
|
|
Term
| two main purposes of TechCom |
|
Definition
|
|
Term
| 4 Parts to a Memorandum Header: |
|
Definition
1. To
2. From
3. Subject
4. Date |
|
|
Term
|
Definition
1. Problem statement (often two sentences)
2. Task statement (your task or job)
- Any Criteria
- Any Constraints
3. Purpose Statement |
|
|
Term
| 5 Parts of a Memorandum Summary: |
|
Definition
1. Actions Taken
2. Findings
3. Implications
4. Conclusions
5. Recommendations |
|
|
Term
| Definition of a discussion |
|
Definition
| Discussion of the details; The bulk of the memorandum, meant for analysis by concerned readers |
|
|
Term
| Three recognized appeals: |
|
Definition
| To Emotion; To Ethics; To Reason |
|
|
Term
| Two Appeals used commonly by engineers |
|
Definition
|
|
Term
|
Definition
1. Authoritative
2. Motivational
3. Substantive |
|
|
Term
|
Definition
| Depends on the authority a person has to be believed on an issue; Their experience IS the warrant |
|
|
Term
|
Definition
| Appeals to an audience's specific morals or values |
|
|
Term
|
Definition
| Uses devices such as C&A, Analogies, or Generalization to lead an audience to a conclusion |
|
|
Term
| Six types of substantive warrant |
|
Definition
1. Cause and Effect
2. Sign
3. Parallel Case
4. Analogy
5. Generalization
6. Classification |
|
|
Term
| Parts of a Classical Argument |
|
Definition
1. Problem/Introduction
2. Credentials
3. Position/Solution
4. Background of Problem
5. Argument for Position/Solution
6. Conclusion |
|
|
Term
| 6 Types of logical fallacies |
|
Definition
1. Hasty Generalization
2. False Cause
3. Undistributed Middle
4. Irrelevant Appeal
5. Non-Sequitur
6. Equivocation |
|
|
Term
|
Definition
1. So other can find your sources
2. Honesty
3. Lends authority |
|
|
Term
| Reasons not to plagiarize |
|
Definition
1. Taking credit for others' work
2. People may wrongly trust you
3. If caught, heavy price to pay |
|
|
Term
|
Definition
1. When using another's words
2. When using another's ideas/argument |
|
|
Term
|
Definition
1. Quotation marks for verbatim extracts
2. Brackets/Source/Page citations for anything else |
|
|
Term
| 4 Purposes of a progress report |
|
Definition
1. To show progress
2. To show that you are on-time
3. To justify changes
4. To give findings/explain developments |
|
|
Term
| Progress reports should be organized... |
|
Definition
| By topic rather than chronologically |
|
|
Term
| 2 Parts of a Progress Report Introduction: |
|
Definition
1.Description
a. Motivation
b. Product Description
2. List/Description of Tasks
a. Tasks listed/described clearly
b. Start/Completion Dates |
|
|
Term
| 3 Parts of a Progress Report Main Body: |
|
Definition
1. Tasks completed
2. Tasks remaining
a. projected completion dates
3. Preliminary findings/conclusions |
|
|
Term
| 4 Parts of a Progress Report Conclusion: |
|
Definition
1. Assessment of progress
2. Explanation/Justification of scope changes
3. Completion forecast
4. Name/Contact Info |
|
|
Term
| 4 Requirements of Good Oral presentations: |
|
Definition
| Language, Visuals, Organization, Practice |
|
|
Term
|
Definition
No more than seven words/line
No more than seven lines/slide |
|
|
Term
| Unintended consequences of technology: |
|
Definition
| Illusions of: Safety, Control, Security, Strength, Well-Being |
|
|
Term
| Faulty assumptions result in... |
|
Definition
| Compounded errors that get amplified within nonlinear systems |
|
|
Term
| 3 levels of systemic change: |
|
Definition
Systemic Structure: Generative ==>
Patterns of Behavior: Responsive ==>
Events: Reactive |
|
|
Term
| Definition of Reactive System: |
|
Definition
1.Short time scale
2. No future model
3. No strategy/plan
4. Needed for rapid responses
5. Hard to make robust due to adversity over time |
|
|
Term
| Definition of Responsive System: |
|
Definition
1. Short-Medium time scale
2. Future model based on historical pattern(Cause of pattern unknown)
3. Strategy based on past events
4. Needed for flexible response in ambiguous situation
5. Robust design is only as good as history allows |
|
|
Term
| Definition of Generative System: |
|
Definition
1. Time scale short to long
2. Future model understands Cause/Effect (New scenarios can be studied using causal model)
3. Planning/Strategy based on causes
4. Can be used to generate new scenarios by varying causes
5. Robust design only as good as causal model |
|
|
Term
|
Definition
1. Title
2. Recipients' names/titles
3. Authors' names/titles
4. Project dates
5. Date of preparation
6. Distribution list |
|
|
Term
|
Definition
| Material that would interrupt the flow of a report or is too lengthy for the body |
|
|
Term
| Order of formal report components: |
|
Definition
1. Executive summary
2. Table of contents
3. Report
4. Citations list
5. Appendices |
|
|
Term
| 6 Parts of an Executive Summary |
|
Definition
1. Problem statement
2. Task statement
3. Purpose statement
4. Results
5. Conclusions/implications
6. Recommendations |
|
|
Term
| R. Kelly's 9 Qualities of a Star Performer: |
|
Definition
1. Blaze Trails (Initiative)
2. Know who knows (Maximize resources)
3. Proactive Self-Management
4. Get the Big Picture
5. Correctly follow (Alert, Bounce, Gently Question)
6. Teamwork as Joint-Ownership
7. Small-L Leadership
8. Street Smarts
9. Show/Tell Appropriately (Focus on audience as well) |
|
|
Term
|
Definition
The combining of constituent elements of
separate material or abstract entities into a single or unified entity |
|
|
Term
|
Definition
| The separating of any material or abstract entity into its constituent elements |
|
|
Term
| 6 characteristics of robust systems: |
|
Definition
1. Dynamic interconnection
2. Feedback
3. Multiscale
4. Heirarchical organization
5. Heterogeneous constituency
6. Nonlinear strength/mode |
|
|
Term
| Top 10 of the 20 greatest 20th century engineering achievements |
|
Definition
1. Electrification
2. Automobile
3. Airplane
4. Safe/Abundant Water
5. Electronics
6. Radio/Televison
7. Agricultural Mechanization
8. Computers
9. Telephone
10. Air Conditioning/Refrigeration |
|
|
Term
| Full names of authors of tech com text: |
|
Definition
1. Elizabeth Hildinger
2. Erik Hildinger
3. Pauline Bary-Khan |
|
|
Term
| Definition of Constraint: |
|
Definition
| Clearly-defined limits that can be framed as a binary choice |
|
|
Term
| Definition of design specification: |
|
Definition
| An identified property that all designs should have, which can be measured, and allows for success/failure testing of the design |
|
|
