The whole process needs to change. The classical, waterfall lifecycle does not take full advantage of modern technology and does not facilitate the change that is inherent in all systems development. The classical, waterfall lifecycle has been around for 30 years and is basically the solution to an old problem – that of not having a coherent approach to solving the problem before starting to code a solution. The waterfall approach of a strict sequence of stages has been seen to be flawed for some years now. Several attempts have been made to move away from it, including Boehm’s (1986) iterative style of development using a spiral model of planning, risk analysis, engineering and customer evaluation.
Ni muhimu kutafuta njia mbalimbali za ujenzi wa mifumo ya IT. teknolojia ambayo sasa inapatikana kwa watengenezaji inaruhusu kwa ajili ya uzalishaji speedier ya mifumo, lakini jibu uongo si tu katika matumizi ya zana. mchakato mzima inahitaji mabadiliko. classical, maporomoko ya maji lifecycle haina kuchukua faida kamili ya teknolojia ya kisasa na haina kuwezesha mabadiliko ambayo ni asili katika yote ya maendeleo mifumo. classical, maporomoko ya maji lifecycle imekuwa karibu kwa miaka 30 na kimsingi ni ufumbuzi wa tatizo umri wa â € “”ile ya kutokuwa na mbinu madhubuti ya kutatua tatizo kabla ya kuanza kwa kificho ufumbuzi. mbinu maporomoko ya maji ya mlolongo kali ya hatua imekuwa kuonekana kuwa na kasoro kwa miaka kadhaa sasa. majaribio kadhaa yamefanywa ili kuhamisha mbali na hayo, ikiwa ni pamoja na Boehmâ € ™ s (1986) iterative mtindo wa maendeleo kwa kutumia mfano ond ya kupanga, uchambuzi wa hatari, uhandisi na tathmini kwa wateja.