1. 1
Table of Contents
System Prototype ...........................................................................2
Part I: Main Menu ............................................................................................................... 3
Part II: Project Information ................................................................................................. 3
System Recommendation................................................................4
Part III: Transmittal Letter................................................................................................... 5
Part IV: Executive Summary................................................................................................ 6
Part V: Detailed Results of Analysis .................................................................................... 7
Part VI: Systems Alternatives............................................................................................ 10
Part VII: Systems Analysts’ Recommendations................................................................. 11
Part VIII: Proposal Summary ............................................................................................. 15
Appendix A: System Proposal ........................................................17
Part I: Service Request...................................................................................................... 18
Part II: Goals and Objectives............................................................................................. 21
Part III: Feasibility Study.................................................................................................... 22
Appendix B: Business Analysis .......................................................32
Part I: Conduct of Analysis................................................................................................ 33
Part II: Software Requirements Specification (SRS).......................................................... 35
Part III: Infrastructure Analysis ......................................................................................... 50
Appendix C: Systems Analysis ........................................................54
Part I: Use Case................................................................................................................. 55
Part II: Activity Diagrams................................................................................................... 66
Part III: Class Diagram ....................................................................................................... 75
Part IV: Sequence Diagram ............................................................................................... 76

2. 2
System Prototype

3. 3
Part I: Main Menu
Part II: Project Information

4. 4
System Recommendation

5. 5
Part III: Transmittal Letter
May 4, 2015
SpirosVeliantis
CaliforniaDepartmentof Technology
1325 J Street#1600
Sacramento,CA 95814
ProfessorVelianitis,
Our teamhas gatheredthe necessaryinformationtobuildanintegratedwebsite anddatabase tomeet
the CaliforniaDepartmentof Technology’srequirements.TeamOne hasdeterminedthatall your
requestsforthe website anddatabase applicationsare feasible.Therefore,TeamOne willcreate a
website anddatabase applicationtomeetthe standardsthatthe CaliforniaDepartmentof Technology
needsforlongtermsuccess.
Duringthe durationof the SpringSemester,TeamOne hasgatheredthe necessaryinformationand
designrequirementstobeginworkingonthe firsthalf of the SystemsDevelopmentLifeCycle forthis
project.TeamOne will startworkon the designandimplementationduringthe Fall Semester.The final
applicationswill notbe operationalandreadyforuse until November2015. I hope thisstill meetsyour
approval.If not,contact us immediatelysowe candetermine analternative course of action.
Team One will stayinconstantcontact and provide periodical updatesonthe progressof the project to
confirmthe standardsand applicationsusedmeetthe CaliforniaDepartmentof Technology’sapproval.
Sincerely,
Thang Nguyen x
Darrell Nygard x
DavidScott x
MatthewGibbs x
NickGrant x
YenTran x

6. 6
Part IV: Executive Summary
A. Descriptionof the Problem
A problemexistswhenthere isadifference betweenthe expectedperformance of software,
and the relativelypooractual performance of the software.TeamOne identifiednoproblemswiththe
CA-PMMtool kitsince the software performsasexpected. However,TeamOne identifiedseveral
potential opportunitiestoimprove the tool kit. One opportunityisaccessibility.Currently,ITProject
Managers have trouble accessingthe correctversionof the CA-PMMtool kitquicklyandeasily.Asan
excel file, the tool kitusesthe file basedapproachtostorage,andcomeswithall the disadvantagesof a
file basedsystem.Examplesof disadvantagesinclude dataredundancy,datainconsistency,data
isolation,dataatomicity,datadependence,datasharing,datasecurity.Eachof these factorsaffect
accessibilitytosome degree.Accessibilitycouldbe improvedbychangingfroma file basedstorage
systemtoan applicationwithadatabase solution.Anotheropportunitypresentedisthatof sharingan
collaboration.Sharingisalsoaffectedbythe use of a file basedsystem(discussedabove).Inparticular,
sharingisaffectedbythe followingdisadvantagesof the filebasedsystem:datasharing,data
redundancy,anddata inconsistency.Evenif teammembersshare the excel file usingacloudservice
(e.g.Google Drive,Dropbox),if theytrytoaccess the file atthe same time theycouldrun intoissues
mergingthe fileswhenmultipleversionsof the same documentare created.Synchronouscollaboration
wouldsolve these issues,butthe software providingsynchronouscollaborationwithmicrosoftexcel
files(Office 365 andGoogle Sheets) alsohave reducedfunctionality,andwouldnotmeetthe
requirementsof the CA-PMMtool kit.The final opportunitypresentedwasauser interface.Since the
currenttoolkitismade inexcel,there isplentyof roomforimprovementwhenitcomestodesigningthe
interface.Three areasof improvementinclude organizing,economizing,andcommunicatingusingaGUI
interface.Whenitcomestoorganization,consistencyandnavigabilitycouldespeciallyuse some
improvement.
B. ProposedSolution
Team One will create afullyfunctioninganddynamicwebapplicationwhere ProjectManagers
will be able tocreate,access,and editmultipleprojects.ProjectManagerswill have the capabilityto
create accounts fornewusers,grant usersaccessto theirprojects,andsetauthorizationsforthese
users(i.e.,view,edit).Withineachproject,userswillbe able toaccesswebformswhere theycan
update the contentof the CA-PMMtoolkitfortheirproject.TeamOne will create adatabase where the
data submittedinthe webapplicationwillbe stored,reducingdataredundancy.Since formswill be
automaticallyupdatedwhenopenedorrefreshed,datainconsistencywill alsobe reduced.Application
Administratorswill be givenfull accesstoeveryaccount,project,andforminthe database to assist
userswithtechnical issues,make necessarychangestoprojectsif a managerbecomesunavailable,and
archive useraccounts.

7. 7
C. Cost / BenefitSummary
Team One will developthe software usingMicrosoftSharePointandSqlServerforfree sothese
costs will be zero.Inaddition,all serverswillbe leasedsonew hardware costswill alsobe zero.The
mainexpenseswill be thatof the salariesof the new employeesthatwill maintainthe information
systemandthe newusertrainingof thisapplication.Inadditionthere will be annual recurringcostsfor
storage backup,incremental communication,andleasingof the application,web, anddatabase servers.
However,afterlookingatkeyfinancial statisticsandratios,TeamOne estimatesthatthisapplication
shouldresultinanannual financial benefitof $677,360.85.
D. ImplementationTime Frame
Team One determinedthe requirementsof the projectinthe Springsemester.TeamOne
analyzedbusinessprocesses,scope,anddesignrequirementsof the webapplicationandthe database.
Withthat in mind,TeamOne will be buildingaproof of conceptof the prototype thatwill be partially
functional andwill be presentedMay11, 2015. We will demonstrate the inputof informationof the web
applicationandcontinuallycheckthe applicationanddatabase foranybugs or securityissues.
In the fall semester,TeamOne will make anynecessaryandrequestedchangestothe designof
the webapplicationanddatabase inthe firsttwoto three weeksaslongas itis economicallyfeasible to
implement.Afterhavingtestedandrefinedall requirementsof the prototypesinsix tosevenweeks,
Team One will installthe actual implementationof the webapplicationanddatabase.The followingtwo
weekswill be dedicatedtoassistingthe clientintestingall aspectsof the webapplicationanddatabase
to ensure overall satisfaction.Inthe lasttwoto three weeks of the semester,TeamOne will document
all componentsandimplementthe applications.If the programs’ use ismetwithsatisfaction,TeamOne
will close downthe projectandevaluate the overall successof the project.
E. Outline of SystemsStudy
Duringthe course of the Springsemester,TeamOne waswentthroughthe planningand
analysisphase of the SystemsDevelopmentLife Cycle of the project.Inthe fall semester,TeamOne will
move onto the design,implementation,andprovidingsupportafterthe close downof the project.The
time frame forthisprojectcomesto roughlysix months.The clientfindsthisdeadline acceptable forthe
time being.
Part V: DetailedResultsof Analysis
A. SystemProposal
The SystemProposal reportwill gatherinformationaboutthe proposedsolutionthatwe will be
givingtoour clients.Inorderto gatherinformationforthe report,we will needtofindoutwhatour
clientsdesire bymeetingupwiththem.We will thenorganize andcollectthe informationtopropose a
database solutionthatwill be necessaryfortheirneeds.Once we have abetterunderstandingof our

8. 8
clients’needs,we willaskformore informationonwhatelse theywouldwanttoaddto the project.
Afterwe have establishedthe client's’core needsforthe proposedsystem, we cancreate a wishlistof
functionalitiesthatcanbe implementedata laterdate.For example:aclientmightpropose we adda
time anddate stampon projecteditsoradd projectmanagerpermissionswithinthe application.Atthe
final clientreviewof the proposedsystem, we cancheckto see if there are any additional functionalities
that couldbe expandedfurtherormade better.Onlythenwillwe release the finalversiontothe client.
For more information,checkoutthe SystemProposal reportinAppendixA.
B. BusinessAnalysis
We alsoperformedaBusinessAnalysistodescribethe informationsystem’sbusiness
requirements.Inthisreport,we summarize ourdatacollectionmethodsinthe sectiontitledConductof
Analysis.We heavilyreliedondocumentationforthe existingCA-PMM.Specifically,ourteamprimarily
usedthe CA-PMMReference Manual andthe CA-PMMTemplate Instructionsinouranalysis.We also
usedthe existingexcel templatetoidentifyfeaturesthatwouldbe necessaryinthe new web
application.
We outlinedthe system’sbusinessrequirementsinthe Software RequirementsSpecification.
Thissectionidentifiesthe application’sexternal interfaces,functions,usabilityrequirements,required
performance,logical databaserequirements,designconstraints,andsoftware systemattributes.The
external interfacesfromourapplicationincludeusers,hardware,andsoftware.Humansinteractwith
the interface throughsight,sound,andmotion.The applicationwill interactwithclienthardware and
software througha browser,makingitsowe do nothave to considerwhichoperatingsystemthe client
will have.The serverside of the applicationwill needtooperate withinthe Sharepointframework,
whichrequiresanupto date WindowsServerwithintegratedASP.NETandInternetInformation
Services(IIS),aswell asSQLServer.The functionalityof oursystemessentiallyincludescreatingand
managingaccountsfor users,creatingandassigninguserstoprojects,editingandmanagingprojects,
and editingformswithinprojects. Usabilitywasmeasuredacrosssuccessfactors,suchas consistency,
efficiencyandease,formatandflexibility,aswell asusabilitycharacteristicslikethe type of user,task,
systemandenvironment.Ourperformance sectionidentifiedrequiredperformance factorsacrossfive
essential functions,suchasdatabase response time andsystemdependability.Forlogical database
requirements,we estimate thatwe will needtoallow 2,000 to 2,500 accountsto assignindividualsto
about500 projectsperyear.
Finally,we describedthe systemarchitecture inthe InfrastructureAnalysis.The hardware
requiredforourapplicationincludesaWebServeranda Database server.Itwill alsorequire aclient
computerwithan Internetconnection.The software we will use includesavirtual machine toinstall the
applicationinanindependentoperatingsystem, WindowsServerwithIISandASP.NETinintegrated
mode,SQL Server,andSharepointservices.Fordevelopment,we will use SharepointDesignerand
Visual Studio,andwe will code inVisualBasic,HTML, andan importedlibraryof code fromSharepoint
Designer.
For more information,reference the full BusinessAnalysisatAppendix B.

9. 9
C. SystemsAnalysis
We performedaSystemsAnalysistodescribe the relationshipsbetweenusers,the application,
and the database itself.Inthe SystemsAnalysiswe hadtothinkcriticallyabouteachrelationshipandall
the interactionstherein.OurUse Case diagramis crucial to our understandingof eachfunctionbetween
the team members,projectmanager,database administrator,andentitiesthroughoutthe proposed
application.Eachapplicationentityisdetailedinthe Use Case descriptions,asare eachuser-application
relationshipinthe ActivityDiagrams.The ClassDiagramoutlinedthe methodsandfieldsof the
application,while the Sequence Diagramdetailsthe orderof eventsforactivitiesandconditional
statementsperformedbythe system’svariouscomponents,includingthe user,application,SharePoint,
and the database.
For more information,checkoutthe complete SystemsAnalysisinAppendixC.

