Domain specific Software Architecture and Product Lines
اسلاید 1: Domain-Specific Software Architecture and Product LinesSoftware Architecture Lecture 24
اسلاید 2: ObjectivesConceptsWhat is domain-specific software engineering (DSSE)The “Three Lampposts” of DSSE: Domain, Business, and TechnologyDomain Specific Software ArchitecturesProduct LinesRelationship between DSSAs, Product Lines, and Architectural StylesExamples of DSSE at work2
اسلاید 3: ObjectivesConceptsWhat is domain-specific software engineering (DSSE)The “Three Lampposts” of DSSE: Domain, Business, and TechnologyDomain Specific Software ArchitecturesProduct LinesRelationship between DSSAs, Product Lines, and Architectural StylesExamples of DSSE at work3
اسلاید 4: Product LinesA set of related products that have substantial commonalityIn general, the commonality exists at the architecture levelOne potential ‘silver bullet’ of software engineeringPower through reuse ofEngineering knowledgeExisting product architectures, styles, patternsPre-existing software components and connectors 4
اسلاید 5: Domains vs. Product LinesDomainConsumer electronicsAvionicsCompilersVideo gamesProduct LineSony WEGA TVsBoeing 747 FamilyGNU compiler suiteSuite of games built on same engine5Domains are in the problem space, product lines are in the solution space
اسلاید 6: Business vs. Engineering Product LinesBusiness Product LineA set of products marketed under a common banner to increase sales and market penetration through bundling and integrationEngineering Product LineA set of products that have substantial commonality from a technical/engineering perspectiveGenerally, business product lines are engineering product lines and vice-versa, but not alwaysApplications bundled after a company acquisitionChrysler Crossfire & Mercedes SLK V66
اسلاید 7: Business Motivation for Product Lines7Traditional Software EngineeringSoftware Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 8: Business Motivation for Product Lines8Traditional Software EngineeringSoftware Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 9: Business Motivation for Product Lines9Product-line-based engineeringSoftware Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 10: Capturing Product Line ArchitecturesCommon: features common to all productsA: features specific to product AB: features specific to product BProduct A = Common + AProduct B = Common + B10Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 11: A Product-Line ArchitectureDefinition: A product-line architecture captures the architectures of many related products simultaneouslyGenerally employs explicit variation points in the architecture indicating where design decisions may diverge from product to product11
اسلاید 12: A Lunar Lander Product Line12“Lite”“Demo”“Pro”Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 13: Product Component TableHelps us decide whether creating a product line is viable or feasible13Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 14: Group Components into FeaturesNot a mechanical processAttempt to identify (mostly) orthogonal features, or features that would be beneficial in different products14Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 15: Reconstitute Products from FeaturesUse technical and business knowledge to identify which combinations form feasible or marketable products that will be constructed15Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 16: Modeling Product Line ArchitecturesArchitectural models need to be diversified with information about variation points and featuresNot all ADLs have good support for thisExceptions includeKoalaxADL 2.0These ADLs have explicit support for capturing variation points16
اسلاید 17: 17Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 18: SelectionProduct-line selection is the process of extracting a single product architecture (or smaller product line) from an architectural model that contains explicit points of variationADLs such as Koala and xADL 2.0 can do selection automatically with tools18Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 19: Product Lines for EvolutionProducts in a product line don’t have to exclusively capture alternativesThey can also capture variation over time19Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 20: Product Lines for Evolution20Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 21: Product Lines for ‘What-If’ AnalysisIn addition to alternative products and different versions of the same product, product lines can capture different potential productsSelection can be used to quickly generate product architectures for potential productsThese can be checked for certain properties or subjected to more rigorous analysis for feasibility or qualityCan also be used to generate new product ideas21
اسلاید 22: Implementation IssuesImportant to partition implementations along variation-point boundaries22BadGoodSoftware Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 23: Implementation Issues (cont’d)Keeping evolving architectures and version-controlled source repositories (e.g., RCS, CVS, Subversion) in sync23Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 24: Unifying Products with Different HeritageOften, the idea to create a product line emerges after several products have been implemented and commonality is noticedStrategies includeNo product lineIt may be more expensive to create a product line or there may not be enough commonalityOne master productOne product architecture becomes the basis for the product lineHybridA new product line architecture emerges out of many productsSeems ideal but can be hard in practice24
اسلاید 25: Architectural Styles, DSSAs, Product LinesArchitectural StylesCan be general or domain-specificProvides general guidelines for diverse kinds of applications; focus on –ility developmentDSSAsDomain specific; includes elaborate domain model and specific reference architectureProduct linesExplicit set of related products with common aspects25StyleDSSA / Ref ArchProduct Line
اسلاید 26: Families of Styles26Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 27: ObjectivesConceptsWhat is domain-specific software engineering (DSSE)The “Three Lampposts” of DSSE: Domain, Business, and TechnologyDomain Specific Software ArchitecturesProduct LinesRelationship between DSSAs, Product Lines, and Architectural StylesExamples of DSSE at work27
اسلاید 28: KoalaAn ADL and tool-set for developing product lines of consumer electronicsA successor to Darwin in terms of structural modelingOne of the first ADLs to capture points of variation explicitlyHas tight bindings to implementations such that architecture descriptions can be “compiled” into application skeletons28
اسلاید 29: Lunar Lander in KoalaNo product line features yetNote similarities to Darwin, xADL 2.0xADL 2.0 Archipelago visualization is derived from Koala 29interface IDataStore{ void setAltitude(int altitudeInMeters); int getAltitude(); void setBurnRate(int newBurnRate); int getBurnRate(); ...}Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 30: Lunar Lander PL in KoalaSwitch construct routes calls to one of two potential data stores‘Diversity interface’ lets game logic component select callee from external config componentSame IDataStore interface ensures call compatibility30Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 31: Software Defined RadiosVariation points in radio configuration, board configuration, software configuration31Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 32: SDR in xADL 2.0Two-node “SCARI” SDR with just device drivers loaded32Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 33: SDR in xADL 2.0Same radio with one waveform deployed33Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; (C) 2008 John Wiley & Sons, Inc. Reprinted with permission.
اسلاید 34: SDRs in xADL 2.0By applying product line techniques to SDRsCan manage different configurations of the radioDeploying components on alternative hostsDeployments withNo waveformsOne waveformDifferent combinations of waveformsCan show radio in different states as radio starts up or transitions from one waveform to another34
نقد و بررسی ها
هیچ نظری برای این پاورپوینت نوشته نشده است.