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

clarify Hardware Developer option if dependency delivery is slow

Browse Source
This commit is contained in:
Joe Britton 2019-01-18 15:02:29 -05:00
parent a69b34a1fe
commit a1f5f2cd5d
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
pp.md
View File

@ -38,8 +38,11 @@ If shipment budget or hardware-flaw budget is exhausted the Developer may
- cancel dependent task(s) and receive payment for up to 50% task cost
- renegotiate contract terms for dependent task(s) with TPOC
## 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 Dependency Resolution
Hardware Developer task HT5 depends on deliverables from Software and Gateware Developer and Integration and Timing Developer. Two provisions are forseen to account for slow or failed delivery of dependencies by other Developers.
- If critical dependencies for HT5 are delayed beyond April 20, the scope of work for HT5 can be renegotiated with TPOC.
- If other Developers provide notice that HT5 dependencies will not be supplied, Hardware Developer may ship demonstration system to UMD without successful completion of a subset of tests ST1, ST2, ST3 and ST4.
# Definitions
Let __TS-MTCA__ be a micro TCA crate configured as follows: