Requirements Document v1 0
Version 5 (Jeremy Wright, 04/30/2012 07:09 pm) → Version 6/51 (Jeremy Wright, 05/01/2012 02:34 am)
h1. Requirements Document v1.0
Draft: 2012-04-28
This requirements document is currently being discussed on the forum "here":https://opendesignengine.net/boards/4/topics/72
Each requirement is labeled with STSR (Shepard Test Stand Requirement), followed by the number of the "initial question":https://opendesignengine.net/projects/shepard-ts/wiki/Initial_Questions_v1_0 that the requirement corresponds to, followed by a dot and then the ID number of the requirement.
*STSR 1.1* Must accommodate low power, commercially available amateur rocket motors sized A through E.
*STSR 1.2* Must be mobile enough to enable live demonstrations as part of educational and outreach activities.
*STSR 2.1* Must be well documented so as to meet the needs of open source spaceflight designers who will design and build future test stands (at Mach 30 or elsewhere).
*STSR 2.2* The documentation and procedures must be complete enough that Mach 30 operators, students and educators who want to bring rocket engineering into the classroom, and anyone else interested in how rockets are tested can learn how to use it.
*STSR 2.3* Document the engine testing procedure from test stand setup, to running tests, and ending with stowing the test stand.
*STSR 3.1* Must be useful for the verification of Estes thrust vs time "motor performance data":http://estes.aptinet.com/images/page%2033.pdf .
*STSR 3.2* Must be able to record exhaust temperature vs time of Estes motors and transport that data to a laptop computer.
*STSR 6.1* Any desktop computer based control software should run on all three major PC platforms (MS Windows, Mac OS X, and Linux).
*STSR 6.2* Must use standard connections to the computer running the control software (for example, USB, Ethernet, or similar connections).
*STSR 7.1* All design documentation must be open and complete enough so that ANYONE, without necessarily a technical education in rocketry, propulsion, or engineering, would be able to build and operate a Shepard test stand.
*STSR 8.1* The design must enable the completion of at least one operational test stand.
*STSR 8.2* Whenever and wherever possible, considerations should be made so that this design can be used as a kit in the future.
*STSR 9.1* The cost of the first operational test stand must not exceed $200 excluding "consumables" and tools.
*STSR 10.1* If at all possible, the test stand should be completed within 3 months of formal launch as an exercise of agile design.
*STSR 11.1* Disposal of the spent Estes motors should conform to all local, state, and federal guidelines.
*STSR 11.2* Electronic waste items, including batteries and circuit boards, must also be disposed of according to all local, state, and federal guidelines.
*STSR 11.3* If the frame of the test stand is damaged beyond repair during operation, proper disposal/recycling guidelines must be followed for the materials used in its construction.
*STSR 11.4* Wherever possible, the design should make it as easy as possible to replace components which are consumable or relatively easy to damage.
Draft: 2012-04-28
This requirements document is currently being discussed on the forum "here":https://opendesignengine.net/boards/4/topics/72
Each requirement is labeled with STSR (Shepard Test Stand Requirement), followed by the number of the "initial question":https://opendesignengine.net/projects/shepard-ts/wiki/Initial_Questions_v1_0 that the requirement corresponds to, followed by a dot and then the ID number of the requirement.
*STSR 1.1* Must accommodate low power, commercially available amateur rocket motors sized A through E.
*STSR 1.2* Must be mobile enough to enable live demonstrations as part of educational and outreach activities.
*STSR 2.1* Must be well documented so as to meet the needs of open source spaceflight designers who will design and build future test stands (at Mach 30 or elsewhere).
*STSR 2.2* The documentation and procedures must be complete enough that Mach 30 operators, students and educators who want to bring rocket engineering into the classroom, and anyone else interested in how rockets are tested can learn how to use it.
*STSR 2.3* Document the engine testing procedure from test stand setup, to running tests, and ending with stowing the test stand.
*STSR 3.1* Must be useful for the verification of Estes thrust vs time "motor performance data":http://estes.aptinet.com/images/page%2033.pdf .
*STSR 3.2* Must be able to record exhaust temperature vs time of Estes motors and transport that data to a laptop computer.
*STSR 6.1* Any desktop computer based control software should run on all three major PC platforms (MS Windows, Mac OS X, and Linux).
*STSR 6.2* Must use standard connections to the computer running the control software (for example, USB, Ethernet, or similar connections).
*STSR 7.1* All design documentation must be open and complete enough so that ANYONE, without necessarily a technical education in rocketry, propulsion, or engineering, would be able to build and operate a Shepard test stand.
*STSR 8.1* The design must enable the completion of at least one operational test stand.
*STSR 8.2* Whenever and wherever possible, considerations should be made so that this design can be used as a kit in the future.
*STSR 9.1* The cost of the first operational test stand must not exceed $200 excluding "consumables" and tools.
*STSR 10.1* If at all possible, the test stand should be completed within 3 months of formal launch as an exercise of agile design.
*STSR 11.1* Disposal of the spent Estes motors should conform to all local, state, and federal guidelines.
*STSR 11.2* Electronic waste items, including batteries and circuit boards, must also be disposed of according to all local, state, and federal guidelines.
*STSR 11.3* If the frame of the test stand is damaged beyond repair during operation, proper disposal/recycling guidelines must be followed for the materials used in its construction.
*STSR 11.4* Wherever possible, the design should make it as easy as possible to replace components which are consumable or relatively easy to damage.