Report Sample

TABLE I OF I CONTENTS
INTRODUCTION ....................................................................................................................................
4
LITERATURE iREVIEW ...........................................................................................................................
6
1) An iEmpirical iStudy ion iuse iof iSocial iNetworking iSites: ................................................................
6
2) Social iNetwork iConnects iServices ...............................................................................................
7
3) Making ia iSense iof iCommunity: iExperience ifrom iWeb-chat ........................................................ 8
4) Communication iGoes iBeyond iWords: iFuture iwith iChat-Bot ....................................................... 9
TECHNOLOGY iREVIEW ......................................................................................................................
10
1) PHP iMyAdmin .......................................................................................................................
10
2) Bootstrap...............................................................................................................................
11
3) QSEE iSuperlite ......................................................................................................................
11
4) Sublime iText i3 .......................................................................................................................
12
5) Microsoft iProject ...................................................................................................................
12
6) Xampp ...................................................................................................................................
13
7) Google iDrive ..........................................................................................................................
13
8) Trello .....................................................................................................................................
13
METHODOLOGY .................................................................................................................................
14
1) Feasibility iStudy ....................................................................................................................
15
AAYUSH IRAJ IPOKHREL 1

2) Technical iFeasibility ..............................................................................................................
16
3) Economic iFeasibility ..............................................................................................................
16
4) Operation i Feasibility
..............................................................................................................17
5) Social i Feasibility
.....................................................................................................................17
REQUIREMENT iANALYSIS
..................................................................................................................17
1) Functional i Requiremtents
..........................................................................................................17
2) Non-Functional iRequirements ...................................................................................................
18
PRODUCT iDESIGN ..............................................................................................................................
19
A) System iDesign i(DIAGRAM) .......................................................................................................
20
B) Entity iRelationship iDiagram i(erd iDIAGRAM) ............................................................................ 21
C) USE iCASE iDIAGRAM .................................................................................................................
22
ADMIN iUSECASE ..........................................................................................................................
22
USER iUSECASE ............................................................................................................................
23 PRODUCT iIMPLEMENTATION
........................................................................................................... 24
PRODUCT iTESTING ............................................................................................................................
25
A) Gossip: iSocial iNetworking iSIte i(Implementation iTesting) ......................................................... 25
1) Registration i& ilogin ...............................................................................................................
26
2) Registration iSteps .................................................................................................................
27
3) Login iPage .............................................................................................................................
28

4) Admin iDashboard ..................................................................................................................
29
SYSTEM iTESTING ...............................................................................................................................
31
1) Unit iTesting ...............................................................................................................................
32
2) Integration iTesting ....................................................................................................................
35
A) Successful iRegistration iand iSteps ......................................................................................... 35
B) User iPost iand iComment ........................................................................................................
37
C) Add iFriends iand iRequest .......................................................................................................
39
D) Use iGossip iHelpline i(Chat iBot) ..............................................................................................
40
E) User iPrivate iChat ...................................................................................................................
41
F) Admin iDashboard iDetails ......................................................................................................
42
3) Stress iTesting ............................................................................................................................
42
A) Create iNew iAdmin ................................................................................................................
44
B) Upload iInvalid iImage iFor iPost ...............................................................................................
45
C) EDIT iPICTURES .....................................................................................................................
46
D) SEARCH iUSERS .....................................................................................................................
50
E) VIEW iFRIEND’S iPROFILE ...................................................................................................... 51
F) UPDATE iUSER iINFORMATION .............................................................................................
52
4) Compatibility iTesting ................................................................................................................
53

PRODUCT iEVALUATION ....................................................................................................................
55
PROJECT iEVALUATION ......................................................................................................................
57
CONCLUSION ......................................................................................................................................
58
BIBLIOGRAPHY ...................................................................................................................................
59
INTRODUCTION
Social iNetworking isites ican ibe ibroadly icharacterized ias iany iother isites ifor ionline icommunication ithat
ipermits iindividuals ito iinteract iwith ieach iother. iweb ijournal, iBlogging iand iwriting i ito ibegin iwith
iinvented iout iin ithe ilate i1990’s. iAs iwith iincrease iin iusers iit igot imore ipopular, ia ipure isocial iorganizing isite
iemerged iknown ito ibe ias iSixDegrees.com i(1997-2001), ibasically ipermitting ithe iusers ito imake ipersonal i
iprofiles iand iinteraction iwith iothers. iThis itrend iwas ipursued iby iFriendster iand isometimes irecently iby
iFacebook, iTwitter iand iMyspace. i(123helpme.com, i2018)
iIn igeneral, ia isocial inetworking, iform ia igrouping iof ionline iusers iinto imore iformalized icommunity. iThe
iforemost icommon iapproach ifor ia isocial inetwork isite iis ithrough iwebsite iand ieach isocial iorganization
itends ito ifollow ithe icommon itheme iassociated iwith iwebsite. iFollowing ion ia iprinciple iof icreating ia isocial
ihub, iand iinspired iby itrending isocial isites ilike iFacebook, iTwitter iand iViber, ithis iproject iis iabout ia inewly
icreated isocial inetworking isite
“Gossip: iA iSocial iNetworking iSite” iis ia iweb iapplication idesigned iand icreated ito iserve ias ia isocial ihub ifor
idiverse iindividuals. iThe iwebsite ifacilitates ithe iusers ifor iinteraction iwith ipeople ithrough itimeline iposts
iand icomments, ia ichat ibased isystem, ipublic ichat isystem iand ia ichat ibot ihelpline ialong iwith icrud
ifunctionality ifor iprofiles. iThe iaim iof ithis iweb iapplication iis ito iprovide iinteractive iplatform ifor ipeople ito
icommunicate iand icreate ia iknowledge isharing icultural icommunity. iA iuser iwanting ito ijoin ithis
icommunity ineeds ito iregister ito ithe isite ithrough iregistration iforms ifollowing iup ithrough ithree idifferent
iauthentication isteps. iA ilogged-in iuser imay iview ipost ifrom idifferent ipeople iin ithe itimeline. iHe/she imay
iupload ipictures ias ia ipost ito ithe itimeline ito ibe iviewed iby icommunity. iThe iuser imay icomment ion iposts
ias iwell ias iadd iother iusers ias ifriends. iA igroup ichat isession ihelps ithe iwebsite iusers ito ijoin ithe ipublic
imessaging iforum. iThe iapplication iallows ione-to-one iprivate imessage iinteraction ias iwell. iA idistinct
ifeature iof ichat ibot ihelpline iis ithe iwebsite’s iunique ifeature ialleviating iuser’s iproblem iin ithe isystem. iFor
ithe iadministrative isession, ithe iweb iapplication iis isupervised iby ione isuper iadmin iwho ihas iprivilege ito

iview, iupdate ior idelete iany ifunctionality iof ithe iwebsite. iThe iadministrator ican iutilize iits icrud
ifunctionality ito iupdate ior idelete iany iposts ior itake iactions iagainst iusers. i iEnsuring ithat ithe iwebsite
idevelops iwithin ia itrail ibased ipurely ifocusing ion isocial inetworking ihub, isome iresearch iwas iundertaken
ito ianalyze ion ihow isocial inetworking isite ifunction iand iproper itechnologies iand imethodologies ito ibe
iimplemented ifor isuccessful ioutcome.
The iresearch ibegins iwith iinvestigation iof icurrent iSocial iNetworking isite iand ithe iweb ibased itechnologies
iused ito icreate ione. iFollowed iby ia ipartly isocial inetwork ianalysis ion icurrent ibusiness istrategies iused iby
isocial inetwork isites ito iattract icustomers iand ithe isecurity imeasures itaken ito iensure
iprivacy iof iuser’s idata. iThe idata ifacts iand istatistics iretrieved ifrom isocial inetwork isite ilike iFacebook igives
iinformation iand iknowledge iabout imost iof ithe ihistorical ipatterns iof isocial inetwork ienvironment iand
iclarifies iabout ifuture itrends. iThese ianalyses ialso imap ito iidentify iand iquestion ion iwhat ifacilitates ithe
iinformation iand iknowledge iflow iwithin iinteracting iunits; ii.e. iwhich iuser iknows iwho iand iwhat
iinformation iand iknowledge iis ishared iwithin. iThe iinformation isharing iwithin iusers iare idone ithrough
ichat ior iposting.
iArticle ireviews ion ithe isocial isite iand itheir ichat imessaging iservice igave iinsight iview iof isocial inetworking
iand ichat imessage isystem. iA iresearch iwas ialso icarried iout ion ichat imessaging iservice iin isocial inetwork
ienvironment ialong iwith iweb-based ichat-bot iAPI. i
The iresearch ipapers iand iarticles isuggests ivarious iimplementation iof itechnologies iand itools ifor icreating
ia isocial inetwork isite, ihowever, ionly ithe irequired iones iare ito ibe imentioned ifor ithis iproject. iAt ipresent
icontext ithe iproject iuses itechnologies isuch ias: iPHP, iMySQL, iXAMPP, iCordova iand iNodes iand ialso
ichatbot iAPI ithrough iGupshup. iMajor iresearch ithat ihave ibeen istudied ifor ithis iproject iwill ibe idiscussed
ialso
ianswering iabout ithe iuse iof icertain itechnologies. iA ibrief iexplanation iwill ibe idone iin ithe itechnical ireview
isection iabout ithe ichoices imade ifor iselecting icertain itechnologies iover iothers iand ithe iresults iof imade
ichoices iwill ibe idiscussed ias ihow iit iaffected ion idesign iand iimplementation iof ithe iproduct. iIn ithe iend,
imajor ifindings iduring ithe iproduct idevelopment iwill ibe idiscussed iand iconcluded iwith ifuture ichanges ito
ibe imade iand iuse iof ialternative imethods.
This ireport ihighlights ithe iuse iof iSystem iDevelopment iLife-cycle i(SDLC) ifor idevelopment iof ioverall
isystem. iThe ilife-cycle imodel iis icomposed iwith ifive idistinct iwork iphases ifor icreating ia isuccessful
iapplication. iThese iphases iare i(in iordered ilist): iPlanning, iAnalysis, iDesign, iImplementation iand
imaintenance i(Gwentechembedded.com, i2018). iThe ireport ipoints iout ithe iuse iof iliterature iand itechnical
ireviews ias iPlanning iand ianalysis ifor ioverall iproject. iInformation iis igathered iand ianalyzed ito imake isure
ithat ithe irequirements ican ibe ifulfilled ito ibe iincorporated ito ithe iproject. iIn ithe idesigning iphase iof iSDLC,
iconversion iof irequirements ispecification ifrom iplanning iphase iis idone iby iusing iQSEE iTechnical itool ito
icreate iEntity iRelationship iDiagram i(ERD) iand iData iFlow iDiagram i(DFD). iThe idesign istage ishows ithe
ihardware iand isoftware irequirements ias iwell ias ioverall isystem iarchitecture. i iFollowing iup iwith ithe
idesign, ithe inext iphase iis iabout iImplementation iand itesting. iReviewing ion ithe iblue iprint icreated iin ithe
idesign iphase, ithe idevelopment iphase iand iimplementation iphase iis iwhere iall ithe icoding iis idone ito

icreate ia iproduct ifollowed iup iby ia iunit itesting. i iThe ioverall idevelopment ipart iis ithe imost icritical iand
ilongest ipart iin iSDLC. iThe iwritten icodes iare itested iin ithe itesting iphase ito iperform ia irequired
ifunctionality ithat ihas ibeen idetermined iin ithe ifirst istage. iEvaluating ithe iproduct iin ithe itesting iphase iis
icrucial ipart iof iSDLC i(Gwentechembedded.com, i2018).
LITERATURE iREVIEW
The iLiterature iReview idescribes ithe isearch iand ievaluation iof iliterature iin ithe ichosen itopic iarea isuch ias
isocial inetworking irelation, ichat ibased isystem, iand icontrol iover iprivacy. iIt icoherently ianalyzes ithe
iinformation iand iidentifies ithe igaps iin icurrent iknowledge. i
The iresearches iin ithis ipaper ishows ithe iinfluence iof isocial inetwork isites iand iextended irelationship iwith
ithe icommunity. i
1) An i Empirical i Study i on i use i of i Social i Networking i Sites:
The Research conducted by Kuan-Yu Lin and Hsi-Peng Lu in article of Computers in Human Behavior
explains the study of integrating network with externalities and motivation theory about people using
social networking sites. iIn ithis ifast ichanging iworld iwith itechnical iand icommunicational iadvancement,
isocial inetworking isites ihave ibecome ia imedia icorrespondence ifor ideveloping ipersonal inetwork
ithorough ionline. iThe istudy iapplies inetwork iexternalities iand imotivational itheory iexplaining iwhy ido
ipeople itend ito ijoin isocial inetworking isites. The study applies network externalities and motivational
theory explaining why do people tend to join social networking sites. i i(ScienceDirect, i2018)
They iconcluded itheir ifindings ishowing ithat ienjoyment iwas ithe imajor ifactor ifor ipeople iattractions
itowards iusing iSocial iNetworking iSites. iAdding ifurther ito ithe iresearch, icluster ianalysis ion igender iwas
idone iwhich ishows inotable idifference iamong imen iand iwomen ifor iusing iSNS. iPeers ior inumber iof
imembers iin ifriend ilist ishowed ian iimportant ifactor iaffecting iwomen iusers ito iget iattracted ito isocial isites,
iwhile ithis iwas inot iin icase ifor imale iusers. iThe ifindings iconcluded ithat igenders idifferences ialso iproduced
idifferent iinfluences iamong ipeople ifor iusing iSocial iNetworking iSites.
Social iNetworking isites ihave ibecome ia icommunity ihub ifor ipeople isharing isame iinterests. iThese
icommunities ican ibe iclassified ias iknown ior iunknown icommunity. iSometimes iknown icommunity ido
imeet iup iin iperson iand iwhile imost iof ithe itimes ithey icommunicate ionline. iAdditionally, imany ipeople ijoin
ithe icommunity ito imeet ifamilies iand ifriends iwho ilive ifar iaway ifrom ithem. i iFinding ithe iright icommunity
iis iimportant ifor iusers iwho ijoins ithe iSSN. i