10. 10
Part VI: SystemsAlternatives
Belowisa listof the informationtechnologysolutionswe considered.The firstcolumnliststhe
potential technologyincludedinthe informationsystem.The secondcolumnprovidesashort
descriptionof howeachsolutionoperationalproblemsoropportunities.
InformationSystem Alternatives Operational Benefits
A. ASP.NET with Sharepoint
Developer Tools: Visual Studio, Sharepoint Developer
Code Languages: Visual Basic, HTML, CSS, Sharepoint Library
Hardware: Client device, (Virtualized)WebServer, ApplicationServer,
Database Server
Operating System: Installed ina Virtual Machine
Server Technologies: Windows Server (IIS / .NET Frameworkin
integratedmode), SQL Server
Thisoptionprovideseffective collaboration
betweenusersandsignificantlyimprovingproductivity
due to betterplanningandcontrol.Initial costswillbe
zerobut recurringcostswill rise tomaintainthe system.
The recurringcosts will be negligible due toincreased
productivity.SharePointiseasytoimplement,thisisthe
bestoptionandour recommendation.
B. ASP.NET
Developer Tools: Visual Studio
Code Languages: Visual Basic, HTML, CSS
Hardware: Client device, (Virtualized)WebServer, ApplicationServer,
Database Server
Operating System: Installed ina Virtual Machine
Server Technologies: Windows Server (IIS and .NET Framework), SQL
Server
Thisalternative wouldrequire asignificant
amountof codinginVisual Basicandthe .NET
framework,lengtheningthe projecttimelinefor
essentiallythe same desiredresult asthe Sharepoint
solution.
C. PHP
Developer Tools: SublimeText
Code Languages: PHP, HTML, CSS
Hardware: Client device, (Virtualized)WebServer, ApplicationServer,
Database Server
Operating System: Installed ina Virtual Machine
Server Technologies: Apache (web server), MySQL Server (database
server)
Thisalternative wouldalsorequire asignificant
amountof codingforessentiallythe same desiredresult.
PHP iswidelyused,thus,supportwouldbe plentiful but
for ease of integration,we donotrecommendthis
option.
D. Excel Template File (CurrentSolution)
Developer Tools: None
Code Languages: None
Hardware: Client Devices
Operating System: Any
Server Technologies: None
This alternativewould keep the current system as is
but as discussed previously,hinders collaboration between
users and will inhibitprojecttimelines from completion.
Stayingwith the current system would keep initial costs down
but ultimately end up costingmore in the longrun due to
limitations on collaboration.Wedo not recommend this
option.

11. 11
Part VII: SystemsAnalysts’ Recommendations
A. Summary of the ProposedSystem and Operational Benefits
Our teamwill create a webapplicationwhere ProjectManagerswill be able tocreate,access,
and editmultipleprojects.ProjectManagerswill alsobe able tocreate accountsfornew users,grant
usersaccessto theirprojects,andset authorizationsforthese users(i.e.,view,edit).Withineach
project,userswill be able toaccesswebformswhere theycanupdate the contentof the CA-PMM
toolkitfortheirproject.The datasubmittedthroughaform will be storedinadatabase,reducingdata
redundancy.Since formswill be automaticallyupdatedwhenopenedorrefreshed,datainconsistency
will alsobe reduced. ApplicationAdministratorswillbe givenfull accesstoeveryaccount,project,and
formin the database to assistuserswithtechnical issues,make necessarychangestoprojectsif a
managerbecomesunavailable,andarchive useraccounts.
These featuresare meanttoaddress three opportunitieswe identified toimprove the CA-PMM
toolkit.These opportunitiesare 1) improvedaccessibility,2) improvedsharingandcollaboration,and3)
improvedperformance.Since oursolutionisawebapplication,userswill be able toaccessanup to date
versionof the toolkitfromanydevice withinternetaccess.Inaddition,if theyare workingonmultiple
projects,theycouldaccesseachof those projectsfromthe same application. Collaborationisimproved
by the abilitytoaddmultiple userstoaproject,and to create authorizationsforthose users.Inthisway,
ProjectManagerscan authorize varioususers toworkoncertainprojects,anduserscan update
differentformsforthe same projectat the same time.Since the datais storedina database,theywill
not have to thinkabouthowto save the data and share it withotherusers.Theycan justfocuson
completingwork.Improvedperformance referstothe performance of usersandnotthe system.We
expectuserstobe quickerandmore effective whenwe create astreamlinedandconsistentuser
interface.We alsoexpectmore accurate inputsbyprovidingdatavalidation. The factthatmanagersor
teammemberscanaccess and review workimmediatelymeansperformance shouldbe improved.Also,
we expecttocut some time byautomaticallypopulatingfieldsinsome formswiththe datafromother
forms.
We chose to develop the webapplication usingMicrosoft’sSharePointtechnology. SharePoint
was developedbyMicrosoft toincrease the accessibilityandeffective use of informationwithin
organizations.SharePointiscloselyintegratedwithASP.NETandInternetInformationServices(IIS). For
example,aSharePointWebApplicationwill typicallycreate asingle corresponding Website (thoughit
can span multiple websites) inthe IISframework,andaSharePointwebpage isactuallyanASP.NETweb
page. Most of the contentwill be developedinSharePointDesignertoexpedite development,though
some pageswill require custommodificationinVisual Studio. The codinglanguageswe plantouse
include Visual Basic,HTML,and possiblysome javascript.Javascriptwill allow ustocreate interactive
websitesthroughclientside scripting. We will alsoheavilyrelyonMicrosoft’s InfoPathapplication to
create customizedformswhichuserscanaccess usingthe front endGUI of the SharePointwebsite.
Whenthe user submits(the wholeform) orupdates(partof a form),the data will update aSharePoint

12. 12
liststoredonthe database.WhenotherInfoPathformsare openedwithfieldsusingthe same data,the
fieldswillbe populatedwiththe updateddata.
We will installthe applicationinaVirtual Machine.Virtual machinesallowone operatingsystem
to be openedwithinanotheroperatingsystem,souserswill nothave torebootthe machine tomanage
the application.SharepointrequiresthatIISandASP.NETbe installedinIntegratedMode,sothey
functionasa single platform.Also,SharePointstoresitslists,libraries,contenttypes,andfieldtypesin
SQL Server,sowe will needtoinstall anupto date versionof SQL Server.Fordevelopmentpurposes,we
will continue touse the serveravailable inProfessorVelianitis’ officeonthe CSUScampus viaVirtual
Private Network(VPN).ThisserveralreadyhasWindowsServerinstalled,whichwill allow ustovirtualize
the Web ServerandDatabase server.We will alsodevelopthe applicationindependentlyof anyexisting
SharePointinformationsystemwithinthe CaliforniaState Government,andconsiderpossible
integrationata laterdate.
B. Cost / BenefitAnalysis
For the fiscal yearendingJune 30, 2016, the State of California budgetedexpendituresof
$373,006,000 for the Departmentof Technology.Inaddition,the Departmentof Technologyistracking
active projectswithatotal expectedcostof $4,624,072,501. Improvingthe CA-PMMpromotesthe
efficientandeffectivemanagement of these resources,andcouldresultinsignificantbenefits.The
estimatedcostsandbenefitsare brokendownbelow.
i. Benefits
Most of the tangible benefitsrelatedtothe CA-PMMare cost reductions.The benefitsof
improvedprojectoutcomesare still intangiblesince we cannoteasilyestimate them.Forthisreason,we
will focusoncalculatingthe financial benefitof reducingprojectcosts.Inorderto identifythe annual
benefit,we decidedtodeterminethe expectedtotal annual cost,estimate the percentage reductionsof
the cost whenour informationsystemisimplemented,andthencalculate the annual benefit.The
expectedannual costwascalculatedbasedonthe active projectsonMarch 27, 2015. To take the data
fromprojectsactive ona single date andextrapolate ittorepresentanannual amountisnotan optimal
estimationprocedure,butitwasthe bestavailable withthe datawe foundonline.Toestimate the
annual cost,we tookthe total amount foreach of the projects,anddividedeachbytheirestimated
duration.We estimate onlyaboutfive percentof thisamountcanbe affectedthroughmore efficient
and effective use of the CA-PMMtoolkit.Of thisfive percent,we calculatedbenefitsbyestimating
increasedproductivitydue toseveral keyfactors.Due tothe new userinterface,easieraccess,and
collaboration,the time needtoworkonthe tool kitshoulddecrease,resultinginanincrease in
productivityof 0.25%.We expectthatthe enhanceduserinterface andcentral storage providedbythe
database shouldreduce errors,increasingproductivitybyanadditional 0.25%.We alsoexpecta 0.50%
increase inproductivitydue tobetterplanningandcontrol asa resultof the improvedtool kit.Overall,
thisshouldresultinanannual financial benefit of $677,360.85.

13. 13
Annual Project Cost * 1,354,721,690.45$
Percentage Attributable to CA-PMM 5%
Cost Attributable to CA-PMM 67,736,084.52$
Category In $US
% Increase in
Productivity
Cost reduction or avoidance -$ 0.00%
Error reduction 169,340.21$ 0.25%
Increased flexibility -$ 0.00%
Increased speed of activity 169,340.21$ 0.25%
Improvement in management planning and
control 338,680.42$ 0.50%
Other -$ 0.00%
Total Tangible Benefits 677,360.85$
Tangible Benefits
*Annual project cost is based on a calculation of the total annual cost of projects
under construction on March 27, 2015. Since our sample only includes projects
active on a single day, it is more likely to exclude short term projects. Since
projects with shorter development periods have less risk, the tangible benefits
associated with the sample selected should be relatively larger. Therefore, our
estimation should be conservative since it may exclude projects that would have
less tangible benefits.
i. One Time Costs
Our teamwill developthe softwareforfree sothese costswill be zero.Inaddition,all servers
will be leasedsonewhardware costswill alsobe zero.Site preparationwill be zerodollarssince the
software will notbe usedina particularlocation,butratherviathe weboveruser’sdevices. We will not
have to investinadditional software either.There willbe no upfrontcostsforthisapplication.
Category In $US
Development costs -$
New hardware -$
New software -$
Site preparation -$
Other -$
Total Tangible One-Time Costs -$
Tangible One-Time Costs
i. RecurringCosts
The most expensive recurringcostwill be the salaryforthe new employeeswhowill maintain
the informationsystem.We expectthiscosttobe around$120,000 to covereach of their$60,000
annual salaries.Usertrainingwill alsobe expensive.We calculatedthatthere wouldbe anaverage of
8.46 newprojectsperyear (44 projects/ 5.22 yearsaverage development).If projectmanagersfor
these newprojectshave anaverage billable rate of $150 per hour,and the usertrainingtakesfour

14. 14
hours,thenthe average annual cost of usertrainingshouldbe $5,076.90 ($150 perhour x 4 hours=
$600 per projectx 8.46 projects).The onlynecessaryincrementalstorage willbe tostore a backup of
the application,userdocumentation,andtechnical documentation.Thisstorage shouldbe minimal,so
we estimate ittocost around $6,000 peryear.Incremental communicationwill be necessarytoprovide
supportfor the application.We estimatethiscosttobe around$7,000 peryear. Inaddition,we expect
to have about$40,000 peryear to lease application,web,anddatabase servers.Overall,the annual
recurringcost will be $178,076.90.
Category In $US
Application software maintenance 120,000.00$
User training 5,076.90$
Incremental data storage required 6,000.00$
Incremental communications 7,000.00$
New software or hardware leases 40,000.00$
Supplies -$
Other -$
Total Tangible Recurring Costs 178,076.90$
Tangible Recurring Costs
C. NPVAnalysis
For our netpresentvalue analysis,we chose adiscountrate of 6.00%. Thisrate isappropriate
for thisprojectsince itislowrisk.We usedthe resultsof ourcost / benefitanalysistoperformthis
calculation.Basedonthiscalculation,ourprojectwill resultincumulative discountedcostsavingsof
$462,299.95 inthe firstyear of implementation,androughly$1,993,496.02 by the endof the fifthyear
afterimplementation.Evenafterdiscountingcashflows,the benefitsoutweighcostsbothinthe short
termand longterm.
Usingthe netpresentvalue,we canalsocalculate the ReturnonInvestmentbytakingthe
cumulative NPV anddividingitbythe cumulative PV of all costs.Eventhoughthisapplicationwouldbe
usedindefinitely,since therewere no upfrontcostandthe annual benefitsandcostsneverchange the
ROI will neverchange nomatterhowlongthe projectlasts.The overall returnoninvestmentis280.38%.
Thisis an outstandingreturn.

