▁▁ ▁Project ▁management . ▁Man age ▁project ▁plans , ▁task ▁assign ments , ▁sched uling . ▁Another ▁common ▁way ▁to ▁distinguish ▁CASE ▁tools ▁is ▁the ▁distinction ▁between ▁Upper ▁CASE ▁and ▁Lower ▁CASE . ▁Upper ▁CASE ▁Tools ▁support ▁business ▁and ▁analysis ▁model ing . ▁They ▁support ▁traditional ▁diagram m atic ▁languages ▁such ▁as ▁ER ▁diag rams , ▁Data ▁flow ▁diagram , ▁Str ucture ▁charts , ▁Dec ision ▁Tre es , ▁Dec ision ▁tables , ▁etc . ▁Lower ▁CASE ▁Tools ▁support ▁development ▁activities , ▁such ▁as ▁physical ▁design , ▁debugging , ▁construction , ▁testing , ▁component ▁integration , ▁maintenance , ▁and ▁reverse ▁engineering . ▁All ▁other ▁activities ▁span ▁the ▁entire ▁life - cycle ▁and ▁apply ▁equally ▁to ▁upper ▁and ▁lower ▁CASE . ▁ ▁Work ben ches ▁ ▁Work ben ches ▁integrate ▁two ▁or ▁more ▁CASE ▁tools ▁and ▁support ▁specific ▁software - process ▁activities . ▁Hence ▁they ▁achieve : ▁a ▁hom ogeneous ▁and ▁consistent ▁interface ▁( presentation ▁integration ). ▁se am less ▁integration ▁of ▁tools ▁and ▁tool ▁ch ains ▁( control ▁and ▁data ▁integration ). ▁ ▁An ▁example ▁work ben ch ▁is ▁Microsoft ' s ▁Visual ▁Basic ▁programming ▁environment . ▁It ▁incorpor ates ▁several ▁development ▁tools : ▁a ▁GUI ▁builder , ▁smart ▁code ▁editor , ▁debugger , ▁etc . ▁Most ▁commercial ▁CASE ▁products ▁t ended ▁to ▁be ▁such ▁work ben ches ▁that ▁se am lessly ▁integrated ▁two ▁or ▁more ▁tools . ▁Work ben ches ▁also ▁can ▁be ▁class ified ▁in ▁the ▁same ▁manner ▁as ▁tools ; ▁as ▁foc using ▁on ▁Analysis , ▁Development , ▁Ver ification