; Gateway To Space
Learning Center
Plans & pricing Sign in
Sign Out

Gateway To Space


  • pg 1
									Gateway To Space
ASEN / ASTR 2500

Class #06

Colorado Space Grant Consortium

- We are now a class of 68

- HW 03 Assigned Today and next week
- Movie Night This Thursday at 6:00 PM in ECCR 108 - I bring the food, you bring the drinks - General Questions?

One Minute Paper:

One Minute Paper:

Team Videos

Class #06

Colorado Space Grant Consortium

Fall 2006 Team Video

Your Mission

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.

Request for Proposals

Class #06

Colorado Space Grant Consortium

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


To Recap RFP:
- Final weight shall not exceed 1000 grams - Shall image the Earth or the Balloon during flight and shall record internal and external temperature - Must have an additional experiment http://www.parallax.com/html_pages/resources/custapps/app_ nearspace.asp Chapter 8 - Must follow all the guidelines while writing proposal

- Why and How – this is your plan and foundation for project
- Using screen shots…

- 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 23, 2008 - Launch is November 15, 2008

What You Get…

What You Get…


Camera on Mars

Semester Theme

Class #06

Colorado Space Grant Consortium

Fundamental Problems…
- Weather - Night/daylight - Other

The Main Point
A high-altitude, balloon-borne optical telescope could generate high resolution images on a par with HST. But do it at a tiny fraction of the cost.

The value of High Angular Resolution is obvious.

14,000 ft

250 miles

Just how high up do you have to go to avoid all clouds and stormy weather and start having space-like astronomical observing conditions?

A photo taken from the window of a TR-1 (U2) aircraft from an altitude of around 75,000 ft.

Lake Tahoe, CA

View of Oregon from a U2 flying at 70,000 ft. The cloud deck is more than 30,000 ft below. There is simply no weather above 60 kft. And the sky gets very dark.

Closing Items:

Science Theme:
1.0 Sky Brightness Measurements

2.0 Video Capture of Stars Using CCD Imaging System
3.0 Stabilized Video Capture of Stars

4.0 Attitude Determination of Instrumentation
5.0 Attitude Determination and Control of Instrumentation

Presentation Templates

Final Written Report:
Design Document Template

Final Presentation:
- Should cover same items in report

- team video


Functional Block Diagram:

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.

Step 1: General definition. Subjective description and a few numbers


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

Step 2: Numbers and ranges. Focus in on defining the problem.

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 3: Subsystems. Repeat step 2 for every subsystem, tracing from system requirements.

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. 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) Ex.
1.SYS2 The system shall determine the densities of neutral particles to a 1-sigma precision of 2x10-13 kg/m3. (Goal 1x10-13 kg/m3). O3

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

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! 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 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:

2. A requirement has some standardized wording
– – – – – –

3. A requirement is succinct, strong, and gets to the point fast

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.


Special Class Discussion

Class #06

Colorado Space Grant Consortium

Special Class Discussion

Class #05

Special Class Discussion

Class #05

Special Class Discussion

Class #05

Special Class Discussion

Class #05

To top