15. 15
Discount Rate: 8.00%
YEAR OF PROJECT >>> 0 1 2 3 4 5
Discount Rate 100.00% 92.59% 85.73% 79.38% 73.50% 68.06%
Net economic benefit -$ 677,360.85$ 677,360.85$ 677,360.85$ 677,360.85$ 677,360.85$
PV of Benefits -$ 627,186$ 580,728$ 537,711$ 497,880$ 461,000$
Cumulative PV of Benefits -$ 627,186$ 1,207,914$ 1,745,625$ 2,243,505$ 2,704,505$
One-time COSTS -$ -$ -$ -$ -$ -$
Recurring Costs -$ (178,076.90)$ (178,076.90)$ (178,076.90)$ (178,076.90)$ (178,076.90)$
PV of Costs -$ (164,886.02)$ (152,672.24)$ (141,363.18)$ (130,891.84)$ (121,196.15)$
-$ (164,886.02)$ (317,558.26)$ (458,921.44)$ (589,813.28)$ (711,009.43)$
NPV -$ 462,299.95$ 428,055.51$ 396,347.69$ 366,988.60$ 339,804.26$
Cumulative NPV -$ 462,299.95$ 890,355.46$ 1,286,703.15$ 1,653,691.76$ 1,993,496.02$
ROI 280.38% 280.38% 280.38% 280.38% 280.38%
Economic Feasibility Analysis - Customer Tracking System Project
Cost Benefit Analysis using Present Value
0 1 2 3 4 5
NPV $- $462,299. $428,055. $396,347. $366,988. $339,804.
Cumulative NPV $- $462,299. $890,355. $1,286,70 $1,653,69 $1,993,49
$-
$500,000.00
$1,000,000.00
$1,500,000.00
$2,000,000.00
$2,500,000.00
Part VIII: Proposal Summary
In a requestfromthe CaliforniaDepartmentof Technology,TeamOne hasdecidedtocreate a
webapplicationanddatabase incompliance tothe standardsof the state department.Of those
standards,TeamOne will be implementingawebapplicationwhere ProjectManagerswill be able to
create,access,and editmultipleprojects.ProjectManagerswill have accesstocreate accounts,grant
usersaccessto theirprojects,andsetauthorizations.Userswill have accesstothe webformstoupdate
the contentof the CA-PMMtoolkitfortheirproject.A database will be createdtostore informationand
reduce data redundancy.Finally,administratorswill have fullaccesstoeveryaccountto assistuserswith
needsthatmay arise.Due to insufficiencieswiththe currentCA-PMMtoolkit,TeamOne’sprimaryfocus
isto create a whole newwebapplicationanddatabase thatissufficient,reliable,andeasy-to-use.Team
One has effectivelyanalyzedboththe businessandsystemportionsof the projectandhas determined
the necessarystepstobuildanintegrateddatabase forthe CaliforniaDepartmentof Technology.

16. 16
A prototype hasbeenconstructedtodemonstrate how the final productwillfunctionwhenthe
projectisultimatelyfinished.The toolsusedinthisendproductinclude MicrosoftSharepointand
SqlServer.All the necessarytoolsTeamOne hasusedorplanon usingrequire zerocoststo the end
usersand shouldfinanciallybenefitthe annual budgetof the CaliforniaDepartmentof Technology.With
the necessarytools,TeamOne hascreateda prototype versionof the webapplicationanddatabase
withthe lookand feel of the CA-PMMtoolkittoperformthe necessaryfunctionspreviouslymentioned.
The newfunctionalitywill provide the enduserswithawebapplication thatissimple touse andwitha
professionallook.The final designandimplementationwill notbe readyuntil the endof the Fall
semesterof 2015.

17. 17
Appendix A: System Proposal

18. 18
Part I: Service Request
A. Company Summary
Name: CA Departmentof Technology
Address: 1325 J Street
Suite 1600
Sacramento,CA 95814
Phone: (916) 319-9223
Contact: n/a
General Description:
The CA Departmentof Technologyhasthe followingmandatedresponsibilities:
●Advisethe Governoron the strategicmanagement and direction of theState’sinformation
technology resources.
●Minimize overlap,redundancy,and costin stateoperationsby promoting theefficientand
effectiveuse of information technology.
●Coordinateactivitiesof Agency Information Officers,agency Chief Information Officers,and the
Director of OTech for purposesof integrating statewidetechnologyinitiatives,ensuring
compliancewith information technologypoliciesand standards,and promoting alignmentof
information technology resourcesand effectivemanagementof information technology
portfolios.
●Workto improveorganizationalmaturity and capacity in theeffective managementof
information technology.
●Establish performancemanagementand improvementprocessesto ensurestateinformation
technology systemsand servicesareefficient and effective.
The reorganizationof the CaliforniaTechnologyAgencyintothe CaliforniaDepartmentof
Technologyincludedthe creationof the Statewide TechnologyProcurementDivision,whichmanages
procurementforthe statesIT projects.
B. Project InitiationDescription
As of January1, 2009, the CaliforniaDepartmentof Technologyrequiresall ITProjectManagers
to use the CaliforniaProjectManagementMethodology(CA-PMM).The CA-PMMtoolkitisan excel

19. 19
template thatassistsProjectManagersinmeetingthe requirementsof the CA-PMM.OurMIS 160
Professor,SpirosVelianitis,heardof some complaintsfromprojectmanagersaboutusingthisexcel
template,includingthe difficultyof sharingandaccessingthe tool kit.Afterreviewingthe CA-PMMtool
kit,he identifiedseveral issuesanddeterminedourclasscouldcreate aneffective solutiontothese
issues.Whenhe presentedthispotential projecttothe class,our teamagreedtodevelopasoftware
solutionforthisproblem.
C. BusinessDrivers
1. Problems
A problemexistswhenthere isadifference betweenthe expectedperformance of software,
and the relativelypooractual performance of the software.Atthispoint,there are noidentified
problemswiththe CA-PMMtool kitsince the software performsasexpected.
2. Opportunities
An opportunityexistswhenthere isadifference betweenthe actual performance of software,
and the potentiallyimprovedperformance of the software.We identifiedseveralpotential
opportunities toimprove the tool kit.
i. Accessibility
Currently,ITProjectManagershave trouble accessingthe correctversionof the CA-PMMtool
kitquicklyandeasily.Asanexcel file,the tool kitusesthe file basedapproachtostorage,andcomes
withall the disadvantagesof afile basedsystem.Examplesof disadvantagesinclude dataredundancy,
data inconsistency,dataisolation,dataatomicity,datadependence,datasharing, anddatasecurity.
Each of these factorsaffectaccessibilitytosome degree.Accessibilitycouldbe improvedbychanging
froma file basedstorage systemtoanapplicationwithadatabase solution.
ii. Sharingand Collaboration
Sharingisalso affectedbythe use of a file basedsystem(discussedabove).Inparticular,sharing
isaffectedbythe followingdisadvantagesof the filebasedsystem:datasharing,dataredundancy,and
data inconsistency.Evenif teammembersshare the excel file usingacloudservice (e.g.Google Drive,
Dropbox),if theytryto accessthe file atthe same time theycouldruninto issuesmergingthe fileswhen
multiple versionsof the same documentare created.Synchronouscollaborationwouldsolve these
issues,butthe software providingsynchronouscollaborationwith MicrosoftExcel files(Office 365 and
Google Sheets) alsohave reducedfunctionality,andwouldnotmeetthe requirementsof the CA-PMM
tool kit.

20. 20
iii. User Interface
Since the currenttoolkitismade inexcel,there isplentyof roomforimprovementwhenit
comesto designingthe interface.Three areasof improvementinclude organizing,economizing,and
communicatingusingaGUI interface.Whenitcomesto organization,consistencyandnavigabilitycould
especiallyuse some improvement.
3. Mandated Compliance
Compliance issuesexistwhenthe actual performance of the software doesnotmeetmandated
requirements.Thisprojectdoesnotaddressanyspecificcomplianceissues,butbyaddressingthe
opportunitieslistedabove,the software shouldassistprojectmanagersinmeetingthe CA-PMM
requirements.
D. AnticipatedBusinessBenefits
By improvingthe accessibility,sharing,andinterface andmovingfromafile basedstorage
systemtoa database storage system,we expectproductivitytobe significantlyincreased.Productivityis
a functionof bothefficiencyandeffectiveness.Effectivenessisthe successful completionof objectives,
while efficiencyisminimizingthe resourcesneededtocompletethose objectives.Forobviousreasons,
improvingaccessibilityandsharingwillimproveproductivitywhenprojectmanagersneedtouse the
tool kiton multiple devices,orwhenmultiple usersneedtoaccessthe kit.Inaddition,allowingmultiple
usersto easilyaccessthe tool kitwill capitalize onthe unique knowledge,skills,andexperience of those
members.Bychangingfroma file basedstorage system, we canavoidthe several disadvantages
associatedwithsuchsystems(dataredundancy,inconsistency,isolation,atomicity,dependence,
sharing,andsecurityandprogram maintenance).Byreducingthe effortnecessarytomake sure the
correct data isenteredintothe tool kit,we will significantlyincrease efficiency.Inaddition,we will
reduce the riskthat managerswill relyonincorrectorout of date information,therefore increasing
effectiveness.
E. SystemCapabilities
The newsystemneedstobe accessible tomanyusersondifferentdevicesindifferentlocations.
Multiple userswillneedtobe able toaccessthe systematthe same time.Authenticationand
authorizationwillbe necessary.Itwill be necessaryforuserstobe able tocreate new projectswithin
the system,aswell asopenand editexistingprojects.AnupdatedGUIisalsoa requiredcapability.As
mentionedbefore,we plantoaddressthe organizationof the userinterface byimprovingconsistency
and navigability,thoughwe alsoplantoaddress otherfactorsrelatedtoorganizing,economizing,and
communicatingonuserinterface.
We alsohave a wishlistforcapabilities.Itwouldbe nice if we couldmake atool for creating
formsthat couldbe sentto a clientthatwouldautomaticallyupdate data inthe system.Also,providing
synchronouseditingof a projectwouldbe aplus,thoughitmay not be absolutelynecessary.

21. 21
F. Company Size and Locations
Accordingto the CaliforniaGovernor’sProposedBudgetforthe fiscal yearendingJune 30,2016,
the Departmentof Technologyhas910.7 positions,andhastotal fundsof $373,006,000.
G. Organizational Chart
The CA Departmentof Technologyhaseightdepartmental branches.See Figure 1foran
organizational chartof the Departmentof Technology,andFigure 2for an organizational chartof the
State of California.The Departmentof Technologyispartof the GovernmentOperationsAgency.Our
applicationwillprimarilyserve the ITProjectOversightDivisionwithinthe Departmentof Technology.
H. Transaction Typesand MonthlyVolumes
The monthlyvolume forthisapplicationiscurrentlyunknown,butwe estimatethataroundfive
hundredprojectswill be managedonamonthlybasis.
Part II: Goalsand Objectives
A. MissionStatement
The IT ProjectOversightand Consulting Division overseestheState’sIT projectportfolio.To that
purpose,wepromotesmartITinvestmentsand effectiveprojectmanagementpractices.Asa
CapabilityMaturityModelIntegration (CMM) certified organization,westandardizeproject
managementand offeradvice on projectmanagementbestpractices.
B. Organizational Goals
1. StrategicGoals
Goal 1. Responsive,Accessible,and MobileGovernment
Goal 2. Leadership and Collaboration
Goal 3. Efficient and Reliable Infrastructureand Services
Goal 4. Secured Information
Goal 5. CapableInformation Technology Workforce
Goal 6. Responsiveand EffectiveIT ProjectProcurement
2. Guiding Principles
Principle 1. Be Accountable
Principle 2. Be Service Driven

22. 22
Principle 3. Collaborate&Cooperate
Principle 4. Understand EnterpriseValue
Principle 5. DemonstrateStrong Leadership
C. Objectives
Objective 1. Increase the successrate of informationsystemsprojectsbyfive percent,startingJuly
1, 2017.
Objective 2. Decrease the cost of completinginformationsystemsprojectsbyten percent,starting
July1, 2017.
Objective 3. Decrease the time neededtocompleteinformationsystemsprojectsbytenpercent,
startingJuly1, 2017.
Part III: FeasibilityStudy
A. Operational Feasibility
Whenassessingthe operationalfeasibilityof aninformationsystemsproject,itisimportantto
have a clear understandingof the plannedfeaturesof the informationsystemsandtheirpotential
impacton businessprocesses.
1. Functionality
In orderto capitalize onthe potential benefitslistedinthe opportunitiessectionabove(seePart
I: Service Request,BusinessDrivers),includingimprovingaccess,collaboration,andthe userinterface,
we have identifiedseveralelementsthatneedtobe presentinthe new informationsystem.Accessto
the applicationneedstobe availableoverthe web.Inaddition,multiple userswill needtoaccessthe
applicationatthe same time.The informationwill needtobe updatedautomatically,withoutthe
disadvantagesof the file basedstorage systemthe excel tool kitreliedon(dataredundancy,
inconsistency,isolation,atomicity,dependence,andsharing,andprogrammaintenance).
Authenticationandauthorizationwill alsobe necessaryfeatures.
Some optional (orwishlist) featurescouldpotentiallybe implemented,butare notabsolutely
necessaryforthe informationsystemtosucceedinthe organization.These featuresincludecreating
desktopandmobile applicationsthatsyncwiththe online application.Also,allowinguserstogenerate
formsthat couldbe sentto clientstofill out and update the database wouldbe beneficial.A signoffand
issue managementfeature couldalsobe includedtofacilitatecollaboration.
2. Impacton BusinessProcesses
Making these changestothe functionalityof the informationsystemshouldnotrequire
substantial changestobusinessprocessesandstructures,thoughitwillrequireafew minorchangesfor

