Environment Remote Sensing System

Software Development Plan - Group 4

AdamBlaine,CraigCabrey,PeterMikitsh,KristenMills
Page1of26

Table of Contents
Section1:Overview Section1.1:Assumptions Section2:Goals&Scope Section2.1:Inscope Section2.2:Outofscope Section3:HighLevelFunctionality Section3.1:Administration Section3.2:Monitoring Section3.3:SensorStations Section3.4:Sensors Section4:Deliverables Section4.1:Release1 Section4.2:Release2 Section4.3:Release3 Section4.4:Release4 Section5:ProjectOrganization Section5.1:Roles Section5.2:Structure Section5.2.1:ERSSApplicationServer Section5.2.2:ERSSStationServer Section5.2.3:ERSSSensorClients Section6:RiskManagement Section7:Scheduling&Estimates
Page2of26

Section7.1:ScrumMethodology Section7.1.1:FeatureEstimation Section7.1.2:Scheduling Section7.2:RUPMethodology Section7.2.1:SizeEstimation Section7.2.1.1:ApplicationServerSize Estimation Section7.2.1.2:StationServerSizeEstimation Section7.2.1.3:SensorClientSizeEstimation Section7.2.2:Scheduling Section8:Measurements Section8.1:User/customersatisfaction Section8.1.1:Howwillitbeused Section8.1.2:Whywasitchosen Section8.2:Numberofdefectsfoundduring development Section8.2.1:Usage Section8.2.2:Rationale Section8.3:Numberofdefectsfoundafterarelease Section8.3.1:Usage Section8.3.2:Rationale Section8.4:Numberofchangesorchangerequests Section8.4.1:Usage Section8.4.2:Rationale Section8.5:Documentationcompleteness/accuracy Section8.5.1:Usage Section8.5.2:Rationale
Page3of26

Section9:TechnicalProcess Section10:Conclusion Section11:Glossary

Page4of26

Section 1: Overview
ThisSoftwareDevelopmentPlanfortheEnvironmentRemoteSensingSystem(ERSS)will coverthefunctionality,platform,customers,schedule,anddevelopmentresponsibilityofthe system.Theprimarygoalofthesystemistoallowanonprofitenvironmentalorganizationto monitormigrationandbehavioralpatternsofanimalsthatareendangeredorprotectedspecies. Varioussensorstations,whicharepartofanationalnetwork,willbeplacedintheproximityof theareasbeingstudied.Statisticsfromsensorswillbesenttothesensorstationsonregular intervals.Administratorswillbeabletoviewthecollectedinformationandpermitusersat specificlocationstoviewspecificcollectedinformation.Userswithappropriateversionswillbe abletogeneratereportsandmapsoftheinformation. Customersofthesystemincludethenonprofitenvironmentalgroup,theDepartmentof EnvironmentalConservation(DEC)andtheNationalParkService(NPS),anagencyoperating withintheDepartmentoftheInterior(DOI).

Section 1.1: Assumptions

Assumption Connectivity Description Thissystemassumestheexistenceofa connectionbetweenthemainapplication serverandallstationsthattheapplication serverisconfiguredfor.Thestationsare capableofbufferingdatauptoacertain extent,butafterthisthresholdisreacheddata maybelost. TheERSSassumesthatallsensorhardware willworkasintendedandisnotdesignedto handleordetectanytypeofhardwareerror. Furthermore,theERSSdoesnothaveany safetyalertsystemsbuiltinasaresultof hardwarefailure. TheERSSassumesthatallsystemswillbe upandonlineatalltimes.Anypotentialpower issuescausedbyhumanerrorornatural causesshouldbetakencareofviaadevices suchasauniversalpowersupply. TheERSSapplicationandstationsoftware wasdesignedtorunonPOSIXcompatible operatingsystem.TheERSSassumesthe useofthistypeofoperatingsystem. Page5of26

HardwareMalfunctions

PowerInterruption

SoftwareEnvironment

TeamSize