2) Social i Network i Connects i Services i
As iSocial iNetworking isites iare iplaying iincreasingly iimportant iroles iin ithe icommunity, ibusinesses iare
iexploring ithe idimension iand ifinding iways ito imarket itheir iproducts iand iservices. iThe iimportance iof
isocial inetwork igrabbed iattention iof imany ibusiness iand imedia. iThey irealized ithat isocial inetworking iis ia
ithriving iplatform ifor ioffering itheir iproducts iand iservices ithrough ionline imedia imarketing. iMany
ibusinesses ioffered ijob iroles iand irecruitment iservices ithrough ithis imedium. iAcross ithe iglobe, icompanies
iare itransferring itheir ibusiness imarketing ithrough isocial inetworking imedium. iAs iLaura
iMcGarrity i(Vice iPresident iof iMarketing iat iMondo, ian iIT isourcing iand istaffing ifirm) iexplains ithat
inetworking iin iany iindustry iis ione iof ithe ivaluable iways ito ibuild ione’s icredibility iboth iprofessionally iand
ipersonally. iIt idoes irequire ihuge iamount iof iinvestment iof itime iand iprofessional irelationship iand iIt iwon’t
ihave isignificant ireturn iright iaway ibut ican iyield iand ifoster ithe ibusiness irelationship iin ilong irun. iLikewise,
isocial inetworking ican iprovide iemployment iopportunities, iimmediate ifeedback isuch ias: icustomer
ifeedbacks ion iproducts iand iservice, ibusiness ifeedbacks ion iproduct iqueries, iwrongful idismissal iof
iemployee. iA isocial inetworking isites ican iprovide ipages ifor iprofessional iorganizations iwhich ioffer
iopportunity ito iconnect iwith ipeople iwithin iparticular iindustry ior iarea iof iinterest.
A iresearch iwas iconducted iby iPhD, iMBBS iand iMD iholder irespectively: iYeshe iFenner, iSuzanne iM
iGarland, iElya iE iMoore, iYasmin iJayasinghe, iAshley iFletcher, iSepehr iN iTabrizi, iBharathy iGunasekaran,
iand iJohn iD iWark iin iJournal iof iMedical iInternet iResearch i(J iMed iInternet iRes) iexplaining ian iexploratory
istudy ion iWeb-based iRecruiting iSystem ifor iHealth iResearch iusing ia isocial inetworking isite ilike iFacebook
i(NCBI, i2012). iThe ibackground iof ithe iresearch iwas ifocused ion isubstitution iof itraditional iapproach iof
irecruiting iyoung iindividual ifor ihealth iresearch iby ipresent iinnovative iinternet irecruitment imodality. iThe
iobjective iof ithe iresearch iwas ito isurvey ithe ifeasibility iof ihiring ifemale imembers iusing itargeted
iadvertisement ithrough isocial inetworking iplatform. iThe isurvey ioutcome iwas iabout i500 ifemale iusers
iresponding ito ithe iads ithrough iFacebook iand iabout inearly i90% iagreeing ito iparticipate. iThe
iadvertisement iobtained ia ibroad igeographic idistribution iand ifinancial idistribution ifor iparticipants
imatched ithe itarget ipopulation. iThe icost iof iadvertisement iwas ivery icost ieffective ithan itraditional
irecruiting iapproach. i(NCBI, i2012)
They iconcluded itheir idemonstration iemphasizing ion ithe iuse iof imodern iinformation iand
icommunication itechnologies iis icost ibeneficial ias iwell ias ithe irecruitment iinformation ido ipenetrates iinto
inonurban icommunity ias iwell. iTheir imethod iwas isuccessful iand ihad iimplication ifor ifuture imedical iand
ipopulation iresearch. i
3) Making i a i Sense i of i Community: i Experience i from i Web-chat
In 2001, a research was done by Sveningsson, Malin in the Linköping University, Faculty of Arts and
Sciences in which he explained the experiences from Swedish web chat. To solve a common question

about what a web chat was all about, he conducted an observation research in a Swedish web chat room
for about two and half years (Sveningsson,M 2018). Communication imedia imay ihave icreated ilink
ibetween iphysical iand igeographical ilimitation iin ithe ipast iwhere ipeople icommunicate ithrough iletters
iand itelegraph ior itelephony, ihowever iit iwas inever ia ibetter ioption ithan iinternet. iThe iinternet imay ihave
ishared isimilar iproperties ito ithat iof iearlier icommunication itools ibut ithey ido inot ishare isame
icharacteristics. iOne iof ithe icharacteristics ithat imakes iinternet idifferent ithan itraditional icommunication
imedia iis: iit ihas iradically iincreased ithe inumber iof ipeople ito iwhich ia irelationship ican ibe iestablished.
i(Sveningsson,M i2018)
The iinternet iallows ius ito iseek iinformation iand icommunicate iwith inumerous ipeople iaround ibut iit ialso
iprovides ius inew iways ito imeet ipeople iand icreate irelationship. iThe iusers iof isuch ienvironment iinteracts
iwith inumber iof iways iand iapproaches iin ithe iinternet. iOne iof ithem iapproach iis ichat. iMoving ifurther
iaway ifrom ithe ilimitation iof igeolocation iand iphysical iunavailability, iwe ihave icome iacross ithe imodern
icommunication imedium. iThe iinternet imedium iof icommunication imay icreate iarenas ifor inews ior
ipersonal irelationship ifor isome imember iof ithe igroup ibut ifor iother iIt imay iserve ias iweb ichat, ihowever,
ithe imotive iis ito ifulfill ithe ineed iof isocial iinteraction. iThe iinternet iand icybercafé ihas inow ibecome ia inew
igathering iplace ifor ipeople. iUsers icommunicate iwith ieach iother iin isuch ienvironment idespite ithe ifact
ithat imost iof ithem ihave ino iidea iwho ithe iother iare iin itheir ioffline iworld. iThey ihave ifeelings ifor ieach
iother iand ioften icreate ia ibond iwith ieach iother iwhile imost iof ithem igets ideeply iattach ito itheir ionline
ienvironments.
In i2001, ia iresearch iwas idone iby iSveningsson, iMalin iin ithe iLinköping iUniversity, iFaculty iof iArts iand
iSciences iin iwhich ihe iexplained ithe iexperiences ifrom iSwedish iweb ichat. iTo isolve ia icommon iquestion
iabout iwhat ia iweb ichat iwas iall iabout, ihe iconducted ian iobservation iresearch iin ia iSwedish iweb ichat iroom
ifor iabout itwo iand ihalf iyears i(Sveningsson,M i2018).The iobservation ifindings iwere ifollowed iup iby
ipersonal iinterview iwith igroups iof ithe iweb ichat iusers. iIn ia iweb ichat, iusers igathered ia isubject iof
idiscussion iand iactivities iin iwhich isome iwere ifun iand isome iwere igenuine idiscussion, isome iwere ipractical
italks iwhile iothers iwere icasual italks iwith imade iup icomponents. iThese iobservations idid icast
isome iaspect iof iweb ichat; ia iweb ichat ican iact ias idynamic iconversation iplatform ithat iis ifrequently
irelocating iits icourse iwhere ithe imembers icould imake icreative iuse iof ilanguages iand icommunication
iformat ithus, igrouping ithe iconversation ito icertain istyle iand igenre. iAs ithe iobjective iof ihis iresearch iwas ito
ifind ithe isense iof icommunity ithrough imedium iof iinternet imessaging, ihis iobservation idid iforecast ion
ihow ithe iusers icommunicated iexpressing itheir iviews iand itheir iactivities ithrough icommunicative istyle
iand itheir ivalues iand inorms iand ibehavior. i
He iconcluded ithat ihis ianalysis imainly irelied ion itheory iof icommunity iand iGoffman’s itheory iof isocial
iinteraction. iHis iretrieved idata ishowed isome iissue iabout ithe iin idistinction iof ifriend’s icircle iby iusers.
iUsers igenerally idrew ia iboundary iagainst iunknown iusers ishowing ithe idistinctness ibetween icommunity.
iUsers iwere iaware iabout itheir icommunity iand ilimits i(Sveningsson,M i2018).

4) Communication i Goes i Beyond i Words: i Future i with i Chat-Bot
Over iperiod iof imany iyears, isocial inetworking iand isocial imedia ihave icurved ithe iways ifor ibusiness ito
icommunicate iwith ithe iaudience. iThese iplatforms iopened ia idoor ifor ieasier iadvertisement iand
imarketing iof ithe ibrands. iIn ireturn ithey iprovided iinstant ifeedbacks ito ibusiness ias iwell. iHowever, iin ithis
ifast igrowing imarket, ibusiness irealized ithat ithere iis ino itime iof ibreaks iand itime ioff. iCompanies icannot
irespond ito itheir icustomer i24/7 iand iif ithey icannot isome ido ilose itheir imoney. iA isolution ito ithis iproblem
iis ito iutilize ithe ichat-bot isystem iin ithe ibusiness i(Clark, i2018). iThis iautomated iartificial iintelligence idriven
isystem isolution iprovides inumerous ibenefits ito ithe ibusiness. iBot itechnology ido ichanges ithe iway
ibusiness icommunicate iwith icustomers. iOn iadaptation iof ibot itechnology, ibusiness ichanged itheir iway iof
iproviding icustomer iservice. iWe imay iencounter ithe inoticeable ichanges iaround iour ibusiness icommunity
ias iwell. iBusiness ihave istarted ito iuse ithis itechnology ifor imanaging icustomer iservices, ionline ibookings,
iinternal isupport ihelpline, iand iproviding ihealth iinformation ias iwell i(Clark, i2018). i
So iwhat iare ithese ibots iand ihow ido ithey iperform? iAn iarticle iby iLisa iClark ion ichat iand imessenger ibots ias
inew iresearch ifor imarketer’s istates ithat ibots iare iartificial iintelligence isystem iwhich iinteracts iwith ithe
iuser ithrough ithe imedium iof itext, ispeech, ior imessaging. iThey iallow ithe ibusiness ito icommunicate iwith
icustomer iwithout ithe iinvolvement iof ihuman iparticipation i(Clark, i2018). i iIn ipresent icontext, iwe isee
ithere iis ia ibig ichange ibeing imade iin ithe ionline imarketing iwhere ibusiness istarted ito imarket itheir ibrands
ithrough imessaging iapps iand ibot itechnology. iThe istatistics ishows ius ithat ibot iwill ibe ithe ifuture iin
icommunication itechnology. i
A iresearch iand iproduct idevelopment iof ismart ibot iapp iknown ias iHarlie iwas idone iby iresearchers iat
iCSIRO iand iUniversity iof iQueensland. iResearcher ibelieved ithat ihuman icommunication iwas ibeyond
iwords ias iit iwas icomplex iand imost ioften iincluded inon-verbal isign ilanguages. iHowever, idespite ithe
itechnical iimpediments iit iwas inot iimpossible ito icopy isome iof ithe iactions iof ihuman icommunication iby
ithe imachine i(The iConversation, i2018). iThe iobjective iof idevelopment iof iHarlie iapp iwas imainly ifocused
ion ibuilding ifor ipeople iwho iwere isuffering ifrom iParkinson’s idiseases iand idementia iand ihave idifficulty iin
icommunicating idue ito ineurological iconditions. iA itest iwas icarried iout ito iobserve ithe icommunication
ipattern ibetween ihuman isuffering ifrom iautism iand iHarlie. iThe iAI iasked iquestions, ispoke iabout
icommunity igroups iand iuser’s ihobby. iHarlie icould iask iquestions iabout irelated ifield iand iinterconnected
ithe itopics iwith ithe iquestions iand ireceived ianswer. iThe iAI iself-created iNodes iand ibranches iof iquestions
iand iresponses ireceived iinternally. iHarlie ias imany iother iAI ihad ino iconcept iof icommunity igroups ior
iwood iworks. iSelf-learning iby ia ibot iwas iseen iwhile iobserving ithe icase iof iHarlie. iThis icould imean ithe ibot
icould iwrite iown iconversation iand iinteract iwith iusers. iThe ipossibility iof iHarlie iself-writing ithe
iconversation iand ihelping ithe iusers istruggling iwith icommunication icould ibe ithe ifuture iof
icommunication. iCommunication iwith imachine iwould ibe ieasier iand icommunity irelationship ibetween
ihuman iand iAI ibot iwould idevelop ito ibring inew iscenario ito ithe itechnical ienvironment. iCommunication
imay igo ibeyond iwords iwith ithe ihelp iof iAI ibots. i(The iConversation, i2018).