23. 23
all projectmanagerswithinthe organization.Twowaysthe new informationsystemwill impactthe
organization’sprocessesinclude 1) the webapplicationwillrequireaninternetconnection,and2) the
flexibilityprovidedbythe excel applicationwillbe lost.
If the desktopapplicationisnotincludedinthe system,thenthe webapplicationwill require a
reliable internetconnectiontofunction.Thiscouldpresentaproblemif the projectmanagersvisitclient
sitesthatdo not have a reliable internetconnection.However,thisshouldnotbe toobigof an
organizational change since areliableinternetconnectionisalsonecessaryforotherapplicationsa
projectmanagerwill needtouse.
Anotherissue isrelatedtomovingfromexcel.Excel isanextremelyflexibleapplication,and
projectmanagerscouldpotentiallyeditthe CA-PMMtoolkittoperformtheirownanalysiswithout
leavingthe program.Theycouldnotperformthistype of flexible analysisinawebapplication.This
shouldnotimpactthe projectmanagersactivitiestoomuch,since theycouldopenanexcel spreadsheet
separatelytoperformanyof theirowntheirownanalysisif necessary.
3. AlignmentwithOrganizationalGoals
The functionalityof the newapplicationisinline withmanyof the Department’sgoals.This
includespromotingaresponsive,accessible andmobile government,increasedleadershipand
collaboration,providingefficientandreliable infrastructureandservices,securinginformation,
increasingthe capabilityof theirinformationtechnologyworkforce,andprovidingresponsive and
effectiveITprojectprocurement.
4. OperationalFeasibilitySummary
Since changesto the organization’s structuresandproceduresare notsubstantial and
widespread,thisprojecthaslowrisk.Inaddition,the projectalignswithorganization’sgoals.
Conclusion:The projectisoperationallyfeasible.
B. Technical Feasibility
1. ProjectSize
The projectsize is relativelysmall.There are onlysix membersonthe projectteamworkingpart
time to complete the project,the projectdurationislessthanone yearsince itstartedinMarch 2015
and shouldbe completedbyDecember2015, there shouldonlybe one organizationaldepartment
involvedwhenwe dointroduce the projecttothe CA Departmentof Technology’sITProjectOversight
and ConsultingDivision,andthere willbe nooutsourcinginvolved.

24. 24
2. ProjectStructure
Overall,the projectstructure shouldhave alow levelof complexity.The projectisarenovation
of an existingsystemwithfewchangestothe requirementsof the existingsystem.The requirementsof
the existingsystemare welldefined,highlystructured,andeasilyobtainable.We alreadydiscussedthe
organizational,procedural,andstructural changesduringoperational feasibility.Usersare already
willingtoacceptthe applicationandshouldbe willingto participate inthe developmenteffort.We
haven’tintroducedthe applicationtomanagement,sowe don’tknow whethertheywill be committed
to the newsystem.We alreadyhave anideaof the functionalityusersdesire inthe new application.Any
furthercontact withuserswill be toclarifyandmake small adjustmentstothe functionality.
3. DevelopmentGroup
The membersof our groupare alreadyfamiliarwithdevelopingawebapplicationfromour
experiencesinMIS120. The software we planto use to developthe applicationinclude VB.NETandSQL
Server2008. We have extensive experience withVisual Studio afterworkingwithitinMIS 15 and MIS
120. We had some experience workingwithSQLServer2008 in MIS 120. In addition,we shouldbe
gettingmuchmore experience indesigningdatabasesandworkingwithSQLinMIS 150. In addition,the
developmentteamisfamiliarwiththe problemsthisinformationisfacedwith(e.g.,pooruserinterface).
4. UserGroup
As IT projectmanagers,the usergroupshouldbe familiarwiththe informationsystems
developmentprocess.Inaddition,manyof themhave proposedthe change toa webapplicationbe
made so theyshouldbe familiarwiththe applicationarea.The use of the systemwill notchange much.
Theywill have toaccess the projectoverthe weband create andmanage the projectsviathe web
applicationinsteadof witha file basedstorage system.Theyshouldbe able tocreate andaccess their
account fairlyeasily,andthe projectmanagementfunctionalityinthe applicationshouldbe easierthan
a file basedstorage system
5. Technical Feasibility Summary
The projectsize isrelativelysmall andthe projectstructure isnotverycomplex.Inaddition,the
developmentgroupandusergroup are sufficientlyfamiliarwiththistype of project.
Conclusion:The projectistechnicallyfeasible.
C. Economic Feasibility
1. Cost/ Benefit Analysis
For the fiscal yearendingJune 30, 2016, the State of Californiabudgetedexpendituresof
$373,006,000 for the Departmentof Technology.Inaddition,the Departmentof Technologyistracking
active projectswithatotal expectedcostof $4,624,072,501. Improvingthe CA-PMMpromotesthe

25. 25
efficientandeffectivemanagementof these resources,andcouldresultinsignificantbenefits.The
estimatedcostsandbenefitsare brokendownbelow.
i. Annual Benefits
Most of the tangible benefitsrelatedtothe CA-PMMare cost reductions.The benefitsof
improvedprojectoutcomesare still intangiblesince we cannoteasilyestimate them.Forthisreason,we
will focusoncalculatingthe financial benefitof reducingprojectcosts.Inorderto identifythe annual
benefit,we decidedtodeterminethe expectedtotal annual cost,estimate the percentage reductionsof
the cost whenour informationsystemisimplemented,andthencalculate the annual benefit.The
expectedannual costwascalculatedbasedonthe active projectsonMarch 27, 2015. To take the data
fromprojectsactive ona single date andextrapolate ittorepresentanannual amountisnotan optimal
estimationprocedure,butitwasthe bestavailable withthe datawe foundonline.Toestimate the
annual cost,we tookthe total amount foreach of the projects,anddividedeachbytheirestimated
duration.We estimate onlyaboutfive percentof thisamountcanbe affectedthroughmore efficient
and effective use of the CA-PMMtoolkit.Of thisfive percent,we calculatedbenefitsbyestimating
increasedproductivitydue toseveral keyfactors.Due tothe new userinterface,easieraccess,and
collaboration,the time needtoworkonthe tool kitshoulddecrease,resultinginanincrease in
productivityof 0.25%. We expectthatthe enhanceduserinterface andcentral storage providedbythe
database shouldreduce errors,increasingproductivitybyanadditional 0.25%.We alsoexpecta 0.50%
increase inproductivitydue tobetterplanningandcontrol asa resultof the improvedtool kit.Overall,
thisshouldresultinanannual financial benefitof $677,360.85.
Annual Project Cost * 1,354,721,690.45$
Percentage Attributable to CA-PMM 5%
Cost Attributable to CA-PMM 67,736,084.52$
Category In $US
% Increase in
Productivity
Cost reduction or avoidance -$ 0.00%
Error reduction 169,340.21$ 0.25%
Increased flexibility -$ 0.00%
Increased speed of activity 169,340.21$ 0.25%
Improvement in management planning and
control 338,680.42$ 0.50%
Other -$ 0.00%
Total Tangible Benefits 677,360.85$
Tangible Benefits
*Annual project cost is based on a calculation of the total annual cost of projects
under construction on March 27, 2015. Since our sample only includes projects
active on a single day, it is more likely to exclude short term projects. Since
projects with shorter development periods have less risk, the tangible benefits
associated with the sample selected should be relatively larger. Therefore, our
estimation should be conservative since it may exclude projects that would have
less tangible benefits.

26. 26
ii. One Time Costs
Our teamwill developthe softwareforfree sothese costswill be zero.Inaddition,all servers
will be leasedsonewhardware costswill alsobe zero.Site preparationwill be zerodollarssince the
software will notbe usedina particularlocation,butratherviathe weboveruser’sdevices.We will not
have to investinadditional software either.There willbe no upfrontcostsforthisapplication.
Category In $US
Development costs -$
New hardware -$
New software -$
Site preparation -$
Other -$
Total Tangible One-Time Costs -$
Tangible One-Time Costs
iii. RecurringAnnual Costs
The most expensive recurringcostwill be the salaryforthe new employeeswhowill maintain
the informationsystem.We expectthiscosttobe around$120,000 to covereach of their$60,000
annual salaries.Usertrainingwill alsobe expensive.We calculatedthatthere wouldbe anaverage of
8.46 newprojectsperyear (44 projects / 5.22 yearsaverage development).If projectmanagersfor
these newprojectshave anaverage billable rate of $150 per hour,and the usertrainingtakesfour
hours,thenthe average annual cost of usertrainingshouldbe $5,076.90 ($150 perhour x 4 hours =
$600 per projectx 8.46 projects).The onlynecessaryincrementalstorage willbe tostore a backup of
the application,userdocumentation,andtechnical documentation.Thisstorage shouldbe minimal,so
we estimate ittocost around $6,000 peryear.Incremental communicationwill be necessarytoprovide
supportfor the application.We estimatethiscosttobe around$7,000 peryear. Inaddition,we expect
to have about$40,000 peryear to lease application,web,anddatabase servers.Overall,the annual
recurringcost will be $178,076.90.
Category In $US
Application software maintenance 120,000.00$
User training 5,076.90$
Incremental data storage required 6,000.00$
Incremental communications 7,000.00$
New software or hardware leases 40,000.00$
Supplies -$
Other -$
Total Tangible Recurring Costs 178,076.90$
Tangible Recurring Costs
2. PaybackPeriod /Break Even Point
Usingthe cost / benefitanalysisfromthe priorsection,we alsocalculatedthe payback.There
are no benefitsinyearzerosince the projectisstill indevelopment.Howeverthisprojectwillalsohave

27. 27
no up frontdevelopmentcost.Since recurringannual benefitsandcostsstart inyear one of
implementation,andannual benefitsexceedannual costs,the breakevenpointwill be exactlythe
beginningof the application’simplementation.
Benefits of option 0 1 2 3 4
Annual Benefits -$ 677,361$ 677,361$ 677,361$ 677,361$
Total Benefits -$ 677,361$ 677,361$ 677,361$ 677,361$
Costs of option 0 1 2 3 4
Initial Cost -$ -$ -$ -$ -$
Annual Recurring Cost -$ 178,077$ 178,077$ 178,077$ 178,077$
Total Costs -$ 178,077$ 178,077$ 178,077$ 178,077$
Net benefits/costs -$ 499,284$ 499,284$ 499,284$ 499,284$
Cumulative benefits/costs -$ 499,284$ 998,568$ 1,497,852$ 1,997,136$
Break Even Period in Years 1.00
Payback Analysis (CA-PMM Web Application)
3. Net PresentValue(NPV)
For our netpresentvalue analysis,we chose adiscountrate of 6.00%. Thisrate isappropriate
for thisprojectsince itislowrisk.We usedthe resultsof ourcost / benefitanalysistoperformthis
calculation.Basedonthiscalculation,ourprojectwill resultincumulative discountedcostsavingsof
$462,299.95 inthe firstyear of implementation,androughly$1,993,496.02 by the endof the fifthyear
afterimplementation.Evenafterdiscountingcashflows,the benefitsoutweighcostsbothinthe short
termand longterm.
Usingthe netpresentvalue,we canalsocalculate the ReturnonInvestmentbytakingthe
cumulative NPV anddividingitbythe cumulative PV of all costs.Eventhoughthisapplicationwouldbe
usedindefinitely,since therewere no upfrontcostandthe annual benefitsandcostsneverchange the
ROI will neverchange nomatterhowlongthe projectlasts.The overall returnoninvestmentis280.38%.
Thisis an outstandingreturn.

