▁might ▁be ▁divided ▁into ▁several ▁sub tasks ▁( or ▁domains ), ▁each ▁representing ▁a ▁different ▁business , ▁techn ological , ▁or ▁other ▁areas ▁of ▁interest . ▁ ▁Each ▁sub task ▁would ▁be ▁analyz ed ▁separately . ▁ ▁Im plementation ▁constraints , ▁( e . g ., ▁conc urrency , ▁distribution , ▁pers istence , ▁or ▁how ▁the ▁system ▁is ▁to ▁be ▁built ) ▁are ▁not ▁considered ▁during ▁the ▁analysis ▁phase ; ▁rather , ▁they ▁are ▁addressed ▁during ▁object - orient ed ▁design ▁( O OD ). ▁ ▁The ▁concept ual ▁model ▁that ▁results ▁from ▁O O A ▁will ▁typically ▁consist ▁of ▁a ▁set ▁of ▁use ▁cases , ▁one ▁or ▁more ▁U ML ▁class ▁diag rams , ▁and ▁a ▁number ▁of ▁interaction ▁diag rams . ▁It ▁may ▁also ▁include ▁some ▁kind ▁of ▁user ▁interface ▁mock - up . ▁ ▁The ▁input ▁for ▁object - orient ed ▁design ▁is ▁provided ▁by ▁the ▁output ▁of ▁object - orient ed ▁analysis . ▁Real ize ▁that ▁an ▁output ▁artifact ▁does ▁not ▁need ▁to ▁be ▁completely ▁developed ▁to ▁serve ▁as ▁input ▁of ▁object - orient ed ▁design ; ▁analysis ▁and ▁design ▁may ▁occur ▁in ▁parallel , ▁and ▁in ▁practice ▁the ▁results ▁of ▁one ▁activity ▁can ▁feed ▁the ▁other ▁in ▁a ▁short ▁feedback ▁cycle ▁through ▁an ▁iter ative ▁process . ▁Both ▁analysis ▁and ▁design ▁can ▁be ▁performed ▁increment ally , ▁and ▁the ▁artifact s ▁can ▁be ▁continu ously ▁grown ▁instead ▁of ▁completely ▁developed ▁in ▁one ▁shot . ▁ ▁Some ▁typical ▁( but ▁common ▁to ▁all ▁types ▁of ▁design ▁analysis )