| ... |
... |
@@ -8,7 +8,7 @@ |
| 8 |
8 |
| [[Agile|doc:Software Engineering.Agile.WebHome]] | See link. | |
| 9 |
9 |
| Assertion | An assertion function, a crucial part of testing. If the input values don't satisfy a certain condition, the test containing the assertion fails. Example: `assertEquals(expectedResult, actualResult)`. | |
| 10 |
10 |
| Awareness | A class A is aware of class B if it contains a reference to class B in its source code. If no such reference exists, class A is unaware of class B. | |
| 11 |
|
-| Behavior | Counterpart to implementation. It refers to the externally visible actions performed by a component. For example: A class may have the public method `sort(Collection: SomeCollection)`, which says what it does, but no implementation details like what concrete sorting algorithm or private methods are used. | |
|
11 |
+| Behavior | Counterpart to implementation. It refers to the observable actions performed by a component. For example: A class may have the only observable method `sort(Collection: SomeCollection)`, which says what it does, but no implementation details like what concrete sorting algorithm is used. | |
| 12 |
12 |
| Best Practices | Widely accepted guidelines designed to enhance programming productivity and code quality. Adherence can prevent many potential issues. | |
| 13 |
13 |
| Business | Non-technical decision makers in the organization developing the software. | |
| 14 |
14 |
| Business Value | The worth of a feature in terms of its benefit to the business. | |
