(w.e.

f 2015-16)

JNTUA College Of Engineering (Autonomous):: Anantapuram

Department of Computer Science & Engineering

MCA V Sem. T P C
4 0 4
15F05503 OBJECT ORIENTED ANALYSIS AND DESIGN

Course Objectives:

• Concisely define the following key terms: class, object, state, behavior, object class, class
diagram, object diagram, operation, encapsulation, constructor operation, query
operation, update operation, scope operation, association, association role, multiplicity,
association class, abstract class, concrete class, class-scope attribute, abstract operation,
method, polymorphism, overriding, multiple classification, aggregation, and composition.
• Describe the activities in the different phases of the object-oriented development life
cycle.
• State the advantages of object-oriented modeling vis-à-vis structured approaches.
• Compare and contrast the object-oriented model with the E-R and EER models.
• Model a real-world application by using a UML class diagram.
• Provide a snapshot of the detailed state of a system at a point in time using a UML
(Unified Modeling Language) object diagram.
• Recognize when to use generalization, aggregation, and composition relationships.
• Specify different types of business rules in a class diagram.

UNIT I
Introduction to UML: Importance of modeling, principles of modeling, object oriented
modeling, conceptual model of the UML, Architecture, Software Development Life Cycle.

UNIT II
Basic Structural Modeling: Classes, Relationships, common Mechanisms, and diagrams.
Advanced Structural Modeling: Advanced classes, advanced relationships, Interfaces, Types and
Roles, Packages.
Class & Object Diagrams: Terms, concepts, modeling techniques for Class & Object Diagrams.

UNIT III
Basic Behavioral Modeling-I: Interactions, Interaction diagrams.
Basic Behavioral Modeling-II: Use cases, Use case Diagrams, Activity Diagrams.

UNIT IV
Advanced Behavioral Modeling: Events and signals, state machines, processes and Threads,
time and space, state chart diagrams.
Architectural Modeling: Component, Deployment, Component diagrams and Deployment
diagrams.

UNIT V
(w.e.f 2015-16)

Patterns and Frameworks, Artifact Diagrams.Case Study: The Unified Library application

TEXT BOOKS:
1. Grady Booch, James Rumbaugh, Ivar Jacobson : The Unified Modeling Language User
Guide, Pearson Education 2nd Edition
2. Hans-Erik Eriksson, Magnus Penker, Brian Lyons, David Fado: UML 2 Toolkit,
WILEY-Dreamtech India Pvt. Ltd.

REFERENCE BOOKS:
1. Meilir Page-Jones: Fundamentals of Object Oriented Design in UML, Pearson Education.
2. Pascal Roques: Modeling Software Systems Using UML2, WILEY-Dreamtech India Pvt.
Ltd.
3. Atul Kahate: Object Oriented Analysis & Design, The McGraw-Hill Companies.
4. Mark Priestley: Practical Object-Oriented Design with UML,TMH.
5. Appling UML and Patterns: An introduction to Object – Oriented Analysis and Design
and Unified Process, Craig Larman, Pearson Education.
6. Object-Oriented Analysis and Design with the Unified Process By John W. Satzinger,
Robert B Jackson and Stephen D Burd, Cengage Learning.
7. UML and C++,R.C.Lee, and W.M.Tepfenhart,PHI.
8. Object Oriented Analysis,Design and Implementation,B.Dathan,S.Ramnath,Universities
Press.
9. OODesign with UML and Java,K.Barclay,J.Savage,Elsevier.
10. Learning UML 2.0,Russ Miles and Kim Hamilton,O’Reilly,SPD.
(w.e.f 2015-16)

JNTUA College Of Engineering (Autonomous):: Anantapuram

Department of Computer Science & Engineering

MCA. V Sem. T P C
0 4 2

15F05517 OBJECT ORIENTED ANALYSIS AND DESIGN LAB

Course Objectives:
Students are divided into batches of 5 each and each batch has to draw the following
diagrams using UML for an ATM system whose description is given below.
UML diagrams to be developed are:
1. Use Case Diagram.
2. Class Diagram.
3. Sequence Diagram.
4. Collaboration Diagram.
5. State Diagram
6. Activity Diagram.
7. Component Diagram
8. Deployment Diagram.
9. Test Design.
Description for an ATM System
The software to be designed will control a simulated automated teller machine (ATM) having a
magnetic stripe reader for reading an ATM card, a customer console (keyboard and display) for
interaction with the customer, a slot for depositing envelopes, a dispenser for cash (in multiples
of Rs. 100, Rs. 500 and Rs. 1000), a printer for printing customer receipts, and a key-operated
switch to allow an operator to start or stop the machine. The ATM will communicate with the
bank's computer over an appropriate communication link. (The software on the latter is not part
of the requirements for this problem.)
The ATM will service one customer at a time. A customer will be required to insert an
ATM card and enter a personal identification number (PIN) - both of which will be sent to the
bank for validation as part of each transaction. The customer will then be able to perform one or
more transactions. The card will be retained in the machine until the customer indicates that
he/she desires no further transactions, at which point it will be returned - except as noted below.
The ATM must be able to provide the following services to the customer:
1. A customer must be able to make a cash withdrawal from any suitable account linked to
the card, in multiples of Rs. 100 or Rs. 500 or Rs. 1000. Approval must be obtained from the
bank before cash is dispensed.
2. A customer must be able to make a deposit to any account linked to the card, consisting
of cash and/or checks in an envelope. The customer will enter the amount of the deposit into the
(w.e.f 2015-16)

ATM, subject to manual verification when the envelope is removed from the machine by an
operator. Approval must be obtained from the bank before physically accepting the envelope.
3. A customer must be able to make a transfer of money between any two accounts linked to
the card.
4. A customer must be able to make a balance inquiry of any account linked to the card.
5. A customer must be able to abort a transaction in progress by pressing the Cancel key
instead of responding to a request from the machine.
The ATM will communicate each transaction to the bank and obtain verification that it was
allowed by the bank. Ordinarily, a transaction will be considered complete by the bank once it
has been approved. In the case of a deposit, a second message will be sent to the bank indicating
that the customer has deposited the envelope. (If the customer fails to deposit the envelope
within the timeout period, or presses cancel instead, no second message will be sent to the bank
and the deposit will not be credited to the customer.)
If the bank determines that the customer's PIN is invalid, the customer will be required to re-
enter the PIN before a transaction can proceed. If the customer is unable to successfully enter the
PIN after three tries, the card will be permanently retained by the machine, and the customer will
have to contact the bank to get it back.
If a transaction fails for any reason other than an invalid PIN, the ATM will display an
explanation of the problem, and will then ask the customer whether he/she wants to do another
transaction.
The ATM will provide the customer with a printed receipt for each successful transaction
The ATM will have a key-operated switch that will allow an operator to start and stop the
servicing of customers. After turning the switch to the "on" position, the operator will be
required to verify and enter the total cash on hand. The machine can only be turned off when it is
not servicing a customer. When the switch is moved to the "off" position, the machine will shut
down, so that the operator may remove deposit envelopes and reload the machine with cash,
blank receipts, etc.

List of Tasks for which students have to design all UML diagrams:
1. Banking system
2. Online bookshop system
3. University Systems
4. Library management system
5. Hospital management system
6. Result processing system