Object Oriented System Software Engineering (OOSSE) - CE00204-7

Page 1 of

Object Oriented System Software Engineering with Java

Individual Assignment
Weightage !"e co#rsewor$ is 0% of t"e assessment for t"e mod#&e' Learning Outcomes 1' (a)e a t"oro#g" $now&edge of one object orientated met"od down to detai&ed design' 2' (a)e t"e e*+erience to im+&ement an object oriented design in an object oriented &ang#age' Assessment Criteria I !O"#A$#% !"is is an indi)id#a& assignment, a&& s#bmitted com+onents m#st be yo#r own wor$ or a++ro+riate&y accredited' !"e assignment is scenario based (see attac"ed scenario)' -o# are enco#raged to ma$e any ass#m+tions yo# deem necessary w"en ana&ysing t"e re.#irements o#t&ined in t"e scenario, "owe)er, t"ese m#st be c&ear&y stated in t"e re+ort' -o#r re+ort s"o#&d address t"e fo&&owing t"ree tas$s/!as$ 1/0esign t"e system re.#ired #sing t"e 123 met"od' !as$ 2/Prod#ce a wor$ing +rototy+e of t"e system #sing 4a)a' !as$ 5/Objecti)e&y e)a&#ate yo#r so&#tion inc&#ding an a++raisa& of t"e s#itabi&ity of 123 and 4a)a as too&s for im+&ementing object oriented so&#tions' &eliverables -o# s"o#&d s#bmit a "ardco+y and an e&ectronic co+y of t"e assignment' !"e s#bmission s"o#&d not be &onger t"an 40 +ages inc&#ding diagrams b#t e*c&#ding t"e 6++endices' 7nstr#ctions on "ow to insta&& and r#n t"e +rogram s"o#&d be +ro)ided in an 6++endi*'

3e)e& 2

6sia Pacific 1ni)ersity of !ec"no&ogy and 7nno)ation (6P1)

2014

Object Oriented System Software Engineering (OOSSE) - CE00204-7

Page 2 of

'rading 8i&& be assigned #sing t"e fo&&owing g#ide/ !ass ( 'rade C )*+,9enera& S#bmission is of a semi-+rofessiona& standard wit" reasonab&e str#ct#re, a&& notations are syntactica&&y correct' 6 f#ndamenta& #nderstanding of Object Oriented 0esign is e)ident wit" t"e 123 met"od and tec"ni.#es a++ro+riate&y a++&ied' :e+ort is +rofessiona&&y +resented, s#itab&y str#ct#red, inde*ed and containing references and bib&iogra+"y' !as$ 1 !"e design is re+resentati)e of t"e so&#tion wit" a&& major 1se Cases c&ear&y identified and doc#mented' C&ass diagram(s) s"ow f#ndamenta& #nderstanding of a++ro+riate attrib#tes, met"ods and m#&ti+&icity for eac" c&ass identified' 6n attem+t is e)ident to inc&#de 7nteraction 0iagram (Se.#ence 0iagram etc')' 6n attem+t is e)ident to inc&#de State !ransition 0iagrams and;or 6cti)ity 0iagrams' !as$ 2 6c"ie)ed basic re.#irements as +er design (#se case diagram)' Code is a++ro+riate&y annotated and +rofessiona&&y +resented' !as$ 5 -o# dis+&ay a f#ndamenta& #nderstanding of Object Oriented 0esign' -o# dis+&ay some e)idence of additiona& reading in t"e s#bject area' 6++raisa& ade.#ate&y e)a&#ates t"e s#itabi&ity of t"e too&s' erit ( 'rade . )/+,!o ac"ie)e a 2erit, yo# m#st s#ccessf#&&y meet a&& of t"e criteria for a Pass and !as$ 1 2ost as+ects of t"e design are co)ered' 6&& a++ro+riate tec"ni.#es are #ti&ised in design i'e' in"eritance, enca+s#&ation and +o&ymor+"ism 6++&ication of at &east one (1) design +attern' !as$ 2 6&& major re.#irements of t"e so&#tion are im+&emented' Object oriented conce+t ref&ected in fina& so&#tion' !as$ 5 6 so#nd a++raisa& is s#bmitted ade.#ate&y s#++orted by e)idence of additiona& reading'

