Antipattern

In software Genius, the anti-owners or antipattern are current errors of design of the software. Their name comes owing to the fact that these errors appeared as of the phases of design of the software, in particular by the absence or the misuse of owners of design, called design pattern in English.

The anti-owners are often characterized by an excessive slowness of the software, costs of raised realization or maintenance, behaviors abnormal and the presence of bugs.

There exist also the GreyPattern S (of which the benefit or the disadvantages are not clearly established).

Some anti-owners

Opposite abstraction

The abstraction reverses occurs when one builds a software object with a interface which does not offer functions required by the Développeur S which use it, whereas it could offer them. The interface offers only more complex functions. The result is that the user of the object must make use of the complex functions provided by the object to program a simple behavior.

Example: to have an object which makes only floating-point calculations, and being obliged to use this object to make calculation with entireties.

Remote action

The remote action is characterized by the immoderate use of aggregate variables or the increased interdependences between objects.

Boat anchors

The anchor of boat is component unutilised but which is kept in the software for political reasons, by thinking that this code will be useful later.

Active waiting

Active waiting indicates a loop which contains only one instruction: to test a condition, until it is finally checked, and which the piece of code can continue its unfolding. This anti-pattern is current in concurrent Programmation, because these is the process which must modify variables to be able “to release” the loop of active waiting. Waiting is active since the process which waits spends machine time, which constitutes a wasting. One can free from this bad technique thanks to the event-driven Programmation, or by the use of signals.

Deadlock S and famine

They are current errors due to a bad design of the concurrent parts of the software (for example during the use of Thread S). They appear when several pieces of code want to use one or more resource S at the same time, and that the strategy of allowance of the resources is vitiated or non-existent. That results in deteriorated performances, even of “plantings”.

Error to copy/stick

The duplication of code without checking involves inconsistencies. The best solution being still to factorize the common parts instead of duplicating them.

Programming spaghetti

Dish of lasagnes

By analogy with the programming spaghetti, the dish of Lasagnes refers to a software built in several layers resting the ones on the others, without any possibility of intervening on the sub-bases.

To reinvent the square wheel

By analogy with the useless réinvention of the wheel, the square wheel refers to the fact badly of reinventing an existing solution or of reinventing a bad solution, nonexisting of this fact.

Lava flow

The lava flow occurs when part of code still immature is put in production, forcing the lava to solidify itself by preventing its modification.

Overload interfaces

The overload of the interfaces refers to current practices in design of user interfaces Web, where several buttons have the same effect.

The divine object

The divine object is component software ensuring too many essential functions. It is the opposite of the method to divide to reign.

Antipattern architectural

ArchitectureAsRequirements : consisting in specifying an architecture by simple preference or because it is new, whereas there for of does not require and that the customer did not express the desire of it.
ArchitectureByImplication : consisting in not documenting the architecture used by a project and not specifying it.

Random links: