The growing popularity of the Agile Development, Feature Driven Development (FDD) and Extreme Programming and other Rapid Application Development (RAD) models pushing developers away from the traditional software development life cycle (SDLC) and system analysis and development (SAD). The managers and decision makers are in illusion of getting rapid production from the development team. The fact is, these practices (Agile and XP) may not be a good fit for all software projects and may even cost more than traditional SDLC’s mixed models such as traditional SDLC and Waterfall models if not followed properly.
In my college, I had a paper on Software Development Life Cycle (SDLC), Systems Analysis & Design (SAD), and Software Engineering each. I spent about 6 months just learning these three papers. In my early carrier, I learned how to put SDLC practices in real world software development by following SDLC phases - Requirements Gathering, Analysis, Design, Testing, and Maintenance. What happened to these practices today?
Today, I see more and more IT managers and decisions makers are leaning towards quick results. They don’t care if the final product they get is the optimal solution or not. In many companies, developers get requirements verbally (what document?? We don’t have requirement documents), and it is expected to done in next couple of days. Now, due to this stress, developers Google and get some code from a website (probably not the most optimized solution for a problem) and have it ready as soon as possible.
yepp chanPosted Apr 28, 2008, 11:00 PM
it looks like no one talks about them around me