Weareassumingthattheteamsizewillbe largeenoughtoaccommodatethebreadthof theproject. Weareassumingthatthereisasignificant enoughbudgettobeabletosupportthe projectinitsentiretyrangingfromuseof technology,toemployees,toreleaseand maintenanceoftheERSS. Weareassumingthattherewillbeenough timegivenandscheduledsuchthatthe projectwillbeabletobeaccomplished reasonably. Giventhatthisisagovernmentprojectthere willbeexceedingconstraintsinvolving security,scalability,deadlines,andbudget.

Budget

Schedule

GovernmentConstraint

Section 2: Goals & Scope

Section 2.1: In scope
TheEnvironmentRemoteSensingSystem(hereinreferredtoastheERSS)willtargeta numberoffeaturesandfunctionalitypoints.ThecorefunctionalitythatisdeliveredbytheERSS istoprovideamechanismbywhichlargeamountsofdatacanbecollectedfromavarietyof remotelocations.Toachievethis,theERSSwillbedesignedasahierarchicalsystem.Thecore collectioncomponentwillberealizedasanapplicationonacentralserver.Fromthere,each remotelocationwillfeedthecentralapplicationserverwithinformationthroughastandard protocoldevelopedfortheERSS.WhiletheERSSwillprovideagenericsolutionforthestation thatwillconnecttothecentralapplicationserver,theclientwillbeabletomodifythe implementationtomeettheirspecificneeds.SeeSection3:HighLevelFunctionalityformore specificdetailsontheproductsfunctionalityrequirements.

Section 2.2: Out of scope

TheERSSfocusesonthesoftwareimplementationmorethanthehardware implementation,soanyhardwaredesignwillbeoutofthescopeoftheERSS.Thisinclude everythingfromcommunicationarraysonsensorstationstothesensorimplementations themselves.Finally,theinterfacingbetweenthehardwareandsoftwareisalsoconsideredoutof scope.TheERSSusesstandardprotocolstocommunicatewithallclientsanddevices,sothe ERSSdependsonthosedevicesproperlyimplementingstandardprotocols.

Page6of26

Section 3: High-Level Functionality

Section 3.1: Administration Thesystemshouldrunfromacentralapplicationserver Applicationserverwillgrantaccesstostationstodifferentusersdependingon
accessprivileges

Managerscansetprivilegesforusers Throughtheinterface,usersareabletofiltertheincomingdatafromthedifferent
stationstowhichtheyhaveaccess

Newstationscanbeaddedasclientstotheapplicationserver Criticaleventswillbereportedtousersdependingonthelocalityoftheevent Sensorissueswillbereportedtothelocalstationtowhichthesensorhas

beenadded

Stationconnectivityissueswillnotifyusersofthecentralserverofthe
issue

Eachstationshouldactasasensordatacollectionserver Sensorsmaybepolledforupdatesonacertaintimeinterval(configurable) Eachsensorcanbeaddedasaclienttoitslocaldatacollectionserver Sensorsshouldbesetupforthetypeofdatacollectiontheysupport(GPS,audio,

images,etc)

Section 3.2: Monitoring

Monitoringofsensorstationsshouldbedonethroughaperuserbaseduserinterface Whenauserlogsintothesystem,onlythestationsheorshehasaccesstowill bedisplayed AUsermayviewanyhistoricaldataassociatedwiththestationsthatthey currentlyhaveaccessto Thestatusofthemonitoringstationstheuserhasaccesstowillbe updatedonacertaintimeinterval(configurablefromonlythemanagement interface) Auserwillbeabletoexportcollecteddatainavarietyofforms Rawdataexportedwillbesupported Generationofreportswillalsobesupported(charts,timeseries,etc) Themanagementinterfacewillhaveconfigurableoptionsthatrelatetothemonitoring system Alimitcanbesetoftheamountofhistoricaldataisretained(weeks,months, years,etc) Alimitcanbeplacedonhowfarbacktheuserisallowedtogothroughhistorical Page7of26

data(onlywhentheiraccountwascreated,sometimeperiod,ornorestriction) Optionssuchashowoftennewdatashouldberetrievedfromtheclient monitoringstationswillalsobeconfigurablefromthemanagementinterface Theuserandmanagementinterfacesthemselvesmaybeimplementedthroughvarious meanssuchasnative(andmobile)applicationsandawebinterface Restrictionsmaybeplacedonhowtheapplicationcanbeaccessed(i.e.auser mayberestrictedtoonlyusingtheapplicationinstalledoncompanycomputers)

