Impact of Design Pattern on Technical debt mitigation
Technical debt is one of the crucial issue within the realms of software development. Companies have heavily invested in the improvement of the code quality of their software systems. Those who do not care about the technical debt lands into the deep waters of maintainability issues and higher cost of maintenance with extreme level of complexity. On contrast design patterns are the best practices to solve a problem, design patterns are used to solve the problem in the best possible ways to achieve longer maintainability and loose coupling.
This paper tries to address the impact of design pattern on the technical debt by comparing the results of technical debt on the problem solved with and without the implementation of design patterns. This research paper focus on identifying a ratio or difference using which anyone can easily pick a design pattern to refactor the code and dramatically reduce the technical debt from the software systems under consideration. To read more download
- Impact of Design Pattern on technical debt mitigation Long Report
- Impact of Design Pattern on technical debt mitigation Short Report.
Identification and Eradication of Technical Debt from Software Applications
Technical debt is the debt which is incurred due to the negligent behavior of software engineers and project managers towards an application code quality. There are several reasons for the accumulation of technical debt some reasons are quite obvious and known and some reasons are really obscure and indirect. This nature of problem keeps the technical debt hidden until and unless their effect starts appearing. In this research I have focused on these direct and indirect causes of technical debt and suggested a solution to address these issues from the very first day. This research will not only help the developers primarily but will also help the organizations to adopt a pattern that will help them mitigate this issue. This research can also serve as a check list for anyone willing to improve this problem within their codebase. There are several types of technical debts which have been discussed here in this report and the remedies have been suggested against these types of debts. Cost and value attached with these bugs are also discussed and prioritization techniques have been suggested as well
Exploring Cross-Site Scripting (XSS) Attacks on Web Applications and Their Possible Remedies
Cross site scripting (XSS) is one of the mostly found attacks on website. As any sort of negligence from the programmer or developer can make the application vulnerable to cross site scripting. In this research work I have studied different mechanism of cross site scripting attacks and ultimately come to a conclusion to have a sort of Anti-XSS plug-in for browser. As the victim of XSS attacks are user of the application so it is best to save guard them at the user side i.e. client side. Each and every browser has the ability to parse the response stream of server and render it as a web page. The function of Anti-XSS will be to sit in between the parsing engine and response stream. It will intercept the stream before parsing engine parse it and render the page. The Anti-XSS will maintain a database for XSS attacks as Anti-Virus software do maintain a virus definition. This database will be automatically updateable. This way if a XSS attack is discovered anywhere in the world or any penetration tester found any sort of XSS attack it can be made public as a vulnerability and all the browsers that are protected by Anti-XSS will update their databases.