Lesson Plan Ooad

download Lesson Plan Ooad

of 3

Transcript of Lesson Plan Ooad

  • 8/12/2019 Lesson Plan Ooad

    1/3

    Bharath Niketan Engineering College, Aundipatty 625 536

    Department of Information e!hnology

    Format No: BNEC"2#$3%$&"I"'(")I

    'E**+N ('AN

    Subject Code and Name: C*2353 +BEC +-IENED ANA'.*I* AND DE*I/N

    Class : III year IT

    Name of the Faculty, Designation & Dept: !"#$%'T(, ", IT

    +01e!tie4

    To learn basic )) analysis and design s*ills through an elaborate case study

    To identify conceptual classes related to the current iteration, creating and modeling

    the domain model

    To use the +%' interaction diagrams to identify system eents and to create system

    se-uence diagrams for the use case scenarios To apply the appropriate design patterns

    To introduce +%' state diagram notations .ith e/amples and arious modeling

    applications

    +ut!ome4

    bility to understand the arious +%' %odeling

    bility to understand the basic principle of 0#S" "atterns

    bility to Design and implement a reusable soft.are code

    bility to Identify and Sole problems in such a .ay as to proe that they hae made

    a responsible choice, based on critical and creatie thin*ing

    (re!ri0ed tet Book4

    %$ Craig 'arman,1pplying +%' and "atterns: n Introduction to object2oriented

    nalysis and Design and iteratie deelopment3, Third $dition, "earson $ducation,

    4556

    -eferen!e Book4

    -%$%i*e )7Docherty, 8)bject2)riented nalysis & Design: +nderstanding System

    Deelopment .ith +%' 453, 9ohn iley & Sons, 4556

    -%2 9ames 2 Cooper, ddison2esley, 89aa Design "atterns ; Tutorial3, 4555

    -%3 %icheal ??6

    7NI%I arget 8our4 #9

    *l No

    No of

    hour

    re:uired

    opi! to 0e !oered;ode of

    ea!hingBook

    (age

    No

    > > Introduction to ))D >2@

    4 > hat is ))D =2AB > hat is +%' >>2>

    > hat are the +nified "rocess "hases >=2B?

    Page 1 of 3

  • 8/12/2019 Lesson Plan Ooad

    2/3

    6 > Case Study2Ne/t 0en "os System >2B

    @ > Inception =26>

    = > +se Case %odeling22?4

    A > +se Case %odeling2$/amples ?B2?A

    ?> #elating use cases2Include, $/tend and

    0eneraliation ?B2??

    7NI%II arget 8our4 #9

    >5 > $laboration >4B2>B5

    >> > Domain %odels >B>2>B=

    >4 >Finding Conceptual & Description

    Classes

    >B?2>B

    >B > ssociations, ttributes >?2>@A

    > > Domain %odel #efinement 65>26B4

    >6 > Finding Conceptual Class (ierarchies >B?2>B

    >@ > ggregation 6>?

    >= > Composition 645

    >A > +%' ctiity diagrams & %odeling ==2A

    7NI%III arget 8our4 #9

    >? >System se-uence diagrams ESSDs ;

    Introduction, %otiation

    >=B2>==

    45 >#elation bet.een SSDs and use cases >==2>A5

    4> >'ogical architecture 2 'ayers, Soft.are

    rchitecture

    >?=2455

    44 >+%' "ac*age diagrams 45>24>4

    4B >'ogical architecture refinement 6?26=A

    4 >

    +%' interaction diagrams 2 Se-uence

    and Communication diagrams, Strengths

    and .ea*ness, Notation

    44>245

    46 >+%' class diagrams ; Introduction,

    Notation, designing class diagram,

    Classifier

    4?2464

    4@ >+%' class diagrams 2)perations and

    methods, #elationships

    464246@

    4= >+%' class diagrams ; $/amples 46@24=5

    7NI%I) arget 8our4 #9

    4A >0#S"2Designing objects .ith

    #esponsibilities

    4==24?>

    4? > Creator, Information e/pert, 'o.

    coupling

    4?>2B54

    B5 > Controller B542B>

    B> > (igh Cohesion B>2B>A

    B4 > Designing for !isibility B@B2B@A

    BB > pplying 0of Design "atterns B62B@

    B > dapter, Singleton B@25

    B6 > Factory "atterns 524

    B@ > )bserer "atterns @>2=>

    7NI%) arget 8our4 #9

    B= > +%' State Diagrams and $/amples of +%' State %odeling A@2?4B? > )peration Contracts >A>2>?>

    5 > %apping Design to Code B@?2B?5

    Page 2 of 3

  • 8/12/2019 Lesson Plan Ooad

    3/3

    > > +%' Deployment2

    4 > $/amples of +%' Deployment diagrams @64

    B > +%' Component %odeling a Component Interface @6

    6 > +%' Component diagrams2$/amples @62@66

    et and Eam4

    Sl No Name of the $/am "ortions Tentatie schedule

    > Internal Test I I Efull & II E>sthalf unit >=54> to 4454>

    4 Internal Test II II E4nd half & III Efull unit >=5B> to 445B>

    B %odel $/am ll fie units >65> to 4>5>

    Aignment4

    Sl NoNo of

    ssignmentsTopics

    Date of

    ssign

    gien

    Submission

    Date

    > ssignment I Implement %onopoly 0ame system >=5>> 45>>

    4 ssignment II Different relationship of Class Diagram 5=54> >54>

    B ssignment III Comparison SSD & Collaboration Diagram 5@5B> >B5B>

    ssignment I! Compare Different "atterns 45@> B>5B>

    6 ssignment !Conference %anagement Implementation

    Diagram

    5B5> >55>

    Prepared by Approved by