Introduction to on Object Oriented Technologies and the UML Method

Introduction to on Object Oriented
Technologies and the UML Method

1. Introduction to on Object Oriented
Technologies and the UML Method
•OOPisthemostpopularprogrammingparadigmforbuildingsoftwaresystemsinthe
ITindustry.OOPconceptbymakingacomparisonwiththeconventional
programminglanguages(e.g.C,PASCAL,COBOL,FORTRANetc.)whichusethe
Procedure-OrientedProgramming(POP)approach.
•InPOPapproach,aprogramisdividedintoanumberofcomponentscalledfunctions,
whileinOOPapproach(e.g.C++,Java,Python,Rubyetc.);theprogramisdivided
intocomponentscalledobjects.Anotherpointisthatobject-orientedprogramming
followsthe“bottom-up”approach,whileproceduralprogrammingfollowsthe“top-
down”approach.
•Becauseobjectsaremoreversatile,OOPcanbeusedtodevelopcomplexprograms
withlesscode.Theuseofobjectsalsofacilitatescodereuse.InPOP,thefocusis
placedonthefunctionsandsequenceofactionstobeperformedandnotondata.In
OOP,however,thefocusisplacedonthedataandnotthefunctions.Thatiswhy
object-orientedprogrammingapproachcanprovideamorerealisticviewofa
softwaresystem.

2. Essential features of OOP
♦Encapsulation:Thisisanimportantconceptthatbindstogetherthe
dataandfunctionsthatmanipulatethedata,andthatkeepsbothsafe
fromoutsideinterferenceandmisuse.EncapsulationledtotheOOP
conceptofdatahiding.
♦Inheritance:Itistheprocedurebywhichoneobjectacquiresthe
propertiesofanotherobject.Thisincreasescodere-usability.
♦Polymorphism:Thisconceptenablesoneentitytobeusedasgeneral
categoryfordifferenttypesofactions.Thespecificactionisdetermined
bytheexactnatureofthesituation.Theconceptofpolymorphismcan
beexplainedas“oneinterface,multiplemethods”.

3. Basics of UML
•TheUMLstandsforUnifiedmodelinglanguage,isastandardized
general-purposevisualmodelinglanguageinthefieldofSoftware
Engineering.Itisusedforspecifying,visualizing,constructing,and
documentingtheprimaryartifactsofthesoftwaresystem.Ithelpsin
designingandcharacterizing,especiallythosesoftwaresystemsthat
incorporatetheconceptofObjectorientation.Itdescribestheworking
ofboththesoftwareandhardwaresystems
•UnifiedModelingLanguage(UML)isastandardnotationfor
modelingreal-worldobjectsasafirststepindesigninganobject-
orientedsystem.

4. •TheUMLoffersastandardwaytowriteasystem’sblueprints,
includingconceptualthingssuchasbusinessprocessesandsystem
functionsaswellasconcretethingssuchasprogramminglanguage
statements,databaseschemas,andreusablesoftwarecomponents.”
•TheimportantpointtonotehereisthatUMLisa‘language’for
specifyingandnotamethodorprocedure.TheUMLisusedtodefine
asoftwaresystem;todetailtheartifactsinthesystem,todocument
andconstruct–itisthelanguagethattheblueprintiswrittenin.The
UMLmaybeusedinavarietyofwaystosupportaSoftware
DevelopmentMethodology(suchastheRationalUnifiedProcess)–
butinitselfitdoesnotspecifythatmethodologyorprocess.

5. •TheUMLrepresentsacollectionofbestengineeringpracticesthat
haveprovensuccessfulinthemodelingoflargeandcomplexsystems.
•TheUMLisaveryimportantpartofdevelopingobjectsoriented
softwareandthesoftwaredevelopmentprocess.
•TheUMLusesmostlygraphicalnotationstoexpressthedesignof
softwareprojects.
•UsingtheUMLhelpsprojectteamscommunicate,explorepotential
designs,andvalidatethearchitecturaldesignofthesoftware.

