Level 1 Requirements - Revision history

Strangelv: Removing controversial tag -- there is no evidence of this article being a problem

2007-06-17T16:44:30Z

Removing controversial tag -- there is no evidence of this article being a problem

Jriley: reformat

2007-05-26T13:26:16Z

reformat

Jriley: Should we figure out what we are doing?

2007-03-17T12:45:10Z

Should we figure out what we are doing?

New page

==Level 1 Requirements for Lunarpedia==

How do you get started on a technical design?

How do you know when you are finished?

===Lunarpedia as a Technical Design===

We will need to design many technical devices and systems to return to the Moon. Not surprisingly there are formal procedures for this type of design work. These procedures can be very powerful.

Designing a wiki, Lunarpedia, to support our return to the Moon can be seen as a technical design project. We can apply our technical design procedures to this task if we wish.

One of the first steps in a technical design is to define exactly what it is that you are trying to do. This process is called defining the Level 1 Requirements.

All the articles in the [[Purposes List]] category are bits and pieces of ideas we can use for this task. We can, as a community, figure out what we are doing.

Or, we can choose not to and follow the path of [[Serendipity]].

===Good Space Example===

There is a good example of the successful application of this task in the Shuttle main engines. Shortly after launch, the engines are throttled up to 105%. The question is 105% of what? This certainly cannot mean 105% of their rated output or they would blow up.

The answer is that they are now run at 105% of their initial design requirement. They simply work better than first planned.

However, you can not do better than you first planned unless you do the first planning.

===Level 1 Requirements for Lunarpedia===

If anyone would like to work up formal Level 1 Requirements for Lunarpedia and practice to working them up for technical projects we will have to accomplish to establish a lunar settlement, please put a note in the discussion table of this article.

----

Return to [[Purposes List]].

----

[[Category:Purposes]]
[[Category:Business]]

← Older revision		Revision as of 16:44, 17 June 2007
Line 1:		Line 1:
−	~~{{Controversial}}~~
−
	{\|align=right		{\|align=right
	\|__TOC__		\|__TOC__

@@ Line 1: / Line 1: @@
-==Level 1 Requirements for Lunarpedia==
+{{Controversial}}
 How do you get started on a technical design?
@@ Line 6: / Line 14: @@
-===Lunarpedia as a Technical Design===
+==Lunarpedia as a Technical Design==
 We will need to design many technical devices and systems to return to the Moon.  Not surprisingly there are formal procedures for this type of design work.  These procedures can be very powerful.
@@ Line 19: / Line 27: @@
-===Good Space Example===
+==Good Space Example==
 There is a good example of the successful application of this task in the Shuttle main engines.  Shortly after launch, the engines are throttled up to 105%.  The question is 105% of what?  This certainly cannot mean 105% of their rated output or they would blow up.
@@ Line 28: / Line 36: @@
-===Level 1 Requirements for Lunarpedia===
+==Level 1 Requirements for Lunarpedia==
 If anyone would like to work up formal Level 1 Requirements for Lunarpedia and practice to working them up for technical projects we will have to accomplish to establish a lunar settlement, please put a note in the discussion table of this article.