TECHNOLOGY I REVIEW
In ithe itechnical ienvironment, iwe imay iencounter inumerous itools ifor ideveloping ia iproduct. iSome imay
icontain isame iproperties ias iother itools iand isome imay ibe ihaving iunique ifunctionality iwithin. iIdentifying
ithe ifunctionality iof ia itool iis icritical iaspect iwhen ideveloping ia iproduct ibecause ithese itools imay ihave
isimilar iproperties ibut imay ihave idifferent ifeatures iwithin ithat imakes ithem iunique iin itheir iown iway. iThe
irequired ifeatures ifor ideveloping iour iproducts imight ibe iscattered iwithin idifferent itools, iso iwe imust
iidentify iand iallocate ithe ionly itools irequired ifor idevelopment iof iour iproducts. iIn ithis isection, iwe iwill ibe
iidentifying iand idisusing ivarious itools ithat iwere iadopted ito imake ithis iproject.
Some iof ithe itools ithat iwere irequired ifor ideveloping ithis iSocial iNetworking iweb iapplication iare:
1) PHP i MyAdmin
It iis ia ifree iopen isource iweb iapplication itool ithat iprovides ia ihandy iGUI ito iwork iwith iMYSQL idatabase
iframework. iBeing ian iopen isource ias iwell ias ipopular iMySQL iadministrative itool, iit iis iused iby imillions iof
ipeople iworldwide. i iThe iProgram iof ithis itool iis iwritten iin iPHP iand ihas iall ithe ifunctions ithat iis ineeded ifor
ideveloping ia iMySQL ibased iweb iapplication. iPhpMyAdmin iis iavailable ifor iwindows iand ialmost ievery
iOperating iSystem. iThe imain ifeatures iof iPHP iMyAdmin iis iit iallows iMySQL iDatabase iwhere ia iuser ican
iprocess ia icrud ifunctions isuch ias iCreate, iUpdate, iDelete iand iRetrieve. iIt ican imanage ithe iimport iand
iexport iof idatabase icreated iby iMySQL iDBMS iand ialso iobtains ithe ifeature iof iworking iwith iother idata
iformats isuch ias iSQL, iCVS, iCodeGen, iMS iword i2000, iLaTex, iMediaWiki iTable, iPDF, iPHP iarray, iText! iand
imany imore i(Server iand iLLC, i2018). iThe ibenefit iof iusing ithis itool iis iit iallows ibackup iof icreated iSQL
iDatabase iand ican ibe iworked iupon iat iany itime. iFurthermore, iSQL iqueries ican ibe iwritten idirectly iin ithis
itool. iThe iwritten iqueries imay ibe isubmitted iand iwould iallow ius ito imake iCrud iOperation ithrough iour
iown iqueries. i
PHP iMyAdmin ihas imany ifeatures, ithe imost igeneral ifeatures iused iare i(Server iand iLLC, i2018): i
• Using icrude ifeature iof icreate iupdate iand idelete iof itables. i
• Creating iand iremoving iusers iand imanaging iuser’s iprivileges.
• Create, ialter iand idrop idatabase, itables iand ifields. i
• Search ientire idatabase ior icertain itable iwith ithe ihelp iof iSQL icommands ior isearch ioption. i
• Importing iand iexporting iof idatabase ifiles iwith idifferent iformat isuch ias: iSQL, iXML, iCSV, iLaTex. i
• Executing ithe icustom imade iSQL iqueries. iBacking iup iof idatabase imanually. i
PHP iMyAdmin ialso ioffers ivarious istorage iengines isuch ias: iMyISAM, iInnoDB, iMaria iDB iand isome imore.
iEach iof ithese istorage iengines ihas idifferent ifeatures. iMyISAM iis ithe imost icommon iabout iall ithe iengines
ibecause imany ihosted ipackages iallow ithe iuse iof iMyISAM. iAdditionally, iit iis ilimited iin ithe irelationship
icontrol iaspect iso iit iallows ieasier isetup iand iuse. iMyISAM iallows iportability iand iquick iimplementation
iacross imultiple ihosting iscenarios iso iit iis ithe imost icommon iamong iothers i(Bodnar, i2018).
iHowever, ifor ithis iproject iI ihave iused iInnoDB ibecause iit iallows ius ito icreate irelationships iamong itables

i and iallows ius ito isafeguard ithe idata iintegrity iby ilinkage iof iconstraints ikeys iamong itables. iIt iallows
i correct iperformance iof iOLTP iapps, igood ireliability, iAcid itransactions iand iconcurrency imanagement.
iThe iSocial iNetworking iSite idatabase idepends iupon ievery itables iand iconnection iand irelation iamong
itable iis imust iwhen iwe ideal iwith isuch iproject. iInnoDB ialso iallows itransaction iin itwo ior imore iDML
ioperation. iFor irelationship imanagement, ithe ichosen istorage iengine iwas ibest ifor ithis iproject. i
PHP iMyAdmin iallows ithe iuse iof iuser iprivileges ito ithe idatabase iso ithat ionly ithe igranted iuser imay iget
iaccess ito ithe itables iand idatabase. iManaging ithe iprivileges ihelps ifor igrouping iof ithe iusers iand itheir
iaccess iauthority ito isame idatabase iobject. iA iwebserver isuch ias iApache iis irequired ifor iconnection iand
iusing iPHP iMyAdmin.
Similarly, iOracle’s iApplication iExpress ishare ithe isame ifunctionality iof ithe idatabase imanagement ilike
iPHP iMyAdmin. iApex ican ihelp ibuild ithe iapplication iand idata ireports ias iwell iunlike iPHP iMyAdmin iwhich
iprovides ionly ithe iuse iof iadministrative iinterface. iThe ireason ifor ichoosing iPHP iMyAdmin iover iOracle
iApex iis ifor imanaging ithe itime iand ifor iconvenience. iPHP iAdmin icould ihelp ito ibuild iPHP isites ieasily
iwithout imuch ihassle ibecause ithe icodes iwritten iare iconvenient iand iconnection iwith ithe idatabase iis
ieasier. iThis iis inot ithe icase iif iwe iwere ito iuse iAPEX ibecause iwe ihad ito ichange ithe ilanguage iof ithe icode
ifrom iSQL iqueries ito iOCI iqueries, ialso ithe iconnection iwith idatabase ifollows idifferent iqueries. iThe iAPEX
iapplication iwould irequire iinstant iclient ifor iconnection iof iXAMPP iserver iwith ithe idatabase. iThis iwould
itake imuch itime iand iwould ibe itroublesome.
2) BOOTSTRAP
A ibootstrap iis ia icompelling ifront-end iframework ifor iweb idevelopment iin iagile iand iuncomplicated
imanner. iIt iincludes ithe iuse iof iHTML, iCSS iand iJavaScript itemplates ifor icommon iusers. iAlong iwith iit,
ibootstrap iuses icomponents ilike iForms, iButtons, iNavigation ibars, iDropdowns iand ialert ibox, iTabs iand
iaccordion, icarousel, itypography iand imany imore. iIt icontains ioptional iJavaScript iextensions ias iwell. i
Bootstrap iis ia ifree itool ifor icreating ia iresponsive iwebsite ithat iis iflexible iand istylish. iIt ialso icontains iother
iinterface icomponents ilike iScrollspy iand iTypeheads isuch ias imodal idialog ibox. i
Development iof ithis iproject iis idone iwith ithe ihelp iof ibootstrap iframework ibecause iit iis ieasier ito iuse,
isaves itime, igives iresponsive ifeatures, ihas iconsistent idesign, iand iis icompatible iwith ivarious ibrowsers
iand idevices. i
3) QSEE ISUPERLITE
QSEE iis ia imulti-CASE itool ithat ihelps ito imodel ia inetworking istructure. iThis itool icontains icollection iof
iother igraphical itools ithat ihelps ito ianalyze iand idesign ithe isystem isoftware. iThe isub-tool iwithin ithis

iCASE itool ihelps iprovides isupport itechniques ito icreate idesigns isuch ias idata iflow idiagram i(DFD), ientity
irelationship idiagrams i(ERD), iUSECASE idiagrams, inetwork icharts, idecision itree, ihierarchy ichat iand
i XML iModel. iThese isub itools ihelp ius ito iidentify iand isolve ithe isoftware irelated iproblems. i
For iuse iin iSocial iNetworking iSite, ithis itool ihelped ito icreate iDFD, iERD iand iUSECASE imodels ithat iacted
ias iblue iprint iduring ithe iSDLC iproject iplanning iphase.
4) SUBLIME ITEXT I3 I
Sublime itext i3 iis ia icross-platform itext ieditor ithat iruns iin ia iPython iprogramming iusing iAPI. iIt ihas ithe
ifunction iof isupporting imany iprogramming ilanguages iand iHTML ilanguages. iIt iallows ithe iusers ito iadd
ifunctionality iand iacts ias icommunity-build isoftware. iSublime iallows ithe ifiles ito ibe iuploaded iand iedited.
iProjects ican ibe iopened iin isublime iand iworked ithrough iallowing imultiple iselection iand ichanges. iMy
iproject iwas iall icoded iunder ithis itext ieditor ias iit iwas ieasier ito icode iand iits istylish idesign iand iinstant
icoding ierror igave iconvenience ito iwork ifor ilong ihours iand iwithout imuch ihassle. iSublime ioffers ivarious
ifeatures isuch ias i(En.wikipedia.org, i2018):
• Quick iNavigation
• Adaptive iMatching icommands
• Multiple iselection iand iMultiple ichanges
• Python ibased iplugins
• Customizability ivia iJSON isettings ifiles
• Cross iPlatform
• Compatible ito iuse iwith imany ilanguage iand igrammars.
• Easier iSearch ioption ifor ifinding icodes iand iwords iin ithe ifile
• Minimal imode ifor icompressed iversion iof icodes.
• Allows ieasier ijump ifrom iblock iof icodes.
The imain ifeature iof iSublime itext i3 ithat idifferentiate iit ifrom irest iof ithe iversion iis ithe iuse iif isymbol
iindexing iand ipane imanagement. iSymbol iindexing ifeature ihelps ito iscan ithe irequired ifiles iand iself-build
isome iindex ito ifacilitate ithe ifeatures iof igo ito idefinition iand igo ito isymbol. iPane imanagement iis iuseful
ifeature ifor iusers ias iit iallows ito imove ibetween ipane ivia ihotkeys i(En.wikipedia.org, i2018).
5) MICROSOFT IPROJECT
Microsoft iProject iis ia itool iused ifor iproficient iand iorganized iproject iassistance iand imanagement. iThe
isoftware itool ihelps ito iassists iproject irelated iline iof iwork iin imany ifields iof iworks isuch ias ifor
iconstructions, imanufacturing, imedicine, igovernment, iretail iand ifinancial iservices. iThe itool iis ideveloped

