• Keine Ergebnisse gefunden

Software Product Line Engineering

N/A
N/A
Protected

Academic year: 2022

Aktie "Software Product Line Engineering"

Copied!
7
0
0

Wird geladen.... (Jetzt Volltext ansehen)

Volltext

(1)

Software Product Line Engineering

Lab Class 3

(2)

Outline

• Discussion Task 2 & 4

• Remarks on first submission

(3)

Recap Modularity

• Coupling: Connectivity across modules

• Cohesion: Connectivity within modules

weak coupling strong coupling

low cohesion high cohesion

(4)

Recap UML

• Entities

• Classes

• Interfaces / Abstract Classes

• Associations

• normal: “x corresponds to y”

• composition: “x(s) is/are part of y”

• Generalization

• Implementation of interfaces

X Y

X Y

* *

1 *

(5)

Chat base implementation

(6)

Chat with features

Interfaces Color

Authentication Encryption Logging

(7)

Scattered and Tangled Code

Modeling Implementation

Referenzen

ÄHNLICHE DOKUMENTE

About 80% of all software systems today are software product lines or can at least profit. from product

(a) The development process for a software product line includes domain and application engineering. What are the outcomes of the last step of domain and application

 Modules can be composed within a new context of another project (variability).. Design Patterns for Variability.. Observer Pattern. “Define[s] a one-to-many dependency

From the manual page, extract the features that correspond to the compression mode (2 points), and construct a feature model (6 points) with FeatureIDE.. Note: The application

 Make feature explicit in source

building systems [...] in a particular domain in the form of reusable assets [...], as well as providing an adequate means for reusing these assets (i.e., retrieval, qualification,

• //every method invocation inside the method Server.broadcast() unless the target is an instance of class Connection pointcut

 Use case of aspects and collaborations depend on the implementation problem.  Aspects and collaborations have different pros