| User | Post |
|
11:03 am
February 16, 2010
|
Rocket-To-The-Moon
| | Altus, Oklahoma, USA | |
| Member | posts 685 | |
|
|
Post edited 11:04 am – February 16, 2010 by Rocket-To-The-Moon
I have begun a Requirements Document for OHKLA. Please have a look and expand it/fill in the blanks. We will probably need to open a discussion for each line so that we can work through each parameter as a team.
OHKLA Requirements Document
This could be a topic for our next IRC meeting.
|
Main Workgroups: Propulsion & Spacecraft Engineering
|
|
|
6:06 pm
February 16, 2010
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
Is nosecone material really a requirement? I thought it would be something we chose on the basis of other requirements?
That aside, good on you for starting this document, I look forward to us fleshing it out durng a meeting.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
6:15 pm
February 16, 2010
|
Rocket-To-The-Moon
| | Altus, Oklahoma, USA | |
| Member | posts 685 | |
|
|
Good point. I suppose the logical process is to define the requirements and then find solutions that satisfy those requirements (the entire purpose in the first place).
I'm not sure if you noticed, but there are tabs at the bottom of the page for different components.
|
Main Workgroups: Propulsion & Spacecraft Engineering
|
|
|
8:21 am
February 17, 2010
|
DenisG
| | Saarbrücken, Germany (GMT+1) | |
| Member | posts 69 | |
|
|
Very good starting point. It would be cool though if we had a running requirement management system (OSRMT or OSEE for example) for that, because spreadsheets are a little cumbersome and can't handle interdependencies.
|
|
Login 
Register 
Search 
Home
Topic RSS 
