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

UNCLASSIFIED//LES
UNCLASSIFIED//LES Page18
o Thespecificrevisioninversioncontrolofthesourcecodethatwasusedtobuildthe
binarycanbeidentifiedusingtheversioninformation.
 Shallusebugortickettrackingsoftwaretotrackallfeatures,bugs,andprojectmilestones
 Shallmaintainaminimalsetofrequirementstostand‐upanewdevelopermachine.For
example,anewdevelopermachinemayrequireonlyanoperatingsystem,theproject
standardizedIntegratedDevelopmentEnvironment(IDE),versioncontroltools,andaworking
copycheckoutofthelatestsourcecodefromversioncontrolinordertocompileandrunthe
applications.
 Shallhaveallartifactsandrele vantprojectdatabackeduponare gularbasisinaccordancewith
theparentorganizationspolicies.
6.2.2 DOCUMENTATION
Theprojectshouldprovide allnecessarydocumentationfor eachstakeholderwhileminimizingthe
burdenofdocumentationdevelopmentandmaintenance.Theprimarygoalofthedocumentationisto
facilitatecommunicationandunderstandingamongthestakeholdersduringtheentiresoftware
developmentlifecycle.Thesecondarygoalistoassistthenecessaryknowledgetransfertoanew
individualorstakeholderwhomayb ebroughtonmid‐projectasanadditionalresourceorin
replacementofkeypersonnel.
Tomeetthisobjective,theproduct:
 Shallprovideasoftwarerequirementsspecificationatasufficientlevelofspecificityto
o Expressthecustomersneeds
o Allowthecustomertoprovideagreementtoasetofproductgoalsandfeatures
o Allowthedeveloperstoimplementanapplicationtothesatisfactionoftheagreedupon
requirements
o Allowthetesterstodevelopatestplantoverifythattheimplementationmeetsthe
customersrequirements.
 Shallprovideausersmanualwhich
o Describesthepurposeanduseoftheapplication
o Specifies th erequirementsandsupportedusesof theapplication
o Providesdetailedwalkthroughsonhowtousetheapplicationsufficienttotrainnew
users
o Providesaquickreferenceforreturningusers
o Enumeratesanyknownbugsorrisks
o Providessupportcontactinformation
 Shallprovidesourcecodedocume ntationofpublicAPIsfo rdevelopers
o Thisdocu mentationshouldbeautomaticallygeneratedfromthesourcecodeitselfas
muchaspossibletominimizerework andout‐of‐syncdocumentation.
6.2.3 TESTABILITY
Therearethreemaincategoriesof teststhatwillbeutilizedinthedevelopmentandmaintenanceofthis
product:unittesting,systemtesting,anduseracceptancetesting.

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