iby iMicrosoft. iIt iis ione iof ithe imost icommonly iused iPC-based iproject imanagement itool idesigned ito iaid
imanagerial itask isuch ias iDevising iplans, isetting irealistic igoals, iassigning itasks imonitoring iworkloads,
iGantt icharts iand ischeduling imeetings i(WhatIs.com, i2018).
In ithis iproject, iI ihave iuse ithis itool ito icreate iGantt iChart iillustrating ia iproject ischedule iand iactivities iwith
icurrent istatus. iThe ichart ihelped ito ikeep idependency irelationships ibetween iactivities. iIt iincluded istart
iand iend idates iwhich ihelped iin iview ithe iproject iprogress itrack irecord.
6) XAMPP
XAMPP istands ifor icross-platform, iApache, iMySQL, iPHP iand iPerl. iIt iis ia iplain iand ilightweight iapache
idistribution ithat imakes ithe idevelopers ito icreate ilocal iweb iserver ifor itesting iof icommon iPHP iand iHTML
ibased iwebsites. iXAMPP iserver isetup ihas ivery ieasy iformat iwith iserver iapplication i(apache), idatabase
i(SQL) iand iscripting ilanguage i(PHP) iis iincluded iin ivery iconvenient iextractable ifile. iIt iincludes iPHP
iMyAdmin iwhich ihelps ius ito imanage ithe idatabase iSQL ialong iwith iapache ithat ihelps iwith iconnection
iwith ithe iserver. iBeing ia icross-platform itool iit iworks iequally iwell ion iLINUX, iMac iand iWindows. iSince
ivarious iweb iserver ideployment iallows iuse iof isame icomponents ilike iXAMPP, iit imakes ithe
itransformation ifrom ilocal iserver ito ilive iserver ivery ieasy iwhich imeans iuser iwill ibe iable ito iview iknow ihow
itheir iwebsite ilooks iwhen ihosted ionline. iWeb idevelopment iusing iXAMPP iis ivery ibeginner ifriendly iso ithis
iproject iwas iworked iusing iXAMPP i(Mikoluk, iK i2013). i
7) GOOGLE IDRIVE
It iis ian ionline ifile istorage iand idocument isharing iservice ideveloped iby iGoogle iInc. iThe idrive iacts ias iactual
ihard idrive ibut ionline. iGoogle idrive iallows iusers ito istore ifiles ion itheir iserver iand ihas ifeatures iof icross-
platform iand isynchronization iof ifile iacross idevices. iFile isharing iis ione iof ithe isole icomponent iof igoogle
idrive. i
Google idrive iuses iplain ifolders ito iorganize ithe iuser’s ifiles. iUsers ican iupload ivarious ifile iformats isuch ias
idoc, itxt, iimage ifiles iand ialso ivideos. i
The ireason ifor ichoosing igoogle idrive ifor ithis iproject iis: iit iis ieasier ito iaccess iwith isimple igoogle iaccount
ilogin. iFiles iare iseparated iby ifolder iwhich imakes ifiles iorganized, ithe idrive iallows isharable ilinks iof ithe
ifolder, ithe idrive ican ibe iaccessible ifrom ianywhere iwhich imakes iit ieasier ifor ime ito iwork ion ithe iproject
iand iupdate iit iin itime iof ineed iand ithe ibest iadvantage iof iusing ithis idrive iis iit iallows ifree iaccount isetup
iand ioffers ithe iusers iwith i15 iGB iof ifree ispace ithat iwhich iis ienough ifor istoring ithe irequired ifiles ionline
iand isave iown ispace iin ithe icomputer.
8) TRELLO
iTrello iis ian iassociative itool ithat iform ithe iprojects iinto iboards. iTrello iserves ias ian iassistant ito ithe
iproject. iIt ikeeps itracks iof ion-going itasks, icompleted itask iand ito-do ilist. iTrello itells ithe iuser iwhat iis

i being iworked ion iand iwhich imember iof ithe iteam iis iworking ion icertain itask. iIt igives ius ithe itrack iof ithe
i project i(Help.trello.com, i2018). i
Trello iacts ias ia iwhiteboard ifilled iwith inumber iof isticky inotes iand iwritten itasks ifor ieach imember iof ithe
iteam. iIt ishows ithe iroles iand itask ifor ieach imembers iand ishows ithe iprogress iof ioverall itask. iTrello ihas
ireal itime isync iof idata ibetween ivarious idevices. iCards ican ibe iadded ito ithe iboard iand ikept itrack iof
ideliverables. iA idue idate ican ibe iassigned ito ithe itask iand ifiles iattachment iis ialso ia igreat ifeature iof iTrello.
i
This itool iwas iused ifor ithe iproject ibecause, ithe iproject ihas ivast ifeatures iand ifunction iand iworks ito ibe
idone. iEach iwork-to ibe idone icannot ibe iremembered iso iwith ithe iuse iof iTrello, iI iwas iable ito ikeep ithe
itrack iof iongoing, icompleted iand iupcoming iworks.
METHODOLOGY
The iformat iand ithe inature iof ithe iproject idefines ithe iuse iof icertain imethodologies. iA imethodology iis ia
ipractice, ior imoreover iof ia itechnique iwith iprocedures iand irules ithat ibinds ithe iwork iin idiscipline.
iChoosing ia icorrect imethodology iis ivery iimportant iwhile icreating ia iproduct ibecause ithe idevelopment iof
iproduct ibended iby ithe irules iresults iin ia iquality iof iproduct. iA imethodology ithat iis ibeing irooted iin isome
ivital iwork idefines iwhy iwe ichoose ito ido ithings iin icertain iway. i
A iproject ican ibe idelivered iin imany idifferent iways. iAnd iusing ia icorrect imethodology iwithin iwould imean
imaking ia istructural iplan ifor ithe iprocess iof ideveloping ia iproduct. iThere iare idifferent imethodology
iframeworks ithat icould ibe iapplied ito ia iproject, iand iin ithis iproject, iI ihave iresearched ito iapply iIterated
iAgile iFramework. iThe iIterated iand iincremental iframework iwas ichosen ias isoftware idevelopment
imethodology ithan ia itraditional ilinear iframework. iThe ilinear iframework iwould imake ia iperfect isense ion
ipaper ibecause ithe iwork iwould ibe idivided iinto ieach iphase iand isteps, iand ieach iphase iwould ibe ithe inext
ilogical istep, ihowever, iin ipractical iit iwould inot ibe ipossible ito icontinue ito iwork iin istep iwise iphases. iAs
ideveloping ia iproduct iwould ineed iconstant ichanges ibeing imade iand iwe iwould ineed ito ifrequently ijump
iback-and-forth ion ithe itask ifor iadding ior ireplacing ithe isection iof ithe iproject, ia ilinear iframework iwould
inot iallow ifor ithe iamendments iafter ithe icompletion iof icertain iphase i(Matsugu, i2014). iIn ishort, ia isystem
iperformance icould inot ibe itested iat igiven itime iuntil ithe icompletion iof iwhole iproduct. i
Out iof imany iiterated iframeworks, iagile imethod iwas ichosen ias ithe imethodology ifor ithis iproject. iThe
iiterative iframework isuch ias iagile iwas icreated iin ia iresponse ito iovercome ithe iinefficiency iand iproblem
ithat ihad ibeen ifound iin iwaterfall imodel. iThe iidea iof ithis imethodology iis ito idevelop ia iproduct ithrough
irepeated icycle icalled iiterative iand iin ilesser ifragment iof itime i(incremental). iThis iallows ithe ideveloper ito
itake ithe iadvantage iof iwhat iwas ilearned iduring ithe idevelopment iof iearlier iparts iand imake inecessary
ichanges iwithin ithe iproject iphases. iFurthermore, ithe idevelopers ican ibreakdown ithe iparts iinto ismaller

iunit iand imake ithe iproject imanageable ito iwork ion ias iit iwould iallow ithe ideveloper ito ilook iupon ivery
iminute iparts iof ievery isingle iunit. iAgile imethodology ihas igreater iflexibility isuch ias iit ihas ilesser iattention
iin irequirements iand igreater idependence iupon iuser’s istories iand ichanges iwith ihigher ipriority ion itesting
ias idevelopments igoes ion. iNew ichanges ican ibe imade iat iany itime iin ithe iproject. iThe iproduct iwill ialways
ibe iseen ias iin idevelopment iphase ias inew ifunctionality iwill ibe ifrequently iadded iat iany isection. i
iCompared ito ilinear iwaterfall imodel, iAgile imethodology iis isimpler ito iimplement, iutilizes ilesser
iresources iand iis imore ifocused ion ioutput. iOverall ithe iAgile imethodology iis ibetter ifor iproject
imanagement iand iis ialso ibeen ichosen ifor ithis iproject idevelopment i(Itinfo.am, in.d.).
A iwaterfall imodel iis ione iof ithe ipopular imethodology iof iSDLC. iOften iknown ias itraditional iapproach ito
ithe isystem idevelopment ilife icycle, iit idescribes ithe idevelopment iof ithe iproduct ito ibe irigid iand imore
ilinear. iThere iis ino iturning iback iin ithis imethodology, ias ithe iproduct iis ideveloped ion icertain igoals iand
iphases iwhere ion icompletion iof ieach iphase ithe inext iones iget istarted. iIt imeans ithat ioutcome ifrom ione
iof ithe iphase iis ithe iinput ifor ithe inext iphase. iThe iproduct idevelopment iphase inever iexperiences ithe iideal
iphase ias ithere iis ino istopping ibecause ieach iof ithe iphases iis iconsidered ito ibe ia ideveloping iphase.
iRequirements iare iclassified iin ifull iin ithe ibeginning iof ithe iproject i(top iof iwaterfall) ibefore iany iwork
istarts. iA iwaterfall iapproach iobtains ithe ititle iof isingle icycle iapproach i(Itinfo.am, in.d.). iThere iis ilittle
iscope ifor ireviewing iand iadapting ionce ithe iproject iis icompleted. iIt ibecomes iquite iimpossible ito iturn
iback ionce ithe iproject iis iin itesting iphase. iThis iapproach imakes ieven iharder ifor ibusiness ibecause ithere iis
inothing ito ishow ito ithe iclient iwhen ithe iproject igoes ialong, imeans, ithe iwork-in-progress icannot ibe
ianalyzed. iThere iis ipotential irisk iadapting ithis iapproach ibecause iwe icannot itell ihow igood ior ibad ithe
iproject iis iuntil iit igets ifully ideveloped. i
Whatever ithe iscenario iis, iboth iwaterfall iand iagile imethods iare ithe isystem idevelopment ilifecycle
imethodologies iand iare iabided iby ithe irules iof iSDLC iphases: iplanning, iAnalysis, iDesign, iImplementation
iand iMaintenance. iThe iagile imethod idoes ifollow ithe iSDLC iprocess ibut itends ito ikeep iin ithe ibackground
ias iit ioften ichanges ithe isteps iand iphases iwith iconstant itesting iand idevelopment. iThe iAgile imethod ido
inot idemand ifor istrict irequirements iand iamendments iof irules ito iglide iby ithe irequirements, ihowever,
iafter ithe iplanning iwith ibase iis icreated ifor ithe iproject iit ioften iadvances iwith ithe idesigning. iDesigning iis
ifound ito ibe iimportant iaspect iof iAgile iMethod. iThe idesign iphase iincludes isorting iout ithe irequirements
iand idesigning ithe iERD iand iCASE idiagrams ithat iacts ias iblue iprint ifor ioverall isystem. iThe iuse iof iCASE
itools ihelps ito icreate ithese idiagrams. iThe idesign ifocuses iupon ithe idevelopment iof idatabase
imanagement isystem ias iwell. i
The iinitial iphase iof idevelopment ifor ithis iproject iwas ibuilding ian iinitial iplan iwhich iincluded ithe imain
iobjectives iand iaims ifor ioverall iproject. iThis igave ithe iinsight iview iof iwhat ithe iproject iout ilooks ilike.
iFollowed iby ithe idesign iof iERD, iUSECASE idiagram iand iDatabase. iThe iData idictionary iwas icreated ifor
ibriefing ithe ioverall istructure iof ithe idatabase. iThere iwas ialso ithe iuse iof iGantt iChart ifor iproject ischedule
iand iTrello iwas itechnical itool ithat iwas iused ito itrack ithe idetails iof ithe iprojects. iOn imidway iof ithe iproject,
itesting iwas icarried iout ito icheck ifor iworking ifunctionality iof ithe iproject. i(see iAppendix iDiagram). i

1) FEASIBILITY ISTUDY
A ifeasibility istudy iis idone ibefore ibeginning iof iany iproject. iA ifeasibility istudy iconcludes ithe inature iof ithe
iidea iand iensures ithat ithe iproject iis itechnically iand ieconomically iviable ito iwork ion. iThe ifeasibility istudy
iis idone ifor ievery iproject ibecause iit ishows ithe ireports iif ithe iproject iis ijustified iand iworth iinvesting. iThe
iproject iwith itoo imuch irequirement iof ithe iresource imay inot ibe iconsider ifeasible ibecause iit imay inot ionly
ibe icost iless ieffective ibut imay ialso ihamper iother itasks iand iwould inot ibe iprofitable ifor ithe icompany.
A ismall ifeasibility istudy iwas ialso idone ito ithis iproject iof isocial inetworking isite iand ithe iproblems iwere
ichecked iand ianalyzed itoo. iThe i i iresources iwere isorted iout iand iany irecommendation ifrom ithe ithird
iparty iwere ilooked iupon. iAdditional iinformation ineeded ifor ithe iproject iwere ialso inoted iand istudied.
2) TECHNICAL I FEASIBILITY
Technical ifeasibility idefines ithe ifeasibility istudy ithat iis irelated ito ispecify ithe iuse iof iequipment iand
isoftware iwhich iin iturn iwill isatisfy ithe iuser’s irequirement. iIt idefines ithe itechnical ineeds ifor ithe isystem.
iThe ibold imeaning ito ithis iterm idefines, iwhether ithe iproject iis ifeasible ito iachieve ior isome ichanges ineed
ito ibe imade iwith idifferent iapproach, iwhether iit iwould ibe icompleted iwithin ithe irequirements iand icosts
iavailable. iThe istudy itroubleshoots ithe iproblem iand icontinues ito idevelop ion ithe iprocess. iThe iproject
iprocess igrows iforward iand itries ito ireach ithe iuser’s irequirement. iThe istudy ilooks iupon ithe iproject
ifinancial iconsiderations iand itries ito iachieve iany itechnical idevelopment ifor ifuture iuse.
In ithis iSNS isystem, iall ithe ianalytical idata ihas ibeen ireviewed ito imake iit itechnically ifeasible. iAll ithe itools
irequired iand iOS ihas ibeen iseen ias icompatible iand ieconomically iand itechnically ifeasible ito ithe isystem
3) ECONOMIC I FEASIBILITY
This ifeasibility iis itypically iassociated iwith ithe icost-benefit ianalysis iof ithe iproduct. iIt ihelps ithe iproject
ideveloper ito ianalyze iand idetermine ithe icost, igrowth iand ibenefits iby ithe iproject ibefore iany ibudget
iallocation iis iconcluded. iMoreover, ithe istudy ilooks iinto ithe iindividual iprojects iand iimprove ithe iproject
iintegrity iwhich iin iturn ihelp ithe ideveloper ito iforecast ithe ieconomic iprofitability ior ireturns iby ithe
iproposed iproject. iThe ieconomic ifeasibility iincludes:
• Budget iallocation ithrough isystem ianalysis.