28. 28
Discount Rate: 8.00%
YEAR OF PROJECT >>> 0 1 2 3 4 5
Discount Rate 100.00% 92.59% 85.73% 79.38% 73.50% 68.06%
Net economic benefit -$ 677,360.85$ 677,360.85$ 677,360.85$ 677,360.85$ 677,360.85$
PV of Benefits -$ 627,186$ 580,728$ 537,711$ 497,880$ 461,000$
Cumulative PV of Benefits -$ 627,186$ 1,207,914$ 1,745,625$ 2,243,505$ 2,704,505$
One-time COSTS -$ -$ -$ -$ -$ -$
Recurring Costs -$ (178,076.90)$ (178,076.90)$ (178,076.90)$ (178,076.90)$ (178,076.90)$
PV of Costs -$ (164,886.02)$ (152,672.24)$ (141,363.18)$ (130,891.84)$ (121,196.15)$
-$ (164,886.02)$ (317,558.26)$ (458,921.44)$ (589,813.28)$ (711,009.43)$
NPV -$ 462,299.95$ 428,055.51$ 396,347.69$ 366,988.60$ 339,804.26$
Cumulative NPV -$ 462,299.95$ 890,355.46$ 1,286,703.15$ 1,653,691.76$ 1,993,496.02$
ROI 280.38% 280.38% 280.38% 280.38% 280.38%
Economic Feasibility Analysis (CA-PMM Web Application)
Cost Benefit Analysis using Present Value
4. EconomicFeasibility Summary
Our applicationwillhave annual benefitsof $677,360.85, initial costsof $- , and recurring
annual costs of $178,076.90 . Thisresultsina paybackperiod/ breakeven pointof 1.00 year.The project
will recoup itscostsveryquickly.AfterperformingaNPV analysis,the cumulative netpresentvalue of
the projectfor cash flowsthroughthe endof yearfive afterthe implementationis$1,993,496.02.
Finally,we alsocalculatedthe ReturnonInvestment.The overall ROIwillbe 280.38% regardlessof the
durationof the benefitsof the project.
Conclusion:The projectiseconomically feasible.
D. Schedule Feasibility
Since we were notcontactedby the client,there isnoparticulardeadlineforthisproject.The
deadline forourclasswill be December2015. Our teamisconfidentwe canfinishthisprojectbythat
date.If we fall behindschedule,agroupfromthe Spring2016 class couldpotentiallyfinishthe project.
The breakdownof the time necessarytocomplete majorareasandmeetmilestone deadlines follows.
1. Planning
The planningphase isessentiallycomplete afterthe submissionof thisfeasibilitystudy.We had
to pushback our milestonedeadlineforthisphase since we hadtorejectour firstpotential projectand
choose a newone.

29. 29
2. Analysis
i. BusinessAnalysis
The milestone deadline forbusinessanalysisisApril15,2015. Thiswill be a difficultdeadline to
meetsince ourfeasibilityreportwaspushedoutwhenwe changedourproject.Luckily,we have two
people assignedtoperformbusinessanalysiswhothinktheycancomplete the activitiesinthe required
amountof time.The activitiesincludeconductinganalysis,describingthe userrequirements,and
defininginfrastructure requirements.Unfortunately,noneof these activitiescanbe completed
concurrently.Asa result,we plantoworktogetheroneach activitytoshortenthe time neededtofinish
and move onto the nextactivity.Determiningthe conductof analysisshouldtake aboutthree days.
Identifyinganddefininguserrequirementsand performinginfrastructureanalysisshouldtake abouttwo
dayseach.
ii. SystemsAnalysis
The mile stone deadline forsystemsanalysisisApril 27,2015. Activitiesrelatedtothismilestone
include creatinguse case diagramsandactivitydiagramsforthe existingsystemandthe proposed
system,aswell asclassdiagramsand sequence diagramsforthe proposedsystem.These taskswillbe
difficulttoaccomplish.However,we alsohave afull twoweekstocomplete the workandhave two
people whoare confidentthey cancomplete the work.Otherteammemberscanbe assignedtowork
on the systemsanalysisif necessaryaswell.Infact,we are planningoninvolvingmostourgroupin the
systemsanalysisinsome waysoourentire groupcan have a clearunderstandingof the systems
requirementsduringdesignandimplementation.
iii. SystemPrototype andInterface
The milestone deadline foroursystemprototype andinterface isMay6, 2015. We will have a
total of fourdays afterour systemsanalysis.We will nothave muchtime tocomplete the activities
relatedtothismilestone,butmostof the workwill be guidedbythe activitiesfromthe systemsanalysis
phase.Activitiesfromthisphase include prototypingthe GUIinterface,database,andreporting,aswell
as documentinginstallationanduse instructions.Deliverablesincludeacompleteddatabase (definedby
UML diagramsfrom systemsanalysis),the completedmainGUIinterface andall submenusand
interfaces,aformand a report,and the installationanduse documentation.We expecttobe able to
complete these requirementsinthe time allotted.We willalsobegintoconsiderthe designof manyof
these deliverablesduringsystemsanalysis,makingiteasiertomeetthismilestone deadlineinsucha
short periodof time.
iv. SystemRecommendation
The systemrecommendationcanbe completedconcurrentlywiththe systemprototype and
interface.The milestonedeadlineisMay7, 2015. Deliverablesforthismilestone include the Transmittal
Letter,Executive Summary,DetailedResults of Analysis(updatedBusinessAnalysisandSystems

30. 30
Analysis),SystemsAlternatives,SystemsAnalysts’Recommendations,ProposalSummary,anda
Presentation.All of these deliverablescanbe workedonconcurrentlyandwill be brokenupbetween
fourmembers of our group,twoof whichwill alsobe workingonthe systemprototype concurrentlyand
can be flexiblyreassigned.We expectthe transmittal letter,executive summary,recommendations,and
proposal summarytotake one dayeach, the detailedresultsof analysisandsystemsalternativestotake
three dayseach,and the presentationtotake the full five daysavailable.The presentationwill be
updatedaswork on the systemprototype andsystemrecommendationsiscompleted.
3. Design and Implementation
Designandimplementationwillbe performedduringthe Fall 2015 semesterinshort,
incremental cyclesprovidingchangingfeatureswitheachiteration.Itisimpossibletoprovide specific
deadlines atthispoint.However,basedonthe preliminarysystemrequirements,the size of the project,
and the developer’s familiaritywiththe technologywe willbe using,we shouldbe able tocome upwith
a solutioninthe time allottedbetweenSeptemberandDecember2015.
4. ScheduleFeasibility Summary
All activitiesfromthe planning,analysis,design,andimplementationphasesshouldbe
completedbytheirmilestonedeadlines.Inaddition,thisprojectwasnotpresentedtothe Department
of Technologyyet,sothe projectcouldbe completedbythe Spring2016 MIS 161 class if necessary.
Conclusion:The project’sschedule isfeasible.
E. FeasibilitySummary
Basedon the operational,technical,economical,andschedulingfeasibilitystudies,the projectis
feasible.
Conclusion:The projectisfeasible

31. 31
Figures
Figure 1. CA Departmentof Technology OrganizationalStructure
Figure 2. Stateof California OrganizationalStructure

32. 32
Appendix B: Business Analysis

33. 33
Part I: Conduct of Analysis
A. AnalysisMethodsUsed
1. Documentation Collected
Team 1 examinedharddocumentsinorder toreceive andanalyze the informationforthis
project.The informationexaminedandanalyzediscurrentlyonthe CaliforniaDepartmentof
Technologywebpage underthe CaliforniaProjectManagementMethodology(CA-PMM).
2. Conducting End UserInterviews
Due to the nature of thisprojectand the deadline required,team1didnot possessthe time and
resourcestoconduct interviewsandaskenduserquestions.
3. Survey Conduction
Surveyswere notconductedbyTeam1. The informationprovidedbyProfessorSpirosandthe
hard documentsexaminedbyTeam1 were sufficientinorderconductandsubmitthe necessary
documentation.
4. Observation
Team 1 was not able toobserve state workersatthe CaliforniaDepartmentof Technologyand
otherfacilitiesimplementingthisprojectdue toconflictingschedulesanddeadline requirements.
However,the informationprovidedbyProfessorSpirosandotherharddocumentsfoundonthe website
allowedTeam1 to accesscritical informationtobypassthisstepinthe process.
5. PrototypeDevelopment
Duringthisphase of the project,Team1 focusedattentionprimarilyonthe Software
SpecificationRequirements(SRS)andInfrastructure Analysis.However,Team1was able toanalyze the
original systemunderthe toolkitpresentedunderthe CaliforniaProjectManagementMethodology
sectionof the CaliforniaDepartmentof Technologywebsite.The initial prototype Team1will presenton
May 4th isgoingto prepare,design,andconstructduringthe designphase of thisproject.
6. JAD Sessions
JointApplicationDesign(JAD)sessionswerenotheldtoretrieve the informationneededto
continue withthisproject.Time restraintsandconflictingschedulesimpactsthe availabilitytomeetand
discussthisprocess.The users,managers,andTeam1 (the analysts) were notable tosetaside afew
daysto holdintensive meetingstospecifyorreview systemrequirements.

34. 34
7. Examination of OutsideVendorSoftware
Team 1 has alreadyestablishedthe software thatwill be usedtoprepare,design,andconstruct
the prototype forthisproject.Therefore,Team1didnot seekoutand examine outsidevendor
software.
B. End UsersContacted
Team 1 acceptedthisprojectwiththe knowledgethatthisprojectneededtobe constructedon
an acceleratedbasis.Inaddition,the time restraintisalsocompoundedwithconflictingschedulesof the
teammembersandmanagersand endusersto meetanddiscussthe systemrequirements.Because of
thisfact, ProfessorSpirosprovidedTeam1withthe resourcesandobjectivesthatisrequiredof this
projectforthe CaliforniaDepartmentof Technology.Team1understandsthroughProfessorSpiros’s
descriptionof the project,aswell asthe documentationgenerouslyprovidedonthe California
Departmentof Technologywebsite the necessaryrequirementsand desirable qualitiesthatneedtobe
available forthe enduserswhenthe projectisultimatelycompleted.Therefore,Team1didnot contact
the endusersto discussthisproject.
C. Records, Forms,and Reports Analyzed
Team 1 analyzeda varietyof records,forms,andreportssolelyprovidedbythe California
Departmentof Technologyunderthe CaliforniaProjectManagementMethodology(CA-PMM).The two
documentswhere the majorityof the informationwascollectedwerefromthe CA-PMMReference
Manual andthe CA-PMMTemplate Instructions.The CA-PMMReference Manual coversanoverviewof
the methodologyframework,projectlifecycle,andanin-depthanalysisof the differentstageswhich
include the Conceptstage,Initiatingstage,Planningstage,Executingstage,andClosingStage.Another
keydetail thatisincludedisanoverview of the toolkitusedandthe differenttemplatesusedduringthe
differentstages.The othermajordocumentationincludesthe CA-PMMTemplate Instructions.This
documentincludeshowtogetstartedwiththe workbook,toolkitcontents,workbooknavigation,how
to use the workbook,savingandexitingthe workbook,andhow toprintthe workbook.Other
supportingdocumentationusedbyTeam1 includesthe frequentlyaskedquestions,requirements
summary,projectstatusreports,andthe trainingrequirements.The frequentlyaskedquestionsisa
documentrespondingtovariousCA-PMM-relatedquestions.The requirementssummaryusesatable
summarizingthe CaliforniaQualifiedtrainingandother CA-PMMrequirements.Team1examinedsome
portionsof the ProjectStatusReportare to be completedandforwardedtothe CaliforniaTechnology
Agency.Finally,Team1 analyzedinformationpertainingtothe trainingrequirementsinclude
informationforITprojectmanagers,projectteamleads,executives,andsponsors,alongwithCA-PMM
traininginformationandrecommendedqualificationsforITprojectmanagers.
D. ProcessesObserved
Team 1 was not able toobserve the processesfirsthanddue toconflictsof time andscheduling.
However,Team1 knowsthe processesthatneedtobe usedand functionalityof the systemdue to

35. 35
informationresearchedandprovidedfromthe CaliforniaDepartmentof Technologywebsite and
ProfessorSpiros.
E. ProblemsEncounteredwith Data Collection
Team 1 was not able toschedule appointmentsandmeetingswithmanagers,supervisors,and
endusersto discussandgather data forthe project.Therefore,Team1didnot encounteranyproblems
inconductingand gatheringdata.
F. Data CollectionInstruments
Team 1 membersextractedandrecordedqualitativedatadescribingthe systemsfunctionalityin
a google sheetsdocumentbyexaminingandanalyzingthe currentfunctionalityrecordedinthe hard
code documentsprovidedonthe CaliforniaProjectManagementMethodologysectiononthe California
Departmentof Technologywebsite.
G. Synopsisof Interviews
No interviewswereconductedbyTeam1 forthisreport.Due to previouslylistedconstraints,
Team 1 gatherednecessaryinformationfromProfessorSpirosandthe harddocumentsobtainedoff the
CaliforniaDepartmentof Technologywebsite.
Part II: Software RequirementsSpecification(SRS)
A. External Interfaces
1. UserInterfaces
The systempresentstohumanwitha displaycalledauserinterface.The usersinteract withthe
systembybothvisual andmotion.The userinterface couldhave a“creatingaccount” tab, “login” tab,
“mainmenu”and otherprimarycategoriestabs.
2. HardwareInterfaces
For hardware to interactwiththe webapplication,ithastogo throughthe operatingsystem
(OS).Because itmanagescomputerhardware andsoftware resourcesandprovidesservicestothe web
applicationitself,the OSiscompatiblewithdifferentcomputerdevicessuchasWindowsand
Macintosh.
3. SoftwareInterfaces
Team 1 will be usinga webapplicationassoftware forthe webpage.The webpage usesto
supportingprogramminglanguagesthatthe webpage hasoffered.Alongwiththe supporting

