In the development and operation of software we want over the life of our systems as low as possible modification and operating costs, and high intelligibility ( Fig. 1 ).
for medium to large systems, this ideal situation in reality occurs only rarely. Time pressure, construction and management failures and short-term oriented design decisions ensure that quite the opposite is happening: Although initially everything was clean developed and designed degenerate systems over time – the phenomenon of “rotting Software” strikes. Changes are difficult, risky and always take longer. In the development and operation problems increasingly occur on rectifications more and takes more time and resources. This is accompanied by change and rising operating costs. The actual situation of commercial software shown in Fig. . 2
Very different reasons this predicament – some common examples
- A lack of conceptual integrity: identical problems are solved differently within a system, there are several different, sometimes contradictory solutions
- Excessive structural complexity, complicated concepts or processes within the. system.
- Evil source code that violates example Basics of Clean Code [1], having suffered excessive coupling or low cohesion, contrary to coding conventions, redundancies contains or is simply incomprehensible.
- (“using a sledgehammer to crack a nut”) to technical problems inappropriate choice of technologies, frameworks or other infrastructure
.
This list I could almost carry on any – and each new entry would be me it remind you of a real situation of my career to date,
Aufmacherbild . Businessman working with laptop on new projects of Shutterstock / Copyright alphaspirit
No comments:
Post a Comment