• Calculating ithe ifuture ireturns iby ithe iproject.
• Budget ifor ibuying ithe iproject’s ihardware.
The iproject iis iconsidered ito ibe ieconomically ifeasible iwhen ithe iproject isubsists iof:
• Tangible ibenefits: iuse iof iinformation isystem,
iincreasing ithe ispeed iof iprocessing,
igranted iaccess ito iinaccessible idata, iaccessible ito idata iin itimely imanner
• Intangible ibenefits: ibetter ianalysis iof iinformation iand iquicker idecision imaking iprocess,

i providing ibetter icustomer iservices, iincreate iin ijob isatisfaction, imaintaining ithe
i business iname.
• Tangible icosts: ilower icost iof iequipment isuch ias ihardware iand isoftware, ilower icost iof
iresources, ilesser isystem ianalyzing itime
• Intangible icosts: ilower icustomer idissatisfaction, iinnovative ileaders iin ithe iprojects,
iquicker iinformation iaccess.
4) OPERATION IFEASIBILITY
In ithis ilevel iof ifeasibility istudy, iit iinvolves ito istudy ito ianalyze iand iconclude iwhether ithe iproject
iobjectives ican ibe imet ior inot. iIt ialso istates ithat iif ithe iinitial iproject iplan iwould igratify ithe iproject
irequirement ithat ihad ibeen iidentified iin irequirement ianalysis iduring iSDLC.
5) SOCIAL IFEASIBILITY
User’s isatisfaction iwith ithe iproject iis ithe icrucial ipart iin ithe isystem. iFor ithis, ifrequent ichanges iin ithe
isystem iis ilikely ito ibe iexpected iif ithe iuser iis inot ihappy iwith ithe isystem. iSo, ithe icontinuous icall iup ifor itask
iload ito icope iwith iuser’s irequirement iwill ibe ithe isystem itop ipriory isuch ias: isearching ifor ifriends ion ithe
isystem, iadding ifriends, imanaging itimeline, ideleting ipost iand icomments, iviewing ithe irequested
ifriend ilist iand ion-going ievents iwith iminimal ierrors. iMaking ia isystem ithat iis isocially ifeasible iwould iadd
icredibility iand isuccess ito ithe iproject. iThus, ia isystem iwould inot ibe iconsidered ito ibe igood ifor ithe
idevelopment iif iit iis inot isocially ifeasible.
REQUIREMENT I ANALYSIS
Requirement ianalysis iis ithe iprocess iof idescribing ithe iuser’s iexpectation ifrom ithe inew isystem. iIn iother
iwords, iit iis ialso iknown ias iinformation igathering ior irequirement icapturing. iIt icircumscribes ithose iworks
ithat ineeds ito igo iinto idetermining ithe ineeds iand iconditions ifor imeeting ithe iproject. iAdditionally, iit
itakes iinto iaccount iof ithose iconflicting irequirement ifrom ivarious istakeholder, idocumentation iand
ivalidating ithe isoftware iand isystem irequirements.
This iphase iaims ito ideal iwith ispecified idocuments iso ithat ithe irequirements iare ifair iand istructured.
iDeciding ithe irequirement ithat iwill ibe iinvolved iis iimportant, ias iit iinvolves ithe iuse iof itraditional imethods
iof iinformation icollection, ianalyzing ithe idocuments iand iother ipart iof isystem iwhich iwould ibe isimple,
ireliable iand iprofitable. iThe iwork iis idone iwhen ithere iis ivery iless irisk iinvolved iin ithe iproject. iDeveloping
ithe isystem iinvolved ianalyzing ithe isystem irequirements. iAs ithe isystem igrows iwith iadditional ifeatures
iand irequirements iit igets icomplex iand ithe igoal iwould ibe ieasily iunderstood. iThus, ithe iprocess iof
irequirement ianalysis ibegins. i
1) FUNCTIONAL IREQUIREMTENTS

The ifunctional irequirements idefine ithe iactions iand ifunctionality iof ivarious isegment iin ithe isystem.
iThese iare ishared iwhen idifferent iusers iinteract iwith ieach iother iin ithe isystem i(Eriksson, iU i2012).
In ithe icase iof ithis isystem iof iSocial iNetworking iSite, iit iconsists iof ivarious iusers isuch ias iAdmin, icommon
iuser, inon-registered iusers iand ifriends. iThis iweb iapplication iis ideveloped iso ithat ithe iusers iinteracts iand
ishare itheir iideas, iinformation iand icultures iwith ieach iother iand idevelop ithe ifeeling iof icommunication
iwith ivarious ipeople iacross ithe iglobe. iThe iusers ihave itheir iown ilogin iinformation iwhich ihelps ithem ito
ilog iinto ithe isystem ifollowed iby itheir iown ibasic iinformation iin itheir iabout ipage, iand itheir ipictures iin
ialbum ipage. iThe iuser iis igiven iwith itheir iown iuser ipanel ito iupdate ior idelete itheir iinformation. iFor ithe
iadmin, ithere iis ione isuper-admin ithat icontrols ioverall isystem. iThe iadmin iwill ibe iable ito icreate, iupdate ior
idelete iany iusers, ievents, iimages, iposts ior icomments. iSuper-admin igets ithe iprivilege iof icontrolling
ithe ientire iapplication. iUsers iwill ibe iable ito isearch ifriends iand iadd inew ifriends, ichat iwith ithe ifriends, iand
italk iwith ichat-bot ihelpline. iUsers iwill ialso ibe iable ito ipost iimages iand itext iand iwill ibe iable ito icomment
ion iother iuser’s iactivity.
2) NON-FUNCTIONAL I REQUIREMENTS
This iis ithe irequirement ithat iis ias iuseful ias ifunctional irequirements iin ithe isystem ibecause iit ispecifies ithe
ioverall istandards iused ifor ireviewing ithe isystem. iIt iis ialso idefined ias isystem iqualities irequirements. iThey
idefine ithe iusability iand ieffectiveness iof ientire isystem. iIf ithe isystem ifails ito iachieve iany ione iof ithe inon-
functional irequirements, ithey iresult iin isystem ifailure ito imeet ithe iusers, ibusiness ior imarket ineeds. iThe
iNon-functional irequirements ihas ithe itype iof imanaging irequirement ilike: ifunctionality, iusability,
ireliability iand iperformance i(Eriksson, iU i2012).

PRODUCT iDESIGN
In ithe iDesign iphase iof ithe iSystem iDevelopment iLife-Cycle, ithe iSystem iis idesigned iin ian iappropriate
iformat ireferencing ithe irequirement ithat ihave ibeen ilisted iin ithe iPlanning iphase iof iSDLC. iReferencing
ithe iblue iprint ifrom irequirement ianalysis, ithe iproduct idesigning iwill ithe icrucial ipart iin ithis iphase. iWe
itake inote iof ithe ilooks iof iproject iand imockup ithe ioverall iproject. iListing ithe ifunctionality iof ivarious
isection iof iproduct, ispecifying ithe irules iand idesigning ithe isection iwill ibe ithe imajor itask iin ithis iphase.
iAdditionally, ithe iproduct idesign iphase icarries iout ithe itask iof iconsolidating idifferent imodules iand
iadding ifunctional ispecification ito irun ithe iproject. i
The idesign ipart iis iclassified iinto itwo igroups, ii.e.: isystem idesign iand icomponent idesign. iThe ioverall
idetailed iinformation iof ithe isystem iexplaining ihow iwell ithe icomponents iinteracts iwith ieach iother iis
idone iis isystem idesign iphase iof iSDLC. iThe iinformation iand ifeedbacks igenerated iby ithe iclients iare
icollected iin ithis idesign iphase ialong iwith ithe ifundamental idesign isuch ias: idevices iused, isecurity icheck,
idata itype, iflow iof idata iover isystem ifor idefining icertain ifeatures iand ioperations ilike iuser iinformation,
irules, idiagrams iand iprocedures iand ifunctions iThe icomponent idesign iin ithe iSDLC ishows ithe
ifunctioning iof ithe isystem iand icomponents iand itheir iresults igenerated iafter ifull icompletion iof ithe
iproducts. iThe iprocess iof iinput, ioutput, idatabases iand ifiles, iand imain icomponents iare ifurther ilooked
iand ianalyzed iand idesigned iwith iproper idiagrams ilike iSequence idiagram, icomponent idiagram iand idata
iflow idiagram. i
In ithis iproject iof iSocial iNetworking isites, ithe iwork idone ifor ipreparation iof iproduct idesign iwas icarried
iout ifirst iby idesigning ia iData iflow idiagram i(DFD) i[Appendix iA]. iThe iDFD iwas icreated ito ishow ihow ithe
idata iwould iflow iin ithis iproject. iInvestigating ion ithe iproject, ithe iDFD idefines iinput iand ioutput iof ithe
idata iand icomponents ithat iare iinvolved iin ithis iprocess. iAfter isuccessful idesigning iof ithe iDFD, ithe inext
istep iwas ito icreate ia isystem idesign. iThe isystem idesign ibegan ifirst iwith icreating ia iERD idiagram. iAn iERD
iis iEntity iRelationship iDiagram ithat idefines ithe irelationship ibetween idifferent ientities, iattributes
iand itheir irelation ithat ihave ibeen iincluded iin ithis iproject. iThe ientities iinvolved iin ithis isocial inetworking
isite iwere ithe iusers, iadmin iand ivarious ievents ithat iwould iuse ithis isystem. iIn ithird istep iof isystem idesign,
iData iDictionary iwas icreated i[Appendix iA]. iA idata idictionary ithe ioverall idesign iof ithe idatabase. iIt
iincludes iattributes, itables iand idatatypes. iThe iERD iand iData idictionary idefines ithe idesign iof ithe
ioverall idatabase. iThe ifourth istep iin ithis iprocess iof isystem idesign iwas ito icreate ia iproject ispecification
idocuments. iWhich istates ithe ioverall irequirements ineeded ito idevelop ithe ifinal iproduct. iThe
irequirements iare ilisted iin ithe iproject ispecification. iThe isystem idesign iwas iended iwith icreating ia
iUSECASE idiagram ito irepresent ithe icommunication iand iinteraction iof iusers iwith ithe isystem. iThe
iUSECASE iconsists iof ithe iprotagonist iuser ias iactor iand iits irelation iwith ivarious icomponents iof ithe
isystem.

A) System i Design i (DIAGRAM)
FIG i1: iSYSTEM iDESIGN i

B) Entity i Relationship i Diagram i (ERD IDIAGRAM) I
FIG i2: iERD iDIAGRAM
C) USE ICASE IDIAGRAM

ADMIN IUSECASE
FIG i3: iADMIN iUSECASE

USER IUSECASE
FIG i4: iUSER iUSECASE
After ithe icompletion iof isystem idesign, ithe inext istep iwas ito icreate ia iproduct idesign ifor ithe isystem. iThe
iproduct idesign ibegan iwith icreating ia iDatabase iManagement iSystem i(DBMS). iDesigning ia iDBMS iis
icomparatively iimportant ias ia icreating ifrontend iframework ifor ithe iproject. iCreating ithe iDBMS ifor ithe
iproject ifollows ithe iuse iof iPHP iMyAdmin ias ia idatabase iadministrative itool. iWith ithe ihelp iof ithis itool,
idatabase iwas icreated iwhich iwas ithe isole ibackbone iof ithe iwhole iproject. iThe iuse iof itool iallowed ithe
icrud ifunctionality ito ibe iapplied ito ithe iSQL iqueries. iTables iand idata iwere icreated iin ithe idatabase. iAnd
idatabase iwas icreated ion ilooking iat ithe isystem idesign. iThe iTables icreated iwere ibased ion ithe idesign
imade iin ithe iERD idiagram iand ithe irelationship iamong itables iwere iimplemented ilike iwise. iDatabase
icreation iwas ithe irequired ifor ithe iproduct ito ibe iimplemented iand itested iaccordingly. iCreation iof
irelation ibetween itables iin ithe idatabase iis ivery iimportant iand ispecifying ithe iconstraints ihelps ifor
imaintaining iintegrity iamong idata iwhich iprevents iduplication i[SEE iAPPENDIX]. iThe ifully icompleted
isystem iand iproduct idesign ihelped ito imove ion ito ithe iimplementation iphase iof ithe iSDLC.