6. Goals of UML
•TheprimarygoalsinthedesignoftheUMLare:
•Provideuserswithaready-to-use,expressivevisualmodeling
languagesotheycandevelopandexchangemeaningfulmodels.
•Provideextensibilityandspecializationmechanismstoextendthecore
concepts.
•Beindependentofparticularprogramminglanguagesand
developmentprocesses.
•Provideaformalbasisforunderstandingthemodelinglanguage.
•Encouragethegrowthofobjectorientedtoolsinthemarket.
•Supporthigher-leveldevelopmentconceptssuchascollaborations,
frameworks,patternsandcomponents.
•IntegratebestpracticesinSoftwareDevelopmentLifeCycle(SDLC).

7. Software Development Process
•Softwaredevelopmentprocessisamethodicalwaytocreateand
managesoftwarethatinvolvesseveralsteps:
•Understandwhatthesoftwareshoulddoandplanhowtobuildit
•Designhowthesoftwarewillworkandlook,followedbywritingthe
actualcode
•Conductrigoroustestingtoensureitfunctionsproperly
•Deploythesoftwaretomakeitavailableforusers
•Oncedone,performongoingmaintenancetokeepitrunningsmoothly.

8. The 7 Steps of Software Development
Process

9. 1.Analysis:UnderstandingtheRequirements
2.Planning:SettingtheFoundation
3.Design:CraftingtheDetails
4.Development:WritingtheCode
5.Testing:EnsuringItWorks
6.Deployment:ReleasingtotheWorld
7.Maintenance:KeepingItRunning

10. The Waterfall Model vs. The Spiral Model
WaterfallandSpiral modelsare two of the most famous
and widely utilized project management models in
software development. These are the process models
that are utilized to create software in a well-defined,
systematic, and cost-effective manner.

11. Waterfall Model
•Thewaterfallmodelisasoftwaredevelopmentprocessmodel.
•itisastructuredandsequentialprojectmanagementapproachthatcanbeuseful
fordevelopmentprojectswithwell-definedrequirementsandclientswhoare
unlikelytochangetheprojectscope.thatfollowsalinearsequentialflow.Itisa
traditionalparadigmforthesoftwarelifecycle.Asthenameimplies,theflowof
themodelissequential,whichiscomparabletoawaterfallinatop-down
approach,whichiswhyitisalsoknownasthelinearsequentialmodel.
•Although,ifanyphaseofthemodelhasbeencompleted,wecannotchangeit,
whichimpliesthatwhateverisdoneintheearlierphasecouldbealtered.The
processflowcannotpassfrombottomtotop,anditalwaysflowsfromtopto
bottom,whichmakesitcriticaltobefullypreplannedtominimizethechancesof
productfailure.Ithasseveralstages:requirementanalysis,design,coding,
testing,integration,implementation/deployment,andmaintenance.

12. Phases of waterfall model

13. 1.FeasibilityStudy
•ItisthefirstphaseofSDLC.Inthisphase,thecostandbenefitsare
assessedoftheproposedapplication.Thefeasibilityanalysismust
generateadocumentthatincludesthefollowinginformation:issue
description,technicalandeconomicviability,alternatesolutions,
requiredresources,cost,anddeliverydates.
2.Requirementsgatheringandanalysis
•Itincludesgatheringneedsfromstakeholdersandanalyzingthemto
understandtheproject'sscopeandgoals.Itdecidestheproject's
qualityintermsofeaseofuse,performance,functionality,portability,
etc.TheSoftwareRequirementSpecification(SRS)document
includesathoroughstatementoftheissue,alikelysubstituteanswerto
theproblem,afunctionalrequirementofthesoftwaresystem,and
limitationsonthesoftwaresystem.

14. 3.Design
•Itisamulti-stepprocessthatfocusesonfouraspectsofaprogram,
includinginterfacerepresentations,softwarearchitecture,data
structure,andalgorithmicdetails.Thedesignphasetransformsthe
prerequisitespecificationintoasoftwarerepresentationthatmaybe
evaluatedpriortothecodingphase.
4.Implementation
•Itcontainscodingthesoftwareinaccordancewiththedesign
necessitates.Inthisphase,unittestingisalsoutilizedtocheckthat
everycomponentofthesoftwareisfunctioningproperly.