36. 36
programminglanguages,there will be SQLservertomanage the database,since SQLserverprimary
functionisto store andretrieve dataas requestedbythe programinthe webpage.
B. Functions
To properlyassessthe functionsrequiredof the informationsystem, we designatedclassesof
usersand definedthe functionsforeachclass.The userclasseswe definedinclude:1) ProjectTeam
Member,2) ProjectManager,3) Projectteammembers(includesprojectmanager),and3) Application
Administrator.Systemwide authorizationswill be definedandenforcedforeachtype of useron a
hierarchical basis(i.e., the ProjectManagerwill have all of the ProjectTeamMember’ssystemwide
authorizations,andthe ApplicationAdministratorwill have all of the ProjectManager’ssystemwide
authorizations.
1. ProjectTeam Member
i. AccountRegistration
Description:All users shouldbe able toregisterforanaccount createdforthemby an existing
ProjectManager or the ApplicationAdministratorviathe web.Havingthe ProjectManageror
ApplicationAdministratorthe accountshouldeliminate the creationof unnecessaryaccounts.Users
shouldreceive anemail fromthe systemafterthe ProjectManagerorApplicationAdministratorcreates
an account (see below)withinstructionstoregister.Afterfollowingthe instructions(eithertofollowa
linkor copya key,navigate toa webpage,andenterthe keyina form),userswill needtoenter
informationonaregistrationform(e.g.,required:username,password,reenterpassword,email;
optional:phone;possible:registrationkey,securityquestions).Datavalidationshouldbe performedon
each of the fieldstomake sure theymeetrequirements(e.g.,inputmaskforemail andphone,
usernamesandpasswordsmeetrequirements).Datavalidationcouldbe performedafterthe userexits
a field(forthatspecificfield) orafterthe user clickstosubmit(forall fieldsonthe page).If the data
validationfails,anappropriate messageshouldappearonthe webpage and askthe userto reenter
some information.If the datavalidationsucceeds,thenaverificationpage shouldbe presented,asking
the userto double checktheirinformationbefore submitting.If the userdecidesthe informationis
wrongtheyshouldbe able toeditthe information(whetherthisreturnsthemtothe previouspage or
allowsthemtoeditinformationindividually).Whenthe userverifiesthe informationiscorrect,theyare
directedtoa confirmationpage whichnotifiesthemtheyare able tologin.
Dependencies:Create anaccount(Projectmanager).
Rationalization:Creatinganaccountforall userswill provide the authenticationnecessaryto
properlyimplementanauthorizationmodel forthe application.ProjectManagersandApplication
Administratorscouldcreate authorizations[DS1] fortypesof users,or potentiallyforindividual usersif
we discoverthisisnecessaryata laterphase.Thisis an essential partof the new applicationsince the
informationsystemwillbe storedonanonline database,insteadof anexcel file thatthe managercan
easilymanage byonlysharingitwiththose whoneedaccess.Inaddition,one of the goalsof the new

37. 37
applicationistofacilitate collaboration.Havingthese authorizationssetandcentrallystoredwill allow
Projectteammemberstoeasilyview andeditwhattheyare supposedtowithoutcompromisingthe
system.
ii. Log In
Description:Userswill needtologinto access the application.A loginfieldshouldbe available
on the home screenforthe website,or navigationtoa loginscreenshouldbe available.Userswill need
to entertheirusernamesandpasswordstoaccessthe site.Whenthe usersubmitstheirinformation,
data validationwill occuronthe username andpasswordfieldstocheckwhethertheyare null orfail to
meetrequirements.If theydonotmeetrequirements,the userneedstobe notifiedandpromptedto
returnto the loginscreenandretry.If theyare successful,theywillbe grantedaccessanddirectedto
the applicationdashboard.
Dependencies:Accountregistration(Allusers).
Rationalization:Thisrepeatedauthenticationateachsessionwill ensure onlythoseusers
authorizedtoeditorviewthe informationsystemorportionsof the informationsystemwill be able to.
iii. User Name ResetorRetrieval
Description:The usershouldbe able toresetorretrieve theirusername shouldtheyforgetit
withouthavingto login totheiraccount. The userwouldaccessa username resetpage fromthe home
or loginscreen.There are a multiple waysthisfunctionalitycanbe achieved(e.g.email withalink,email
witha verificationcode,username resetformusinganemail andsecurityquestion).
Dependencies:Accountregistration(Allusers).
Rationalization:One of the goalsforour informationsystemisincreasedaccessibility.If the user
forgetstheirusername,theywouldnotbe able toaccess theiraccount.Havinga resetpage would
increase accessibilitybyallowinguserstoresettheirownusername.Itwouldalsomaintainsecurityby
authenticatingthe userwithsome formof identifyinginformation.Thiswouldalsodecrease the burden
on applicationadministrators,whowouldhave toresetthe usernamesif the userscouldnot
themselves.
iv. PasswordResetorRetrieval
Description:The usershouldbe able toresetorretrieve theirpasswordshouldtheyforgetit
withouthavingtologin totheiraccount. The userwouldaccessa passwordresetpage fromthe home
or loginscreen.There are a fewwaysthisfunctionalitycanbe achieved(e.g.email withalink,emailwith
a verificationcode,passwordresetformusinganemail andsecurityquestion).
Dependencies:Accountregistration(AllUsers).

38. 38
Rationalization:One of the goalsforthe informationsystemisincreasedaccessibility.If the user
forgetstheirpassword,theywouldnotbe able toaccesstheiraccount.Havinga resetpage would
increase accessibilitybyallowing userstoresettheirownpassword.Itwouldalsomaintainsecurityby
authenticatingthe userwithsome formof identifyinginformation.Thiswouldalsodecrease the burden
on applicationadministrators,whowouldhave toresetthe passwordsif the userscouldnotthemselves.
v. EditAccount Information
Description:All usersshouldbe able toedittheirbasicaccountinformation(i.e.,username,
password,email,optional phone,etc.).Inordertodothis,theyshouldhave toverifytheirinformation
(evenif theyare loggedintothe webapplicationalready).Afterverifyingtheiridentity,theywouldbe
broughtto a page where theywouldbe able toedittheiraccountinformation(e.g.,eitherdirectlytoa
page where theycouldedittheiraccountinformation, ora page where theycouldview theiraccount
informationandselectabuttontoeditall or part of theiraccountinformation).Aftertheyenterthe
desiredchangesintoaform,data validationshouldbe performedoneachof the fieldstomake sure
they meetrequirements(e.g.,inputmaskforemail andphone,usernamesandpasswordsmeet
requirements).Datavalidationcouldbe performedafterthe userexitsafield(forthatspecificfield) or
afterthe user clickstosubmit(forall fieldsonthe page). Thenaverificationpage shouldbe presented,
askingthe userto double checktheirinformationbeforesubmittinginformation.If the userdecidesthe
informationiswrongtheyshouldbe able toeditthe information(whetherthisreturnsthemtothe
previouspage orallowsthemtoeditinformationindividually).If the userdidnotedittheiremail,they
shouldbe directedtoa confirmationpage.If the usereditedtheiremail address,theyshouldbe
directedtoan email verificationpage askingthemtovisittheiremail withinstructionstoverifytheir
email.Whenthe userverifiestheiremail (e.g.,alinkora keyto enterinthe email verificationpage sent
inthe email) theyare directedtoaconfirmationpage.
Dependencies:Accountregistration(ProjectTeamMember)
Rationalization:ProjectTeamMembershouldbe able toedittheirownidentifyinginformation
to keepitup to date and to change passwordstomeetsecuritystandards.Byhavingthe user
authenticate again,youensure itisthe userchangingtheirownaccountinformation,andallow themto
easilyupdate theirowninformationwithoutcontactinganApplicationAdministrator.
vi. Work PaperCompletionandOperations
Description:The workpapersincludedinthe CA-PMMtool kitcan be verydifferent, buthave a
commonsetof featuresthatare reused.A commonfeature inall workpapersisthe abilitytoquickly
navigate toand the previousandsubsequentworkpapers.Some are simpletextboxesthatdonot
populate othercellsinthe currentworkbook. Othersdosimplypopulateothercellsinthe same work
paperor in otherworkpapers,and othersare usedinformulastomake calculations.Theseoutput
calculationsare sometimesusedtoproduce graphics,suchascharts. These charts andcalculationswill
needtoupdate as the informationisenteredintothe webpage.Anexampleof awork paperwithtext
box input,calculations,andgraphical outputisthe complexityassessment.Thistakesestimatesfor

39. 39
variousfactorsaffectingbusinessandsystemcomplexity,averagesthe valuesentered(won’tinclude
valuesinthe average if valuesare notentered),anddisplaysthe complexityonagraph withthe average
businessandsystemcomplexityasthe axis.The graphichelpsthe userdecide whichcomplexityzone
the projectfallsunder,askssome questionswithradiobuttonanswers,andthenprovidesthe
recommendedexperience level forthe projectmanager.
Dependencies:Create aproject(ProjectManager)
Rationalization:The tool kitsworkpapershelpguide project manager’sthroughthe CA-PMM
process.Improvingthe processof workingonandusingthese workpaperstomanage the projectwill
improve the outcomesof ITprojects.
vii. Optional Feature:WorkPaperandSectionSignoff
Description:Foreachworkpaperwithin the tool kit,individualsshouldbe able tosignoff when
the work paperiscomplete.Since the tool kitdoeshave amulti-level hierarchical structure,itwouldbe
goodif we couldclearlyshowthe hierarchyof the entire toolkitona single page.Individualsresponsible
for a workpaper couldsignoff ona workpaperwhenitis substantiallycomplete orupdated.In
addition,whenateammemberfinishesupasection,theycouldsignoff onthe entire sectionasbeing
completed.Ideally,everyworkpaperandsectioncouldbe displayedonone summarypage thatshows
whenitwas signedoff on.
Dependencies:Create aproject(ProjectManager).
Rationalization:Signoffsallowuserstoquicklyorganizeandidentifywhichsectionsof the toolkit
needtobe worked on,andallowmanagerstodecide whichworkpapersare readyto review.
viii. Optional Feature:Create Issues,LinkIssuestoWorkPapersor Sections
Description:Individualsshouldbe able tocreate multiple issuestobe addressed.Thiswould
essentiallyreplace the issue loginthe existingCA-PMM.Issuesare definedas“unansweredquestions
and differencesof opinion”.The issuewouldhave tobe assignedtoaspecific“owner”whois
responsible forresolvingthe issuebyadue date.The complete listingof fieldsforthe issue logincludes
the issue number,date opened,issue description,impact,raisedby,bestresolvedby,actiontakento
date,owner,nextsteps,due date,anddate resolved.Of course the creationof the issue wouldonly
require the issue number(mostlikelyautomaticallygenerated),date opened,issue description,impact,
raisedby,owner,anddue date to be answered,thougheveryotherfieldbutdate resolvedcould
potentiallybe answered.
Team 1 can alsoconsideraddingafunctionalitytorelate issuestomultipleworkpapersandto
multiple sections.Obviously,some issuesforthe projectwillnotbe relatedtothe workpapersinthe
CA-PMM,so thiswouldhave to be optional.If itisrelatedtoworkpapersin the tool kitthiswouldadd
an extralayerof convenience.Inthiscase,we couldshow issuesbothinanissue summaryandina
hierarchical overview of the toolkitand workpapers.

40. 40
Dependencies:Create aproject(ProjectManager).
Rationalization:Signoffsallowuserstoquicklyorganizeandidentifywhichsectionsof the toolkit
needtobe workedon,andallowmanagerstodecide whichworkpapersare readyto review.
ix. Optional Feature:EditIssue
Description:Usersshouldbe allowedtoeditandupdate issuestokeepthemcurrent.The every
fieldbutissue numbermayhave tobe correctedif a mistake ismade,butsome attributeswill likely
have to be updated,suchas issue description,impact,bestresolvedby,actiontakentodate,owner,
nextsteps,anddue date.
Dependencies:Optionalfeature:Create issues,linkissuestoworkpapersor sections(Project
Team Member)
Rationalization:Asprogressismade,new informationcomestolight,orestimatesare adjusted,
makingitnecessarytoupdate these attributes.
x. Optional Feature:Issue Signoff
Description:Usersshouldbe able tosignoff ona resolvedissue.Eitherfromaview showingthe
issue log(accessedfromthe projectdashboard) orbyselectinganissue fromalistof issuesassociated
witha documentor section(accessedfroman overview of the tool kitsectionsandworkpapers).The
signoff shouldautomaticallyupdatethe date resolvedattributeof the issue withthe currentsystem
date.
Dependencies:Optionalfeature:Create issues,linkissuestoworkpapersor sections(Project
Team Member)
Rationalization:Issue signoffsimproveefficiencybyallowingworkerstoindicate whenanissue
has beenresolved,andallowsmanagerstosee whenandwhosignedoff onanissue.
xi. Optional Feature:Delete Issue
Description:Usersshouldbe able toselectandchoose todelete anissue fromthe issue log
screenor fromthe issuesassociatedwithaspecificworkpaperorsection.
Dependencies:Optionalfeature:Create issues,linkissuestoworkpapersor sections(Project
Team Member).
Rationalization:Sometimes,issueswill be createdbymistake.The creatorof the issue will need
to delete the issue soitdoesnotcrowdthe issuesneededtobe reviewedbythe projectmanager.

41. 41
2. ProjectManager
i. Create an Account
Description:A projectmanagerandaccount administratorshouldbe able tocreate anaccount
for eachteammember.Thisactionwouldhave tobe performedafterthe userloggedintothe web
application.Thenthe userwouldnavigatetoa page to create the account. The projectmanageror
administratorwouldenterthe teammember’semail intoatextbox onthe webform.Whenthey
submit,datavalidationwouldchecktosee if the fieldisnull;inputvalidationwouldensure the emailis
enteredcorrectly.If the email isenteredincorrectly,amessage indicatingthe emailwasnotenteredor
isinvalidwouldappearonthe page andask the user to reenterthe email.If the email iscorrect,itwould
directthe userto a confirmationpage andsendanemail tothe team member.The teammemberwould
followinstructionsonthe email toactivate the account(e.g.copyand paste a registrationkeyorfollow
a link).See registrationforall usersabove forcomplete activationof the account.
Dependencies:Assignteammemberstoprojectmanagementposition(Application
Administrator).
Rationalization:Whenanewmemberjoinsthe team, theywill needanaccountto access the
tool kit.It isnot necessarytocontact an ApplicationAdministrator,since we donotexpectthe Project
Manager to needlesslycreate accounts.Thisprovidesconvenience forthe ProjectManager,whointheir
busyschedule mightneedtointroduce the new membertothe tool kitrightawaywithoutwaiting
aroundfor it to be createdbyan ApplicationAdministrator.
ii. Create a Project
Description:ProjectManagersshouldbe able tocreate projectsonce theyhave loggedintotheir
account fromthe applicationdashboard.Theyshouldbe navigatedtoa page where theywill fill inthe
informationforanewproject.Thisinformationincludesthe Agency,AgencyOrg#, Department,
DepartmentOrg#, TechnologyAgencyProject#,ProjectName,ProjectStartDate,and ProjectDue
Date.The agencyname and numberindicate the primaryCaliforniaState Agencyforthe technology
project.The departmentname andnumberindicate the project’sspecificdepartmentwithinthe
agency.The TechnologyAgencyProjectnumberuniquelyidentifiesthe projectsmanagedbythe
departmentof technology.The applicationshouldcheckthe referential integrityof the Agency Org
NumberandDepartmentOrganizationNumbertomake sure these entitiesalreadyexistinanother
table.Also,these valuesare mandatoryandmustbe filledin.The technologyagencyprojectnumber
mustbe checkedforentityintegrity,ensuringitcanproperlybe usedasprimarykey(mustbe a unique,
nonnull value).Othertypical validationcheckscanbe performedonall fieldsatthispointaswell.If the
validationfails,amessage shouldappearonthe page indicatingthe reasonsitfailed.If the validation
doesnotthrow an error,thena confirmationpage shouldbe displayed.
Dependencies:Assignteammemberstoprojectmanagementposition(Application
Administrator).

42. 42
Rationalization:ProjectManagersshouldhave the informationnecessaryandrequisite trustto
create projectsinthe informationsystem.ByallowingProjectManagerstocreate theirownprojects,
the burdenon ApplicationAdministratorsdecreases.
iii. EditProjectInformation
Description:ProjectManagersshouldbe able toeditprojectinformationonce theyhave logged
intotheiraccount fromthe applicationdashboardand / or the projectdashboard.Theyshouldbe able
to navigate toa page where theycaneditinformationforexistingprojects.The projectinformation
includesthe Agency, AgencyOrg#, Department,DepartmentOrg#, TechnologyAgencyProject#,
ProjectName,ProjectStartDate,and ProjectDue Date.The agencyname and numberindicate the
primaryCaliforniaState Agencyforthe technologyproject.The departmentname andnumberindicate
the project’sspecificdepartmentwithinthe agency.The TechnologyAgencyProjectnumberuniquely
identifiesthe projectsmanagedbythe departmentof technology.The applicationshouldcheckthe
referentialintegrityof the AgencyOrgNumber andDepartmentOrganizationNumbertomake sure
these entitiesalreadyexistinanothertable.Also,these valuesare mandatoryandmustbe filledin.The
technologyagencyprojectnumbermustbe checkedforentityintegrity,ensuringitcanproperlybe used
as primarykey(mustbe a unique,nonnull value).Othertypical validationcheckscanbe performedon
all fieldsatthispointas well.If the validationfails,amessage shouldappearonthe page indicatingthe
reasonsitfailed.If the validationdoesnotthrow anerror, thena confirmationpage shouldbe
displayed.
Dependencies:Assignteammemberstoprojectmanagementposition(Application
Administrator).
Rationalization:ProjectManagersshouldhave the informationnecessaryandrequisite trustto
create projectsinthe informationsystem.ByallowingProjectManagerstocreate theirownprojects,
the burdenon ApplicationAdministratorsdecreasesandthe application’susabilityisimproved.
iv. AssignTeamMembersto Projects
Description:ProjectTeamMemberswillbe grantedinitial access(i.e.,nospecial authorizations)
to a projectviaan invitationfromaProjectManageror ApplicationAdministrator.Thiscouldbe
accomplishedinafewdifferentways.One examplewouldbe toaccessaninvitation page fromthe
project’sdashboardand search forthe user’saccount to grant access.Thiswouldmake the mostsense
since ProjectManagerswill eventuallysetauthorizationsatthe projectlevel.Ingeneral,itmakesmore
sense toadd teammemberstoa projectat the same time,thanto searchfor individual accountsin
differentviewsandaddthe projectsto an account.Afterenteringthe teammembers,the entrieswould
have to be checkedforreferential integrity(i.e.,the userexists,oralternativelythe projectexistsif the
projectisaddedto the userfrom the useraccount view).
Dependencies:Accountregistration(ProjectTeamMember),Create aproject(Project
Manager).

43. 43
Rationalization:ItisimportantthatProjectManagersbe able togrant usersaccess to individual
projects.Theywill make the decisiontoinclude the individual onthe team, sotheyshouldalsobe able
to grant accessin the informationsystem.
v. AssignAuthorizationstothe ProjectTeamMemberUserClassor to Individual Project
Team MembersforIndividual Projects
Description:Accessprojectauthorizationsettingspage foranindividual projectfromthe project
dashboardor fromthe applicationdashboard.Setthe authorizationsettingsforthe ProjectTeam
Memberuserclass or to individual ProjectTeamMember’sassignedtothe projecttoeitherview oredit
and submitthe page.
Dependencies:Create aproject(ProjectManager),Assignteammemberstoprojects(Project
Manager).
Rationalization:Assigningauthorizationstoanentire projectwill be more convenientthan
settingauthorizationsforindividualworkpapers.Thiswillallow the projectmanagertoselectproject
teammemberswhowill editinformationinthe tool kit,andstill allow otherstoview the tool kitevenif
theyshouldnotbe editingit.
vi. AssignAuthorizationstothe ProjectTeamMemberUserClassand to Individual Project
Team MembersforIndividual WorkPapers
Description:Accessthe workpaper’sauthorizationsettingspage foranindividual workpaper
fromthe projectdashboard.Setthe authorizationsettingsforthe ProjectTeamMemberuserclassor to
individualProjectTeamMember’sassignedtothe projecttoeitherview oreditandsubmitthe page.
Work paperauthorizations shouldoverrideprojectwideauthorizationsforthe individual workpaper.
Dependencies:Create aproject(ProjectManager),Assignteammemberstoprojects(Project
Manager).
Rationalization:Assigningauthorizationstoaworkpaper will providemore precise
authorizationsthanprojectwide authorizations.Forthisreason,we canassume thatthe authorizations
for an individual workpapershouldoverrideprojectauthorizationsforthe useror userclass.
vii. Optional feature:ReviewSignoff
Description:A workpapersignoff shouldindicate that awork paperor sectionisreadyto
review.The workpaperorsectionmaybe preparedandreviewedbythe projectmanager.Once the
projectmanagerissatisfiedthatthe workpaperiscompletedorupdatedcorrectly,theyshouldperform
a reviewsignoff. Forexample,we mightmake itsothe projectmanagercan signoff on the work paper
or sectionfromthe workpaper summaryonthe projectdashboard.
Dependencies:Optionalfeature:Workpaperandsectionsignoff (ProjectTeamMember).

44. 44
Rationalization:Implementingareview procedure helpsmanagerstokeeptrackof the work
theyhave actuallychecked,whichshouldimprove the qualityof the workperformedonthe CA-PMM.
3. Application Administrator
i. Delete andEditAccountInformationforAll Users
Description:AnApplicationAdministratorshouldbe able toaccessand editthe account
informationforall users.Theyshouldbe able todothisusingsome identifyinginformationtofindthe
account,and usingsome formof authenticationtoverifyitisthe correct userif the userrequeststhe
account be changed.
Dependencies:Accountregistrationforthe ProjectTeamMemberandApplication
Administrator(ProjectTeamMember).
Rationalization:The ApplicationAdministratorneedstofix issuesif the usercannotaccessand
fix issueswiththeiraccountinformationontheirown.
ii. Delete andEditProjectsCreatedbyOtherUsers
Description:AnApplicationAdministratorshouldbe able toaccessand editthe projectsforall
users.
Dependencies:Accountregistrationfor the ProjectTeamMemberandApplication
Administrator(ProjectTeamMember).
Rationalization:The ApplicationAdministratorneedstoaccessandeditthe projectif the Project
Manager isnot available.Thisisespeciallytrue if the ProjectManagerhasleftpermanentlyandanew
ProjectManager needstobe assigned.
iii. AssignTeamMembersto ProjectManagementPosition
Description:The ApplicationAdministratorwill be responsibleforgrantingProjectManager
statusto certainaccounts. There are differentwaysthiscanbe achieved.Forexample,the Application
Administratorcouldaccessapage where theywouldsearchforthe ProjectTeamMember’saccount and
grant access,or we could make itso the ApplicationAdministratoraccessesasummaryof the user’s
account and choosestogrant access fromthat page.Eitherway,the ApplicationAdministratorshould
have be requiredtoretrieve theirpasswordtoauthenticate themselvestodecrease the riskthat
someone else couldgrantProjectManagerstatuswithoutlegitimateauthorization.
Dependencies:Accountregistration(ProjectTeamMember).

45. 45
Rationalization:GrantingProjectManagerstatusisan importantfunctionforthe application.
Theywill be primarilyresponsibleforthe completionof the toolkit,andneedto have special
authorizationstocomplete theirwork.
Note:Fromthe documentationwe have analyzed,we see noreasontorequire thata project
managerbe assignedtoa specificprojectbefore havingprojectmanagerstatus.Forthisreason,we
decidedtonotinclude asa prerequisiteforthisfunctionalitythataprojectmanagerbe assignedtoa
project.Thisalsoallowsprojectmanagerstocreate projects,since theydonothave to be part of the
projectbefore havingprojectmanagerstatus.Thisappearscounterintuitive,since projectmanagers
mustmanage projects.However,consideringthatprojectmanagersare responsible forinitiating
projects,itmakessense toorganize the informationsysteminthiswaysothata projectmanagercan
create the project.
C. UsabilityRequirements
1. UsabilitySuccessFactors
i. Consistency
Consistencywill be veryimportantforthisapplication.Thisapplicationwill be referredtooften
throughoutthe life of the project,andthe amountof contentin thisapplicationisrelativelylarge.If the
formatof eachpage,methodsof navigatingthe applicationortitlesandterminologyare inconsistent,
the applicationwill be virtuallyunusable.The usercouldnotpossiblyrememberhow touse everysingle
part of the application,orrefertoa manual everytime somethinghastobe done.We have to make
sure to followasetof rulesthatthe user can learnto helpthemfigure outwhatissupposedtobe done
indifferentareasof the application.
In addition,consistentresponse timewill be important.Performance requirementswill be
discussedlater,butrightnowitis importanttomentionthatuserswill be confusedif sometimesthe
response time isshort,whilethe responsetime atothertimesitislong.Forexample,itmightbreak
theirworkflowif the response time goesfromunderasecondtofive secondsatothertimes.
ii. EfficiencyandEase
Decreasingthe costand time to implementinformationsystemprojectsisakeybusiness
objective forourapplication.Forthisreason,improving efficiencyandease will be instrumental in
improvingthe informationsystem.Fortunately,the formsforthe informationsystemalreadyexistand
are clearlydocumented.These formsneedlittle tonoimprovementsince the informationisgrouped
and orderedappropriately(formattingisadifferentissue,see below).One thingthatcouldbe improved
on the formsis makingsure thatrelevantoutputsfromotherforms(orotherplaceson the active form)
are available,orevenautomaticallygeneratedif possible.The existingsystemaccomplishesthisinsome
cases,but notalways(whichalsoraisesanissue withconsistency).Ialsosee potential toincrease the
ease of navigatingthe system.Currently,youcansort of stepintothe systemone hierarchical layer ata

46. 46
time.Somethingthatwouldallowyoutosee everysectionandworkpapersimultaneously,and
potentiallythe date completedif ouroptional workpapersignoff feature isincluded,wouldgreatly
increase the efficiencyandease of navigatingthe system.
iii. Format
In thissection,Iwill reemphasize the importanceof consistencyforusability.Userscannot
memorize howanentire systemworks,buttheycanmemorize rulesthatwill helpthemfigure outhow
to navigate anduse the system.Consistencyinformattingisessentialtohelpusersidentifytypesof
featuresineachviewof the informationsystem.Also,itshouldgenerallyenhance the user’sabilityto
viewandinterpretthe databy makingsure importantdataisnot “buried”inthe interface.Ithink the
CA-PMMhas plentyof roomforimprovementwhenitcomestothe format of each workpaper.It will
be importantto be able to quicklychange andview the changedformatof certainelementsonall of the
pages(e.g.,usingaCascadingStyle Sheet).This way,elementswill be presenteduniformlyandcanbe
changedquicklyonall pagesif desired.
iv. Flexibility
Flexibilitywill notbe amajor concernforthe applicationsince mostof the requirementsforthe
CA-PMMtool kitare clearlydefined.However,the toolkitdoesallow managerstomake changesif
needed,whichwouldbe alossof functionalityatthispoint.If we determine thatthisfeature isneeded
at a laterpoint,we couldpotentiallyincludesome featuresthatwouldimproveflexibility.Forexample,
perhapsbuildingworkpaperswithfieldtitles.Thiswouldalsoprovide structure forthe processof
editingaform.Or perhapsallowinguserstomove fieldswithinaformandadd typesof fields.If these
featuresare required,we wouldhave toreturn to the feasibilitystudyreporttoanalyze whetheritis
possible forourteamto add these features.
2. UsabilityCharacteristics
i. User
Users shouldbe familiarwiththe conceptsinthistool kit.Althoughwe shouldmake aneffortto
simplifyusingthe toolkit,we shouldalsomake sure toinclude the featuresandflexibilitythatan
educateduserwouldneedtobe effective inpreparingthe tool kit.Documentationandusertrainingfor
the existingsystemadequatelyinformsthe type of people whowill be usingthissystemaboutthe
businessandprojectmanagementconceptsinthissystem.We shouldmake sure toinclude these
conceptsinour trainingto make sure usersare prepared.
ii. Task
Task demandssuchas time pressure,costof errors,and workduration(fatigue)decrease
usability.Unfortunately,complyingwiththe CA-PMMincreasesthese taskdemands.Forthisreason,we
feel like we couldhave astrongimpactby decreasingthe stressassociatedwiththese taskdemands.For
example,we canhelpuserstodecrease theirtime pressure byidentifyingif andwhenportionsof the

47. 47
tool kithave beencompleted.Thiswaytheywillknow thatthe workpapersdonot have to be
completedagain.The costof errors inthe systemwill still be there,butwe canminimize errorsby
centrallystoringandupdatingthe system.Workdurationcanbe decreasedbyautomaticallypopulating
and calculatingthe valuesforotherfields.
iii. System
The informationsystemwill be made available viathe usersownhardware viatheirweb
browser.The usershouldbe familiarwithusingtheirownmouse,keyboard,operatingsystem, and
browser,whichwill increase usability.The functionalityof webapplicationsoverabrowserisgenerally
lowerthanthat of a desktop,whichmaydecrease usability insome ways.Thisisespeciallytrue whenit
comesto flexibility.However,asdiscussedbefore,there isnotusuallyaneedforflexibilitywiththe CA-
PMM toolkit,andthe needtocentrallystore andupdate the toolkitshouldhave agreaternetincrease
on the environment.Also,there will be increasedflexibilitywhenitcomestowhichsystemthe userwill
be able to workon. The usercould potentiallyswitchtoa differentdeviceif the one theyare usinghas
issueswithouttransferringthe file.
iv. Environment
One veryimportantenvironmental factoristhatthe userswill oftenbe atclientlocations.Ata
clientlocation,itisoftenimportanttohave quickaccessto informationinthe tool kitjustincase the
clienthasa question,soitisimportantthat the projectteammemberbe able toaccess the application
and locate the relevantinformationquickly.The factthat thisisa webapplicationimpliesthatthe user
will be able toaccessthe webapplication.If the internetconnectionisslow,thenunfortunatelythere is
nothingwe can control to decrease the time takentoaccessthe application.The application’sGUI
navigationalsoneedstobe clearandconcise to helpthe userlocate relevantinformationquicklyand
easily.
D. Performance Requirements
The requirementsinthissectionprovideadetailedspecificationof the userinteractionwiththe
software andmeasurementsplacedonthe systemperformance.
1. Accessand SaveFiles
Title:Accessandsave informationto/fromthe server.
Description:Accessingandstoringinformationfromthe servershouldbe fast,userfriendly,and
easyto understand.
Performance:95%of data retrieval andstorage shall take 5 secondsorless.

48. 48
2. Links Between Views
Title:Linksbetweenprojectviews.
Description:Linksbetweenformsof projectshouldbe immediateandseamless.
Performance:100% of all linksinwebapplicationshall be seamlessandrequire noextratime for
loading.
3. Collaboration ResponseTime
Title:Collaborationbetweenusers.
Description:Updatestoretrievedprojectfilesshouldsave tothe database uponclickof the save
feature andshouldbe available immediatelytootherusersaccessingthe project.
Performance:100% of all savedmaterial shouldbe available immediatelyuponsavinginunder5
secondstospecifieduserscollaboratingonthe project.
4. UpdateLog
Title:Each save promptsnewupdate logentry.
Description:Everysave andchange to the currentdocumentshall provide anew time/date
stampto the update logalongwitha shortdescriptionof changesmade,andbywhom.
Performance:100% of all savesautomaticallylognew entrytothe updateslogavailable for
usersto see uponupdating.
5. SystemDependability
Title:Systemdependabilityrequirement.
Description:The systemshouldbe accessibleany time.If the systemlosesconnectiontothe
Internetordatabase,the usershouldbe informed.
Performance:100% of the time the usershouldbe informedof systemconnectionslost.
E. Logical Database Requirements
The logical database requirementsforthe CA-PMMwebapplicationare fairlysimpleandare
designedthatwaytoensure higherreliabilityandfewerproblems.There are generally500projectsa
year,so allowingfrom2000-2500 accountscoversthe minimumaccesses neededandallowsroomfor
growth. For authorizationandpermissions,we plantouse three differentuserauthenticationlevels.
The team memberlevelof userauthenticationisthe mostbasicof accesspermissions.Theyhave

49. 49
permissiontoreadandeditonlythe documentsthatthe projectmanagergrantedthemaccessto. The
seconduserauthenticationlevel wouldbe the Projectmanagerpermissionlevel.Thislevelhasthe rights
to create a newproject,grantteammemberpermissions,aswell asall permissionsthatcome withthe
teammemberlevel. The administratorlevelpermissionsinclude all of the permissionsfromthe Project
managerlevel aswell asthe abilitytoaccessall projects,andaccount informationforadministrative
purposes.
F. DesignConstraints
The primarydesignconstraintswith the CA-PMMwebapplicationare makingthe appmore
efficientandmore userfriendlyforinformationsharingandease of collaboration.Since the currentCA-
PMM isrelativelysimpleandeasytouse,we wantto emulate the same designtomake iteasierfor
currentusersof the software tobe comfortable withthe new software.Creatingauserinterface which
isboth effective andeasilynavigable will pose adifficultchallenge.Duringthe process,if we decide the
currentsoftware couldbe improvedbydesign,we will change ourdesigntobetterfitthe userneed.
Otherconstraintssuchas limitedmemoryandprocessingpowerof mobiledevicesandbrowser
compatibilityare alsoworthconsidering.The new CA-PMMismeantto be quickand responsive while
alsoeasilysharable forcollaboration,eachfeature mustbe designedandimplementedwithefficiencyin
mind.
G. Software SystemAttributes
The graphical userinterface of the CA-PMMwebapplicationistobe designedwithusabilityas
the firstpriority.The appwill be presentedandorganizedinmannerthatisboth visuallyappealingand
easyfor the userto navigate.
To ensure reliabilityandcorrectness,there will be zerotolerance forerrorsinthe algorithmthat
allowsconnectivitywiththe webserverforease of collaborationandsharingbetweendevices.To
maintainflexibilityandadaptability,the appwill take intoaccountsituationsinwhichauserloses
internetconnectionorforwhateverreasoncannotestablishaconnectionwiththe server.These users
will still be able touse the application,butanychangesmade inthe documentwhile disconnectedwill
be cached until the connectionisrestored.The userswill needtobe vigilantinsavingtheirworkto
ensure the documentgetsupdatedtothe servershouldanoutage occur.
The software will feature useraccountsforauthenticationwhenworkingonprojectsand
collaboratingwithakeyfeature forthe ProjectManagerto alsobe an administratorof the document
whocan assignprivilegesforusersina workgroup ona project.Thisfeature will enhance securityof
documentsforunauthorizedusersandpreventmaliciousaccesswhileensuringdataprivacy.
Portabilityof the webapplicationismeanttobe a highpriorityas thisisthe largestadvantage
overthe current implementationof the CA-PMM.The webapplicationwill be host-dependentonthe
serveranduptime of the serverisa highpriorityto ensure reliabilitytoaccessof information.

50. 50
Part III: Infrastructure Analysis
A. Hardware
The CaliforniaProjectManagementMethodologyiscurrentlyrunningonMicrosoftExcel
application,soitonlyrequiresacomputerwithMicrosoftExcel installed.
The newproposal systemiswebapplicationthatrequiresaWebserveranda database server.
All of these serverswill be virtualizedusingMicrosoftWindowsServerlocatedinDr.Spiros’officeat
SacramentoState University.Italsorequiresadomainname,internetconnectionandacomputerto
interactwiththe system.
B. Software
In thiscase,we will be usingIISWebserver.IISis MicrosoftWeb serverrole thatisincludedwith
all versionsof Windowsoperatingsystem.The WebserverwasredesignedinIIStoenable youto
customize aserverbyaddingor removingmodulestomeetyourspecificneeds.Modulesare individual
featuresthatthe serverusestoprocessrequests.
Additional toIISWebserver,we will be usingMicrosoftSQLserver2008. It is a relational
database managementsystemwhose primaryfunctionistostore and retrieve dataasrequestedbythe
webapplication.Foreachuser,all informationof eachprojectrelatedtothatuserwill be storedina
relational database.Everytime auseraddor change any detail of his/herproject,itwillbe updatedto
the database.Inthisway, the systemensuresconcurrencyof data andimprovessynchronizationif two
or more people are workingonthe same project.
C. Networking
Firstof all,bothuserside andserverside needconnectiontothe Internet.
In orderto access intothe webapplicationandthe database,userswillneedtoconnecttothe
networkof SacramentoState UniversityusingVirtualPrivate Network(VPN).
VPN enablesacomputerora device thatisnot inSacramentoState Universitynetworkto
securelysend,retrievedata,andinteractwithWindowsserverlocatedoncampus.
D. Standards
The standard forthe proposal systeminfrastructure isbasedonthe 3-tierarchitecture.
The top most level of the systemisapplication/presentationlayer.Inthiscase,the webbrowser
such as InternetExplorer,Firefox,Safari andChrome are the mainapplicationsusedinthe system.This
layerallowsuserstouse the CA-PMMwebapplicationtomanage theirwork.Itwill be interactwiththe
middle layer/businesslayer,whichdefinesall the control accessandbusinessrules.Thislayer

51. 51
coordinatesthe application,processescommands,makeslogical decisionsandevaluations,andperform
calculation.The lastlayerisdata layerwhichcontainsthe dataaccess methodsanddatabase.
Informationisstoredandretrievedfromthe database orfile systems.The informationisthenpassed
back to the middle layerforprocessing,theneventuallybacktothe users.Forexample,whenaproject
managerusestheiraccountto log intothe system, the control accesslayertakesthe informationto
verifiesthe authenticationandauthorizationof thisuserbyaccessingtothe data access layerand
compare if the informationismatched,thenitwillbe processedinthe middle layerandpassthe result
back to the user.
Please see figure2for a graphical representationof the differencesbetweenthe three layers.

52. 52
Figures
Figure 1. CA-PMMSummary

53. 53
Figure 2. Three Tier Architecture