Advertisement
Search  
Always will be ready notify the world about expectations as easy as possible: job change page
Oct 21, 2023

Dead End

Source:
Views:
764

AntiPattern Problem

A Dead End is reached by modifying a reusable component, if the modified component is no longer maintained and supported by the supplier. When these modifications are made, the support burden transfers to the application system developers and maintainers. Improvements in the reusable component cannot be easily integrated, and support problems may be blamed on the modification.

The supplier may be a commercial vendor, in which case this AntiPattern is also known as Commercial off-the-shelf (COTS) Customization. When subsequent releases of the product become available, the special modifications will have to be made again, if possible. If fact, it may not be possible to upgrade the customized component, for various reasons such as cost and staff turnover.

The decision to modify a reusable component by a system's integrator is often seen as a workaround for the vendor's product inadequacies. As a short-term measure, this helps a product development progress, rather than slow it down.

The longer-term support burden becomes untenable when trying to deal with the future application versions and the "reusable component" vendor's releases. The only time we saw this work was when the system's integrator arranged with the reusable component vendor that the SI modifications would be included in the next release of the vendor product. It was pure luck that their objectives were the same.

Refactored Solution

Avoid COTS Customization and modifications to reusable software. Minimize the risk of a Dead End by using mainstream platforms and COTS infrastructure, and upgrading according to the supplier's release schedule.

When customization is unavoidable, use an isolation layer (see Vendor Lock-In). Use isolation layers and other techniques to separate dependencies from the majority of the application software from customizations and proprietary interfaces.

A Dead End may be an acceptable solution in testbeds that support basic research such as throwaway code, and significant benefits are realized through the customization.

Similar
Apr 11, 2023
The main thing that you should know about Software Architecture reads as follows, “Graphical interface and data should be separated”. The worst thing you could do to your program is writing your code inside Form1.cs, HomeController.cs, MainWindow.cs etc. Do not...
Oct 21, 2023
BackgroundIn a data-mining expedition, we began looking for insight into developing a standard interface for a particular kind of system. The system we were mining was very similar to those we hoped would eventually support the standard we were working...
Oct 20, 2023
AntiPattern ProblemTechnology is changing so rapidly that developers have trouble keeping up with the current versions of software and finding combinations of product releases that work together.Given that every commercial product line evolves through new product releases, the situation has...
Oct 21, 2023
BackgroundCut-and-Paste Programming is a very common, but degenerate form of software reuse which creates maintenance nightmares. It comes from the notion that it's easier to modify existing software than program from scratch. This is usually true and represents good software...
Send message
Email
Your name
*Message


© 1999–2024 WebDynamics
1980–... Sergey Drozdov
Area of interests: .NET Framework | .NET Core | C# | ASP.NET | Windows Forms | WPF | HTML5 | CSS3 | jQuery | AJAX | Angular | React | MS SQL Server | Transact-SQL | ADO.NET | Entity Framework | IIS | OOP | OOA | OOD | WCF | WPF | MSMQ | MVC | MVP | MVVM | Design Patterns | Enterprise Architecture | Scrum | Kanban