15. 5.IntegrationandSystemTesting
•Itcombinesthesoftwaremodulesinasystematicandplannedway.
Theintegrationofthecomponentscannotbecompletedinasingle
stepbutratherrequiresseveraliterations.Furthermore,systemtesting
isperformedtoensurethatthesoftwaresystemfunctionsasstatedin
theSRSdocument.Therearethreephasesofsystemtesting:alpha,
beta,andacceptance.
6.DeploymentandMaintenance
•Oncethesoftwarehasbeentestedandauthorized,itisdeployedtothe
productionenvironment.Afterthesoftwareisdelivered,itisanalyzed
foraperiodoftimetofindandresolvetheerrorsthatdonotappearin
thestartingphasesofsoftware,whichisknownasmaintenance

16. Advantages and Disadvantages of the Waterfall Model
•TherearevariousadvantagesanddisadvantagesoftheWaterfall
Model.SomeadvantagesanddisadvantagesoftheWaterfallModelare
asfollows:
•Advantages
•TheWaterfallmodelissimpletounderstandanduse,anditisabetter
choiceforsoftwaredevelopmentprojects.
•Itfunctionswellforsmallertasksandprojectswithwell-defined
requirements.
•Itisadependableandpredictabletechniquefordevelopingsoftware.
•Itoffersaclearpictureoftheendproduct'sappearanceand
functionality.
•Itisasequential,linearstrategythatmakesitsimplertoestimatethe
timeandresourcesneededforeveryprojectphase.

17. •Disadvantages
•Itdoesnotenableend-userfeedback.
•Anewphasestartsonlyafterthepriorphasehasbeenfinished.However,it
cannotbekeptinreal-worldprojects.Phasesmayoverlaptoenhance
efficiencyanddecreasecosts.
•Itisunsuitableforcomplicatedprojectsbecauseitslinearandsequential
naturecomplicateshandlingnumerousdependenciesandinterrelated
components.
•Testingisusuallydonetowardtheendofthedevelopmentprocessinthe
WaterfallModel.Itmeansthatdefectscannotbefounduntillateinthe
developmentprocess,whichmaybecostlyandtime-consumingtoresolve.
•Itisastructuredandsequentialapproach,stakeholdersareusuallyengaged
intheinitialprojectphases(suchasrequirementsgatheringandanalysis)
butcannotbepresentinthelaterphases(suchasimplementation,testing,
anddeployment).

18. Spiral Model
•ThespiralmodelisanevolutionarymethodofSDLC,anditisa
combinationofthewaterfallmodelandtheprototypemodel.Itprovides
supportforRiskHandling.ItwasfirstreleasedbyBarryBoehmin1986.It
canapplytheiterativenessoftheprototypemodelandcontrolled
methodicalofthelinearsequentialmodeltodevelopincrementalversions
ofthesoftware.Softwarereleasesthataremadeincrementallyaretheresult
ofthespiralmodel.
•Itisarealisticmethodtodeveloplargeprojectsthathavecontinuous
enhancements,anditisquiteanexpensivemodelthanothers.Thespiral
model'smainconceptisthatyoumustplantheaimsandobjectivesofthe
projectandthencreatethesoftwarefollowingaspiral-likedirection.The
bestpartaboutthismodelisthatyoumaybeginaprojectusingitandthen
continueworkingonthesamemodellateronduringtheproject.

19. Phases of Spiral Model

