FeasibilityEvidenceDescription(FED)
Frenzy
TeamNo-01
ArpanBadeka-Prototyper,UMLModelerAnkurPalav-SoftwareArchitect,PrototyperAshwin Hariharan-SoftwareArchitect,PrototyperJheel Somaiya-ProjectManager,LifecyclePlanner
SaileeRane-RequirementsEngineer,FeasibilityAnalystRishabhSharma-SoftwareArchitect,OperationalConceptEngineerAlanKwan-QualityFocalPoint
12/5/2016
FED_TRR_F16a_T01_V1.2.doc i VersionDate:12/5/16
Date / Author / Version / Changes made / Rationale10/10/16 / SR / 1.0 /
- Original template for use with Frenzy v1.0
- Initial draft for use with Frenzy v1.0.
10/17/16 / SR / 1.1 /
- Updated Cost Drivers
- Added top Risk
- Updated Business Case Analysis
- Completed after feedback from FCR ARB presentation on 10/10/16
12/5/16 / SR / 1.2 /
- Improved consistency in usage of terms in the document
- Added ROI Analysis
- Made corrections to the program Model
- Changed rankings in selecting rationales for architected agile models
- Changed Risk Assessment table to reflect latest risks
- Completed after feedback from FCP on 12/5/16
TableofContents
FeasibilityEvidenceDescription(FED)...... i VersionHistory...... ii TableofContents...... ii
TableofTables...... 1
1.Introduction...... 1
1.1 PurposeoftheFEDDocument...... 2
1.2 StatusoftheFEDDocument...... 2
2.BusinessCaseAnalysis...... 3
2.1 CostAnalysis...... 4
2.2 BenefitAnalysis...... 5
2.3 ROIAnalysis...... 6
3.ArchitectureFeasibility...... 7
3.1 LevelofServiceFeasibility...... ……………………………..7
3.2 CapabilityFeasibility...... 7
4.ProcessFeasibility...... 8
5.RiskAssessment...... 10
6.NDI/NCSInteroperabilityAnalysis...... 11
6.1 Introduction...... 11
6.2 EvaluationSummary...... 11
TableofTables
Table1:PersonnelCosts...... 4
Table2:HardwareandSoftwareCosts...... 5
Table3:BenefitsofFrenzySystem...... 6
Table4: CapabilityRequirementsandTheirFeasibilityEvidence...... 7
Table5:RationalesforSelectingArchitectedAgileModel...... 8
Table6:RiskAssessment...... 10
Table7: NDIProductsListing...... 11
1.Introduction
1.1 PurposeoftheFEDDocument
TheFeasibilityEvidenceDocumentprovidesanoverviewonthe Businesscases,architecture feasibility,processfeasibility,risk assessmentand NDI/NCSInteroperabilityanalysis. It providesdetailsonthefeasibilityoftheprojectandensuresthatitcanbecompletedwithinthe stipulatedtimeperiodandbudget.
1.2 StatusoftheFEDDocument
Thedocumentisthefirst draftfortheFeasibilityevidencecreatedforthe Frenzywebsite.
2.Business Case Analysis
Assumptions(Under what Businessassumptions will this ‘model’ be true)- People are willing to buy the items posted on fashion blogging site.
- People like to buy the clothes that celebs wear.
Stakeholders
(Who is accountable for the initiatives) / Initiatives
(What to do to realize benefits) / Value Propositions
(Benefits i.e Why) / Beneficiaries
(Who derives value)
- Publisher
- Retailer
- Customer
- Maintainer
- Developer
- Client
- Post articles on their blogs
- Access to API’s, database, payment system
- Exposure to latest trends and buying the available items
- Maintains existing and new system functionality
- Developing the front end and adding functionality
- Outreach bloggers and retailers
- Easy access to Fashion blogging website
- Benefit to users from increased efficiency of purchase
- Automated content monetization
- Increased market channel for retailers
- Customer
- Client
- Retailer
- Publisher
Cost / Benefits
- Development Cost
- Maintenance Cost
- COTS
- Advertising
- Affiliate Cost
- Increased number of users on the website
- Ease of shopping Digital media
- Reduced complexity of code and improved documentation for the maintainers
- Improved user experience and functionalities as a result of adding new features
- Good exposure to front end and back end web technologies for developers
Fig.1-BusinessCase
Cost:
CostDriver
-DevelopmentCost:
$19.85/monthforProxyService
$100/monthAWSstagingserver
-MaintenanceCost:
$19.85/monthforProxyService
$100/monthAWSstagingserver
-COTS-
IBMWatson$10/month
GoogleCloudvision$12/month
$0forMySQL,GitLabprivateaccount
-AdvertisingCost:
GoogleAdWordsCampaign$20/month
-AffiliateCost:
2-20%ofAffiliateClothingSaleCommissionspaidtoSitePartner
80%-98%ClothingSaleRevenuepaidto Retailer
2.1 CostAnalysis
Thecostanalysisincludesthetimespentbytheclientinconducting meetingswiththeteam memberstogetusfamiliarizedwiththeexistingcodebase,settingupthesystemenvironment andfinalizingthesprintsonscrumboard.
2.1.1 PersonnelCosts
Table1:PersonnelCosts
Activities / TimeSpent(Hours)ValuationandFoundationPhase(7weeks)
Client:WinWinSession1 / 1
Client:WinWinSession2 / 1.5
Client:Meetingsheldforcodebasereviewandtosetupthe
systemenvironment / 16
DevelopmentandOperationPhase(8weeks)
Owner:Meetingvia email,phonecalls,andothermeans / 16
ArchitectureReviewBoardsandCoreCapabilityDrive-through
session / 4
Deploymentofsysteminoperationphaseandtraining
- Installationanddeployment
- Trainingandsupport / 12
Total / 49.5
2.1.2 HardwareandSoftwareCosts
Table2:Hardwareand SoftwareCosts
Type / Cost / RationaleAWSStagingserver / $100/month / Testing/Dev
ProxyService / $19.85/month / NetworkService
IBMWatson / $10/month / NLP
GoogleCloudVision / $12/month / MediaClassification
GoogleAdWords / $20/month / Advertisement
2.2 BenefitAnalysis
Benefits:
-Increasednumberofuserson the website
-Improved searchresults:
Theresultsreturned byshop similarwillprovidethe userwithrelevantdata.Thedata issortedon the basisofcolor,category, brand andlowprice.
Easyaccessto fashion bloggingwebsite-Buyer
TheBuyercanaccessthe contentof fashion blogging website undertheFrenzyapplication.The buyeris exposed to morethan1000articleswhichsavesaconsiderableamountoftime.
Content Monetization-Publisher
Thepublisherdoesnothavetospend hoursto manuallytagthemediawith theircorresponding URL’s. Byusing theFrenzywebsiteclothing tags,theyareautomaticallytagged fortheuser.
Table3:BenefitsofFrenzySystem
Currentactivitiesresourcesused / %Reduce / TimeSaved(Hours/Year)Browsing
Customer(1article*60 minutes*52
weeks) / 50% / 26
UploadArticles
Publisher(1article*0.1minutes*52
weeks) / 90% / 1400
Total / 1426
2.3 ROIAnalysis
This graph shows the estimate of number of site partners per year, who have agreed to install the Frenzy plugin on their website and use the application
Fig 2 – ROI Analysis
3.ArchitectureFeasibility
3.1 LevelofServiceFeasibility
LevelofServicefeasibilityundecided
3.2 CapabilityFeasibility
Table4:CapabilityRequirementsandTheirFeasibilityEvidence
CapabilityRequirement / ProductSatisfactionCR-1:BrowseArticles / Software/Technologyused:MySQL,PHPcodeigniterframework,
AngularJSLibraries
FeasibilityEvidence:Developedaprototypetodisplaythe articles
browsedbytheuseralongwithadetailedinformationoftheproduct displayedonthe currentpageofthewebsite.
Referredusecasediagram:UC-4
CR-2:ClothingTag / Software/Technologyused:MySQL,PHPcodeigniterframework,
AngularJSLibraries
FeasibilityEvidence:Developedaprototypetodisplaythe clothing
tagspresentontheimagedisplayedonthe website.
Referredusecasediagram:UC-10
CR-3:Shopwidget / Software/Technologyused:MySQL,PHPcodeigniterframework,
AngularJSLibraries
FeasibilityEvidence:AprototypewasdevelopedusingmockNinja
whichshowedtheflowofthefunctionality.
Referredusecasediagram:UC-8
CR-4:SelectItem / Software/Technologyused:MySQL,PHPcodeigniterframework,
AngularJSLibraries
FeasibilityEvidence:Developedaprototypetoselecttheitemto
displaythedetailsintheshopwidget.
Referredusecasediagram:UC-2
CR-5:BuyItemButton / Software/Technologyused:MySQL,PHPcodeigniterframework,
AngularJSLibraries
FeasibilityEvidence:Createdaprototypetorepresentthebuy
functionality
Referredusecasediagram:UC-5
CR-6:ShopSimilar / Software/Technologyused:MySQL,PHPcodeigniterframework,
AngularJSLibraries
FeasibilityEvidence:Developedaprototypetoimplementshop
similarfunctionality
Referredusecasediagram:UC-3
CR-7:ShareItem / Software/Technologyused:MySQL,PHPcodeigniterframework,
AngularJSLibraries
FeasibilityEvidence:Developedaprototypetoimplementshare
functionality
Referredusecasediagram:UC-6
CR-8:Sort Item / Software/Technologyused:MySQL,PHPcodeigniterframework,
AngularJSLibraries
FeasibilityEvidence:Developedaprototypetoimplementsort
functionality
Referredusecasediagram:UC-8
CR-9:ClipItem / Software/Technologyused:MySQL,PHPcodeigniterframework,
AngularJSLibraries
FeasibilityEvidence:Developedaprototypetoimplementclip
functionality
Referredusecasediagram:UC-7
FED_TRR_F16a_T01_V1.2.doc 7 VersionDate:12/5/16
4.Process Feasibility
Table5:RationalesforSelecting ArchitectedAgileModel
Criteria / Importance / ProjectStatus / Rationales30%ofNDI/NCSfeatures / 3 / 3 / Frenzywebsitecurrentlyuses theAngularJSlibrariesand Code IgniterFramework
SingleNDI/NCS / 1 / 3 / Thewebsiteusesmorethan
oneAPI
Unique/inflexiblebusiness
process / 3 / 2 / Theclienthasaclearvisionof
thebusinessprocess.
Needcontroloverupgrade
/ maintenance / 3 / 3 / Theprojectneedstobe
upgradedtoincludenew functionality
Rapiddeployment / 3 / 2 / Thedeploymentisscheduled
thissemester
Criticaloncompatibility / 2 / 1 / Theapplicationmustbe
compatiblewithmultiple phonesandbrowsers.
Internetconnection
independence / 3 / 1 / Thewebsiterequiresinternet
connection
Needhighlevelofservices
/ performance / 3 / 1 / Multipleuserswillbeusingthe
applicationat agiventime.
Needhighsecurity / 2 / 2 / Thetransactioninformationof
theuserduringthecheckout needstobesecured.
Asynchronous
communication / 2 / Thearticlesanddigitalmedia
postedonthesiteneedtobe viewedasynchronously.
Beaccessedfrom
anywhere / 3 / 3 / Thesiterequirestobeamobile
responsivesothatauser can accesstheaccountfrom anywhere
Criticalonmassschedule
constraints / 3 / 1 / Thereareconstraintspresent
fordevelopmentdueto conflictingschedulesofteam members
Lackofpersonnel
capability / 2 / 2 / Onlyfewteammembershave
extensiveknowledgeinthe developmentoffrontend.
Requirelittleupfrontcosts / 3 / 2 / The overall project uses COTS but the team worked with free software for their part in project
FED_TRR_F16a_T01_V1.2.doc 8 VersionDate:12/5/16
Requirelowtotalcostofownership / 2 / 3 / Theservicesusedbythe
websitehaveincurredan overallminimumcostforthe setup
Not-so-powerfullocal
machines / 1 / 1 / Thewebsitedoesnotrequire
powerfullocalmachines
FED_TRR_F16a_T01_V1.2.doc 9 VersionDate:12/5/16
5.Risk Assessment
Table6:Risk Assessment
Risks / RiskExposure / RiskMitigationsPotential
Magnitude / Probability
Loss / Risk
Exposure
CodeIntegrationofsimilaritem queries withexistingcodebase / 4 / 3 / 12 / Substantial changes made in the referenced controllers to reduce redundancy and complexity of the code base
PersonnelShortfalls / 3 / 2 / 6 / Better understanding of the code base after implementing new functionalities
Systemnotfunctioningaccording to userneed / 4 / 2 / 8 / Improved the user interface after conducting meetings with the client and analysing the feedback received
Integration issue of the sort drop down menu in the shop popup widget / 4 / 3 / 12 / N/A
Integration issues of shop similar and shop widget / 3 / 3 / 9 / Item Detail controller was used to reference the same functionality.
6.NDI/NCS InteroperabilityAnalysis
6.1 Introduction
TheNDIusedinthedevelopment ofthewebsitearesuggestedbytheclienttoredesignthe existingsystemwithouthavinganyinteroperabilityissue.
WeareusingtheCodeIgniterPHPFramework toimplementtheshopwidget,shopsimilarand clothingtagfunctionality.AngularJSlibraryisusedtoincorporateMVCarchitecture.Thecode repositoryispresenton GitLabtoprovideeasyaccessand commitchangestothecodebase.
6.1.1 COTS/GOTS/ROTS/OpenSource/NCS
Table7:NDIProductsListing
NDI/NCSProducts / PurposesGitLab / Repository
MySQL / DBMS
AWS / CloudServices
GoogleAPI / UserLogindetails
AngularJSlibraries / MVCarchitecture
6.1.2 Connectors
In thisproject,weusePHP/MySQLConnectorto enablethePHPwebapplicationtoretrieveand querydata fromthedatabase.
6.1.3 LegacySystem
TheCodeIgniterPHPFrameworkisusedtopassthedatabetweenthefrontendandthe database.Theentire Frenzywebsiteisbuiltusingthisframeworkbytheclient.
6.2 EvaluationSummary
AlltheNDI’smentionedaboveareapartofthesystembeingdevelopedsincetheclienthas alreadyimplementedthewebapplication.Theredesigningofthe websitewillrequiretheuseof theexistingtoolsto avoidinteroperabilityissues.