Section 3.3: Sensor Stations

MustbeabletobehookedtoanetworkedPC Antennasandhardwaredeployedbyathirdparty Varietyofhardwaresupportedifhardwaresupportsstandardprotocols PCcanbenetworkedthroughalandlineconnection,cellularconnection,etc Connectedtoanationalgrid. ThisallowsforDECtorunandmonitorthestatusofallofthedatainthegrid Softwareisconfiguredtoaccess(andauthenticatethrough)central authenticationserverwhichinturnallowsaccesstoallconfiguredsensor stations

Section 3.4: Sensors Sensorsmonitorinformationincludingbodytemperature,GPSlocation,gyroscopedata,

audio,andvideo.

Theabilitytomonitoradditionaltypesofinformationovertimewillbesupported. Sensorscollectinformationonconfigurable,regularintervals. Sensordataistransmittedtothestationonitsownconfigurable,regularinterval. Collecteddataisalsobufferedforonelongdataburstinthecaseofaweaksignal Burstwilloccurifandwhenthesensorcomesbackintorange Sensorsarefirstpairedwithsensorstationstosetupcommunicationwiththesensor

station

Pairingwiththestationincludesidentifyingthetype(s)ofinformationthatthe
individualsensorcollectsandwhichprotocolitusestorelaythatdata

Page8of26

Section 4: Deliverables
Section 4.1: Release 1
Forrelease1wewouldlikethefollowingfeaturestobeimplemented: Setuserprivileges Addingnewstations Logintothesystem Restricthowauseraccessthesystem Retrieveinformationfromthesensors Pairsensorswiththesensorstations

Wealsoplantohavealargeportionofthedocumentationdonewiththisrelease.

Section 4.2: Release 2

Forrelease2wewouldlikethefollowingfeaturestobeimplemented: AllowtheDECPersonneltoaccesstheinformationcollectedfromallofthestateparks Allowtheusertoviewhistoricaldataofthestationstheyhaveaccessto Allowforexportforrawdata Limithowfarbackpersonnelcangobackinhistoricaldata Configurehowoftendataisretrievedfromthementoringstation

Section 4.3: Release 3

Forrelease3wewouldlikethefollowingfeaturestobeimplemented: Filterincomingdatafromstationsauserhasaccessto Notificationofcriticalevents Getsensorupdatesatconfigurabletimeintervals Configurewhichtypeofdataasensorcollects Theabilitytogeneratereports Sethowlonghistoricaldataisretained

Section 4.4: Release 4

Forrelease4wewouldlikethefollowingfeaturestobeimplemented: Maximizeuptimeofsystem Onlineconfigurationofstations(includingtheabilitytoaddmorestations) Automateddatabasebackupsystem AddInterfaceforextendingoraccessingtheERSSthroughpluginarchitecture Page9of26

Section 5: Project Organization

Section 5.1: Roles
ThedevelopmentoftheERSSwillmakeuseofsubteamstofocusonthecompletionof individualcomponentswithinthesystem.Thefollowingtabledescribesthedifferentrolesthat willbeutilizeandtheiraccompanyingdescription. Role ProjectManager Description Responsiblefortheoverallprogress,quality, andcompletionoftheERSS.Allteamleads reporttotheprojectmanagerforprogresson individualcomponents. Responsiblefortheteamsrespective progress,quality,andcompletionofa componentoftheERSS.Theteamleadis responsibleformanaginghisownteamand settingthegoalswithinthescopeoftheteam. Responsibleforthetechnicalaspectof architectingtheERSS.Overallsystemissplit intoanumberofcomponentsandfromthere teamsarecreatedbasedontheidentified components. Representsthecustomerandcaninteract withtheprojectmanagertogivefeedback basedontheprojectsperformanceaswell asaddorremovefeaturesfromtheoverall project.Alsoresponsibleforensuringall appropriatemeasuresaretakentomitigate delaysofprojectoccurringdueto bureaucracy. Responsiblefordevelopingandexecuting integrationtests.TestLeadmust communicatewitheachteamstestertokeep trackofoveralltestprogress.Continuous integrationisperformedandfeedbackisgiven toeachteamtomitigateintegrationproblems towardstheendoftheproject. Actsasanimplementerfortheteams assignedcomponent.Workswiththeteam leadandtestertoensurerequirementsare beingmetandthatthetestsuiteisdeveloped Page10of26

