The document discusses various aspects of software implementation and integration. It defines implementation as the process of transforming a design into code and other implementation elements. Key aspects discussed include unit testing, integration testing, configuration management, host-target development, reuse, and prototyping. Implementation involves tasks such as writing code, testing components, integrating work, and debugging. The roles of implementers and integrators in managing this process are also outlined.

1. ImplementationModel

2. Sources
•IvarJacobson,GradyBooch,JamesRumbaugh.TheUnifiedSoftwareDevelopmentProcess(ObjectTechnologySeries)-1998.
•AhmadK.Shuja,JochenKrebs.IBMRationalUnifiedProcessReferenceandCertificationGuide—SolutionDesigner.IBMPress,2008.
•McConnell.,Steve.CodeCompleteSecondEdition-Apracticalhandbookofsoftwareconstruction.MicrosoftPress.2009
•Sommerville,Ian.SoftwareEngineeringNinthEdition. Pearson,2011.

3. •ImplementationModel
•ImportantConcepts
•Integration

4. Before..
Cartoon: NP
Designersand developersdon'treallyspeakthesamelanguage.
(From: http://chetchat.blogspot.fr/2014/08/cartoon-np.html)

5. Somewordsenvolved
•Implementation
•Construction?
•Coding?
Codingimplythemechanicaltranslationofapreexistingdesignintoacomputerlanguage;
Implementation(SWconstruction)isnotatallmechanicalandinvolvessubstantialcreativityandjudgment.
Steve McConnell
lead for the Construction Knowledge Area of the Software Engineering Body of Knowledge (SWEBOK) project.

6. Implementationisvital
Implementationisthecentralactivityinsoftwaredevelopment.Requirementsandarchitecturearedonebeforeconstructionsothatyoucandoconstructioneffectively.Systemtesting(inthestrictsenseofindependenttesting) isdoneafterconstructiontoverifythatconstructionhasbeendonecorrectly. Constructionisatthecenterofthesoftware- developmentprocess.
Steve McConnell

7. Implementationisvital
Constructionistheonlyactivitythat'sguaranteedtobedone.Theidealsoftwareprojectgoesthroughcarefulrequirementsdevelopmentandarchitecturaldesignbeforeconstructionbegins.Theidealprojectundergoescomprehensive,statisticallycontrolledsystemtestingafterconstruction.Imperfect,real-worldprojects,however,oftenskiprequirementsanddesigntojumpintoconstruction.Theydroptestingbecausetheyhavetoomanyerrorstofixandthey'verunoutoftime.Butnomatterhowrushedorpoorlyplannedaprojectis,youcan'tdropconstruction;it'swheretherubbermeetstheroad.Improvingconstructionisthusawayofimprovinganysoftware-developmenteffort,nomatterhowabbreviated.
Steve McConnell

8. ImplementationModel
•TheImplementationmodeldescribeshowdesignmodel’selementsareimplementedintermsofcomponents.
•Italsodescribeshowcomponentsareorganizedaccordingtostructurationandmodularizationapproachesavailableintheenvironmentolanguage.
•Itimpliesdependence

9. ImplementationModel
From: "The Unified Software Development Process (Object Technology Series)“-1998

10. More in deep…
TheImplementationexplainshowtodevelop, organize,unittest,andintegratethecomponentsastheyareincrementallydevelopedineveryiteration.Testingduringimplementationislimitedtounittesting.Othertests,suchasthesystemtestandtheintegrationtest,arecarriedoutwithintheTest.

11. More in deep…
Sommervilleintroducessomeaspectsofimplementationthatareparticularlyimportanttosoftwareengineeringthatareoftennotcoveredinprogrammingtexts
1.Reuse.Mostmodernsoftwareisconstructedbyreusingexistingcomponentsorsystems.Whenyouaredevelopingsoftware,youshouldmakeasmuchuseaspossibleofexistingcode.
2.Configurationmanagement.Duringthedevelopmentprocess,manydifferentversionsofeachsoftwarecomponentarecreated.Ifyoudon’tkeeptrackoftheseversionsinaconfigurationmanagementsystem,youareliabletoincludethewrongversionsofthesecomponentsinyoursystem.
3.Host-targetdevelopment.Productionsoftwaredoesnotusuallyexecuteonthesamecomputerasthesoftwaredevelopmentenvironment.Rather,youdevelopitononecomputer(thehostsystem)andexecuteitonaseparatecomputer(thetargetsystem).Thehostandtargetsystemsaresometimesofthesametypebut,oftentheyarecompletelydifferent.

12. Aboutreuse
Softwarereuseispossibleatanumberofdifferentlevels:
1. The abstraction level.
2. The object level
3. The component level
4. The system level

13. •Todefinetheorganizationofthecodeintermsofimplementationsubsystems(maybeorganizedinlayers)
•Toimplementthedesignelementsintermsofimplementationelements(sourcefiles,binaries, executableprograms,andothers)
•Totestthedevelopedcomponentsasunits
•Tointegratetheresultsproducedbyindividualimplementers(orteams)intoanexecutablesystem
Purposes

14. •Verifyingthatthegroundworkhasbeenlaidsothatconstructioncanproceedsuccessfully
•Determininghowyourcodewillbetested
•Designingandwritingclassesandroutines
•Creatingandnamingvariablesandnamedconstants
•Selectingcontrolstructuresandorganizingblocksofstatements
•Unittesting,integrationtesting,anddebuggingyourowncode
•Reviewingotherteammembers'low-leveldesignsandcodeandhavingthemreviewyours
•Polishingcodebycarefullyformattingandcommentingit
•Integratingsoftwarecomponentsthatwerecreatedseparately
•Tuningcodetomakeitfasterandusefewerresources
Specifictasksinvolved
Steve McConnell

15. •TheImplementationModelisacollectionofcomponentsandtheimplementationsubsystemsthatcontainthem.
•Thetermmodelhereisnotmeanttoconnotediagramsandothermoreabstractrepresentations.Instead,anImplementationModelconsistsofImplementationElements,ImplementationSubsystems,andelementscreatedtosupportdevelopertesting.
ImplementationModel

16. Workersinvolvedin theImplementationModel

17. •TheSoftwareArchitectisresponsibleforstructuringtheImplementationModel.
•StructuringtheImplementationModelinvolvesestablishingtheImplementationModelstructure,adjustingimplementationsubsystems,definingimportsforeachimplementationsubsystem,decidinghowtotreatexecutableprogramsandotherderivedobjects,decidinghowtotreattestassets,updatingtheimplementationview, andevaluatingtheImplementationModel
ImplementationModel

18. ImplementationModel

19. Workersinvolvedin theImplementationModel

20. So…

21. •Implementdesignelements—TheImplementerimplementstheelementsinthedesignmodel;thatis,hewritessourcecode, adaptsexistingsourcecode,compiles,andlinksandperformsunittests.Ifhediscoversdefectsinthedesign,hesubmitsreworkfeedbackonthedesign.
•Fixcodedefects—TheImplementeralsofixescodedefectsidentifiedduringtheunittestsandperformsfurtherunittestingtoensurethatnonewdefectshaveemergedandthatthechangeisverified.
•Evaluatequality—Finally,theImplementerreviewsthecodetoevaluatequalityandcompliancewiththeProgrammingGuidelines.
ImplementationModelconsiderate!!

22. TheImplementerisresponsibleforthefollowing:
•Implementingdesignelements-Thisinvolvespreparingforimplementation,transformingthedesigntoimplementation,completingtheimplementation,evaluatingtheimplementation,andprovidingfeedbacktodesign.Inimplementingthedesignelements,theImplementerproducesanImplementationElementandImplementationSubsystem
ImplementComponents

23. TheImplementerisresponsibleforthefollowing:
•Analyzingruntimebehavior—Thisisdonebydeterminingtherequiredexecutionscenario,preparingimplementationcomponentsforruntimeobservation, preparingtheenvironmentforexecution,executingthecomponentandcapturingbehavioralobservations, reviewingbehavioralobservationsandisolatinginitialfindings,analyzingfindingstounderstandrootcauses, identifyingandcommunicatingfollow-upactivities,andevaluatingtheresults
ImplementComponents

24. TheImplementerisresponsibleforthefollowing:
•ImplementingtestabilityelementsandproducingtheTestabilityElementandtheTestStub—Thisinvolvesimplementingandunittestingdrives/stubsandimplementingandunittestingtheinterfacetotheautomatedtesttool(UnitFramework,TestNG…).
ImplementComponents

25. TheImplementerisresponsibleforthefollowing:
•ImplementingandproducingtheDeveloperTest—Thisisachievedbyrefiningthescopeandidentifyingthetests,selectingtheappropriateimplementationtechniques,implementingthetest, establishingexternaldatasets,verifyingthetestimplementation, andmaintainingtraceabilityrelationships.
•ExecutingdevelopertestsandproducingtheTestLog—Thisrequiresexecutingtheunittests,evaluatingtheexecutionoftests, verifyingthetestresults,andrecoveringfromhaltedtests.
ImplementComponents

26. So…

27. So…

28. So…

29. Integration
Largesoftwaresystemsrequiremultiplesoftwarecomponents,someofftheshelfandotherscustomdeveloped,tobeintegratedintoawholesystem.Thisisaspecializedsoftwaredevelopmentactivitythatcombinesseparatesoftwarecomponentstoproduceasoftwaresystem.
ImportantConcepts

30. Integrationisdoneatseveralstagesandlevelsduringtheimplementation.
-Integratingtheworkofateamworkinginthesameimplementationsubsystembeforereleasingthesubsystemtosystemintegrators
-Integratingsubsystemsintoacompletesystem.
Integration

31. Incrementalintegrationmeansthatcodeiswrittenandtestedinsmallpiecesandthencombinedintoaworkingwholebyaddingonepieceatatime. Thebenefitsincludeeasyidentificationoffaults, fulltestingofcomponents,andearlyfeedbackontheexecutionofthesystem.
Integration

32. So…

33. ImportantConcepts
Prototypes
Prototypesareusedtocheckbusinessviability,todemonstratekeytechnology,toobtainprojectcommitmentorfunding,tofurtherunderstandrequirements,andtocheckusability

34. ImportantConcepts
RuntimeObservationand Analysis
Thisconceptencompassestheobservationofthesoftwareduringruntimeexecutionandanalysisofthecapturedannotationswherepathsaretracedthroughsoftwarecomponentsandthenaggregatedtounderstandglobalsystembehaviorviastatisticalinference.

35. ImportantConcepts
RuntimeObservationand Analysis
Becauseofthepotentialvolumeofthelow-levelinformationthatcanbecapturedfromruntimebehavior,thespeedatwhichthatinformationisgenerated,andthesubsequentdifficultyinunderstandingthepotentiallyvastamountofinformation,automatedtoolsupportisakeyfactorinmakingthispracticefeasible.

36. ABuildisanoperationalversionofasystemorapartofthesystemthatdemonstratesasubsetofthecapabilitiesprovidedinthefinalproduct.TheBuildconstitutesanintegralpartoftheiterativedevelopmentlifecycleandprovidesreviewpoints.Notethatinalliterativeincrementaldevelopmentprocesses,progressisdemonstratedviaanexecutable,a(working)softwaredeliverableratherthanjustdocumentsorthelike.Thelifecycle“providesreviewpoints,”buttheBuildisreviewableandobjectivelydemonstratesprogresstowardcompletion.TheBuildisexaminedatthereviewpointsthatthelifecycleprovides.
Build

37. Build
ThepurposeofaBuild,constructedfromotherelementsintheimplementation,istodeliveratestablesubsetoftheruntimefunctionsandcapabilitiesofthesystem.

38. IntegrationBuildPlan
Thisartifactprovidesadetailedplanforintegrationwithinaniteration.Thepurposeofthisartifactistodefinetheorderinwhichtoimplementthecomponents,determinewhichbuildstocreatewhenintegratingthesystem,anddefinehowtheyaretobeassessed.TheImplementerusesthisartifacttoplantheorderinwhichtoimplementdesignelementsandwhatandwhentodelivertosystemintegration.

39. IntegrationBuildPlan
-Integratorleadstheplanningandexecutionofimplementationelementintegrationtoproducebuilds.
-TheIntegratorusestheintegrationbuildplanasaplanningtool

40. DeveloperTest
ThepurposeoftheDeveloperTestistoprovidetheimplementationofasubsetofrequiredtestsinanefficientandeffectivemanner.
MostoftheDeveloperTestsarecreatedinthesametimeframesasthesoftwarecomponentsthatneedtobetested.

41. Component-UML
Amodularpartofasystemthatencapsulatesitscontentsandwhosemanifestationisreplaceablewithinitsenvironment.Acomponentdefinesitsbehaviorintermsofprovidedandrequiredinterfaces.Assuch,acomponentservesasatype,whoseconformanceisdefinedbytheseprovidedandrequiredinterfaces(encompassingboththeirstaticaswellasdynamicsemantics).

42. Anencapsulatedpartofasystem,ideallyanon-trivial,nearlyindependent,andreplaceablepartofasystemthatfulfillsaclearfunctioninthecontextofawell-definedarchitecture.Thisincludes:
•designcomponent-asignificantencapsulatedpartofthedesign,andsoincludesDesignSubsystemsandsometimessignificantDesignClassesandDesignPackages.
•implementationcomponent-asignificantencapsulatedpartoftheimplementation,generallycodethatimplementsadesigncomponent
Component-RUP

43. ComponentReplaceability(RUP)
•Source-FileReplaceability:Thischaracteristicmakesiteasierforcomponentsourcecodetobeversion- controlled,baselined,andre-used
•DeploymentReplaceability:thereisonefileoronesetoffilesthatdeploythecomponentandnoothercomponent
•Run-TimeReplaceability:Thisenablessoftwaretobeupgradedwithoutlossofavailability.
•LocationTransparency

44. More aboutComponents
•http://www.agilemodeling.com/artifacts/componentDiagram.htm
•http://www.ibm.com/developerworks/rational/library/dec04/ bell/

45. Finally… don’tforgettheTraceability!

46. Finally… don’tforgettheTraceability!

47. Finally… don’tforgettheTraceability!

48. ImplementationEnviromentFeatures(Sommerville)
Asoftwaredevelopmentplatformshouldprovidearangeoftoolstosupportsoftwareengineeringprocesses.Thesemayinclude:
1.Anintegratedcompilerandsyntax-directededitingsystemthatallowsyoutocreate,edit,andcompilecode.
2.Alanguagedebuggingsystem.
3.Graphicaleditingtools,suchastoolstoeditUMLmodels.
4.Testingtools,suchasJUnitthatcanautomaticallyrunasetoftestsonanewversionofaprogram.
5.Projectsupporttoolsthathelpyouorganizethecodefordifferentdevelopmentprojects.

49. Be careful
•Implementationhavepatternsalso….
•SeeCleanCodeofRobertC.Martin,andImplementationPatternsofKentBeck

50. Be careful(http://www.agilemodeling.com/artifacts/componentDiagram.htm)
UML1.0
UML2.0

51. Thanks for your attention
fdgiraldo@uniquindio.edu.co