PRODUCT I IMPLEMENTATION
During ithe iimplementation iphase, ithe iproject itakes ithe ishape. iThe iconversion iof iactual irequirements
iand iobjectives iinto iactual iproduct iis idone iin ithis iphase. iThe iprogrammers iare iengaged iin icoding,
idesigning iand ire-testing ithe iproject. iIt iis ithe iphase iwhen ithe iproject ibecomes ivisible ito ieveryone. i i
The ifirst iphase iof ithe iproduct iimplementation ibegan iwith isorting iout ithe irequirements iand idesigning
ithe iframework iand idatabase. iThen ithe ifront-end ipage iwas ideveloped. iThis igave ithe ioverall iframework
ito ithe iproject ias iwhat iwould ithe isite ilook ilike, ialso, ishows ithe isuccessful iconnection iwith idatabase iand
ithe isite. iThe inext istep iwas ito idesign ithe isite iand iwork ion ithe iCSS iand iadding ifunctionality ito ithe ivarious
isection iin ithe isite. i
The iproduct iimplementation iwas ithen icarried iby icreating ia iuser imodule. iThe iSDLC idesign iphase iof ithis
iSocial iNetworking iSite ishows, iUSECASE idiagram iwhich idefines ithe iuser ias ian iactor ithat iwill ibe iable ito
iLogin iand ipost iinformation ito ithe isite. iThe iCRUD ioperation iis iimplemented iin ithe iuser’s imodel iwhere
ihe/she imay icreate, iupdate ior idelete ithe ipost iand icomments. iThe isame ioperation iwas ifollowed ifor
icreating ithe iadmin imodule. iHe/she imay iuse ithe iCRUD ioperation iand iapply ito iuse ion iCreating iusers,
ideleting iusers, ipost, iand iactivities. i i i
The iERD iof iSocial iNetworking iSite ishows ivarious ientities iinvolved. iThe iERD iof iuser iinvolved
irelationship iwith iadmin, iusers, ifriends, iposts iand ichat. iA iuser iwith iauthorization iwould ibe iable ito ilog
iinto ithe isystem iand ipost ior icomments. iThe iCRUD ioperation iinvolved ihere iwas, iuser iwould ibe iable ito
idelete ior iupdate itheir iown ipost iand ino iother ipost iby iother iusers iwould ibe ihampered. iUsers iwould ibe
iable ito iComment i(insert) iand ialso ichat iwith iother iusers. iThe iPrimary ikey iof ieach iuser iin ithe idata ibase
imakes ievery iuser iunique ito ithe isystem. iEach iand ievery ientity ihas ithe iPrimary ikey iinvolved iand irelation
iwith ithe iuser imakes ieach ione ientity ias iunique. iThe iEntity isuch ias iPost, iComments iand iChat isystem ihave
itheir iown iunique iID ialong iwith icombination iof iforeign ikeys isuch ias: iA iPost imay icontain iforeign
ikey iof iUsers, ia icomment imay icontain iforeign ikey iof iUsers iand iPost iand iso ion. i
At ithe ivery ifirst ibeginning, ia iregistration ipage iwas icreated ialong iwith ia ilogin iarea. iThe iregistration ipage
iwould iget ithe iinformation iof iusers ibefore igiving iaccess ito ithe isite. iThe iregistration ipage iuses iJQuery
ifor iinstant ivalidation iof iany ierror iin iuser iinput, iauthentic iinformation iis istored ito idatabase iand ithe iuser
iis iforwarded ito inext iprocess iof iregistration. iHere iuser iwill ibe iuploading itheir iprofile iimage iand igiving
ifurther iinformation iabout itheir ihobbies ior ipersonal idetail. iThis iis ithe istep ithat ihelps iduring iforget
ipassword isession iwhere iuser ican icreate inew ipassword ientering itheir ipersonal idetails ithat ithey
isubmitted iearlier. iFinally, iafter icompletion iof ithe iregistration iuser iis inow iautomatically ilogged iin iand
ican ibrowse ithe isite. iThe inext iprocess iwas icreating ian iadmin ipanel. iThe iAdmin iPanel iis iseen ias ithe
iSuper iUser iof ithis iwebsite. iAdmin iis ithe iSuper iuser iwho iis iable ito icontrol ithe iusers iand itheir idata. iThe
iAdmin iPanel icontains; iUsers idetails ias iwell ias iforms. iAdmin iis iable ito icreate ianother isuper iadmin ior
iupdate iuser’s idetails. iUser idetails iuses ithe idata-table iwith iCRUD ifunctionality. iAdmin imay iupdate

iwhole iuser’s idetails ior ionly ithe ipart iof iit. iThe iPanel iuses iAjax iand iJQuery ifunctions ithat imakes iit ieasier
ifor ihandling iCRUD ioperation idue ito iless ipage irefresh iand iinstant isession imessage.
PRODUCT I TESTING
A) GOSSIP: I SOCIAL INETWORKING I SITE I(IMPLEMENTATION ITESTING)

FIG i4: iFront iPage iof ithe iSite

1) REGISTRATION I& ILOGIN
Figure i5: iRegistration iand iLogin iPage
2) REGISTRATION ISTEPS

Figure i6: iRegistration iStep i1
Figure i7: iRegistration iStep i2
3) LOGIN I PAGE

Figure i7: iLogin i- iIn iby iregistered iuser

4) ADMIN IDASHBOARD
Figure i8: iAdmin iDashboard

Figure i9: iUser iList
Figure i10: iAdmin iList

Figure i11: iCreate iAdmin iForm
SYSTEM iTESTING
A isystem itesting iis ithe ilevel iof isoftware itesting iwhere ia icomplete iand iintegrated iapplication ior isoftware
iis itested. iThe imain ipurpose iof ithis itesting iis ito ievaluate ithe iconformity iwith ithe isupplied irequirements.
iThe iprocess iof ithis itesting ihelps ito iverify ithat ithe iapplication ior isystem imeets ithe ispecified
irequirements. iThis iis iwhy iit ihappens ito ibe iknown ias ithe icritical istage iof iany iproduct idevelopment
iprocess. iThe iresult iof ithis itesting idefines iwhether ithe iproduct iwill ibe iable ito iget iinto ithe imarket iand
iavailable ito ibe ipublicized ior iwill ibe ineeding isome imore imaintenance iand ichanges i(Kalra, in.d.).
The ipurpose iof ithis itesting iallows ithe ideveloper ito iview iand idiscover iany ikind iof ierrors ifrom ithe isystem
ithat imay ihave ioccurred. iThe isystem itesting iis ithe iinitial istep ibefore iproduct imarketing. iIt ihelps ito
iassure ithat ithe iproduct iworks iaccording ito ithe ispecified irules iand iis iable ito iinteract iwith ithe
irequirements iand idesign ithat igives ia iwhole imeaning ito iitself. iThe iend iresult ifrom ithis itesting imakes
ideveloper iassured ithat ithe iapplication ior ithe isystem iis iable ito iwork iaccording ito iclient ior ibusiness
idemand. iWith ivarious imethod iof ieffective itesting, iit iconcludes ithat iwhether ithe iproduct iraises ithe
iconfidence ilevel iof ithe ideveloper iby igiving iquality iproducts. i
There iare imainly itwo ikinds iof itesting; iA iblack ibox itesting iand iWhite-box itesting. i
The iblack ibox itesting idefines ithe ioverall ifunctionality iof ithe isoftware. iIt iis ialso iknown ias iBehavioral
iTesting. iIn ithis itest, ia isoftware’s iinternal istructures iand idesign iand iimplementation iis iunknown ito ithe
itester. iThe itest ican ibe ifunctional ior inon-functional. iAs ithe iname idefines, ithe iblack ibox itesting iis ilike ia
iblack ibox iwhere itester icannot ihave iseen iwhat iis iinside ithe isystem i(Software iTesting iFundamentals,
in.d.). iHowever, ithe imodes iof itest icarried iout iin ithe iblack ibox itesting iare ito icheck; iIncorrect ifunctions,
iinterface ierrors, iDatabase istructure ierrors, iperformance ierrors, iinitialization iand itermination ierror. iIn
ishort, ia iblack ibox itesting iis itesting iof ifunctional ior inon-functional, iwithout ithe ireference iof iinternal

icomponent iof ithe isystem. iQuite iopposite ito ithe iblack-box itesting imethod iis ithe iwhite ibox itesting. iThis
itechnique ianalyses ithe iprogram istructure iand iassume ithe itest idata ifrom iprogram icode i(Software
iTesting iFundamentals, in.d.). i
For ithe isystem iof ithis iGossip iSocial iNetworking iSite, iblack ibox itesting iwas icarried iout. iThe itest iwas
ispecific iand ineeded ispecific iresult iafter iinputting ithe idata, ithe iresult ifrom ithe itest iwere ias iexpected iand
ishows ithat imost iof ithe ifunctionality iand istructures iof ithe iprogram ihas iworked iproperly iand ias irequired.
i
Some iof ithe isteps itaken ifor isystem itesting iusing iSDLC iapproach ifor ithis isystem iwere:
• Unit iTesting
• Integration iTesting
• Stress iTesting
• Compatibility iTesting
1) UNIT ITESTING
It iis ithe itesting iwhere iindividual iunits iare itested. iThe iaim iof ithis itesting iis ito ivalidate ithat ithe isystem
iperforms ias idesigned. iIt ihas ithe ismallest itesting ipart iin ithe isystem, iusually iinvolve itesting iwith ifewer
iinput iand ione isingle ioutput. iIt iis ialso ithe imain iform iof itesting. iThis iis iusually iconducted iafter icompletion
iof ithe ieach iof ithe iunit iof ithe isystem ithoroughly ichecking ithat ievery ipart iworks ias irequired. iOnce ithe
iunit iis itested iand ishows ibug ifree ireport, ithe inext iunit iof ithe isystem iis icarried iout ifor itesting i(Software
iTesting iFundamentals, in.d.) i. i
Unit itesting iwas icarried iout ifor ithis isystem ias iwell. iThe itest iresult ishows iexpected ireports. iThe ifollowing
iimages ishows ithe itest ibeing icarried iout ialong iwith iprovided iTest-Case ireport.

A) REGISTRATION I FORM I & I LOGIN I FORM I TEST
Figure i12: iRegistration iForm iTesting
A iuser iwas iplanned ito ibe iregistered ito ithe isystem. iThe idetails iwere iinserted ito ithe iregistration iform.
iAfter icompletion iof ithe iinsertion, ithe ierror imessage iwas ishown ithat itwo ipasswords ididn’t imatch. iThe
iunit itesting ifor iregistration iwas isuccessfully icompleted.

Figure i13: iLogin iForm iTesting
The iregistered iusers ihave ito iuse ilogin iform ito iget iinto ithe iwebsite iand ibrowse iit. iHowever, iif ithe iuser
idata iis iinvalid isuch ias iinserted ipassword ior iemail iis iincorrect, ithen ihe/she ishould ibe inotified iabout ithe
ierror.
SL.NO WHAT iWAS iTHE EXPECTED ACTUAL iOUTPUT REMARKS

iTEST iABOUT iOUTPUT
1 Sign iUp ibutton iand After iClicking ion ithe Shows iError idue ito SUCCESS
iRegistration iforms isign iup ibutton, ithe ipassword imiss
iwere itested ito iJQuery ifunction iof imatch
iprevent iuser ifrom ithe isystem ishowed
iinserting iinvalid ishow iif iany ierror
idata
2 Login iFor ithe Login iButton ishould Shows iError idue ito SUCCESS
isystem iwithout iany iopen ilogin ipanel iincorrect ipassword
ivalid iuser iand iallow iuser ito ior iemail
iauthentication i iinsert idata, iand iif
iincorrect iinput, iuser
ishould ibe inotified

2) INTEGRATION I TESTING
In ithis imode iof itesting, iindividual icomponents iof ithe isystem itest iare icombined iand itested iin igroup. iThe
iaim iof ithis itesting iis ito ireveal ithe ifaults iand ibugs iwhile iinteraction ibetween iintegrated iunits. iIn isimple
imeaning, iintegration itesting iis ithe itest iconducted icombining idifferent iunits. iThis iis ithe isecond iphase iof
itesting idone iafter iunit itesting. iWhen ithe ipart iof imove ionward iafter iunit itesting, iit idoes inot inecessarily
imean ithat ithe iparts idoes iwork iwhen iintegrated iwith iother iparts iin ithe iproject. iThe iIntegration itesting
iconsists iof iboth iwhite ibox iand iblack ibox itesting i(Software iTesting iFundamentals, in.d.). iTo ivalidate ithat
ithe iprogram iis iproperly iexecuting iand ishows iboth iusefulness iand iquality iwhen iinteracting iwith iother
iunits, ithe iintegration itesting iis icarried iout.
Integration itesting iwas icarried iout ifor ithis iproject ias iwell. iThe ifollowing iimages ishows ithe itest ibeing
icarried iout ialong iwith iprovided iTest-Case ireport.
A) SUCCESSFUL I REGISTRATION IAND I STEPS
Figure i14: iRegistration