3e)e& 2

6sia Pacific 1ni)ersity of !ec"no&ogy and 7nno)ation (6P1)

2014

Object Oriented System Software Engineering (OOSSE) - CE00204-7

Page 5 of

6 good #nderstanding of t"e met"od is e)ident wit" strengt"s and wea$nesses critica&&y e)a&#ated' &istinction ( 'rade A )0+,!o ac"ie)e a 0istinction, yo# m#st s#ccessf#&&y meet a&& of t"e criteria for a 2erit and !as$ 1 !"e design is com+re"ensi)e identifying a&& of t"e re.#irements' 6++&ication of more t"an one design +attern' E)idence t"at yo# #nderstand and can a++ro+riate&y a++&y a&& major as+ects of 123' !as$ 2 !"e +rototy+e is +resented wit" some f#nctiona&ity and is correct as +er t"e c&asses s"own in t"e c&ass diagram' Co"erence between t"e design and t"e wor$ing +rototy+e' !as$ 5 6n objecti)e a++raisa& is s#bmitted s#++orted by reasoned arg#ments #nder+inned by so&id e)idence of additiona& reading'

3e)e& 2

6sia Pacific 1ni)ersity of !ec"no&ogy and 7nno)ation (6P1)

2014

Object Oriented System Software Engineering (OOSSE) - CE00204-7

Page 4 of

!roblem &escri1tion !"e software to be designed wi&& contro& a sim#&ated a#tomated te&&er mac"ine (6!2) "a)ing a magnetic stri+e reader for reading an 6!2 card, a c#stomer conso&e ($eyboard and dis+&ay) for interaction wit" t"e c#stomer, a s&ot for de+ositing en)e&o+es, a dis+enser for cas" (in m#&ti+&es of <20), a +rinter for +rinting c#stomer recei+ts, and a $ey-o+erated switc" to a&&ow an o+erator to start or sto+ t"e mac"ine' !"e 6!2 wi&& comm#nicate wit" t"e ban$=s com+#ter o)er an a++ro+riate comm#nication &in$' (!"e software on t"e &atter is not +art of t"e re.#irements for t"is +rob&em') !"e 6!2 wi&& ser)ice one c#stomer at a time' 6 c#stomer wi&& be re.#ired to insert an 6!2 card and enter a +ersona& identification n#mber (P7>) - bot" of w"ic" wi&& be sent to t"e ban$ for )a&idation as +art of eac" transaction' !"e c#stomer wi&& t"en be ab&e to +erform one or more transactions' !"e card wi&& be retained in t"e mac"ine #nti& t"e c#stomer indicates t"at "e;s"e desires no f#rt"er transactions, at w"ic" +oint it wi&& be ret#rned - e*ce+t as noted be&ow' !"e 6!2 m#st be ab&e to +ro)ide t"e fo&&owing ser)ices to t"e c#stomer/ 1' 6 c#stomer m#st be ab&e to ma$e a cas" wit"drawa& from any s#itab&e acco#nt &in$ed to t"e card, in m#&ti+&es of <20'00' 6++ro)a& m#st be obtained from t"e ban$ before cas" is dis+ensed' 2' 6 c#stomer m#st be ab&e to ma$e a de+osit to any acco#nt &in$ed to t"e card, consisting of cas" and;or c"ec$s in an en)e&o+e' !"e c#stomer wi&& enter t"e amo#nt of t"e de+osit into t"e 6!2, s#bject to man#a& )erification w"en t"e en)e&o+e is remo)ed from t"e mac"ine by an o+erator' 6++ro)a& m#st be obtained from t"e ban$ before +"ysica&&y acce+ting t"e en)e&o+e' 5' 6 c#stomer m#st be ab&e to ma$e a transfer of money between any two acco#nts &in$ed to t"e card' 4' 6 c#stomer m#st be ab&e to ma$e a ba&ance in.#iry of any acco#nt &in$ed to t"e card' 6 c#stomer m#st be ab&e to abort a transaction in +rogress by +ressing t"e Cance& $ey instead of res+onding to a re.#est from t"e mac"ine' !"e 6!2 wi&& comm#nicate eac" transaction to t"e ban$ and obtain )erification t"at it was a&&owed by t"e ban$' Ordinari&y, a transaction wi&& be considered com+&ete by t"e ban$ once it "as been a++ro)ed' 7n t"e case of a de+osit, a second message wi&& be sent to t"e ban$ indicating t"at t"e c#stomer "as de+osited t"e en)e&o+e' (7f t"e c#stomer fai&s to de+osit t"e en)e&o+e wit"in t"e timeo#t +eriod, or +resses cance& instead, no second message wi&& be sent to t"e ban$ and t"e de+osit wi&& not be credited to t"e c#stomer') 7f t"e ban$ determines t"at t"e c#stomer=s P7> is in)a&id, t"e c#stomer wi&& be re.#ired to re-enter t"e P7> before a transaction can +roceed' 7f t"e c#stomer is #nab&e to s#ccessf#&&y enter t"e P7> after t"ree tries, t"e card wi&& be +ermanent&y retained by t"e mac"ine, and t"e c#stomer wi&& "a)e to contact t"e ban$ to get it bac$'

3e)e& 2

