# Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

### Archimedes

# Fulcrum SRS v0.6

28 June, 2011

- 1
- 2
…
- 17
- 18
- 19
- 20
- 21
- 22

UNCLASSIFIED//LES
UNCLASSIFIED//LES Page19
Theprimaryresponsibilityfordeveloping,maintaining,andexecutingunit testswillresidewiththe
developers.Theapplicationshouldhaveunittestsforallpublicmethodsofamodulewhereeveritis
reasonablypossibletodoso.Eachunittestshouldbeindependentofallotherunittestsandshouldtest
asinglespecificunitfor asinglespecificcondition.Theunittestsshouldberuninaregular,automated
fashionsuchasonsourcecodecommits.Theunittestsshouldalsoberunmanuallywhenever
necessary.
Theprimaryresponsibilityfordeveloping,maintaining,andexecutingthesystemtestswillresidewith
thedevelopers.Thesetestsaretoberunregularly,perhapsaftertheimplementationofeachuser
story.AtaminimumtheyshouldberunpriortoreleasetoIV&V.Theitems thatshouldbetestedand
anyspecializedinstructionsonhowshouldbedocumented;howeverth emajorityofthisleveloftesting
willbedoneinanad‐hocmanner.Thisleveloftestingserve sprimarilyasasmoketestpriortorelease
tothetesting/IV&Vteam.
Theprimaryresponsibilityfordeveloping,maintaining,andexecutingtheuseracceptancetestswill
residewiththetestingorIV&Vteam.Aformaltestplanofshouldbecreatedforthisleveloftesting .
Thereshouldbespecificacceptancetestspreparedforeachuserstoryincludingdetailssuchasatest
description,setup,instructions, andexpectedresults.Deviationsfromtheexpectedresultsshouldbe
reportedbacktothedevelopmentteam.
6.2.4 QUALITY
<TODOSomethinghereaboutcodingstandards,modularity,codecomplexity(e.g.cyclomatic
complexity),defectrate,etc.>

- 1
- 2
…
- 17
- 18
- 19
- 20
- 21
- 22