Sdlc Case Summary

470 Words2 Pages
• Time to market: They often need it “yesterday” which sometimes can lead to mistakes when a well-defined SDLC is not followed. Not to jump on the SDLC bandwagon again, but it will increase the chances of accuracy as well as reduce the chances of introducing new issues when fixing existing ones. It is important that your SDLC is as efficient as possible. When discussing SDLC we often think it’s just an “IT thing”. I disagree. Users, customers and clients of your system(s) should understand the importance of the SDLC. They should understand that it protects them as well! It helps ensure that the tools they use to do their job are functioning to their standards. In the past I found it very helpful to offer to sit with users/customers/clients…show more content…
Why does it cost so much for a small bug fix or minor enhancement? At this point in the article, we know that a good design and coding standards can reduce analysis, coding and testing time and thus reduce cost.
• Correctness: This is obvious, but it is expected that the fix or enhancement is correct, without any side effects introduced to other areas within the system. A good design will lead to efficient and focused testing on maintenance changes and enhancements.
• System Availability: No one wants to hear that a small maintenance fix will require a system outage to implement. People expect seamless implementation of minor fixes and enhancements. System outages are acceptable when major functionality is being implemented. A good design and implementation in place will allow for maximum uptime. From a software perspective – strive for the ability to deploy components of a system (loose coupling) as opposed to an entire recompiled system. From an implementation perspective – strive to have load balanced servers in place running your application. If need be, this will allow you to gracefully remove one server from the load balancer for deployment while the other server(s) continue to service incoming requests. If your system has overnight processing that requires the database to be locked down from updates and inserts at times – implementing a “batch mode” to allow your
Get Access