Syllabus
Course Code: MS-20-23 Course Name: Object Oriented Analysis and Design using UML |
||
MODULE NO / UNIT | COURSE SYLLABUS CONTENTS OF MODULE | NOTES |
---|---|---|
1 | ModelingasaDesignTechnique: Principles of modeling, abstraction,encapsulation,modularity,hierarchy,typing,concurrency, persistence ofobjects,purposeofmodeling UML:Principlesofmodeling,UMLthings–structural,behavioral,grouping, annotational.Relationshipsin UML– dependency,association,generalization,realization.OverviewofUML diagrams, Mechanisms in the UML– specifications, adornments, common divisions, Extensibility mechanisms - stereotypes, tagged values, constraints, UML profiles, UML views. | |
2 | Class Modeling:Object &Class, Links &Associations, Generalization &Inheritance,Association Ends - scope,
visibility, Multiplicity,Rolenames,Ordering,bags & sequences, Qualified association,Aggregation,association
attributes &association classes, propagation of operations,Abstractclass, Metadata, reification, Constraints, derived
data, packages, elements of class diagrams, constructingclassdiagrams. StateModeling:Events,States,Transitions & Conditions, Activity Effects, Do-Activities, Entry & Exit Activities, CompletionTransitions, Sending Signal,Elements of Statediagrams,Nestedstatediagrams, signalgeneralization, concurrency, constructing state diagrams. |
|
3 | Use Case modeling: Actors, Use Cases, relationships - between actors, between use cases and between actor and use
case, elements of use case diagram, constructing use case diagrams. Interaction Modeling: Elements of sequence diagram and communication diagram, constructing sequence diagram and communication diagram Activity Modeling: Elements of activity diagram, constructing activity diagra |
|
4 | SystemAnalysis&design:Systemdevelopmentstages,systemconception,analysis, domainclassmodel, domain state
model,iteratingthe analysis. Applicationinteraction model, application class model, application state model, addingoperations SystemDesign:estimatingperformance,makeareuseplan,organizethesystemintosubsystem,identifying concurrency, allocating subsystems to processors and tasks, management of data stores, handling global resources, choosing software control strategies, handling boundary conditions, setting trade-off priorities, selectingan architectstyle. Class Design: bridging gap, realize use cases with operations, designing algorithms, design optimization, adjustmentofinheritance. |