M-Labs/saymapp
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

handle non-hardware developer failure

Browse Source
This commit is contained in:
Joe Britton 2019-01-18 14:10:39 -05:00
parent 09bbd5a520
commit 0316b04f23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pp.md
View File

@ -39,7 +39,7 @@ If shipment budget or hardware-flaw budget is exhausted the Developer may
- renegotiate contract terms for dependent task(s) with TPOC - renegotiate contract terms for dependent task(s) with TPOC
## Handling Failures Unrelated to Hardware ## Handling Failures Unrelated to Hardware
Hardware Developer task HT5 depends on tasks from Software and Gateware Developer and Integration and Timing Developer. If these dependencies are not met the Hardware Developer may after discussion with TPOC ship demonstration to UMD without successful completion of a subset of the following tests ST1, ST2, ST3 and ST4 as dictated by the missing dependency. Hardware Developer task HT5 depends on tasks from Software and Gateware Developer and Integration and Timing Developer. If these dependencies are not met the Hardware Developer may after discussion with TPOC ship demonstration to UMD without successful completion of a subset of the following tests ST1, ST2, ST3 and ST4 as dictated by the missing dependency.
# Definitions # Definitions
Let __TS-MTCA__ be a micro TCA crate configured as follows: Let __TS-MTCA__ be a micro TCA crate configured as follows: