Colorado Space Grant Consortium Gateway To Space ASEN / ASTR 2500 Class #05 Gateway To Space ASEN / ASTR 2500 Class #05

One Minute Paper:

-Recap of last class -Announcements -One Minute Reports -RFP, Requirements, Block Diagrams, and Design Documents (Oh My) -Next class Soldering 101 Today:

Colorado Space Grant Consortium Last Class Recap ASEN / ASTR 2500 Class #05 Last Class Recap ASEN / ASTR 2500 Class #05

- Work effectively as a team - Remember center of gravity during drop while designing - Good designs can be ruined by how it’s dropped - Design must be strong enough to survive the trip to the scale Things to Think About:

Colorado Space Grant Consortium And the Winners ARE? And the Winners ARE?

Link #1 Link #2

- Find your missing team members - Will meet in DLC 1B70 on Thursday 09/10/09 - Need volunteers to help set up and tear down - Set up help needed at 8:30 AM, tear down help until 11:15 - HW 03 due 09/10/ st Sunday training session 09/13/09 from 3:00 to 9:00 PM - General Questions? Announcements:

- If we decide our team sucks, can we switch? - What will we be doing individually on teams? - Has a team ever not made it to launch? - Why was George Lucas on Pluto? - Where do we start with our project? - How many lego teams have been successful? - How much are we expected to learn on the BalloonSat? 1 Minute Reports:

Colorado Space Grant Consortium Request For Proposals

What is an RFP? - There is a lot of money out there - There are a lot of ideas - Request For Proposal bring them together - Most satellites were at one time an RFP - Most of you will write or help write a proposal in your job - Now is your time to practice

Civilization as you know it has been destroyed by killer tomatoes from Io. You and your clan are trying to understand what’s going on with the planet. Your clan has liberated EOSS headquarters and they are now at your disposal. Your clan also has access to the entire inventory at allelectronics.com, large amounts of gaseous helium, latex balloons, a machine shop, foam core, various batteries and a Noodles & Co, which still continues to operate. The fate of planet Earth is in your hands.

SEE RFP

To Recap RFP: -Final weight shall not exceed 850 grams - Shall image the Earth or the Balloon during flight and shall record internal and external temperature - Must have an additional experiment Chapter 8 nearspace.asp Chapter 8 nearspace.asp - Must follow all the guidelines while writing proposal - Why and How – this is your plan and foundation for project - Using screen shots…

So... -Take the ideas you came up with individually during the HW#2 - Start with these in your team and expand them during HW #3 - But…Keep It Simple Stupid (KISS Principle) - Start now! - You are writing a proposal not a request for proposal - Proposals September 17, Launch is November 7, 2009

What You Get… Plus - Foam core and insulation - Flight batteries - Hot glue and Al tape - Flight tube and flag - Switches

Presentation: Presentation Templates - Final presentation should cover same items in final report

Final Written Report: Design Document Template - You will write you team’s final report throughout the semester with our Design Document revisions - team video

Fall 2006 Team Video

Fall 2008 Team Video

Drawings:

Colorado Space Grant Consortium Functional Block Diagrams Functional Block Diagrams

Functional Block Diagram:

AVR 2MB Flash, Temp, Pressure, XY Accel Onboard 9.0V5.0V3.3V Analog #1 Analog #2 Analog #3 Analog #4 Outputs Inputs 9V Switch Camera Data Line Heater 9V 1.5V 2 GB Data Line 9V Switch

Colorado Space Grant Consortium Requirements

Requirements Definition Marcin Pilinski Chris Koehler Colorado Space Grant Consortium

Anatomy of Requirements Mission Statement (aka Mission Goal) A very general description of the problem being addressed by the system. Mission Objectives 3 to 5 general statements elaborating the Mission Statement. Objective Requirements Quantify each objective: when, what, where, for how long System Requirements The system as a whole must perform to this set of specifications in order to meet the objective requirements, mission objectives, and mission statements Subsystem Requirements Each subsystem must perform to these specifications in order to meet the criteria defined above. This part is done separately for each subsystem i.e. power, mechanical, computer, science, thermal. Step 1: General definition. Subjective description and a few numbers Step 2: Numbers and ranges. Focus in on defining the problem. Step 3: Subsystems. Repeat step 2 for every subsystem, tracing from system requirements G O Requirements Level

An Example from Class: Icarus Goal (G1) The BalloonSat Aquintus shall ascend to an altitude of approximately 100,000 feet to carry out scientific experiments that will measure tilt of the satellite, forces acting upon it, wind speed, and solar energy to better understand the conditions in which high altitude observatories would be in. Goal (G1) The BalloonSat Aquintus shall ascend to an altitude of approximately 100,000 feet to carry out scientific experiments that will measure tilt of the satellite, forces acting upon it, wind speed, and solar energy to better understand the conditions in which high altitude observatories would be in. Goal (G1) The BalloonSat Aquintus shall ascend to an altitude of approximately 100,000 feet to carry out scientific experiments that will measure tilt of the satellite, forces acting upon it, wind speed, and solar energy to better understand the conditions in which high altitude observatories would be in. O1 (comes from G1) Construct BalloonSat to improve understanding of HA conditions at X-100,000 ft for under $YYY dollars by MM/DD/YYYY. O2 (comes from G1) Measure tilt in one axis and forces in the range of X mN to YmN as a function of altitude in the range of X-100,000. O3 (comes from G1) Measure wind speed perpendicular to one face of the BalloonSat and solar energy as a function of altitude.

2. Objective Requirements and System Requirements Before Starting the next level… (system level or level 1 in this scheme) 1.A requirement must be NECESSARY, must have a clear need 2.A requirement must be TRACEABLE 3.A requirement must HAVE A METHOD OF VERIFICATION 4.A requirement must be ATTAINABLE 5.A requirement must be CLEAR 1.SYS2The system shall determine the tilt from 10 to -10 degrees with a precision 0.5 degrees (Goal 0.1 degrees). O2 Ex.

2. Objective Requirements and System Requirements General Guidelines and Wisdom For the Young Engineer 1.A requirement defines the “WHAT” not the “HOW” –“HOW” defines the implementation, i.e. the solution –“WHAT” defines the functionality which is the first thing you need before starting anything! 2.A requirement has some standardized wording –shall: denotes a requirement which must be verified, use it in every requirement “there is no try, only do or do-not” –should: denotes a goal for which a best effort will be made –will: denotes a factual or explanatory statement 3.A requirement is succinct, strong, and gets to the point fast –Avoid “or” statements and “if” stipulations –No wordiness, a brief statement saying WHAT the system shall do. –DO NOT use the following words or ones like it: A FEW WEASEL WORDS TO AVOID: Adequate, Always, Bad, Better, Clearly, Easily, Efficient, Etc., Every, High, Ideal, Large, Maximize, Maximum, May, Most, Minimize, Minimum, Must, Never, Normal, Rapid, Real-time, Satisfactory, Significant, Simultaneous, Small, Sometimes, Sufficient, User-friendly, Worse… These words introduce ambiguity, doubt, and deception… …an engineer craves not these things.