Figure i15: iRegistration iSteps
After isuccessful iregistration, ithe iregistration iuser iis itaken ito ithe ifurther iauthentication istep isuch ias
iuploading iprofile iimage iand ientering iuser iquestions.
Figure i16: iUser iis idirected ito icomplete ithe istep
A iuser iwho ileaves ithe iregistration isteps iand icloses ithe iwindow, ion ithe inext ilogin ihe/she iwill ibe idirected
ito icomplete ithe iregistration istep ibefore iaccessing ithe ihomepage.

1 New iRegistration iof User ishould ibe iable User iis inow SUCCESS
ithe iuser ito iregister ito ithe iregistered iand
isystem. iprovided iwith
ifurther iregistration
isteps
2 User ineed ito ifinish Cancelling ithe When ilogin, iuser iis SUCCESS
ithe iregistration iregistration isteps ire-directed ito ithe
isteps i imust idirect iuser ito icompletion istep.
icomplete ithe istep
ibefore igetting ito
ithe isite
B) USER I POST IAND I COMMENT
Figure i17: iUser iPost iin iTimeline
A ilogged iin iuser iis iable ito ipost ito ithe itimeline iand ion ithe iright iside iof ithe itime-line irecent iactivity iof ithe iusers iin
ithe isystem iis ishown.

Figure i18: iUser iCommenting
User iis iable ito icomment ito ithe ifriend’s ipost iand ican isee ithe ireply iby ifriend ias iwell.
1 User iPosting iinto User ishould ibe iable User iis iable ito ipost SUCCESS
ithe itimeline ito icreate inew ipost ito ithe itimeline
iand isubmit iit ito iwithout iany ihassle
itimeline
2 User icommenting User ishould ibe iable User ican icomment SUCCESS
ion ipost ito icomment i ion ion ifriend’s iactivity
iposts iand ireply ito
icomments

C) ADD IFRIENDS IAND IREQUEST I
User iis iable ito isend irequest ifrom itimeline. iThe iUser iwho igets ithe irequest isee’s ithe inew irequest iin ithe imanage
irequest isection. iAfter iaccepting ithe irequest, ithe iuser iis iable ito iadd iand ican iview ithe iadded iuser iin ifriend’s
isection.

1 Add inew ifriend User ishould ibe iable User iis iable ito ipost SUCCESS
ito iadd inew ifriends ito iadd ifriend ifrom
itimeline
2 Manage iFriend User ishould ibe iable User ican imanage SUCCESS
iRequest ito isee irequest ifrom ifriends ifrom
ifriends iif iany iManage ifriend itab
3 View iAll iadded User ishould ibe iable User iis iable ito iadd SUCCESS
ifriends ito iaccept irequest inew ifriends

D) USE I GOSSIP I HELPLINE I(CHAT I BOT)
Figure i21: iGossip iHelpline
User iis iable ito iuse ithe ihelpline iin ithe isystem. iThe iChat ibot ihelps iusers ito iask iquestion iand iin ireply isolves
iquestions irelated ito ithe isystem.
E) USER I PRIVATE ICHAT

Figure i22: iUser iPrivate iChat
User iare iable ito ichat ionline iprivately. iThe ichat ipage ishows ithe ionline iusers iand imessages ifrom ithe iusers. iUsers
imay ialso ibe iable ito inavigate ito itheir inewsfeed iand isee ifriends ifrom ithe ichat ipages. i

1 User iChat User ishould ibe iable User iis iable ito SUCCESS
ito ichat iwith itheir iprivately ichat iwith
ifriends iother iuser

F) ADMIN IDASHBOARD I DETAILS
Figure i23: iAdmin iSupervises iUser
Since iadmin ihas ithe irole iof iSuper iUser, ithe iadmin imay icontrol iall ithe iuser idetails. iHe/ iShe imay ialso iblock
ior idelete iusers. iAdmin ican iadd iother iadmin ias iwell.

1 Admin iControls Admin ishould ibe Admin iis iable ito SUCCESS
iUser iable ito imake iCRUD iupdate ithe iuser
ioperation ito ithe
iuser iinformation
3) STRESS I TESTING
Stress itesting iis ithe iprocess iof iwork iloading ithe icomputer iapplication, inetwork ior iprogram ito
imaintaining ithe ilevel iof icapability iof isystem iunder iunfavorable icondition. iThe itest ican iinvolve ito

imeasure ithe ierrors. iStress itest ishows iwhether ior inot ithe iapplication iis iable ito iexecute ithe iresult iunder
iunfavorable icondition. iIt iis idone ito icheck ithe iability iof ithe isystem ito ideal iwith ivarious iuser idemands.
iThe istress itesting iis ialso iknown ias iapproval itesting i(Software iTesting iFundamentals, in.d.).
A istress itesting iwas ialso icarried iout ifor ithis ithis. iThe iimages iof ithe iresult ifrom ithe istress itest ialong iwith
itest-case iis ishown ibelow:

A) CREATE INEW I ADMIN
Figure i26: iInvalid iInput iShows iError
The iinsertion iof iblank ifield iin ithe iform ishows ierror ito ithe iadmin. iThis ierror iis iinstant.

B) UPLOAD I INVALID IIMAGE I FOR I POST
Figure i27: iInvalid iFile iUpload
Image iupload ifor ithe ipost ineeds ivalidation ifor ichecking icorrect itype iof iimage ibeing iupload. iThe iallowed
iimage ifile isize iis i5 iMB imax iand ishould ibe iJPG, iJPEG, iPNG, iGIF iformat ifile iextension. i

1 Admin iShould inot Admin ishould ibe The iform iis inot SUCCESS
ibe iallowed ito inotified iabout ithe isubmitted iand
isubmit iinvalid ierror iadmin iis inotified
iform iabout ithe ierror
2 Invalid iImage User ishould ibe User iis inot iable ito SUCCESS
ishould inot ibe inotified ifor ithe ipost iand iis
iuploaded ito ierror inotified iabout ithe
itimeline ierror

C) EDIT IPICTURES
 UPLOAD iCOVER iIMAGE
Figure i26: iUploading iCover iImage i

Figure i27: iUploading iCover iImage iSuccess

i
 CHANGING iPROFILE iPICTURE
Figure i28: iUploading iProfile iImage i

Figure i28: iUploading iProfile iImage iSuccess

1 Change icover User ishould ibe iable On iClick iupload i, SUCCESS

iimage ito ichange icover iUser iis iable ito
iimage ichange icover
iimage
2 Change iProfile User ishould ibe iable On iclick iUpload, SUCCESS

iPicture ito ichange iprofile iuser iis iable ito
ipic ichange iprofile
ipicture

D) SEARCH IUSERS
Figure i29: iSearch iPeople

E) VIEW IFRIEND’S IPROFILE
Figure i30: iView iFriend iProfile
F) UPDATE IUSER I INFORMATION

Figure i31: iUpdating iUser iInformation
4) COMPATIBILITY ITESTING
Compatibility itesting ichecks iwhether ia iprogram iis iable ito irun ion idifferent ihardware iand iOperating
isystem ior inetwork ienvironments ior iMobile idevices. iThis itesting iguarantees ithat ithe iproject ior isoftware
iis iable ito irun ion ivarious ienvironment. i

i
Figure i28: iCompatible iin iGoogle iChrome i

Figure i29: iCompatible iin iMicrosoft iEdge
Figure i30: iCompatible iin iiPad iPro

1 Should iRun iin Able ito irun ion Is iable ito iuse SUCCESS
iGoogle iChrome, idifferent idevices iBootstrap iand iis
iMicrosoft iEdge iand iand iPlatform iresponsive ito
iMobile iDevice ivarious iDevices iand
iPlatform
PRODUCT iEVALUATION

A iproduct ievaluation iis icarried iout iduring iany itype iof iproject idevelopment. iIt iis iessential ito icheck ifor ithe
iproduct irequirements ithat ihave ibeen iassigned iduring iinitial iplanning. iThe ievaluation ichecks iwhether
ithe iproduct ihas ibeen imade iaccording ito ithe iassigned irequirements. iMost ioften, ideveloping ia iproduct
imakes iiteration iof isame iprocess iagain iand iagain idue ito ierrors iduring ithe itesting iand ievaluation iphase.
iDuring iwhich ithe ideveloper ishould ireturn ito iprevious iphase iand irectify ithe ierrors iand ibegin ito idevelop
iand iagain ievaluate ithe iproduct iif iit idoes imeet ithe irequirements. iProduct ievaluation ialso ishows ihow
iwell ithe iproduct ican ibe ifurther iimproved iwith ichange iin ifunctionality, idesign, ior iby iadding iother iunits.
iThe iproduct ievaluation iprocess ialso ihelps ito itake ia inote iif iany ifuture ichanges ito ibe imade ior inot. i
In ithis isocial inetworking isite, ithe iinitial iproposed iproject iplan iwas ito imake ia isocial inetworking isite ifor
ithe icommunity iwhere iusers iwill ibe iable ito ishare itheir iideas, icultures, iand iknowledge ithrough ivarious
iactivity ifrom ithe isite. iUser ishould ibe iable ito ipost, icomment, imake ifriends, iprivate ichat iwith ifriends iand
iuse ihelpline. i
As imentioned iin ithe iinitial irequirement iusers iare iable ito ipost iin ithe itimeline, iusers iare iable ito ipost itext
ior iimages ito ithe itimeline iwhere ipeople imay ipublicly isee itheir iactivity. iUsers iare iable ito icomment ion
iother iunknown iuser’s ipost iand ieven imake ifriends. iUser imay iable ito isend ifriend irequest ito iother iusers
iand iother iusers imay ibe inotified iabout inew ifriend irequest. iUsers ican iadd ifriends iand ibe iable ito iprivately
ichat iwith iother ifriends. iFor ithe ihelpline, iusers imay idirectly icontact ithe iadmin ithrough icontact iform, ior
imay iable ito iuse iGossip-Helpline iwhich iis ia ichat ibot ifor ithe isystem. iThe ichat ibot iis iintegrated iAPI ithat iis
ideveloped iby iGupshup. iThe iChabot ican ibe iassigned iwith ivarious iquestion iand ianswers. i
The iAdmin iDashboard iis ithe isuperior idashboard iin ioverall isystem. iIt icontains ithe iuser iinformation ias
iwell ias iadmin iinformation. iAdmin ican icalculate ithe idata iand igrowth iof ithe iusers iin ithe isystem ithrough
iits iUI. iAdmin ican ichange iinformation iand ican ialso iblock ithe iusers iwho iare iinvolved iin iillegal iterms iof ithe
isystem. iAdmin imay ialso ichange ithe ipassword iof ithe iusers. i
For ithe isecurity ipurpose, ithe isystem iis iintegrated iwith ithe iuse iof ipassword ihashing ifunctionality iof iphp.
iThe isystem ihas istrict isecurity ifor iuser’s iinformation iand iuses ihashing. iUnlike iother ipassword isecurity
ilike iMD5, ipassword ihashing iprovides iintense isecurity ito ithe iuser’s ipasswords, ias iit icannot ibe idecrypted.
iIt icreates ihex istring iwith istandard icrypt i() ifunction ithat ihas i60 icharacter istrings. iPassword ihashing iis
ialso isame ias iusing isalt ihashing. iThe iuse iof ipassword ihashing ialgorithm imakes ithe isystem isecured ifrom
ifuture icyber-attacks.
There imight ibe ivarious ifuture ichanges ito ithe isystem iaccording ito iuser’s ineeds iand isystem irequirements.
iAs ieveryday inew ifunctionality iand ichanges iare irequired iover ivarious isocial isite, iit imay
ialso irequire ichanges ito ibe imade iin ithis isystem ias iwell. iSince isocial inetworking iare ithe isole icommunity
isites, iuser’s idemand imay iarise ifor ivarious ichanges iin ithe isystem. iIn ifuture, ithe isystem imay iinvolve
ifunctions isuch ias isending iauto ireply iemail ifor iauthentication iand iregistration iprocess. iThis imay iallow
ibetter iweb isecurity iinvolvement iin ithe isystem iand ialso imakes ithe isystem igenuine. iThe iwebsite imay

