2.1 Agile methods
In the 1980s and early 1990s, there was a widespread view that the best way to create good software was to use controlled and rigorous software development processes. The processes included detailed project planning, requirements specification and analysis, the use of analysis and design methods supported by software tools, and formal quality assurance. This view came from the software engineering community that was responsible for developing large, long-lived software systems such as aerospace and government systems. These were “one-off” systems, based on the customer requirements.
This approach is sometimes called plan-driven development. It evolved to support software engineering where large teams developed complex, long-lifetime ...
Get Engineering Software Products: An Introduction to Modern Software Engineering now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