20. TherearemainlyfourtypesofphasesintheSpiralModel.Thesephasesareasfollows:
•1.Planning
•Itinvolvesdeterminingtheiteration'scost,schedule,andresources.Italsoentailscomprehending
thesystem'sneedstomaintaincontinuousinteractionbetweenthesystemanalystandtheclient.
•2.RiskAnalysis
•Inthisphase,allpotentialsolutionsareassessedtopickthebestsolution.Afterthat,therisks
associatedwiththatsolutionareidentified,andtherisksarefixedutilizingthebeststrategy
available.Attheendofthisphase,theprototypeiscreatedfortheidealpossiblesolution.
•3.Engineering
•Itistheimportantphaseofthespiralmodelthatcontainscoding,testing,anddeployingsoftware
ontheclientside.
•4.Evaluation
•Riskanalysiscontainsestimating,identifying,andmonitoringtechnicalfeasibility,suchas
timetableslippageandcostoverrun.Attheconclusionofthefirstiteration,aftertestingthebuild,
theuserevaluatesthesoftwareandgivesfeedback.Thedevelopmentprocessmovesontothenext
iterationaccordingtothecustomer'srequirementandthenutilizesalinearmethodtoimplement
theuserfeedback.Thespiraliterationmethodcontinuesforthedurationofthesoftware'slife.

21. Advantages and Disadvantages of Spiral Model
•TherearevariousadvantagesanddisadvantagesoftheSpiralModel.Some
advantagesanddisadvantagesoftheSpiralModelareasfollows:
•Advantages
•Itincludesriskanalysisandmanagementateverystage,increasingsecurity
andthelikelihoodofavoidingassaultsandbreakages.Theiterative
developmentmethodalsomakeseasyriskmanagement.
•Itissuggestedforlargeandcomplicatedprojects.
•TheSpiralModeloffersanincrementalanditerativeapproachtosoftware
development.Itallowsflexibilityandadaptabilityinresponsetoshifting
requirementsorunexpectedevents.
•Itoffersregularevaluationsandreviews,whichmayenhancethe
communicationbetweentheuserandthedevelopmentteam.
•Itenablesnumerousiterationsofthesoftwaredevelopmentprocess,which
mayleadtoincreasedsoftwarequalityandreliability.

22. Disadvantages
•Itiscostlymodelthanothers,soitisunsuitableforsmallprojects.
•Itcanbecomplexbecauseitcontainsnumerousiterationsofthe
softwaredevelopmentprocess.
•Itmayberesource-intensivebecauseitnecessitatesextensive
preparation,riskanalysis,andevaluations.
•Itmaybetime-consumingbecauseitnecessitatesnumerous
assessmentsandreviews.
•ItissignificantlymorecomplexthanotherSDLCmodels.

23. Key Differences between Waterfall and Spiral
Model

24. •SomeofthemaindifferencesbetweentheWaterfallandSpiralModelsareas
follows:
•Thewaterfallmodelislinearinnature,followingastep-by-stepprocess.In
contrast,thespiralmodelisiterativeandevolutionary,repeatingthesamefour
phaseswithdifferentdegreesofcomplexitywitheveryiteration.
•Thewaterfallmodelissuitableforsmallprojectswithclearobjectives.Incontrast,
thespiralmodelissuitableforlarger,morecomplicatedprojects.
•Thewaterfallmodeldoesn'tinvolveanyclientparticipation.Incontrast,thespiral
modelseeksclientfeedbackthroughouttheprocessandprovidesaidtoensurethat
thesoftwarefulfillstheclient'srequirements.
•Thewaterfallmodelrequiresdeveloperstocollectanddetermineproject
requirementsonlyonceatthestartoftheprocessandthenmaketheirprojecttasks
onthesedecisions.Incontrast,thespiralmodelrequiresdeveloperstocollect
requirementsattheoutsetofeachiteration.
•Asthewaterfallmodelnecessitatescompletingonephasebeforebeginningthe
next,thereisnowaytoreturnandreviseworkinaphaseonceit'scomplete.On
theotherhand,thespiralmodelprovidesforarevalidationprocesswheneverthe
developerswanttoaddressanissuefromanearlieriteration.
•Thewaterfallmodelmakesthesinglefinalproductattheprocessend.Onthe
otherhand,thespiralmodelcreatesaroughfunctionalproductaftereveryphase.

25. Head-to-head comparison between Waterfall and Spiral Models