ialso iinclude ivideo ichat iand ibetter ichat isession iwith ifriends. iModules ilike ichat ilive inotification imay ialso
ibe iincluded. iThe isystem iwould ihave ibeen ibetter iif ithere iwere ioption ito icreate igroup ipages iwhere iusers
iwould ibe iable ito icreate, iinvite iand ifollow ithe igroup ipage. iSince ithis iis ia icommunity iknowledge isharing
iwebsite, ia igroup ichat isession iwould imake iit imuch ibetter. i
Requirements ilisted iin ithe irequirement icatalogue iare ifully imet iby ithe iproduct. iThe iproduct iinvolves iuse
iof ivarious ifunctionality ito imake ithe isystem iliable iof iuse. iA ifull isystem itesting iwas icarried iout ito icheck
ievery icomponents iof ithe isystem iwhether ithey iare iworking iat ifinest ior inot. iUnit itesting icarried iout ithe
iunit ivalidity iof ithe isystem. iIt ichecked ifor ivalidity iof iinput ifrom ithe iusers. iSince ithe iproduct ihas
icontained igood iUI iand ibetter ifeatures ithan ipreviously ilisted iin ithe iproject iplan, ithe iproduct ican ibe
iconsidered ias isuccess. iFutures ichanges iin irequirements iand ifeatures iwould imake ithis iproject ieven
ibetter. i

PROJECT iEVALUATION
A iproject ievaluation ihelps ito icheck ifor iwhether ithe iproject igoals iand irequirements iare imet. iThe
ievaluation idiscusses ithe iproject idevelopment iand ifuture iimplementation iof idifferent ifeatures ito imake
ithe isystem ibetter. iThe ifuture iof ithe iproject iis idefined iby ithe istatus iof icurrent iproject. i
The iproject ibegan ifirst iby icreating iinitial iproject iplan. iThe iinitial iplan idiscussed iall ithe irequirements iand
igoals ito ibe iachieved ifrom ithis iproject. iFollowed iby iinitial iplan, ia iproduct idesign iwas icreated iwhich
iacted ias iblue iprint ifor ioverall isystem. iThe iuse iof iAgile imethodology iin ithis iproject ihelped ito ifrequently
irevise ithe iproject iplan iand irequirements. iThe idevelopment iof iproduct iwas idone iadapting ithe ichanges
imade iin irequirements isuch ias iadding imost iimportant ifeatures iand idisengaging iless irequired ifeatures.
iThe iproject idesign iphase iwas ifollowed iby iproduct idevelopment iphase iwhere ia iproduct iwas icreated.
iApart ifrom iproduct idevelopment iphase, iuse iof ivarious iexternal itools iwas iused isuch ias iuse iof iTrello iand
igoogle idrive ifor istoring iof iproject ifiles. iThe iTrello itool ihelp ito inavigate ithe iprogress iof ithe ioverall
iproject. iThen iGantt ichats iwere icreated. iBoth iGantt ichat iand iTrello iwas ifrequently iimprovised iafter ithe
ifeedback ifrom itutor imeetings. i
Research iwere icarried iout ito ifigure iout ithe iimportant ifeatures iof icommon isocial inetworking isites. iThe
ifindings irevealed ithat isocial inetworking isite imust ihave ifeature iwas iallowing iusers ito ishare ipost,
icomments iand iprivate ichat iwith iother imembers ias iwell ias isupport iteam ifor iusers iqueries. iThese
ifeatures iwere iimplemented iand iimprovised ion ithis iSNS isite ias iwell. i
Overall, ithe iproject iwas isuccessful iand ievery iobjectives iand igoals iwere imet. iThe iproject idid iteach isome
ivaluable iinformation iabout irequirements ifor iany iproduct, iAgile iand iother imethodologies, iuse iof icorrect
iSDLC, iimportance iof ivarious itools iand itechniques, ibenefits iof istorage isites ilike igoogle, iand iimportance
iof iresearch ibefore icarrying iout iany iproject. i
CONCLUSION
The iproject iwas isuccessfully icompleted ianalyzing irequirements iand iproject iplan. iThe iProject iwas idone
ias isole isocial inetworking isite ifor icommunity iknowledge isharing. iThe iproduct idevelopment ifollowed
iAgile imethodology. iTesting ion ivarious iunits iof ithe iproduct ishowed ithe iproduct iwas igenuine iin iits
ifunctionality iand irequirements. iVersion icontrol isuch ias iTrello iwas iused ito iview ito iprogress iof ithe
isystem. i
The iend iproduct iis ia isocial inetworking isite icalled iGossip. iThe isystem icontains itwo ientity iknown ias
iadmin iand iusers. iLike iany iother isocial inetworking isite, iusers iare iable ito icommunicate iwith ithe isociety
iand ishare iknowledge iand iideas. iUsers iare iable ito ipost, icomments, iadd ifriends iand ichat iwith itheir
icolleagues. iIf iany ihelp iis irequired iby iuser, ithey imay iuse iGossip ihelpline ichat ibot. i

With ifurther iadded ifeature isuch ias ivideo ichat, ilive inotification iand iuser ionline iemail iauthentication ican
imake ithis isystem ieven ibetter. iNotification ialerts ifor ipassword ichange iand iregistration ican imake ithe
isystem isecurity ibetter.

BIBLIOGRAPHY
123helpme.com. i(2018). iSocial iNetworking iSites: iBeneficial ito iSociety iEssays. i123helpme.com. i[online]
iAvailable iat: i
<http://www.123helpme.com/social-networking-sites-beneficial-to-society-preview.asp?id=191304>
i[Accessed i27th iApr i2018].
Gwentechembedded.com. i(2018). iFive iStages iof ia iSoftware iDevelopment iLife iCycle. iGwentech
iEmbedded. i[online] iAvailable iat: i
<http://gwentechembedded.com/five-stages-of-a-software-development-life-cycle/> i[Accessed i1 iMay

i2018].
ScienceDirect. i(2018). iWhy ipeople iuse isocial inetworking isites: iAn iempirical istudy iintegrating inetwork
iexternalities iand imotivation itheory. iSciencedirect.com. i[online] iAvailable iat:
i<https://www.sciencedirect.com/science/article/pii/S0747563210003766> i[Accessed i26 iApr. i2018].
NCBI. i(2012). iWeb-Based iRecruiting ifor iHealth iResearch iUsing ia iSocial iNetworking iSite: iAn iExploratory
iStudy. incbi.nlm.nih.gov i[online] iAvailable iat:
i<https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3374531/#idm140254999294784title> i[Accessed i28
iApr. i2018].
Sveningsson, iM. i(2018). iCreating ia isense iof icommunity: iExperiences ifrom ia iSwedish iweb ichat. iDIVA
i[online] iAvailable iat: i
<http://www.diva-portal.org/smash/record.jsf?pid=diva2%3A256178&dswid=3272> i[Accessed i30 iApr.

i2018].
Clark, iL. i(2018). iChat iand iMessenger iBots: iNew iResearch ifor iMarketers. iSocialmediaexaminer.com
i[online]. iAvailable iat: i
<https://www.socialmediaexaminer.com/chat-and-messenger-bots-new-research-for-marketers/ i>
i[Accessed i1 iMay i2018].
The iConversation. i(2018). iThe ifuture iof ichatbots iis imore ithan ijust ismall-talk. itheconversation.com
i[online] iAvailable iat: i

<https://theconversation.com/the-future-of-chatbots-is-more-than-just-small-talk-53293 i> i[Accessed
i29 iApr. i2018].

Server, iH. iand iLLC, iN. i(2018). iWhat iIs iphpMyAdmin. iHandybackup.net i[online]. iAvailable iat:
i<https://www.handybackup.net/backup_terms/phpmyadmin-definition.shtml i>
[Accessed i30 iApr. i2018].
Bodnar, iJ. i(2018). iMySQL istorage iengines i- iInnoDB, iMyISAM, iMemory. iZetcode.com i[online]. iAvailable
iat:
<http://zetcode.com/databases/mysqltutorial/storageengines/> i[Accessed i30 iApr. i2018].
En.wikipedia.org. i(2018). iSublime iText. i[online] iAvailable iat:

i<https://en.wikipedia.org/wiki/Sublime_Text> i[Accessed i1 iMay i2018].
WhatIs.com. i(2018). iWhat iis iMicrosoft iProject i(Microsoft iOffice iProject)? iWhatIs.com. i[online]
iAvailable iat: i
<https://whatis.techtarget.com/definition/Microsoft-Project-Microsoft-Office-Project> i[Accessed i1 iMay

i2018].
Mikoluk, iK. i(2013). iXAMPP iTutorial: iHow ito iUse iXAMPP ito iRun iYour iOwn iWeb iServer.
iBlog.udemy.com i[online] iAvailable iat: i
<https://blog.udemy.com/xampp-tutorial/> i[Accessed i1 iMay i2018].
Matsugu, iB. i(2014). iThe iLimitations iof iLinear iMethodology i- iWaterfall ior iAgile? iBlueprint i[online]
iAvailable iat: i
<https://www.blueprintsys.com/blog/the-limitations-of-linear-methodology-waterfall-or-agile/>
i[Accessed i1 iMay i2018].
Itinfo.am. i(n.d.). iSoftware iDevelopment iMethodologies. i[online] iAvailable iat:

i<http://www.itinfo.am/eng/software-development-methodologies/> i[Accessed i1 iMay i2018].
Eriksson, U. (2012). Functional Requirements vs Non Functional Requirements. [online] Available at:
https://reqtest.com/requirements-blog/functional-vs-non-functional-requirements/ [Accessed 1 May
2018].
Software Testing Fundamentals. (n.d.). Unit Testing - Software Testing Fundamentals. [online] Available
at:
<http://softwaretestingfundamentals.com/unit-testing/> [Accessed 10 May 2018].
Software Testing Fundamentals. (n.d.). Black Box Testing - Software Testing Fundamentals. [online]
Available at:
<http://softwaretestingfundamentals.com/black-box-testing/ > [Accessed 10 May 2018].
Kalra, P. (n.d.). How to do System Testing. [online] softwaretestingstuff.com. Available at:

<http://www.softwaretestingstuff.com/2009/12/how-to-do-system-testing.html> [Accessed 10 May
2018]

Report Sample

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Report Sample

Uploaded by

Copyright:

Available Formats

TABLE I OF I CONTENTS

AAYUSH IRAJ IPOKHREL 1

AAYUSH IRAJ IPOKHREL 2

AAYUSH IRAJ IPOKHREL 3

iFacebook, iTwitter iand iMyspace. i(123helpme.com, i2018)

icreated isocial inetworking isite

AAYUSH IRAJ IPOKHREL 4

iimplemented ifor isuccessful ioutcome.

ichat ior iposting.

ibe imade iand iuse iof ialternative imethods.

AAYUSH IRAJ IPOKHREL 5

icrucial ipart iof iSDLC i(Gwentechembedded.com, i2018).

iinformation iand iidentifies ithe igaps iin icurrent iknowledge. i

1) An i Empirical i Study i on i use i of i Social i Networking i Sites:

idifferent iinfluences iamong ipeople ifor iusing iSocial iNetworking iSites.

iis iimportant ifor iusers iwho ijoins ithe iSSN. i

AAYUSH IRAJ IPOKHREL 6

irecruiting iapproach. i(NCBI, i2012)

3) Making i a i Sense i of i Community: i Experience i from i Web-chat

AAYUSH IRAJ IPOKHREL 7

iand itheir ivalues iand inorms iand ibehavior. i

AAYUSH IRAJ IPOKHREL 8

AAYUSH IRAJ IPOKHREL 9

AAYUSH IRAJ IPOKHREL 10

iusing iPHP iMyAdmin.

itake imuch itime iand iwould ibe itroublesome.

AAYUSH IRAJ IPOKHREL 11

ifeatures isuch ias i(En.wikipedia.org, i2018):

AAYUSH IRAJ IPOKHREL 12

iproject iwas iworked iusing iXAMPP i(Mikoluk, iK i2013). i

iand isave iown ispace iin ithe icomputer.

AAYUSH IRAJ IPOKHREL 13

itrack iof iongoing, icompleted iand iupcoming iworks.

AAYUSH IRAJ IPOKHREL 14

iproject iis iuntil iit igets ifully ideveloped. i

imanagement isystem ias iwell. i

AAYUSH IRAJ IPOKHREL 15

iproposed iproject. iThe ieconomic ifeasibility iincludes:

• Budget iallocation ithrough isystem ianalysis.

• Tangible ibenefits: iuse iof iinformation isystem,

iincreasing ithe ispeed iof iprocessing,

AAYUSH IRAJ IPOKHREL 16

idevelopment iif iit iis inot isocially ifeasible.

ivalidating ithe isoftware iand isystem irequirements.

irequirement ianalysis ibegins. i

AAYUSH IRAJ IPOKHREL 17

ion iother iuser’s iactivity.

ireliability iand iperformance i(Eriksson, iU i2012).

AAYUSH IRAJ IPOKHREL 18

iadding ifunctional ispecification ito irun ithe iproject. i

AAYUSH IRAJ IPOKHREL 19

FIG i1: iSYSTEM iDESIGN i

AAYUSH IRAJ IPOKHREL 20

FIG i2: iERD iDIAGRAM

C) USE ICASE IDIAGRAM

AAYUSH IRAJ IPOKHREL 21

FIG i3: iADMIN iUSECASE

AAYUSH IRAJ IPOKHREL 22

FIG i4: iUSER iUSECASE

AAYUSH IRAJ IPOKHREL 23

isection iin ithe isite. i

ideleting iusers, ipost, iand iactivities. i i i

AAYUSH IRAJ IPOKHREL 24