Taxonomy of software change

[DGDanforth]

Changes to the BlackBox framework need a categorization because there are different types.
I suggest the following.

Framework
o Bugs (software is wrong)
o Oversights (missing behavior in an extant module)
o Additions (new capabilities added to framework)
o Removals (capabilities removed from framework)
o Versions (issuance of new framework versions containing any of the above changes)

Libraries
The Component Pascal Collection is an example of a library (of modules).
Arbitrary modifications, additions, or removals may occur to libraries without
the approval of the Center.

[ReneK]

Sounds good to me.

[Ivan Denisov]

I agree with Doug, that Features is very general class. And it can be separated for:

o Oversights (missing behavior in an extant module)
o Additions (new capabilities added to framework)
o Removals (capabilities removed from framework)

Why Removals can be important? Because them can fight the complexity. If only add Features, the IDE will grow as an snow ball.

[DGDanforth]

Why Removals can be important? Because them can fight the complexity. If only add Features, the IDE will grow as an snow ball.

Yes, whenever you create you need to be able to destroy. It needs to be a birth and death process in order to obtain an equilibrium (homeostasis).

Homeostasis or homoeostasis (homeo- + -stasis) is the property of a system in which variables are regulated so that internal conditions remain stable and relatively constant.

-Doug