TeamLead

ProjectArchitect

CustomerLiaison

TestLead

TeamDeveloper

toaccuratelytestthedevelopedcomponent. TeamDesigner Workswiththecomponentassignedtothe teamtodevelopasoftwaredesignthatmeets thegoalsofthecomponentwhileworking withintheconstraintsimposedbytheoverall project.Workswiththeprojectarchitectto ensurethattheproposeddesignfitsand workswellwithintheoverallsystem. Responsiblefordevelopingandexecutinga testsuitethatcoverstheteamsassigned component.Testerisalsoresponsiblefor reportingbreakagetotheTeamLeadsothat communicationremainsfluidbetweenthe wholeteamandtheprojectmanager. Responsibleforintegratingany subcomponentswithintheteams componentasaresultofthecomponents softwaredesign.Workswiththetesterand teamdeveloperstoensurethecomponentis successfullyintegratedcontinuouslyand passesalldevelopedtests. Ageneraloutsideresourcethatmaybeuseful forthedevelopmentofcertainpartsofthe ERSS.Contractorsarenotresponsiblefor thecompletionofcomponentsandteam leadsthatutilizesaidresourcesare responsibleformonitoringthestatusof contractorswork.

TeamTester

TeamIntegrator

Contractor

Section 5.2: Structure

Thestructureoftheprojectsresourcesisbasedoffofhowtheprojectisdesignedfroma technicalaspect.Becauseoftheuseofalargelyclientserverdesign,theoverallproject developmentstructurewillbesplitintothreemajorteams. Eachteamwillbecomposedofatleastthefollowing: TeamLead TeamDesigner TeamDeveloper(s) TeamTester TeamIntegrator Contractorifnecessary Page11of26

Section 5.2.1: ERSS Application Server

Withinthisteam,therewillbethreemoreteamscreated: ERSSWebInterfaceandManagementTeam BackendandDatabaseTeam DataCollectionandStationConnectivityTeam

Section 5.2.2: ERSS Station Server

Withinthisteam,therewillbefourmoreteamscreated: StationInterfaceandManagementTeam DataBufferingandBackupTeam ERSSConnectivityTeam SensorConnectivityandCollectionTeam

Section 5.2.3: ERSS Sensor Clients

Withinthisteam,therewillbethreeteamscreated: HardwareInterfacingTeam PowerManagementTeam StationConnectivityTeam

Additionally,theHardwareInterfacingTeamwillbemakinguseofcontractorsthatarefamiliar withthehardwarethatisbeingusedforthecollarstobeplacedonthetrackedanimals.These contractorswillhelpimprovethequalityandspeedupthedevelopmentprocessandlearning curveofunderstandingthehardwarecomponentsbeingused.

Page12of26

Section 6: Risk Management

ID 1 Description Imprecisetime estimation Type Schedule P 0.7 L (weeks) 4 E 2.8 First Indicator Goalsare notbeing metin smaller deadlines. Mitigation Approach Spendslightly moretimewith schedule planningand timeestimation suchthatitwill beascloseas possible. Makescope slightlybroader inordertoallow forexpected change. Haveregular teammeetings, withtransparent goals accessibleatall times. Activelyinvolve thecustomerin the developmentof theproposal.

Projectscope Budget expansion/featur ecreep

0.3

0.9

Declared scopeis very specificand rigid Thereis redundancy inwork across team members Thereis littletono feedbackor the feedback lagsbehind the proposal. Moretimeis spent researching technologie sthan contributing tothe project. Initial deadlines

Lackof communication inteam.

Operational 0.6

1.2

The requirements elicitation processisslow whenworking withthe government. Relianceupon silverbullets

Slow Environme nt

0.2

0.8

Technical