28. Conclusion
•Waterfallandspiralmodelsarethetwomainsoftwareprocessmodels
inSDLC.Thespiralmodeldiffersfromthewaterfallmodelinthatit
includesadefiniteidentificationoftherisk,whichminimizesthe
chancesofprojectfailure.Incontrast,thewaterfallisriskybecauseit
hasnoiterations,andeverythingmustbeperformedatoncefora
softwareproduct,whichmeansrequirementsmustbecollected,
planned,designed,coded,andintegratedallatonce.Thewaterfall
modelismainlyutilizedforsmallerprojectswithclearrequirements.
Incontrast,thespiralmodelismainlyutilizedforlargeand
complicatedprojects.

29. Software crisis

36. Description of the real world using the
Objects Model
•ObjectModelingTechnique(OMT)isareal-world-
basedmodelingapproachforsoftwaremodeling
anddesigning.
•Itwasdevelopedbasicallyasamethodtodevelop
object-orientedsystemsandtosupportobject-oriented
programming.Itdescribesthestaticstructureofthe
system

37. •Theobjectmodelidentifiestheclassesinthesystemandtheir
relationship,aswellastheirattributesandoperations.•Itrepresents
thestaticstructureofthesystem.•Theobjectmodelisrepresented
graphicallybyaclassdiagram.
•Objectsarekeytounderstandingobject-orientedtechnology.Look
aroundrightnowandyou'llfindmanyexamplesofreal-world
objects:yourdog,yourdesk,yourtelevisionset,yourbicycle.Real-
worldobjectssharetwocharacteristics:Theyallhavestateand
behavior.

38. •We use a rectangle to represent an object in an object
diagram.
1.Attributes and Values. Inside the object box, attributes of the
object are listed along with their specific values.
2.Attributes and Values. Inside the object box, attributes of the
object are listed along with their specific values.

60. Quality software characteristics
•Softwareis defined as a collection of computer programs, procedures,
rules, and data. Software Characteristics are classified into six major
components.Software engineeringis the process of designing,
developing, testing, and maintaining software.

65. Correctness
•Howwellthesoftwareoperateswithouterrorsandpleasestheuser

66. How well users interact with the software, which is important
for facilitating rich interactions between users and technology
Reliability
•How many failures the software has, which depends on the
number and type of mistakes made by software engineers

67. How easy it is to maintain and upgrade the software on a
regular basis

68. Softwareportabilityisadesignobjectiveforsource
codetobeeasilymadetorunondifferentplatforms.An
aidtoportabilityisthegeneralizedabstractionbetween
theapplicationlogicandsysteminterfaces.When
softwarewiththesamefunctionalityisproducedfor
severalcomputingplatforms,portabilityisthekeyissue
fordevelopmentcostreduction.
Softwareportabilitymayinvolve:
•Transferringinstalledprogramfilestoanothercomputer
ofbasicallythesamearchitecture.
•Reinstallingaprogramfromdistributionfilesonanother
computerofbasicallythesamearchitecture.
•Buildingexecutableprogramsfordifferentplatforms
fromsourcecode;thisiswhatisusuallyunderstoodby
"porting".

69. Description of the Object Oriented Analysis
process vs. the Structure Analysis Model

70. What is Structured Analysis
•StructuredAnalysisisadevelopmentmethodthatallowstheanalystto
understandthesystemanditsactivitiesinalogicalway.
•Itisasystematicapproach,whichusesgraphicaltoolsthatanalyzeand
refinetheobjectivesofanexistingsystemanddevelopanewsystem
specificationwhichcanbeeasilyunderstandablebyuser.
•Ithasfollowingattributes−
•Itisgraphicwhichspecifiesthepresentationofapplication.
•Itdividestheprocessessothatitgivesaclearpictureofsystemflow.
•Itislogicalratherthanphysicali.e.,theelementsofsystemdonotdepend
onvendororhardware.
•Itisanapproachthatworksfromhigh-leveloverviewstolower-level
details.

71. Structured Analysis Tools
During Structured Analysis, various tools and techniques are used for
system development. They are −
•Data Flow Diagrams
•Data Dictionary
•Decision Trees
•Decision Tables
•Structured English
•Pseudocode