6sia Pacific 1ni)ersity of !ec"no&ogy and 7nno)ation (6P1)

2014

Object Oriented System Software Engineering (OOSSE) - CE00204-7

Page

of

7f a transaction fai&s for any reason ot"er t"an an in)a&id P7>, t"e 6!2 wi&& dis+&ay an e*+&anation of t"e +rob&em, and wi&& t"en as$ t"e c#stomer w"et"er "e;s"e wants to do anot"er transaction' !"e 6!2 wi&& +ro)ide t"e c#stomer wit" a +rinted recei+t for eac" s#ccessf#& transaction, s"owing t"e date, time, mac"ine &ocation, ty+e of transaction, acco#nt(s), amo#nt, and ending and a)ai&ab&e ba&ance(s) of t"e affected acco#nt (?to? acco#nt for transfers)' !"e 6!2 wi&& "a)e a $ey-o+erated switc" t"at wi&& a&&ow an o+erator to start and sto+ t"e ser)icing of c#stomers' 6fter t#rning t"e switc" to t"e ?on? +osition, t"e o+erator wi&& be re.#ired to )erify and enter t"e tota& cas" on "and' !"e mac"ine can on&y be t#rned off w"en it is not ser)icing a c#stomer' 8"en t"e switc" is mo)ed to t"e ?off? +osition, t"e mac"ine wi&& s"#t down, so t"at t"e o+erator may remo)e de+osit en)e&o+es and re&oad t"e mac"ine wit" cas", b&an$ recei+ts, etc' !"e 6!2 wi&& a&so maintain an interna& &og of transactions to faci&itate reso&)ing ambig#ities arising from a "ardware fai&#re in t"e midd&e of a transaction' Entries wi&& be made in t"e &og w"en t"e 6!2 is started #+ and s"#t down, for eac" message sent to t"e @an$ (a&ong wit" t"e res+onse bac$, if one is e*+ected), for t"e dis+ensing of cas", and for t"e recei)ing of an en)e&o+e' 3og entries may contain card n#mbers and do&&ar amo#nts, b#t for sec#rity wi&& never contain a P7>' !"e 6!2 a&so a&&ows some of its f#nctiona&ities to be #sed by on&y ban$ e*ec#ti)es' 6!2 ban$ officers wi&& be ab&e to c"ec$ tota& de+osits of cas" and c"e.#e and tota& wit"drawa&s of cas" for eac" indi)id#a& 6!2 mac"ine as we&& a&& mac"ines' 6+art from t"at, t"e officers are a&so ab&e to $ee+ trac$ n#mber of transactions t"at were e*ec#ted +er day in an 6!2 mac"ine' 6 ban$ manager +erforms different f#nctiona&ities com+ared to ot"er ban$ officers s#c" as c"ec$ing remaining cas" in 6!2 mac"ines and +rinting tota& de+osits by cas" and c"e.#e and tota& wit"drawa&s of cas"' !"e manager is a&so ab&e to +erform a&& t"e acti)ities w"ic" 6!2 ban$ officers co#&d do'

3e)e& 2

6sia Pacific 1ni)ersity of !ec"no&ogy and 7nno)ation (6P1)

2014