Case study: The AgFur Sahuare Developmant Compary

APMy is a sofware development ctmpary that seciwliet in creating anal mobile applicotions. Aphy has done well at a busineus, hevirs ereated nore thas $50$ wrall noblie applicatiors for motile pentre that curtomers covif phene if they nended hetp with an nppllartion ar $4$ ene of we nokile apps had a mbake $($a fait$/$error$/$bus$)$ is it$,$ and had to be flaed.

The Aopur call cevtre needs a new infomatkes gystem. They have given yos $($the Thuthess Anahot$)$ the following irfomation regardirg the dana model.

Whea a CUSrCMER phoaes to report a faih in one of the moble asplications $($Pnobuct$),$ a CAEn: answen the phone and create a new TOXET, A ticket is a data rebord that contairs all the inlo abost the pooblem, so that it can be fixed. A antomer can phose wamy timec and thas have mary ticketh pontibly hane. A tichet belongi to only ene rustomer. A derk can creace many tichets, posibly none. A ticlet is cueated by are and ont eat derk.

A ticket wilt abo show which prodact $[$app$)$ the cultomer was unhaper wibh, ans the tocie wal be Fried to the dereloper $[$grogramrier$)$ who origiraly created the app. A product can have mamy tikhets linked to ik$,$ pessibly none $($ff so cushomers hawe complaned aboul M$.$ a ticket himed to one

Buminem Prscess Custbener reporti lauh in napbile applcatbon

The srimary butiness process perforned in the rall cevire is the grocesd Oumamer repots fauk in andeers the phone and ca$-$fries rhe contimer's identitr rumber by woing in in on the New Tleast screen. The clerk. thea aus the runtomer which pooduct is gWing a grobiem, and confoms the and then types tor the problem that the cuobower coptains gn to Mew Tidit icieen, aher the clerk number on the seteen, in aisering the ticket so an exwing developer $[$that mast to the problem! $($a$)$ and clobing on the tave batton $=$ which saes a new bibiet recout. The cleth aba the cirorrer if wey nese a relerence wumber for the coll$-$if ves, the tierk reads the ticket rumber to astartaticali, prints out as the process by filling the ticket document.

Draw a complete ERD in UML notation of the new apply system database described above. show all entities, relationships, keys, relationship names, directions and multiplicities. break up any relationships you identify.

write out the input$/$output model for the bysinesbusiness process "customer reports failfault in mobile application".

Draw the cross$-$functional flowchart$($swimlanes$)$ for the business process "customer reports fault in mobile application"