| [ Discussions ] | |
| Function tree and product tree | |
| [ My Settings ] | |
| Question to the ECSS Helpdesk | |
| Register | |
| Why register and login | |
| Log In | |
| [ Search ] | |
| Glossary of Terms | |
| Function tree and product tree |
|
We have been taking a look at the ECSS-M-ST-10C (Rev. 1) and we have several questions about how ECSS standards recommend to evolve a function tree into a product tree in a proper manner. Taking into account what we have read in that standard, we would be very pleased if somebody could give us further clarifications concerning the next issues:
* We use to develop a system-level function tree as a response to a SRD (System Requirements Document), and, afterwards, we use to include the functions identified in the function tree as part of the system-level technical specification (a different document from the SRD); is this a proper manner? (Phase A)
* The technical requirements specification (to be released as an output of the PRR), shall include only the functional requirements identified in the product tree or shall also include any other requirement derived either from the mission statement (usually labeled MRD) or from the SRD?
* Who is the responsible for identifying which is the set of product tree items (deliverable parts) that will implement each subsystem? (Phase B, SRR delivery)
* Will the customer of the proper level have to develop a requirements specification for each deliverable item? (Phase B, PDR delivery)