# 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
…
- 19
- 20
- 21
- 22

UNCLASSIFIED//LES
UNCLASSIFIED//LES Page21
8 APPENDIXB:RISKS
Thissectionidentifiesandquantifiesanyknownrisksthatmaybeassociatedwiththisproduct
developmenteffort.Thisisnotan enumerationofpossiblerisksin thedeploymentand/oruseofth e
productitself.
 Anychangeinkeypersonnel
o PossibleMitigation:Ensurethatsufficientdocumentationofeachphaseof thesoftware
developmentlifecycleiscreatedsuchthatitwouldbepossibleforanotherpersonof
similartechnicalexpertiseandba ckgroundastheindividualvacatingtheteamtofillthe
vacancyinareasonabletimeperiod.
 Thetimebetweentheacceptanceofthesoftwarerequirementsandthedeliveryofthe
implementationistoolong.Ifdurin gthedevelopmentperiodcustomerneedshavechanged
thenfeaturesmaybeimplemented thatarenolongernecessaryordoneinamannerthatisno
longeruseful.
o PossibleMitigation:Implementshortfeedbackcyclesmeasuringnomore30days.This
couldbeaSCRUMlikeprocesswhereproductteammeetswiththecustomerto
formallyagreetoafeature/bugfi xlistforthequarter.Internallyth eproductteamthen
divides this work into monthly sprints which produce completed product
fixes/enhancementsina30‐daytime‐box.Itisunknownwhetherformaltestingshould
beinvolvedat themonthlyorquarterlylevel.
 Thecustomersprioritizationchan gesoutsideofthisspecificeffort,eitherincreasingor
decreasingtheresourcesde dicat edtothisproductand/orincreasingordecreasingtheurgency
ofdeliveryofthisproduct
o PossibleMitigation:Again,useshortfeedbackcyclestoallowthischangeinpriorityto
bereacteduponassoonaspossible.Additionally,makesureallbugs andfeaturesare
welldocumentedandtrackedinabugtrackingsystem.Thiswillal lowtheproductteam
torespondtoapotentialincreaseinurgencyand/orresourcesontheprojectaswellas
provideacontinuouspausepointiftheurgencyand/o resourcesontheprojectare
suddenlyreduced.
 Dependenceonthird‐partysoftware.Purchasing,bugfixing,integration ,etc.
o PossibleMitigation:????




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