0.3

0.9

Identifyall technologies thatshouldbe investigated beforehandand setatimeframe fortheresultsof the investigation. Involveexperts outsideofthe Page13of26

Productis Largerthan

Schedule

0.4

2.8

Estimated

setbythe schedule aremissed.

projecttohelp reevaluatethe scopeandsize oftheproject andreevaluate thescheduleas aresult. Identifyall properchannels for communication beforethestart oftheproject. Havea designated teammember responsiblefor ensuringall bureaucratic deadlinesare met. Identifyall current regulationsand regulationsthat arecurrently pendingthe legislation process. Starttheproject withwell definedprocess

Toomuch Process formality (bureaucratic adherenceto softwarepolicies andstandards) resultsin unnecessary, timeconsuming overhead.

0.3

1.5

Whenit feelslike theproject isstartingto tends towards thrashing ratherthan productive work.

Product dependson government regulations, whichchange unexpectedly.

External Environme nt

0.15 6

0.9

Newbill going through which affects project scope. Thereare highlevels ofthrashing whileno processis initially established Designof theproject didnot consider integration ofmodules, orno thoughtwas putinto integration.

Processis appliedtoolate andtheproject stalls.

Process

0.2

0.4

10

Difficultproject modules integration

Technical

0.3

0.3

Haveadesign thatthoroughly plansforease ofintegration andisfocused onmodularity.

Page14of26

Thereare lotsof modules involved thatare complex.

Page15of26

Section 7: Scheduling & Estimates

Section 7.1: Scrum Methodology
Section 7.1.1: Feature Estimation
ThefollowingtabledetailshowScrumFeatureEstimationisimplemented.Theuserdescription tableidentifiesallactorsinthesystem.Followingtheuserdescriptiontableistheestimation table,whichisalistoffeatureswithassignedstorypoints. User User DEC Personnel NationalPark Personnel NationalPark Managers Description Anyroledetailedinthesystembelow. ThepeopleattheDEC(DepartmentofEnvironmentalConservation) HeadquartersinWashington. Thepeopleatthenationalparkswhoinstallthesystemandmonitoritlocally. Thepeopleatthenationalparkswhohaveadminprivileges.

id 00

StoryPoints 4

User AsaDEC Personnel,

Action Iwanttoaccess theinformation collectedfromall NationalPark stations Iwanttobeable tosetuser privileges, Iwantfilter incomingdata fromstationthatI haveaccessto, Iwantaddnew stations,

Goal SothatIcangenerate nationwidestatistics.

Priorities Medium

01

Asa National Park Manager, AsaUser,

SothatIcanmanagemy personnelsaccessof systemfeatures. SothatIcangenerate reports.

High

02

Low

03

Asa National Park Manager,

SothatIcancollect informationfrommore nationalparksas necessary.

High

Page16of26

04

AsaUser,

Iwant notificationsof criticalevents, Iwanttoget sensorupdates atconfigurable timeintervals, Iwantto configurewhich typeofdataa sensorcollects, Iwanttobeable tologintothe stationsthatI haveaccessto, Iwanttoview historicaldataof stationsIhave accessto, Iwanttoexport rawdata,

SothatIcanrespondto them. SothatIhavechoicein thegranularityinthe generatedreports.

Low

05

AsaUser,

Low

06

Asa National Park Manager, AsaUser,

SothatIcanadapttonew Low needsovertime.

07

SothatIcanuseit.

High

08

AsaUser,

SothatIcangenerate reportsofhistoricaldata.

Medium

09 10 11

2 6 3

AsaUser, AsaUser, Asa National Park Manager, Asa National Park Manager, Asa National Park Manager,

SothatIcanplaywithit.

Medium Low Low

Iwanttogenerate SothatIcandomyjob. reports, Iwanttosetfor howlong historicaldatais retained, SothatIcanmanage spaceconstraintsofdata collected.

12

Iwanttoplace SothatIhidethesecrets. limitsonhowfar mypersonnelcan gobackin historicaldata,

Medium

13

