Requirements
Here is the GENSO requirements tree. It's based on the old G-NET Requirements Tree. It is broken down by workpackage. All of the unique identification numbers are the same, but we're breaking with tradition here.
Requirement Tree Image
The structure of the requirement tree is as follows. The editor who is responsible for writing the requirements is written in green and the authority who is in charge of making sure the requirement is consistent is written in red.
Branch Managers
The branch manager is responsible for both writing subsystem requirements with sys and being an authority on component requirements which are written by the developers as stated by the image above.
| SubSystem | Branch Manager |
| GSS | Bjarke |
| HAL | Johan |
| MCC | Jakob |
| AUS | Bastian |
| UAI | Sandra |
GENSO System Requirements
New requirements system here: http://truc.genso.org/login.php
A - Interface Control (Windows)
B - Interface Control (Linux)
C - Ground Station Server
D - Mission Control Client
E - Authentication Server
F - Hardware
G - System Engineering
H - Infrastructure
I - Administration
J - Review and Testing
Suggestion for new requirements that should be added when migration to the new TRUC is completed.
Attachments
- UpdatedReqTreeOrg.jpg (127.0 kB) -
The Req Tree Organization
, added by D_J_CalPoly_Jason on 03/30/08 14:46:56. - UpdatedReqTreeOrg.2.jpg (29.0 kB) -
diagram of replaced picture
, added by D_J_CalPoly_Bryan on 03/30/08 15:55:12.
