Skip to content
JNTUK · B.Tech study libraryFree access · No sign-up
JNTUK B.Tech · legacy note archive

OOADR16 lecture note archive

Study the subject overview, then download the available files directly. No account, checkout or email address is required.

Regulation
R16
Semester
Not listed
Branch
CSE/IT
Availability
8 direct files
R16 FILE REGISTER

Files in this subject

8 files

Files open directly from jntukmaterials.com. If a file does not open, use the contact page and include this subject title.

Subject overview

Legacy page reference
Mobile reading view Subject overview
Saved only in this browser; no account is used.
Text
Colour
0% read

Object Oriented Analysis and Design using UML

OBJECTIVE:

• to know a way to solve complicated issues

• Analyze and style solutions to issues victimisation object minded approach • Study the notations of Unified Modeling Language

UNIT-I:

Introduction: The Structure of complicated systems, The Inherent complexness of software package, Attributes of complicated System, Organized and disorganised complexness, transportation Order to Chaos, coming up with complicated Systems, Evolution of Object Model, Foundation of Object Model, components of Object Model, Applying the thing Model.

UNIT-II:

categories and Objects: Nature of object, Relationships among objects, Nature of a category, Relationship among categories, interaction of categories and Objects, characteristic categories and Objects, Importance of correct Classification, characteristic categories and Objects, Key abstractions and Mechanisms.

UNIT-III:

Introduction to UML: Why we tend to model, abstract model of UML, design, Classes, Relationships, Common Mechanisms, category diagrams, Object diagrams.

UNIT-IV:

Basic activity Modeling: Interactions, Interaction diagrams, Use cases, Use case Diagrams, Activity Diagrams.

UNIT-V:

Advanced activity Modeling: Events and signals, state machines, processes and Threads, time and house, state chart diagrams.

UNIT-VI:

field Modeling: element, Deployment, element diagrams and preparation diagrams. Case Study: The Unified Library application.

OUTCOME:

• Ability to seek out solutions to the complicated issues victimisation object minded approach

• Represent categories, responsibilities and states victimisation UML notation

• determine categories and responsibilities of the matter domain

III Year – I Semester
L T P C
4 0 0 3

TEXT BOOKS:

one. “Object- minded Analysis and style with Applications”, Grady BOOCH, Robert A. Maksimchuk, Michael W. ENGLE, Bobbi J. Young, Jim Conallen, Kellia Houston, third edition, 2013, PEARSON.

2. “The Unified Modeling Language User Guide”, Grady Booch, James Rumbaugh, Ivar Jacobson, twelfth Impression, 2012, PEARSON.

REFERENCE BOOKS:

one. “Object-oriented analysis and style victimisation UML”, Mahesh P. Matha, PHI

  1. “Head 1st object-oriented analysis and design”, Brett D. McLaughlin, city Pollice, Dave West, O‟Reilly three. “Object-oriented analysis and style with the Unified process”, John W. Satzinger,Robert B. Jackson, Stephen D. Burd, Cengage Learning
  2. “The Unified modeling language Reference manual”, James Rumbaugh, Ivar Jacobson, Grady Booch, Addison-Wesley
Build the readable library

Did you create useful study material?

Send original or permissioned PDFs. Files stay private until they pass rights, quality and safety review.

Private review queue

Contribute material

R16 · CSE/IT OOAD

Your contribution will be attached to this page for administrator review.

PDF files
Permission and publication

Do not send textbook scans, publisher files, paid-course material, confidential information or somebody else's notes without written permission.

No account is created. Nothing is published automatically.