Proceedings. 26th International Conference on Software Engineering
DOI: 10.1109/icse.2004.1317408
|View full text |Cite
|
Sign up to set email alerts
|

Controlling the complexity of software designs

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
12
0

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 12 publications
(12 citation statements)
references
References 36 publications
0
12
0
Order By: Relevance
“…Figure 15 depicts this feature implemented using common FOP concepts. Client is refined by an account management (Lines [16][17][18][19][20][21][22], SIR is refined by a price calculation (Lines 2-5), and SIB charges the account when passing information to the client (Lines 10-12). …”
Section: A Case Studymentioning
confidence: 99%
“…Figure 15 depicts this feature implemented using common FOP concepts. Client is refined by an account management (Lines [16][17][18][19][20][21][22], SIR is refined by a price calculation (Lines 2-5), and SIB charges the account when passing information to the client (Lines 10-12). …”
Section: A Case Studymentioning
confidence: 99%
“…It has been argued that such a replacement of objectoriented techniques without any benefit is questionable [20,26,38], especially with respect to the additional program complexity introduced by aspects [1,39].…”
Section: Explicitness and Scalabilitymentioning
confidence: 99%
“…The LoD states, "Only talk to your immediate friends," which implies that each unit of source code should only have limited knowledge about other units, and only about their so called friends. The LoD is an application of the low coupling principle by making the notion of bad coupling explicit and checkable by tools [4]. The LoD comes in two forms: The object form and the class form.…”
Section: The Law Of Demetermentioning
confidence: 99%
“…While the importance of these principles is beyond controversy, many different heuristics have been formulated that break down the difficult task of writing "good" code to a simple set of rules which developers can follow. One of those rules-of-thumb is the Law of Demeter (LoD), formulated by Lieberherr and Holland in 1989 [2], [3], [4]. Its intent is to achieve loose coupling by limiting the knowledge that one unit of source code has about other units in the system.…”
Section: Introductionmentioning
confidence: 99%