Practical Implications
When organizations adopt rapid development methodologies, care must be taken to avoid role and responsibility confusion and communication breakdown within a development team, and between team and client. In addition, especially in cases where the client is absent or not able to participate with authority in the development process, the system analyst should be endowed with this authority on behalf of the client to ensure appropriate prioritisation of non-functional requirements. Furthermore, no increment of the system should be developed without a thorough and formally documented design phase.
Read more about this topic: Rapid Application Development
Famous quotes containing the words practical and/or implications:
“One of the great triumphs of the nineteenth century was to limit the connotation of the word “immoral” in such a way that, for practical purposes, only those were immoral who drank too much or made too copious love. Those who indulged in any or all of the other deadly sins could look down in righteous indignation on the lascivious and the gluttonous.... In the name of all lechers and boozers I most solemnly protest against the invidious distinction made to our prejudice.”
—Aldous Huxley (1894–1963)
“Philosophical questions are not by their nature insoluble. They are, indeed, radically different from scientific questions, because they concern the implications and other interrelations of ideas, not the order of physical events; their answers are interpretations instead of factual reports, and their function is to increase not our knowledge of nature, but our understanding of what we know.”
—Susanne K. Langer (1895–1985)