take home-oodp

take home-oodp - Vinay Raju A20260918 TAKE HOME 1) Describe...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Vinay Raju A20260918 TAKE HOME 1) Describe 3 anti patterns? Ans) Software development anti patterns - Dead End 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 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 AntiPattern). Use isolation layers and other techniques to separate dependencies from the majority of the application software from customizations and proprietary interfaces. b) Software Architecture AntiPatterns Wolf Ticket AntiPattern Problem
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
There are many more information systems standards than there are mechanisms to assure conformance. Only 6 percent of information systems standards have test suites. Most of the testable standards are for programming language compilers — FORTRAN, COBOL, Ada, and so forth. A Wolf Ticket is a product that claims openness and conformance to standards that have no enforceable meaning. The products are delivered with proprietary interfaces that may vary significantly from the published standard. A key problem is that technology consumers often assume that openness comes with some benefits. In reality, standards are more important to technology suppliers for brand recognition than for any benefits that the standards may offer users. Standards do reduce technology migration costs and improve technology stability, but, differences in the
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 05/04/2011.

Page1 / 12

take home-oodp - Vinay Raju A20260918 TAKE HOME 1) Describe...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online