blob: 4edbd41b37331df3898fcab25287df26dac4e837 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
= AspectJ Design Overview
:doctype: book
:leveloffset: +1
Here are some sobering words:
"Although it is essential to upgrade software to prevent aging, changing software can cause a different form of
aging. The designer of a piece of software usually had a simple concept in mind when writing the program. If the
program is large, understanding the concept allows one to find those sections of the program that must be altered
when an update or correction is needed. Understanding that concept also implies understanding the interfaces used
within the system and between the system and its environment. Changes made by people who do not understand the
original design concept almost always cause the structure of the program to degrade. Under those circumstances,
changes will be inconsistent with the original concept; in fact, they will invalidate the original concept. Sometimes
the damage is small, but often it is quite severe. After those changes, one must know both the original design rules
and the newly introduced exceptions to the rules, to understand the product. After many such changes, the original
designers no longer understand the product. Those who made the changes, never did. In other words, *nobody*
understands the modified product." +
+
Software that has been repeatedly modified (maintained) in this way becomes very expensive to update. Changes take
longer and are more likely to introduce new 'bugs'."
-- David Parnas on "Ignorant Surgery" in his paper on Software Aging
////
ATTENTION: Please do not remove blank lines in between 'include::' statements. Otherwise, section numbers in the
table of contents (TOC) can be wrong and the first section of each document missing completely.
////
include::compiler-weaver.adoc[Guide for Developers of the AspectJ Compiler and Weaver]
include::modules.adoc[Module Structure]
include::language.adoc[Language Design]
|