Iwantto SothatIcancontrol Medium configurehow powerconsumptionwithin oftendatais thesystem. retrievedfromthe monitoring station, Iwantrestrict howausercan accessthe Sothatmypersonnelonly High accessthesystemon authorizedmachines. Page17of26

14

Asa National Park

Manager, 15 5 AsaUser,

system, Iwantretrievethe SothatIcanmonitorit. informationfrom sensors, High

16

Asa National Park Manager,

Iwantbeableto SothatIcanretrievedata High pairasensorwith fromit. asensorstation,

Section 7.1.2: Scheduling

UserStoryID 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 StartDate (weeks) 7 1 13 1 15 16 17 2 7 8 19 20 9 10 3 4 5 Enddate(weeks) Duration(weeks) 12 4 18 2 19 23 21 5 14 11 28 24 14 15 10 11 12 5 3 5 1 4 7 4 3 7 3 9 4 5 5 7 7 7 Page18of26

Section 7.2: RUP Methodology

TheRUPMethodologyrequirescertaintools(Rational)tobeusedanddocumentationtobe availableforthemethodologytoworkasintended.Additionally,RUPcallsfortheuseofthe COCOMOmodeltoestimatethesizeandeffortofthesystemintermsofpersonmonths.

Section 7.2.1: Size Estimation

Section 7.2.1.1: Application Server Size Estimation ModuleName Management Interface Connectivity Subsystem Database Subsystem Authentication Subsystem Total SLOC 15,000 12,000 8,000 5,000 40,000 PersonMonths 10.6159 9.72683 8.29743 6.90126 35.54142 No.ofPeople 6 5 4 3 18 Productivity 1412.97 1233.70 964.15 724.51 4335

Section 7.2.1.2: Station Server Size Estimation ModuleName SLOC PersonMonths 5.64890 6.90126 5.98607 4.81872 9.05591 No.ofPeople 2 3 2 1 4 Productivity 531.08 724.51 584.69 415.05 1104.25

StationInterface 3,000 Connectivity Subsystem LocalDatabase Subsystem Authentication Subsystem Sensor Collection Subsystem Total 5,000 3,500 2,000 10,000

23,500

32.41086

12

2828.5

Page19of26

Section 7.2.1.3: Sensor Client Size Estimation ModuleName SLOC PersonMonths 5.64890 No.ofPeople 2 Productivity 531.08

Sensor 3,000 HardwareBridge Subsystem Station Connectivity Subsystem Power Management Subsystem Total 4,000

6.32324

632.59

2,000

4.81872

415.05

9,000

16.79086

1578.72

Section 7.2.2: Scheduling

ModuleName ManagementInterface ConnectivitySubsystem Database Subsystem AuthenticationSubsystem StationInterface ConnectivitySubsystem LocalDatabase Subsystem AuthenticationSubsystem StartDate April2013 May2014 August2013 January2014 May2013 September2013 April2013 February2014 Duration(ManMonths) 10.6159 9.72683 8.29743 6.90126 5.64890 6.90126 5.98607 4.81872 9.05591 5.64890 6.32324

SensorCollectionSubsystem October2014 SensorHardwareBridge Subsystem StationConnectivity Subsystem September2014 June2014

Page20of26

PowerManagement Subsystem Total

February2014 N/A

4.81872 54.7

Page21of26

Section 8: Measurements
Wetookthefollowingmetrics:

Section 8.1: User/customer satisfaction

Section 8.1.1: How will it be used
Itwillbeusedtoknowwhetherwemettherequirementsthatthecustomerpresenteduswith.

Section 8.1.2: Why was it chosen

Wechoseuserandcustomersatisfactionasametricbecauseitisimportanttodesignthe productinawaythatpleasesthecustomerandinawaythatisusablefortheuser.Thisisone ofthemostimportantmetrics.

Section 8.2: Number of defects found during development

Section 8.2.1: Usage
Wewillusethistomeasurehowattentiveweweretodefectsinthedevelopmentstageand catchingthemearlyonratherthanlateron.

Section 8.2.2: Rationale

Wechosenumberofdefectsfoundduringdevelopmentbecausethatisagoodmeasureof qualityandwhetherdevelopersaretestingtheircodebeforecommitting.

Section 8.3: Number of defects found after a release

