Bl oodBank
ThisProjectreporthasbeensubmittedinfulfillmentoftherequirementsforthe DegreeofBachelorofScienceinSoftwareEngineering.
`
Submi t t edBy
AbdulQuddus I D:161-35-1396
Supper vi sedBy Md.Habi burRahman
Lect ur er
Depar t mentofSoft war eEngi neer i ng
Daffodi lI nt er nat i onalUni ver si t y
APPROVAL( forRoom- 404 )
ThisProject/Thesistitled“BloodBank”,submittedbyAbdulQuddus,161-35-1396to theDepartmentofSoftwareEngineering,DaffodilInternationalUniversityhasbeen acceptedassatisfactoryforthepartialfulfillmentoftherequirementsforthedegree ofB.ScinSoftwareEngineeringandapprovedastoitsstyleandcontents.
BOARDOFEXAMINERS
----------------------------------------------- Dr.TouhidBhuiyan
ProfessorandHead
DepartmentofSoftwareEngineering
FacultyofScienceandInformationTechnology DaffodilInternationalUniversity
Chairman
----------------------------------------------- Dr.Md.AsrafAli
AssociateProfessor
DepartmentofSoftwareEngineering
FacultyofScienceandInformationTechnology DaffodilInternationalUniversity
InternalExaminer1
----------------------------------------------- AsifKhanShakir
Lecturer
DepartmentofSoftwareEngineering
FacultyofScienceandInformationTechnology DaffodilInternationalUniversity
InternalExaminer2
----------------------------------------------- ProfDr.MohammadAbulKashem Professor
DepartmentofComputerScienceandEngineering FacultyofElectricalandElectronicEngineering
DhakaUniversityofEngineering&Technology,Gazipur
ExternalExaminer
Decl ar er at i on
IherebydeclarethatIhavetakenthisprojectunderthesupervissionofHabibur Rahman,SniorLecturer,DepartmentofSoftwareEngineering,DaffodilInternational University.Ialsodeclearethatneitherthisprojectnoranypartofthisreporthas beensubmittedelsewhereforanydegreeoraward.
--------------------------------------------------------- SubmittedBy:
AbdulQuddus 161-35-1396
DepartmentofSoftwareEngineering DaffodilInternationalUniversity.
--------------------------------------------------------- CertifiedBy:
HabiburRahman SeniorLecturer,
DepartmentofSoftwareEngineering DaffodilInternationalUniversity.
A CKNOWLEDGEMENT
Mostimportantly,IofferourthankstotheAlmightyAllahforenablingustofinish thisProject.Iam likewiseappreciativetomyfolkswhoconsistentlybolstermeand empoweraccomplishingsomethingforhumanity.PresentlyImightwanttoofferthe thanksandthankfulnesstoeveryoneoftheindividualswhogavemethelikelihood to make my venture,venture documentation progressively successfuland furthermorefinished.A uniquegratitudetomydirectorandourdecentTeacher
"HabiburRahman",whosehelp,recreationandsupport,helpedmetoorganizemy ventureparticularlycomposingthisdocumentation.
Aspecialthankgoestomyfriend“Shuvo”,whohelpmetoassemblethepartsand gavesuggestiontomakemyprojectindifferentprocesses.
From mysincerethankstofriendswhohavesupportedmyworkontheproject. Specially,DaffodilInternationalUniversity’sfamilymembers,friendsandbrothers, kawser,shuvo,MuktadirSoyebandalsoSirfortheirvaluableandimportantideas.
Finally,Iwouldliketothankmyfamilyandfriendfortheirsupport.Iwouldn’thave beenabletogetherewithoutthem.
AbdulQuddus
Departmentofsoftwareengineering DaffodilInternationalUniversity
A BSTRACT
BloodBankisusedwidelyinanysituationwhereanyoneneedstocontactorfindthe Donor.Thissystem isonlinebase,so,anyonecanfindthedonorthroughinternet. Thisproject’sperspective,Iwouldhavegivenanameandthat’s“BloodBank”.Using thisapplicationseekercanviewthepost,createpost,viewnotification,andsearch.
T ABLEOFCONTAI NS
Cont ent s
Approval……….....ii Declareration……….iii
Acknowledgement vi
Abstract v
Tableofcontains vi
Listoffigure ix
ListOfTable ix
1 Introduction
1
1.1 Overview 1
1.2Purpose 2
1.3Background 2
1.4Objectives 2
1.5Stakeholder 2
1.6ProposedSystem 3
1.7Systemprocess: 4
1.8PROJECTPLAN: 5
1.8.1 GanttChart 5
1.8.2 Risk: 5
1.8.3 Milestones: 5
2 SoftwareRequirementsSpecification 7
2.1 FUNCTIONALREQUIREMENT: 7
2.1.1 DONORREGISTRATION: 7
2.1.2 SEEKERREGISTRATION: 7
2.1.3 LOGIN 8
2.1.4 CREATEPOST: 8
2.1.5 VIEW NOTIFICATION: 8
2.1.6 VIEW PROFILE: 9
2.1.7 ACCEPT,REJECTANDREPLYREQUEST: 9
2.2 PERFORMANCEREQUIREMENTS: 9
2.2.1 SPEEDANDLATENCYREQUIREMENTS: 9 2.2.2 LEGIBILITYANDACCURACYREQUIREMENTS: 10
2.2.3 CAPACITYREQUIREMENTS 10
2.3 DEPENDABILITYREQUIREMENTS: 11 2.3.1 RELIABILITYANDAVAILABILITY: 11 2.3.2 Safetycriticalrequirements: 11 2.4 MAINTAINABILITYANDSUPPORTABILITY: 11 2.4.1 SUPPORTABILITYREQUIREMENTSSPECIFICATION: 11 2.4.2 Adaptabilityrequirements: 12 2.5 Securityrequirements: 12
2.5.1 Accessrequirements: 12
2.5.2 Integrityrequirements: 12 2.6 Usabilityandhumanintegrityrequirements 12
3.1 UseCaseDiagram: 14
3.1.1 Donor 15
3.2 UseCaseDiagram: 16
3.2.1 BloodSeeker: 17
3.3 ActivityDiagram 18
3.3.1 System Activity 18
3.3.3 CreatePostActivity 20
3.4 SequenceDiagram: 21
3.4.1 BLOODSEEKERSEQUENCEDIAGRAM 21
3.4.2 DONORSEQUENCEDIAGRAM: 22
4. Technology&Tools 24
4.1 UserInterfaceTechnology: 24
4.2 Technology 24
4.3 Tools: 24
4.4 ERD: 25
4.5 SchemaDiagram 26
5. Implementation
27 5.1 Hardware&SoftwareSpecifications 27
5.2 UIIMPLEMENTATION 28
5.2.3 LOGIN: 31
6. Testing
33
6.1 TestingStrategy: 33
6.2 Testapproach: 33
6.6 Pass/FailCriteria 34
6.7 TestingEnvironment 35
6.8Testcase: 35 6.8.2 TestCaseforBloodSeekerRegistration: 38
6.8.3 TestCaseforDonorLogin: 39
6.8.4 TestCaseforDonorLoginfailed: 40 6.8.5 TestCaseforBloodSeekerLogin: 41 6.8.6 TestCaseforBloodSeekerLoginFailed: 42 6.8.7 TestCaseforCreatePost: 43 6.8.8 TestCaseforBloodSeekerCreatePostfailed: 44
6.9 TestReport 45
7 Conclusion
46
7.1 ProjectSummary: 46
7.2 Limitations: 46
FutureImprovement 47
9 Appendix
48
L I STOFFI GURE
Fig1.1:ProposesystemModel……….. 03
Fig1.2:SystemProposeModel………. 04
Fig1.3:GanttChart……… 05
Fig1.4:ProjectSummary……….................................................. 06
Fig3.1:UseCaseDiagram forDonor……… 16
Fig3.2:UseCaseDiagram forBloodSeeker……… 18
Fig3.3.1:SystemActivitydiagram……… 20
Fig3.3.2:RegistrationActivityDiagram………................... 21
Fig3.3.3:CreatePost………... 22
Fig3.4.1:BloodSeekerSequenceDiagram………. 23
Fig3.4.2:BloodDonorSequenceDiagram………. 24
Fig4.1:Entityrelationshipdiagram………. 27
Fig4.2:SchemaDiagram………. 28
Fig5.2.1:Homepage……… 30
Fig5.2.2:RegistrationPageDonor……….. 31
Fig5.2.3:RegistrationpageBloodseeker………. 32
Fig5.2.4:Login………................................................................. 33
Fig5.2.5:CreatePost………. 34
L I ST O F T ABLE
Table2.1.1:DonorRegistrationDescription………............. 09
Table2.1.2:BloodseekerRegistrationDescription…………...………... 09
Table2.1.3:LoginDescription………..……….. 10
Table2.1.4:CreatePostDescription………..………............................. 10
Table2.1.5:ViewNotification………................... 10
Table2.1.6:ViewProfileDescription……….............. 11
Table2.1.7:Accept,Reject,ReplyRequestDescription…….……….. 11
Table2.2.1:Speed&LatencyRequirement……….………... 11
Table2.2.1:Legibility&AccuracyRequirement………..……… 12
Table2.2.3:CapacityRequirement………......................... 12
Table2.3.1:Reliability&Availability………............................ 13
Table3.1.1:UseCaseDescriptionforDonor………................................... 17
Table3.2.1:UseCaseDescriptionforBloodSeeker……….......................... 19
Table6.8.1:TestcaseforDonorRegistration………........................ 35
Table6.8.2:TestcaseSendforBloodSeekerRegistration………....................... 36
Table6.8.3:TestCaseDonorLoginsuccessfully……….............................. 38
Table6.1.4:TestCaseDonorLoginFailed……….............................. 39
Table6.1.5:TestCaseBloodSeekerLoginSuccessfully………. 40
Table6.8.6:TestCaseBloodSeekerLoginfailed……….............................. 41
Table6.8.7:TestCaseCreatePostsuccessfully………................................... 42 Table6.8.8:TestCasecreatepostfailed………….……….............................. 43 Table6.9.1:TestReport……….. 44
Chapt er - 1
I nt r oduct i on
1I NTRODUCTI ON
1. 1 O
VERVIEWThisframeworkiscompletelyonline-based.Benefactordataisrecordedinthe ontheweb.Priortoontheweb,wehavetorecordbenefactordatainthepaper -likeregisterbook,structureandalldataarecomposedbyhand.Inthisway,it isso hard to keep up with contributordata.We additionallydiscovera contributorthroughaBloodBank.Subsequently,afewpeopleexploitthissite.
IneedtobreakthisframeworkandIneedtosimple,botherfreediscover benefactorframework.Normally,wesaw thatindividualsaretowardstoa greatextentforlookingthroughBloodifthereshouldariseanoccurrenceof crisis.
Thisframeworkrecordsthegiverdatathatneedstogivebloodforhumankind.
Byutilizingthisframework,asearcherwhofinedthegiverforhis/hercrisiscan enlisttotheframeworkandmakeapostforthenormalBloodGroupwiththe area.Atthatpoint,theframeworksendsawarningtothewholegiverwhohas thatbloodbunchinthatareatogivebloodthatindividual.Atthepointwhen thebenefactoracknowledgesthesolicitation,theframeworksendsthegiver name,Contactdatatothebloodsearcher.
1. 2Pur pose
Online Blood BankRecords Donorinformation so thatanyone can find donor accordingto theBloodgroupandlocation.So,wecandefinethepurposefor DonationBloodformankind.
1. 3Backgr ound
AsnormalBloodBankrecordsitsDonordatainaRegisterbook,paper,andsoforth subsequently,itishardtodiscoveraDonoreffectively.Itisadditionallyhardtokeep upThesepaperbooks.Otherthanthese,agatheringofindividualsexploitsthissite.
Inthisway,Ineedtodevelopthisframeworkcompletelyhumankindwiththegoalthat individualscanwithoutmuchofastretchtodiscovertheDonorattheircrisistime.
TheDonoradditionallygivetheirBloodastheidealspotwiththeirfulfillment.
1. 4Obj ect i ves
EasytocommunicationwithDonor.
SeekercaneasilyfindtheDonor.
Donorcannoticewhen,wherehe/sheDonateBlood.
SeekercanfindDonorintherightplace.
DonorcanmanageBloodDonationRequest.
Easytouse.
1. 5St akehol der
Therearemanymembersassociatewiththisproject.Theyhavehelpedtodevelop thesystem directlyorindirectly.
InternalStakeholders:
1.Admin 2.Donor 3.Seeker
ExternalStakeholders:
1.Patient. 2.Visitor.
1. 6Pr oposedSyst em
TodevelopthisOnlineBloodBank,Iproposedamodelforthissystem.Iclearthe system brieflyhere.
Figure-1.1:ProposeSystem Model
Inthisframework,anybodycanenlistasaDonorwhoneedtoDonateBloodfor humankind.WhoneedstoenlistasaDonor,firsthe/shegivehis/herdata.After register,acontributorcanseehis/herprofilethroughaloginutilizingtheclientname andsecretkey.AnyindividualwhoneedstoBloodadditionallyshouldenlistasa searcher.Atthatpoint,theindividualcanmakeapostforBlood.Thesearchercan seethewarningadditionallythatthegiverreaction.
1. 7Syst em pr ocess:
Figure1.2:System ProcessModel
Usingthissystem anyonecanregistrationasadonororbloodseeker.Donor canviewprofile,handlerequest,login.Bloodseekercancreatepostforblood, viewnotificationetc.
1. 8PROJECTPLAN:
Tofullfilltherequirementsandcompletetheprojecttheattherighttime,project schedulehelpsforproperplanning.Ialsomakeaprojectscheduletocompletemy projectproperly.
1. 8. 1Gant tChar t
Inprojectplanning,IuseGanttcharttomanagemyprojectproperly.Tousethistools, Icantrackallthetaskwhichisnotdoneornot.Alsotrackwhichoneisschedulefor thenexttask.Icontrolmyprojectdurationbythistools.
1. 8. 2Ri sk:
InGanttcharttools,Ishowtheprojectduration.Itook25daysfordeveloping,sothatIcould mitigatemyrisk.Indevelopingpage,Ifindoutariskthatriskisdeveloper.Whomaysickor leave.
1. 8. 3Mi l est ones:
Milestones,atimeframeofaproject,willdefinethetask.Theseprojectmilestones areasfollows:
TaskNo TaskName Duration
01 Planning 14days
02 Requirementgathering&Analysis 13Days
03 System Design 14Days
04 Development 25Days
05 Testing 7Days
06 Implementation 7Days
07 Relies 5Days
Total 85Days
Chapt er - 2
Requi r ementSpeci fi cat i on
2S OFTWARE R EQUI REMENTS S PECI FI CATI ON
Requirementsanalysisistheprocessofidentifyingtheusersatisfactionform the System.So,Requirementsanalysisisanimportantpartofprojectmanagement. WhenIselectedthisprojectIthoughtaboutsomespecificSoftware requirement, likeas…
Whoisthestakeholderofthissystem?
Isithelpfulforthemornot?
Functional&Non-functionalrequirements
Maintenanceofthesystem
2. 1 FUNCTI ONALREQUI REMENT:
Thefunctionalrequirementsofthesystemarelikebelow---
2. 1. 1DONORREGI STRATI ON:
FR-01 DonorRegistration
Description InthisSystem,therearenumerousclientslikeasearcher,guests, andsoforth.Bethatasitmay,theDonorenrollmentpageisjust forthoseindividualswhoneedtogiveBloodforhumanityandhelp theindividuals.ThispagehasrequiredsomedatalikeasNIDNo, Phone No,and so on and store the information as a bitof
contributordata.
Stakeholder BloodDonor.
2. 1. 2SEEKERREGI STRATI ON:
FR-02 SeekerRegistration
Description InthisSystem,therearenumerousclientslikeasearcher,guests, andsoforth.ButSeekerregistrationpageisonlyforthoseperson who search Blood for patient.This page is required some informationlikeasName,PhoneNoetcandstorethedateasa Seekerinformation.
Stakeholder Bloodseeker,patient,Anyonewho’sneedBlood.
2. 1. 3LOGI N
FR-03 Login
Description Inthissystem therearemanyuserslikeseeker,visitor,Donoretc.
ButDonorandBloodseekercanloginaftercompleteRegistration.
Stakeholder BloodDonor,Seeker.
2. 1. 4CREATEPOST:
FR-04 CreatePost
Description Inthissystem onlyseekercancreatepost.Tocreateapostfor Blood,apersonshouldhaveregisteredasaseeker.Hospitalname, Location,BloodGroup,phone,Date,Timearemusttocreateapost forBlood.
Stakeholder BloodDonor,Seeker,patient.
2. 1. 5VI EW NOTI FI CATI ON:
FR-05 ViewNotification
Description BothDonorandSeekercanview notification.Accordingtothe seekerpostdonorgetanotificationtohelpthepatientbydonating Blood.Ifthedonorresponsethenotification,thenseekergetdonor informationnotification.
Stakeholder BloodDonor,Seeker.
2. 1. 6VI EW PROFI LE:
FR-06 ViewProfile
Description Donorcanviewhis/herProfile.Seekercanseenotification.
Stakeholder BloodDonor,Seeker.
2.1.7 ACCEPT,REJECTANDREPLYREQUEST:
FR-07 Accept,Rejectandreplyrequest
Description DonorcanAccept,Rejectrequestagainstthenotification.Seeker canseenotification.
Stakeholder BloodDonor.
2. 2 PERFORMANCEREQUI REMENTS:
It’sverynecessarytosustaintheperformanceoftheproject.Toassurethebetter performance,thisprojecthastomeetsomerequirementswhichwillprovidethe betterperformance.
2. 2. 1SPEEDANDLATENCYREQUI REMENTS:
Whileinsertingorviewingthesystem inthebrowser,system needaminimum amountofspeedtoperformthetask.
SLR-01 Thesystem willbefaster
Description Whentheuserbrowsing,itdependsontheirinternetspeed.Italso dependsonserverbandwidthspeed.
Stakeholders Donor,Bloodseeker,visitor.
2. 2. 2LEGI BI LI TYANDACCURACYREQUI REMENTS:
System havetoconfirm theLegibilityandAccuracyofthedata.
LAR-01 Dataaccuracy
Description Theinputdatashouldbecorrectandrightpatterndata,otherwise theinputinformationneversave.LikeNIDNo,Phoneetctheinput informationisnotvalid,thedataneversave.Ortheinputdata patternisnotmatch,thesystemneversavesoracceptthedata.
Stakeholders Donor,Bloodseeker.
2. 2. 3CAPACI TYREQUI REMENTS
Thesystemshouldmaintaintheallinsertingdata.
CR-01 Managethealldataindatabasesystem.
Description AllregistrationdatalikeDonorregistrationdata,Bloodseeker registrationdata,Postinformationarestoreinthedatabasein rightformat.
Stakeholders Donor,Bloodseeker.
2. 3 DEPENDABI LI TYREQUI REMENTS:
Dependabilitymeans,itmeasuresofasystemavailability,reliability,securityetc.Here, dependabilitymeanstherunningtimeofthisproject.
2. 3. 1RELI ABI LI TYANDAVAI LABI LI TY:
RA-01 Thesystem mustbeavailable24x7 Description It’savailable24hoursinaday
Thesystemmustbeupdatedregularly
Stakeholders Donor,Bloodseeker,visitor,patient.
2. 3. 2S
AFETYCRITICALREQUIREMENTS:
Therearenospecificsafetycriticalrequirements.
2. 4
MAINTAINABILITYANDSUPPORTABILITY:ForMaintenanceThesystem andsupportthesystem,somepeopleassociatethe project.
2. 4. 1SUPPORTABI LI TYREQUI REMENTSSPECI FI CATI ON:
SRS-1.Tounderstandthesystem'sbehavioronatechnicalsupportisrequired bythesystem operator.Thereasonforreadingthem mightbe
SRS-2.System malfunctionhasoccurredandthesystem operatorhastofind theexactpointoftimewhenthishappened
SRS-3.System produceswrongresultsandthedevelopersmustbeableto reproducethedataflowthroughthesystem
SRS-4.Hackertriedtobreachthesystem'ssecuritymechanismsandthe system operatormustunderstandwhathedid.
2. 4. 2A
DAPTABILITYREQUIREMENTS:
TherearenospecificadaptabilityRequirements.
2. 5 S
ECURITYREQUIREMENTS:
SR-1.LoginasaDonor
SR-2.LoginasaBloodseeker
Togetaccesstothissystem oraspecificmodulethesystem mustprovidean authentication mechanism.To preventanyone to exploitstolen Data alluser’s passwordmustbeencryptedinhashprocess.
2. 5. 1A
CCESSREQUIREMENTS:
Thissystem providesaccessesthedifferentmodule,byaccesstheauthentication waytheauthenticuser.
2. 5. 2I
NTEGRITYREQUIREMENTS:
Topreventcredentialsinformationofuserfrom beingstolen,allpasswordsare storedinencryptedform.TheRequirementssignificantlyreducesthevalueofstolen usercredentials,it’snoteasytodecryptthepassword.
2. 6 U
SABILITYANDHUMANINTEGRITYREQUIREMENTSThissystem easytouseandallofthepeoplewhowantstodonatebloodandwho needblood.
2. 7Dat aVal i dat i on
InthisstageIhavetrytovalidatealmostallinputfield
2. 8UserI nt er faceDesi gn
Itisimportanttoconsultthesystem usersandtheirnecessitieswhiledesigningthe userinterface.
Chapt er - 3
Requi r ement sAnal ysi s
3. 1 UseCaseDi agr am:
Inthissystem auser(Donor)whatthingshe/shecando,isdescribeinthispicture thatprovideinbelow.ADonorcanlogininthesystem.Butbeforeloginhe/shemust registrationinthissystemasaBloodDonor.Thanhe/shecanaccesstheloginoption.
DonoralsoviewBlooddonationrequest,profileetc.Donoralsohandletherequest.
Figure-3.1:Use-CaseDiagram user(Donor)
3. 1. 1Donor
UseCaseTitle Donor
Goal InsertDonorInformationtothedatabase.
Precondition UsermustNIDNo,Phone.
Success&EndCondition System storetheDonorinformation.
FailedEndCondition Databasecan’tstorethedata.
PrimaryActors:
SecondaryActors:
Donor
Tigger DonorRegistration
Description WhowanttoDonateBloodismustto registrationinthesystem inserthis/her information.
AlternativeFlows N/A QualityRequirements N/A
3. 2 UseCaseDi agr am:
Abloodsearcher,whatelectivethathe/shecangettoorcandobythisstructureis depictedinthispictureshowedaspursues.Abloodsearchercanmakeapost.Inany case,tomakeapostforblood,he/sheshouldsignintothissystem.Tosignintothis system,he/sheoughttobetakenacrackatthisstructure.Searchercanseepost- response,search.
Figure-3.2:Use-CaseDiagram user(Bloodseeker)
3. 2. 1
BloodSeeker:UseCaseTitle BloodSeeker
Goal InsertBloodSeekerInformationtothedatabase.
Precondition UsermusthaveaPhonenumber.
Success&EndCondition System storetheDonorinformation.
FailedEndCondition Databasecan’tstorethedata.
PrimaryActors:
SecondaryActors:
BloodSeeker
Tigger Bloodseekerregistration,Createpost Description TosearchBloodinthespecificlocationand
createapostforBlood,aBloodseekermustbe registrationinthesystem.
AlternativeFlows N/A QualityRequirements N/A
3. 3 Act i vi t yDi agr am
Followingactivitydiagramsareexactlydescribingtheflow ofthedifferentstateof theproject.
3. 3. 1 Syst em Act i vi t y
BythisfigureIexplainmysystem.Ifanyoneenterthesystem,he/sheseetheallthe
option.Andwhoareregistereduserandhe/shecanlogininthesystem.Afterlogin criteriahe/shecanaccessdifferentoption.
Figure-3.3.1:System Activity
3. 3. 2Regi st r at i onAct i vi t y
BythisfigureIexplainRegistrationprocess.Ifanyoneenterthesystem,he/shesee thealltheoption.Andwhoarewanttoregistration,he/shemightdofollowthe instruction.Aftersuccessfulregistrationhe/shecanlogininthesystem andaccess differentoption.
Figure-3.3.2:RegistrationActivity
3. 3. 3Cr eat ePostAct i vi t y
InthisfigureIshowthecreatepostprocess.Ifanyoneenterthesystem,he/shesee thealltheoption.Andwhoareregistereduserasaseeker,he/shecanlogininthe
Figure-3.3.3:CreatePostActivity
3. 4 SequenceDi agr am:
SequenceDiagramshowtheprocessinsequentialwaythatit’sactordone.
3. 4. 1BLOODSEEKERSEQUENCEDI AGRAM
InthispicturedescribetheBloodseekerworksequencesystem todatabase.Ablood seekercanrequestforregistration,login,createpost,viewnotificationandallthese 1stgotothesystem thancheckindatabase.Iftherequestisvalidthansystem get confirmationandsystemconfirmtheseeker.
Figure-3.4.1:BloodSeekerSequenceDiagram
3. 4. 2DONORSEQUENCEDI AGRAM:
InthisimagedepicttheBloodDonorworkarrangementframeworktothedatabase.A
bloodDonorcandemandforenrollment,login,makeapost,seewarning,seeprofile, andallthesefirstgototheframeworkthanregistrationdatabase.Ontheoffchance thatthe solicitation islegitimate than the frameworkgetsaffirmation and the frameworkaffirmsthesearcher.
Figure-3.4.2:BloodSeekerSequenceDiagram
Chapt er4
Desi gnandDevel opment
4.Technol ogy&Tool s
Fordevelopingthisproject,Ihaveusedsometoolsandtechnologythat’saretalking
4. 1 UserI nt er faceTechnol ogy:
Userinterface (UI)is everything designed into a system view thata person’s associateswiththissystemmayliketheinterfaceofthissystem.
4. 2 T
ECHNOLOGY Programminglanguage:Php
Webserver:Apache
Design:html,CSS,bootstrap,JavaScript,Ajax
Databaseserver:MySQLServer
4. 3 T
OOLS:
Xaamp
SQLServerManagement
Windows10
4. 4 ERD:
Thisfigureshowsthedatabaseconnection.DonorInfotableandBloodGrouptableis balancedrelationship.SinceOneDonorhasoneBloodGroup.Searchertableand Bloodbunchtableadditionallycoordinatedrelationship,sinceonesearchercanpost justforonebloodgathering.Thegiverandclienttablearecoordinatedconnectionsin lightofthefactthatNIDdatajustasinglecontributoranditisaoneofakindnumber. Giverand warning table one such a large numberofconnections since one benefactorcangetmorethanonenotice.Sameaswarningandsearcher.
Figure-4.1:ERDiagram (Physical)
4. 5 SchemaDi agr am
ThisDiagramdescribetherelationshipsamongthetables.
Figure-4.2:SchemaDiagram
5. I MPLEMENTATI ON
5. 1 H
ARDWARE&S
OFTWARES
PECIFICATIONSInthisstageIwanttodescribewhat’sneedtobuildthisapplication.
HardwareRequirements:
PROCESSOR:DualCoreorabove
RAM:2GBorabove
CacheMemory:2MBorabove
HDD:20GBorabove
SoftwareRequirements:
IDE:PHP
Database:MySQLServerManagement.
Web-Server:Apache
5. 2 UII MPLEMENTATI ON
5.2.1 Homepage
NowIam showinghomepageofmyapplication.Inhomepageanyonecan view.
Figure5.2.1:Homepage
5.2.2 Registrationpage:
BloodseekerandDonorregistrationform toaccessthesystem.
Figure5.2.2:Registrationpage
5.2.3 Contactpage:
BloodseekercancontactwithBloodDonor.
Figure5.2.3:Contactpage
5. 2. 4LOGI N:
DonorandBloodseekercanlogininthesystem.
Figure5.2.4:Loginpage
5.2.5 CREATEPOST:
UsercancreatepostforBlood.Thefilltheform andpostit.
Figure5.2.5:CreatePost
6. T ESTI NG
Thetestingoftheproductwasdoneinafullmanualend-clientinformationstream testing style.Because ofthe inaccessibility oftestgiving stage,mechanized programming inferred testing couldn'tbe performed.The testing approach is describedhereprecludingthespecializedsubtleties.
Twonormalkindsoftestingarediscoverytryingandwhiteboxtesting.Discovery testingisadditionallycalledpracticaltesting.Inthisstage,wetestjustusefulness, info,andyield.Whiteboxtestingisstructureleveltesting.Forthisundertaking,Ihave utilizedthediscoverytestingtechnique.
6. 1 Test i ngSt r at egy:
Atestingstrategyisageneralapproachtothetestingprocessratherthanamethod ofdevisingparticularsystem orcomponenttests.Differenttestingstrategiesmaybe adopteddependingonthetypeofsystem tobetestedandthedevelopmentprocess used.
6. 2 Testappr oach:
Atestapproachistheteststrategyimplementationofaproject,defineshowtesting wouldbecarriedout.Testapproachhastwotechniques:
Proactive-Anapproachinwhichthetestdesignprocessisinitiatedasearlyas possibleinordertofindandfixthedefectsbeforethebuildiscreated.
Reactive-Anapproachinwhichthetestingisnotstarteduntilafterdesignand codingarecompleted.
6. 3 Bl ackBoxTest i ng
Blackboxtestingalsocalledfunctionaltestingthatignorestheinternalmechanism ofa
system orcomponentandfocusesontheoutputsgeneratedinresponsetoselectedinputs andexecutionconditions.Wehavedecidedtoperform equivalencepartitioningandBoundary valueanalysisforthissystem.
6. 4 Equi val enceCl assPar t i t i oni ng
Inconsideringthecontributionsforourproportionalitytesting,theaccompanying kinds willbe utilized:LegalInputesteems:Testesteems inside limits ofthe determinationcomparabilityclasses.Thiswillbeinputinformationtheprogram expectsandismodifiedtochangeintousablequalities.IllicitInputValues:Test identicalnessclassesoutsidethelimitsofthedetail.Thiswillbeinputinformationthe programmightbeexhibited,howeverthatwon'tcreateanysignificantyield.
6. 5 Whi t eBoxTest i ng
Whiteboxtestingisaproducttestingstrategyinwhichtheinnerstructure/usageof thethingbeingtriedisknowntotheanalyzer.Theanalyzerpickscontributionsto practicewaysthroughthecodeanddecidestheproperyields.Programmingknow- howandtheexecutionofinformationisbasic.
6. 6 Pass/Fai lCr i t er i a
Theentrancecriteriaforeachphaseoftestingmustbemetbeforethenextphase cancommence.Nowthecriteriaforpassandfailaregivenbelow.
Accordingtothegivenscenariotheexpectedresultneedtotakeplacethenthe scenariowillbeconsideredaspassotherwisethatcriteriashouldbefailed.
Ifanitem tested10times,9timesperfectlyworkedandsingletimedonot
