FinalCapstoneReport

Team:CarlosEspinoza|MicahIriye|GregGreenleaf|TylerNicholson
Client:RickDawson,CSUMBOutdoorRecreation
Advisor:Dr.YoungJoonByun

TableofContents
Abstract
ExecutiveSummary
ProjectDescription
2.1Background
2.2ProblemDescription
2.3TargetAudience
2.4EnvironmentalScanReviewofProjectsSolvingSimilarProblems
SolutionDescription
3.1ProjectDescription
3.2Goal
3.3OtherPossibleSolutionsandTheirDifferences
Methodology
5.1ImplementationPlan
5.2Resources
5.3Expertise
ChangesintheProject
DescriptionofProjectDeliverables
BudgetandTimeline
Evaluation
6.1FunctionalityTesting
6.2UsabilityTesting
6.3EvaluationPlan
CollaborationStatement
FinalDocumentation
AdvisorSignoff

1of19

Abstract

WenoticedhowinefficientitwasthatCSUMBsOutdoorRecreation(O.R.)centerwasusing
handwrittendocumentsandimpracticalsoftwarelikeGoogleSpreadsheetstomanagethedaily
grindoftheirorganization.Themostimportantpainpointstoaddresswerelackofbudgetfor
existingsoftwaresolutions,timewastedusinginefficienttools,andcomplexityfornontechnical
usersandstaff.Wedevelopedanopensourcesoftwaresolutiontoaddressthoseconcernsusing
industryleadingframeworksthatmadeitsimpleenoughforournontechnicalaudience,yet
powerfulenoughtowelcomethemorecomplexcontributionsofourdeveloperbase.

ExecutiveSummary

OurprincipalclientisCaliforniaStateUniversityMontereyBaysOutdoorRecreation(O.R.)
program.OutdoorRecreation,aswellasmanyothersmallbusinesses,nonprofits,schools,and
projects,currentlyrelyoncumbersomespreadsheetsandhandwrittendocumentsintheirnormal
affairs,addingbothcomplexityandinefficiencytothebottomline.Onesuchexampleishowthe
O.R.processestheirrentalforms.TherentersfilloutamultipageGoogleFormwhichis
submittedintoamulticellGoogleSpreadsheet.Lookingupanythingrequiresmanuallyscrolling
throughallsubmissions.Beforetoolong,searching,transforming,adding,removing,and
deletingrecordscanbecomeunwieldyandtheirisnoconvenientorusefullinkbetweenthefront
endoftheiroperationanditsbackend.

ThesolutiontotheproblemisCERSanopensourcemanagementtoolfornonprofitsand
smallbusinessesprovidingasimple,modularizedsystemtomanageassets,events,services,and
pointofsale.Thesystemutilizesacustom,RESTfulAPI,LaravelwithComposeronthe
backend,Ember.jswithBootstrapandBoweronthefrontend.Gruntistheprojecttaskrunner
andGitispoweringtheversioncontrol,makingthiswholeprojecteasytoupdate.Thesoftware
wouldfunctionsimilartoplatformslikeDrupalorWordPress,whichmanyusersmayalreadybe
comfortablewith.Whatsetsourproductapartistheeaseofuseandsimplicityfortheless
technicallyinclinedoperators,thepowerfulAPIfordevelopercontributions,andtheopensource
pathwevedecidedtotake.