Section 8.3.1: Usage
Wewillusethistomeasurehowattentiveweweretodefectsinthedevelopmentstageand helpingusinthefuturesowedonthaveasmanypostreleasedefects.

Section 8.3.2: Rationale

Wechosenumberofdefectsfoundafterareleasebecauseitsimportanttokeeptrackofthis information.

Section 8.4: Number of changes or change requests

Section 8.4.1: Usage
Itwillbeusedtoseehowwellwesticktorequirementsordeviatefromthem.

Section 8.4.2: Rationale

Wechosethisthisbecauseitsusefulinformation

Section 8.5: Documentation completeness/accuracy

Page22of26

Section 8.5.1: Usage

Tomeasurehowwellourdocumentationiswritten.

Section 8.5.2: Rationale

Itisimportanttohavegooddocumentation.Someasuringthecompletenessandaccuracyof ourdocumentationisgoodsothatyourdocumentationisgood.

Page23of26

Section 9: Technical Process

WehavechosentheScrumagileprocessmethodologybecauseitwillallowformorecustomer communicationthroughoutthedevelopmentoftheproject.Becauseoftheprojectslargesize,it wouldbepossibletodeliverthewrongproductduetolackofcommunication.Scrumwillmitigate thisrisk,leadingtothehighestqualitydeliverablebeingproduced. WehavealsochosenScrumforitsabilitytopromoteselforganizationandinnovationonthe project.Teamscanselecttheworktheywanttocomplete,offeringgreaterflexibilityand improvingrelationsbetweenmanagersanddevelopers.Additionally,asmanyteamswillbe workingontheproject,Scrumfreeseachteamtodevelopacommunicationstrategythatworks mosteffectivelytoaccomplishwork. Lastly,Scrumwillallowthedevelopmentteamtodeliveronlythefeaturesofhighestbusiness valuefirst.Bypreventinganyunnecessaryfeaturesorgoldplatingofrequirements,wewill achievegreaterefficiencyinthecompletionofwork.Thiswillleadtodeliveringafullyfunctional deliverableearlierthanwithotherprocessmethodologies.

Page24of26

Section 10: Conclusion

TheERSSisalargesoftwaresystemthatwillbeplanned,designed,documented,implemented, anddeliveredusingtheprocessesandresourcesoutlinedinthisdocument.TheSoftware DevelopmentPlanfortheERSShelpstodocumentthemajordecisionsmadeandthe associatedreasoningforfuturereference. Afterlookingattheprovidedrequirements,majordecisionsweremadetogoaboutincorporating therequestedrequirements.TheERSSasdesignedwillsupportallrequirementsaspresented. Additionally,itwillsupportfeaturesthatmakethemaintenanceandusabilityoftheERSSbetter. Forexample,anautomatedbackupsystemwillbeimplementedandwillbeconfigurableto assistwithpreservingallcollecteddata. Usingtherequirementsasabasisforthesystemarchitecture,aclientservermodelwas decidedupon.ThemainERSSapplicationresidesonacentralserveratthepreferenceofthe customer.Theapplicationservermusthaveaccesstoallthedifferentstationsthathavebeen deployedviasomecommunicationmeans. AsindicatedinSection9,thedevelopmentofthissystemwillutilizetheScrumagile developmentprocess.ThefactorsthatwentintomakingthedecisiontouseScruminvolve analysisofdevelopmenttimeandcost.Scrumallowsthecustomertobehighlyinvolvedwiththe projectandisabletoseetangibleresults,leadingtoamoresatisfiedcustomerandahigher qualityprocess. Finally,thesoftwaresystemwillbeaccompaniedbycomprehensivedocumentationthatoutlines howtousethesystem,howthesystemisstructured,anddocumentationonhowtoextendthe system.Theincludeddocumentationrangesfromtechnicaldocumentstocustomeroriented documentationsuchasarequirementsdocument.

Page25of26

Section 11: Glossary

Term DEC NPS ERSS RUP DOI Definition DepartmentofEnvironmentalConservation NationalParkService EnvironmentRemoteSensingSystem RationalUnifiedProcess DepartmentoftheInterior

Page26of26