▁tool ▁inv ocation . ▁ ▁In ▁practice , ▁the ▁distinction ▁between ▁work ben ches ▁and ▁environments ▁was ▁flexible . ▁Visual ▁Basic ▁for ▁example ▁was ▁a ▁programming ▁work ben ch ▁but ▁was ▁also ▁considered ▁a ▁ 4 GL ▁environment ▁by ▁many . ▁The ▁features ▁that ▁distinguished ▁work ben ches ▁from ▁environments ▁were ▁deep ▁integration ▁via ▁a ▁shared ▁repository ▁or ▁common ▁language ▁and ▁some ▁kind ▁of ▁method ology ▁( integr ated ▁and ▁process - center ed ▁environments ) ▁or ▁domain ▁( 4 GL ) ▁specific ity . ▁ ▁Major ▁CASE ▁R isk ▁Fact ors ▁ ▁Some ▁of ▁the ▁most ▁significant ▁risk ▁factors ▁for ▁organizations ▁adopt ing ▁CASE ▁technology ▁include : ▁▁ ▁In ade qu ate ▁standard ization . ▁Organ izations ▁usually ▁have ▁to ▁tail or ▁and ▁adopt ▁method ologies ▁and ▁tools ▁to ▁their ▁specific ▁requirements . ▁Do ing ▁so ▁may ▁require ▁significant ▁effort ▁to ▁integrate ▁both ▁diver gent ▁techn ologies ▁as ▁well ▁as ▁diver gent ▁methods . ▁For ▁example , ▁before ▁the ▁ad option ▁of ▁the ▁U ML ▁standard ▁the ▁diagram ▁convent ions ▁and ▁methods ▁for ▁design ing ▁object - orient ed ▁models ▁were ▁vast ly ▁different ▁among ▁follow ers ▁of ▁Jacob sen , ▁Bo och , ▁and ▁R umb augh . ▁▁ ▁Un real istic ▁expect ations . ▁The ▁pro ponents ▁of ▁CASE ▁technology — es pecially ▁vend ors ▁market ing ▁expensive ▁tool ▁sets — o ften ▁h ype ▁expect ations ▁that ▁the ▁new ▁approach ▁will ▁be ▁a ▁silver ▁bullet ▁that ▁solves ▁all ▁problems . ▁In ▁reality ▁no ▁such ▁technology ▁can ▁do ▁that ▁and