ActiveNetwork(http://www.activenetwork.com/),RentMaster(http://www.rentmaster.net/),
Square(http://squareup.com/),andWaspBarcodeTechnologies(http://www.waspbarcode.com/)
arecurrentlyofferingsimilarsoftwaresolutions.Noneofwhichareopensource,nortargetedat
ourspecifictargetsetofproblems.

2of19

ProjectDescription
2.1Background
CSUMBOutdoorRecreationoffersavarietyofservicestostudentsthatincludeoffcampus
eventssuchasbiking,camping,kayaking,andclimbing.Theyalsoofferequipmentrental/repair.
Inordertooffertheseservices,theyhaveaninternalrequirementtomanagetheiremployeesand
volunteersandkeeptrackoftheirinventory.RickDawson,theseniorcoordinatorforleadership
developmentandstudentrecreationatCSUMB,approachedusinFebruary,recognizingtheneed
tofindasolutiontomanagingthemanymovingpartsoftheirorganization.

2.2ProblemDescription
Currently,theysufferfromanineffectivemanagementsystemusedtokeeptrackoftrips,
equipmentparts,services,andrentals,forcingstafftoutilizescatteredGooglespreadsheetsand
handwritteninvoices.Thisproducessecurityissues,timeinefficiency,inaccuraterecord,and
bookkeepingwhichresultsin,studentsbeinglesswillingtousetheservice.Thelackofan
allinclusivemanagementsystemhasleadtoadeclineinuseandhadafinancialimpacton
CSUMBOutdoorRecreation.Ratherthanfocusingontheirmaingoalofofferingquality
servicestothestudentsofCSUMB,theyhavefoundthemselvesstrugglingtomeatalloftheir
responsibilities.

2.3TargetAudience
ThisproblemhasbeenfoundtoextendfarbeyondthebordersofCSUMB.Smallbusinesses,
nonprofitorganizations,andcentersthatoffersimilarresourceslikeCSUMBOutdoor
Recreationstrugglewiththesamelackofmanagement.Thesolutionsthatareofferedforthese
smallbusinesseseitherhaveaninitialpricetagthatisfarmorethantheirbudget,takea
percentageperusertransaction,oraretoodifficulttouse.

2.4EnvironmentalScanReviewofProjectsSolvingSimilarProblems
WaspBarcodeTechnologiesisonesuchmanagementsystemoptionforsmallbusinessesthat
haveaninitialcost.Thesoftwarethattheyofferisintuitive,muchlikenavigatingWindowsfile
systems,andtherearetutorialsandtrainingclassesavailable.Theirdownfallisthatthe
equipmentneededtoutilizethefreesoftwareissoldthroughthirdpartyretailers,causingeach
piecetobemoreexpensive.Thesoftwareisalsoprimarilyforinhouseassetmanagementand
notforwhenassetsarebeingrentedoutofthebusiness.Italsooffersnofunctionalityforevent
management.

CSUMBOutdoorRecreationhaspreviouslylookedintomanagementsystemsinthepastand
foundonecalledActiveNetwork,whichisofferedasaSaaS.Ithasassetmanagementoptions
availableaboveandbeyondwhattheclienthasrequestedfromthiscapstoneproject.Active
3of19

Networkhasuser,asset,andeventmanagementsystemsforusesfromracestoschools.Whileit
offersmanyoptionsandanintuitiveuserinterface,ithasapriceof$20,000forayearofservice.
NotonlydoestheSaaShaveupfrontcost,thereisalsoapercentagecostperusertransaction
donethroughthesystem.

Squareisanupandcomingservicethatoffersvarioussolutionsforsmallbusinesses.Theyoffer
managementsolutionsbasedaroundtheiroriginalpointofsales(POS)systemandpayment
gateway.Asofthiswritingtheirrateisbasedonindividualtransactions.Whileatfirstglance,it
appearsthatSquarecouldbeasilverbulletforsmallcompaniesandnonprofits,acloser
examinationrevealsseveralconstraintsthatpreventthemfrombeinganoptionforCSUMB
OutdoorRecreationandothersimilarbusinessesandorganizations.Firstly,Square
is
the
paymentgateway,andassuchthereisnooptionforuserstochooseanother.Thismeansthereis
noseparationfromthemanagementsolutionstheyofferandthewaytheytakepayments.
Secondly,thereisnosystemforeventmanagement,anintegralpartofOutdoorRecreation.
Finally,becauseSquareisnotopensource,usersarelimitedtotheoptionsandservicesthey
provide,andkeepusersfrombeingabletoaddanyadditionalfeatures(likeaneventssystem).

SolutionDescription
3.1ProjectDescription
Thisprojectwillbeaccomplishedbythedevelopmentofageneralpurposemanagementtool,in
theformofawebapplication,thatwillbeabletobehostedbytheclient.Lateriterationsmay
includedeployabilityintheformofaSaaS(SoftwareasaService).Userswillhavetheabilityto
enabletimekeeping,cashhandling,inventorymanagement,registration,pointofsales,and
rentalmanagement.Givingtheuserstheflexibilityandscalabilitytheyneedformanagingtheir
varioussystems.Bytheendofthetwosemesters,thegeneralpurposemanagementtoolshould
beavailabletothepublic,afterfirstbeingdeployedtoCSUMBOutdoorRecreation.Itshould
alsobeavailabletoalldevelopersasanopensourcesoftwareforcompletecustomizability.By
providingsourcecode,thosethatwishtogodeeperthantheprovidedimplementationmay
freely,forthefirsttime,havetheirownmanagementsystemfortheirspecificneeds.

3.2Goal
Themaingoaloftheprojectistoprovidealowhassle,highfunctioningsoftwaresolutionthat
willbridgethegapbetweenourclientsandtheircustomers.Additionalgoalswillbetodesign
theinterfaceofthesoftwareinsuchawaythattheclientsandcustomerswillbeableto
intuitivelynavigateit.

4of19

3.3OtherPossibleSolutionsandTheirDifferences
Therearemanyotherpossiblesolutionstotheproblem.Thebestofwhichinvolveimplementing
aCMSlikeDrupal,Wordpress,orJoomla.WhiletheseCMSsolutionscouldsolvethebasic
issueoftheservicesourclientsoffer,theskillsnecessarytoimplementsuchcomplexsystems
arenotfeasiblefortheskillsetsandtechnicalbackgroundsmostnonprofitorganizationsand
smallbusinesseshave.

Methodology
5.1ImplementationPlan

Theoriginalplanwastodividethemodulesbetweenthefourteammemberssothateach
individualwouldberesponsiblefortwomodulesoutoftheentirewebapp.Therewasaninstance
duringWinterbreakwhereitwasunanimouslydecidedtochangethestructureoftheprogram,
thatcausedconfusionandfrustration.Fromthismiscalculation,eachmemberwasableto
recover,butatdifferentpacing.Thismeantthatsomeoftheoriginalproposedmodulesand
featureswereremovedorreconceived.Theendresultbeing,notaProductionleveloutcome,but
rather,astrongAlpharelease.

Thestructureoftheprojectwasbrokenintoafrontend,writteninEmber.js,andbackend,written
inLaravel,side.TheEmber.jswasdividedbetweenanadminandfrontendfilingsystem,both
containingfoldersformostmodulesbutprovidingdifferentlevelsoffunctionalitydependingon
iftheuserwasgivenadminrightsornot.Laravelcontainseverythingusedfordevelopment
purposesandmanagesthemfortheteam.

(Theanalyticsandreportsmoduleswereremovedfromthefinalversion.Aneventsmoduleand
aservicesmodulewereimplementedseparateofPOS.)

5of19

Thisprojectrequiredmoreteamworkthanhadbeenpreviouslydonebyeachindividual.The
biggestchallengewaslearningandprogrammingwithLaravelandEmber.jsinparallel.Many
YouTubetutorialsandGooglesearchestookplacethroughoutthisproject.

Theteamsgoalwastohavereusablecodethroughouttheproject.Thiswasasmuchfor
programmingsimplificationasitwasfortheflowofuserinteractions.Thereasoningwassothat
eachmemberwasnothavingtospendprecioustimerediscoveringasolutiontohisproblemthat
hadalreadybeensolvedinanothermodule.Havingrefactoredsolutionsprovidedthesame
functionsandsimilar,ifnotthesame,interactionswhichprovideduniformflowforusers.This
conceptofreusabilityissomethingthatismassiveinthecomputerscienceindustryandeach
memberspracticeofitwillservehimthroughouthisfuturecareerpath.

5.2Resources
OutdoorRec
6of19

Structureofanoutdoorprogram
EquipmentRentals
EventPrograming
Sales
CurrentSoftwarebeingused
PotentialSoftware
FundingProposals
SoftwareBeingConsidered
Books
LearningLaravel4ApplicationDevelopment,HardikDangar,2013
WebTutorials
StackOverflow

5.3Expertise
Micah

ClassesTaken:
WebDesign
WebDesignII
HumanComputerInteraction
InternetProgramming
DatabaseManagement
Experience:
Laravel
APIdevelopment
WebAppdevelopment
Designimplementation
Databasedesign/development
Logodesign
ProjectManagement
SkillsNeeded:
Unittesting
Deployablesoftware
ImplementingSaaS

Greg

ClassesTaken:
CST205/231/238MultimediaDesign&Programming/C++/DataStructures

7of19

 CST300/311/328/334/336/337/338/370/395Proseminar/Networking/Digital
Art/OperatingSystems/InternetProgramming/ComputerArchitecture/Software
Design/Algorithms/QualityEngineering
CST438/462S/495SoftwareEngineering/ServiceLearning/CloudDevelopmentwith
Salesforce
Experience:

Softwaredevelopmentlifecycle
Projectmanagement
Softwaretesting
Versioncontrol
Continuousintegration
Documentation,mockups,wireframes,UML,&usecases
C++,HTML,Java,PHP,Python,SQL
TimekeepingportalforFoodBankforMontereyCounty
2015HackUCSC
2013and2014SiliconValleyCodeCamp
2013and2014CSUMBIdeasofMarch
2014SiliconValleyFishackathon
2012GDGDevFestWestatGoogle
SkillsNeeded:
Laravelframework
APIcreation/deployment
SaaScreation/deployment
Writingaformalproposal
Advanceddatabasedesign
Analytics

Carlos

ClassesTaken:
CST306GameEnginePrograming
CST205MultimediaDesign
CST370Algorithms
CST338SoftwareDesign
CST238DataStructures
CST336InternetProgramming
CST438SoftwareEngineering
Experience:
2011InternshipattheNavalPostgraduateSchool.Developedthreemobileappsusing
JavaScript.Focusingonanimation,andsomealgorithms.
8of19

SkillsNeeded:
LearnLaravelusingthetextbook
LearningLaravel4
,aswellasthroughourgroups
residentLaravelexpertMicah.

Tyler

ClassesTaken:
CST300ProSeminar
CST336InternetProgramming
CST438SoftwareEngineering
Experience:
RequirementsDocumentation
UseCasesDesign
SkillsNeeded:
programmingwithLaravel

ChangesintheProject

EventsandServiceseachbecameindividualmodulesandconnectedtothePointofSales
Cartsystem.
Eventswasintheoriginalproposedprojectbutremovedasdevelopmentbeganand
finallyaddedbackin.
ServiceswasoriginallypartofPointofSaleshowever,whendesigned,provedtobe
morethanenoughtoseparate.Italsohassettingsfunctionalityandalistofrequested
servicespage.
AnalyticsandReportswereremovedfromthisprojectsplanastheywouldnotbeableto
bedevelopedparalleltotheothermodules,sincetheteamwantedtodevelopeach
moduleindependentlyaslongaspossible.
PointofSalescausedthecreationofOrders,astheneedforarestocksystemwas
realized.
ThecheckoutfunctionalityofPointofSalesbecameaCartsystem.
Mediawasanadditionfortheeaseofusabilityfornontechnicaluserstostylethe
program.
ABlogpostingsystemforadminswasanaddedfeature.

DescriptionofProjectDeliverables

9of19

ThefirstdeliverableforourprojectwillbeaBitBucketrepositorycontainingthefinal
downloadablesoftware.Giventhatourprojectisopensource,thesourcecodewillbeavailable
onBitbucketaswell.PairedwiththeBitBucketprojectandcode,therewillbeproject
documentationfordevelopersandIT,tobetterunderstandhowtoinstallandruntheprojecton
theirownsystemorhostingservice.TherewillbelivecoderunningattheStudentRecreation
desktocontinuetestingofthesoftwareduringthelastpartofthespring2015semester.

Linkstodeliverables:
http://localhost/cereswebapp/public/

BudgetandTimeline

Forthisopensourceproject,weareprojectingonthebasisoflabor,valueofproduct,and
returnoninvestment.Inbusiness,thereistheconceptof
keystonemarkup
,inwhichthegross
marginis100%ofthecostpriceor50%ofthesaleprice.Giventhis,thecostbreakdownisas
follows:

1.
Thereare800hoursofworktodoperengineer.
2.
Eachengineerispaid$25perhour,whichislowerthantheaveragesoftware
engineer.
3.
Thedevelopmentfirmwillalsoneedtoprofit,aswellasrecouptheresourcesthat
weredivertedtotheengineerstocompletethisproject.

Laborfor4engineersworking800hourseach
=$80,000.00
Keystonemarkup(businessprofit+recovery)
=
$40,000.00
=
$120,000.00

GUIDesign2weeks
(80hours)
1.

WorkflowofWebApp(Usecases,etc.)

a.

Usecases
10hrs

b.

Usabilitytesting
20hrs

2.

DesignofWebApp

a.

Usabilitytesting(closelytiedtoaboveusabilitytests)
20hrs

b.

Design
30hrs

AssetsModules2weeks
(80hours)
1.
Assetmanipulationinterfaceinsert,label,modifyAsset,inventorystock,service,
specialorder
10hrs
10of19

2.

Rentalsystem&interfacecheckoutassetforXamountoftime.
10hrs

3.
Servicesystem&interfacerequestqueue,viewstatus,modifystatus,pushtoPOS
atcompletion.
20hrs
4.
Inventoryassessment&interfaceviewstatus,viewavailability,selectable,pushto
ServiceorPOS.
10hrs
5.
Orderingsystem&interfaceadditemstoorder,vieworderhistory,PushtoAsset
Systemwithorderarrival.
10hrs
6.

Assetmodulearchitecture
20hrs

UsersModules2weeks
(80hours)
1.

Add/modifyusers(attachingrolestousers)
20hrs

2.

Configurablepermissionsbyallowedusers(attachingrolestopermissions)
30hrs

3.
Grantingaccesstoassets/modulesspecificallytothosewiththecorrectpermissions
30hrs
EventsModules2weeks
(80hours)
1.

Displayandeditevents
10hrs

2.

Allowuserstosignupforevents
10hrs

3.

Sendmessagestoeventusers10hrs

4.

Integratelocationservices(likeGooglemaps)
10hrs

5.

Provideawayforuserstosee/managetheeventstheyareapartof.
20hrs

6.

HookintoPOSsystem
20hrs

Analytics3weeks
(120hours)
1.

Hoursofuse(PeaksandValleys)
30hrs

2.

Assettracking(mostandleastuseandwhen)
30hrs

3.

Demographics(gender,age,ethnicity)
30hrs

4.

Eventtracking(takingplacemostandleast,attendance,costs)
30hrs

Reports2weeks
(80hours)
1.

Employeeandvolunteerhours
10hrs

2.

Howmuchofanitemisinstock
10hrs

3.

Generateeventroster
10hrs

4.

Financialassetsandliabilities
10hrs

5.

Overtimereports
40hrs

PointOfSale(POS)7weeks
(280hours)
11of19

1.

Setuppaymentgateway
50hrs

2.

Addrecurringpaymentsystem
50hrs

3.

Refundingsystem
50hrs

4.

Shoppingcartsystem
50hrs

5.

Aggregatedweeklysalesreports
80hrs

Evaluation
6.1FunctionalityTesting
Thequestiontokeepinmindisdoesthispartofthesoftwareexperiencedowhattheuseris
askingittodo?.Forexample,whenauserwishestoperformasearchforaproductcurrentlyin
stock,thedevelopmentteammusttakeintoaccountallofthevariousvalidandinvalidqueries
whatiftheyenterablankquery?Whatofaquerywithmultiplesearchterms?Tobesurethatthe
softwareisfunctional,thedevelopmentteammustmakeahabitofproperlyunittestingthecode.
Frameworkswillbesetupforbothblackboxandwhiteboxtesting.Thecodewillalsobeput
understresstotestitsperformanceboundaries.

Thesoftwaremustalsobeevaluatedonitsabilitytobecustomizedanddeployedinprivate
networks.Evaluationwouldinvolve,inpart,testingwhetherornotausercouldcustomizethe
codeinthecloudandthenseamlesslydeployintotheirownhostingenvironmentatalatertime.
PartoftheprocessmayinvolvedownloadingthesourcecodefromBitBuckettoseeifruns
smoothlyafter.

Thedraganddropfeaturesneedtonotonlyvisuallydemonstratetheireffect,buthavea
measurableresultonthecodebasewhichaimstosatisfytheusersvision.Theuserwillalso
needtobeabletolinkintopaymentgatewaysandotherservicestheycurrentlysubscribeto
withouthassleortechnicalknowledge.Infact,thissoftwaresolutionisbeingdesignedtoallow
nontechnicaluserstoharnessallthesametoolsastheirtechnicalcounterpartswhereasa
developermayknowhowtoexecuteexactlywhatheorshewantsto,soshouldtheaverageuser
followaclicktreetoachievethesameresult.

Thesoftwareservicemustbecompatibleonthewidestpossiblevarietyofhardwareplatforms,
andwiththewidestpossiblevarietyofsoftwarehosts.Specifically,isthisservicefunctionally
equivalentonWindows,Macintosh,andLinuxmachines?Isitfunctionallyequivalentrunningin
InternetExplorer,Safari,andFirefox?Onemustalsoconsiderthedifferentversionsofallthe
aforementioned.Otherconsiderationsinclude:processingpower,systemmemory,screensize,
hardwarearchitecture,andlocalizationconcerns.Allofthesemustbeproperlytestedfor
interoperability,functionalequivalence,andpurposedrivenperformance.
12of19

6.2UsabilityTesting
Inordertoaccomplishthemaingoalofcreatingahighlyfunctionalandusablesystem,a
considerableamountofeffortwillgointomakingsureevenatechnicallyunsavvyuserwill
intuitivelyknowhowtonavigateit.Inordertoaccomplisheffectiveusability,certaintestsat
differentphasesoftheprojectwillbeemployed.

Phase1
Paperprototypes

Evenbeforeconceptualizingthesoftwareandthebackendinvolved,paperprototypeswillbe
createdtogaugewhethertheworkflowofthesystemisintuitiveforamajorityofusers.Each
teammemberwillmockuptheirvisionforthesystem,mappingoutvarioustasksauseroradmin
istoattempt.Afterthesemockupshavebeencreated,theteammemberswillrandomlyselect
peoplewillingtotestthemockup.Givenasingletaskstartingfromthehomepageforthe
system,auserwillhavetoaccomplishitwithoutanyfurtherinstructionsfromtheteammember.
Theteammemberwilltakenotesonanyobservationsmade,fromtheamountoftimeittakesfor
atestertoaccomplishthetask,tothespecificplacesinthesystemtheystruggledwith.Oncethe
taskhasbeencompleted,theteammembercanaskthetesterforanysuggestionsorthoughts
theyhadonthesystem.Aftereachteammemberhasgeneratedalloftheirresults,theteam
memberswilldiscussamongsteachotherandcreateacombinedmockup,incorporatinganyof
theimprovementsorcommentscommonamongthetesters.Thisfinalmockupwillgothrough
thesametestingregimenthatthepreviousmockupsgothroughwithahighervolumeoftesters.
Fromthosenotesandcomments,theteamwillbereadytomoveontophase2ofusabilitytests.

Phase2
Livetesting

Whenthesystemisbeingcreatedbothbackendandfrontendtherewillbeopportunitiesfor
userstotestthesoftware.Thesystemwillbebuiltinamodularfashion,allowingcertainpieces
ofthesoftwaretobetestedatvarioustimes,beforethewholesystemisreadyforalphatesting.
Whenthemodulehasreachedacertainpointofcompletionwewillselecttesters,bothpeersand
clientstaff,toattemptsimilartasksasphase1.

Phase3
Alphatesting

AverysmallamountofAlphatesterswillbeselectedtotrythesystem.Theywilllargelybe
selectedbasedonhowwelltheyfitinwiththetargetaudience(nontechsavvy).However,some
willbechosenasintended"outliers",chosenfortheirselfacclaimed"techsavvy".Thiswillgive
usawaytocomparehowclosethetwoperformwiththesoftware.Thegoalwillbeforthetarget
audiencetofeelnearlyascomfortablewiththesoftwareastheoutliers.Thealphaphasewill
involveteammembersmonitoringhowthetestersinteractwiththedifferentportionsofthe
software.

Phase4
Betatesting
13of19

ThemaindifferencebetweenAlphaandBetatestingwillbethelevelofmonitoringthattakes
place.BecausethepooloftestersduringtheBetaphasewillbehigherthanAlpha,wewillrely
heavilyonthetesterstosubmittheirfeedback.Thisfeedbackcantakeplaceeitherthrough
surveymonkey,googleforms,oranothermethodtheteamchooses.Thegoalwillbetoget
feedbackofthesystemthatiscomparativelyunrestrictedtotheAlphatestingphase.

Phase5
Production

Atthispoint,thesystemshouldberefined,throughthefeedbackreceived.Howeverduring
production,theplanistocontinuemakingimprovementsforthefollowingversionsreleased.In
addition,therewillbeissuetrackingturnedoninBitBucket.Sincethisprojectwillbeopen
sourcetherewillbeaplacewherepeoplecanopenlysuggestfunctionalitytobeadded/
improvedwiththesystem.

6.3EvaluationPlan
Thissoftwaremustprovideaneasytousegraphicaluserinterfacethatbothtechnicaland
nontechnicalusersareabletoefficientlyinteractwith.Itmustalsobeabletohandlereplacingall
existingmanagementmethodscurrentlyusedbyCSUMBOutdoorRecreation,seamlesslyand
withoutfailing.

AssessingthecurrentoperatingformatofOutdoorRecreationwillsetathresholdoffailurefor
thisproject.Measuringtheamountoftimetakentocompletevarioustasks,countingtheamount
oferrorsthatoccurduringtheseprocesses,accountingforlossesbecauseoferrors,aswellas,
reviewsfromtheusersoftheestablishedsystemwillallbeseparatestandards.

Timewillbemeasuredforeachareatobeaddressed.Theaverageswillbetakenforasmany
usersaspossibletogetameanaswellasabellcurveforamoredynamicassessment.
Countingerrortypesandtheirresultwillgaugethesoftwaresabilitytomitigatelossofassetsas
wellaslossincustomersuse.

Lastly,wewillwanttomeasurethedesiretousethesoftware.Thiswillbedonewithan
assessmentdocumentorpagethatwilltabulatehowusersfeelaboutthesoftware.

CollaborationStatement

(Theoriginalproposeddivisionofwork,providedbelow.)

CarlosEspinoza

MicahIriye

14of19

1.AssetModules

1.DesigntheUI

2.PointofSales

2.DeploymentSystem

GregGreenleaf

TylerNicholson

1.Eventsmanagement

1.Analytics

2.Usermanagement

2.Reports

FinalDocumentation

Pleaserefertotheprojectsonlinewikipage.

15of19

AdvisorSignoff

16of19

17of19

18of19