Past wisdom in software development held that the proper sequence of events should start with perfect requirements, followed by perfect design and planning, ending with implementation. The flexibility promised by agile methodologies of software development, according to that view, is as costly as deciding the kitchen in a half-built house is not in the desired location. Besides, what is the meaning of software architecture if we allow for shifting designs and evolving features?
To answer that criticism, one must examine the underlying concepts supporting traditional waterfall development:
Register or login for access to this item and much more
All Information Management content is archived after seven days.
Community members receive:
- All recent and archived articles
- Conference offers and updates
- A full menu of enewsletter options
- Web seminars, white papers, ebooks
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access