08Object Oriented Analysis and Design

7/30/2019 08Object Oriented Analysis and Design

1/65

E.S.ENGINEERING COLLEGE08Object Oriented Analysis and Design-CS 2353

Course PlanUNIT 1.1

Department Name COMPUTER SCIENCE & ENGINEERING

Subject & Code 08Object Oriented

Analysis and Design-CS

2353

Name of the Faculty ThamilmaniV

Unit No 1 Unit Name Introduction to OOAD

Sub Unit No 1 Sub Unit Name Introduction to OOAD

Year/Sem 0 Class Strength -

Start Date End date

Text/Reference books Craig Larman "Applying UML and Patterns: An Introduction to Object-

Oriented Analysis and Design and Iterative Development",Third

Edition,pearson education.

Sl.No Topic Details1 Lesson Title Unit 1.1 -

Introduction to

OOAD

2 Sub Topic Unit 1.1.1 - what is

Analysis and

Design(10 Min)

Period No:1

Unit 1.1.2 - Concept

of OOAD(25 Min)

Period No:1

3 Lesson(Objectives) Define Analysis andDesign

Understand Analysis

and Design

4 Teaching Aids and

Teaching Methods

Black board and

chalk

5 Steps ( Step by step

details to Explain in

the class)

Unit 1.1.1 - what is

Analysis and

Design(10 Min)

Period No:1:

Analysis is an

investigation of the

problem and

requirements.

Example:Online

trading system

Design is conceptual

solution that fulfills

the requirements

rather than its


2/65


Course Plan

implementation

Example:Description

of a database

schema and

software objects

Unit 1.1.2 - Conceptof OOAD(25 Min)

Period No:1:

OOA (Object

oriented

Analysis)focuses on

analysis of

functional

requirements for

the system.

OOD(Object

oriented Design)takes analysis model

as input and

produces

implementation

specification.

6 Title of the Lab.

Practical/Assignment

Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson

UML Diagrams

7 Test Date & Time

(ex:- within two days

after the completion

of the lesson)

-

8 Dates for

communicating test

marks and review


after the test date)

-

9 Follow up /Remedies Including

revision classes ,

retest , assignments,

questions/answers,

review etc.

Revision classes/teston every Saturday

10 Date -

11 No. Of Students Signature with the


3/65


Course Plan

above 50 % date:


4/65


Course PlanUNIT 1.2




2353



Sub Unit No 2 Sub Unit Name What is OOAD?


Start Date End date




Sl.No Topic Details1 Lesson Title Unit 1.2 - What is OOAD?

2 Sub Topic Unit 1.2.1 - Object oriented analysis(10 Min) Period No:1,2

Unit 1.2.2 - Object oriented design(10 Min) Period No:2

Unit 1.2.3 - Define usecases(10 Min) Period No:2

Unit 1.2.4 - Define a Domain model(10 Min) Period No:2

Unit 1.2.5 - Assign object responsibilities and Draw Interaction

diagrams(5 Min) Period No:2,3

Unit 1.2.6 - Define Design class diagrams(5 Min) Period No:3

3 Lesson(Objectives) Define Object-Oriented Analysis and Design

Understand Object Oriented analysis and design

4 Teaching Aids andTeaching Methods

Black board and chalk



the class)

Unit 1.2.1 - Object oriented analysis(10 Min) Period No:1,2:

-An emphasis on finding and describing the objects or concepts in the

problem domain

Example:Flight information system.

Unit 1.2.2 - Object oriented design(10 Min) Period No:2:

An emphasis on defining software objects and how they collaborate to

fullfill the requirements

Example:Flight information system

Unit 1.2.3 - Define usecases(10 Min) Period No:2:

*Requirement analysis may include scenarios of how people use the

application.

*Use cases are not an Object-oriented artifact.

Unit 1.2.4 - Define a Domain model(10 Min) Period No:2:

*Domain model shows domain concepts or objects

*Domain model is not a description of software objects.


5/65


Course Plan

*Domain model is also called Conceptual object model.

Example:Dice game

Unit 1.2.5 - Assign object responsibilities and Draw Interaction

diagrams(5 Min) Period No:2,3:

*Object oriented design is concerned with defining software objects-

their responsibilities and collaborations.*Common notation to illustrate Collaborations is the sequence

diagram(kind of UML interaction diagram)

Unit 1.2.6 - Define Design class diagrams(5 Min) Period No:3:

*dynamic view of collaborating objects in interaction diagrams.

*Static view of the class definitions is usefully shown with a design

class diagram

6 Title of the Lab.


Topic /Seminars/

Guest Lectures/Industrial visits

relevant to the

lesson

UML Diagrams

7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review

(ex:- within two daysafter the test date)

-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.

Revision classes/test on every Saturday

10 Date -

11 No. Of Students

above 50 %

Signature with the date:


6/65


Course PlanUNIT 1.3




2353



Sub Unit No 3 Sub Unit Name What is the UML?


Start Date End date




Sl.No Topic Details1 Lesson Title Unit 1.3 - What is the UML?

2 Sub Topic Unit 1.3.1 - Three ways to apply UML(20 Min) Period No:3

Unit 1.3.2 - Three perspectives to apply UML(15 Min) Period No:3,4

Unit 1.3.3 - Meaning of class in different perspective(15 Min) Period

No:4

3 Lesson(Objectives) Understand UML concepts

Applying UML in different perspectives

Applying UML in different perspectives

4 Teaching Aids and

Teaching Methods


5 Steps ( Step by stepdetails to Explain in

the class)

Unit 1.3.1 - Three ways to apply UML(20 Min) Period No:3:UML as sketch- Informal and incomplete diagrams

UML as blueprint-detailed design diagrams used either for reverse

engineering and forward engineering

UML as programming language-Complete executable specification of a

software system in UML

Unit 1.3.2 - Three perspectives to apply UML(15 Min) Period No:3,4:

Conceptual perspective-describing things in a situation of the real

world or domain of interest.

Specification(software)perspective-describe software abstractions or

components with specification and interfaces.

Implementation(software) perspective

Unit 1.3.3 - Meaning of class in different perspective(15 Min) Period

No:4:

Conceptual class-real world concept or thing

software class-representing a specification or implementation

Implementation class-implemented in a specific OO language

6 Title of the Lab.


UML Diagrams


7/65


Course Plan

Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson

7 Test Date & Time(ex:- within two days


of the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,retest , assignments,

questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



8/65


Course PlanUNIT 1.4




2353



Sub Unit No 4 Sub Unit Name What are the Unified

process phases?


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 1.4 - What are the Unified process phases?

2 Sub Topic Unit 1.4.1 - Inception(10 Min) Period No:4

Unit 1.4.2 - Elaboration(10 Min) Period No:4

Unit 1.4.3 - Construction(10 Min) Period No:4,5

Unit 1.4.4 - Transition(10 Min) Period No:5

Unit 1.4.5 - UP disciplines(10 Min) Period No:5

3 Lesson(Objectives) Define fundamental concepts in the Unified process

4 Teaching Aids and

Teaching Methods



the class)

Unit 1.4.1 - Inception(10 Min) Period No:4:-Approximate vision,business case,scope,vague estimates.

Unit 1.4.2 - Elaboration(10 Min) Period No:4:

-refined vision,iterative implementation of the core

architecture,resolution of high risks,identification of most

requirements and scope,more realistic estimates.

Unit 1.4.3 - Construction(10 Min) Period No:4,5:

-iterative implementation of the remaining lower risk and easier

elements,and preparation for development.

Unit 1.4.4 - Transition(10 Min) Period No:5:

-beta tests,development

Unit 1.4.5 - UP disciplines(10 Min) Period No:5:

-Domain model artifact,to visualize concepts in the application domain.

-Use case model and specification artifacts to capture functional and

non-functional requirements

-design model artifacts,to design the software objects.

6 Title of the Lab.


Topic /Seminars/

UML Diagrams


9/65


Course Plan

Guest Lectures

/Industrial visits

relevant to the

lesson

7 Test Date & Time

(ex:- within two daysafter the completion

of the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,

retest , assignments,questions/answers,

review etc.

Revision classes /test on every Saturday

10 Date -

11 No. Of Students

above 50 %



10/65


Course PlanUNIT 1.5




2353



Sub Unit No 5 Sub Unit Name Case study-The

NextGen POS system


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 1.5 - Case study-The NextGen POS system

2 Sub Topic Unit 1.5.1 - NextGen POS System(50 Min) Period No:5,6

Unit 1.5.2 - Process sale Example(50 Min) Period No:6,7,8

3 Lesson(Objectives) Learning fundamental OOA/D, requirements analysis, UML and

patterns,rather than explaining the problems.

4 Teaching Aids and

Teaching Methods




the class)

Unit 1.5.1 - NextGen POS System(50 Min) Period No:5,6:

*a computerized application used to record the sales and handle

payments.*system used in retail shops for handling payments and sales.

*hardware components - computer,bar code reader,printer and

software to run the system.

Unit 1.5.2 - Process sale Example(50 Min) Period No:6,7,8:

*Usecase name

*Scope

*level

*primary actor

*stake holders and interests

*Preconditions

*Success Guarantee

*Main success scenario

*Extensions

*Special Requirements

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

UML Diagrams


11/65


Course Plan

/Industrial visits

relevant to the

lesson

7 Test Date & Time


after the completionof the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,review etc.


10 Date -

11 No. Of Students

above 50 %



12/65


Course PlanUNIT 1.6




2353



Sub Unit No 6 Sub Unit Name Inception


Start Date End date




Sl.No Topic Details1 Lesson Title Unit 1.6 - Inception

2 Sub Topic Unit 1.6.1 - what is Inception?(20 Min) Period No:8

Unit 1.6.2 - What happened in Inception?(25 Min) Period No:8,9

3 Lesson(Objectives) Define the inception step.

4 Teaching Aids and

Teaching Methods




the class)

Unit 1.6.1 - what is Inception?(20 Min) Period No:8:

What is the vision and business case for the project?

Feasible?

Buy and/or build?Rough unreliable range of cost: Is it $10K-100K or in the millions?

should we proceed or stop?

Unit 1.6.2 - What happened in Inception?(25 Min) Period No:8,9:

*a short requirements workshop

*most actors,goals,and use case named

*most use cases written in brief format

*most influential and risky quality requirements identified

*version one of the vision and specification written

*risk list

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson

UML Diagrams

7 Test Date & Time -


13/65


Course Plan



of the lesson)

8 Dates for

communicating test

marks and review(ex:- within two days


-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



14/65


Course PlanUNIT 1.7




2353



Sub Unit No 7 Sub Unit Name Usecase modeling


Start Date End date




Sl.No Topic Details1 Lesson Title Unit 1.7 - Usecase modeling

2 Sub Topic Unit 1.7.1 - Actors,scenarios,and Usecases(15 Min) Period No:9

Unit 1.7.2 - Usecases and usecase model(15 Min) Period No:9,10

Unit 1.7.3 - Three kinds of actors(10 Min) Period No:10

Unit 1.7.4 - Three common usecase formats(10 Min) Period No:10

3 Lesson(Objectives) Identify and write use cases.

Use brief,casual,and fully dressed formats, in an essential style.

Apply tests to identify suitable use cases.

Relate use case analysis to iterative development

4 Teaching Aids and

Teaching Methods




the class)

Unit 1.7.1 - Actors,scenarios,and Usecases(15 Min) Period No:9:

Actor-something with behavior,such as a person,computer system,or

organization.

Example:Cashier

Scenarios-a specific sequence of actions and interactions between

actors and the system(usecase instance).Example:Purchasing item with

cash

Unit 1.7.2 - Usecases and usecase model(15 Min) Period No:9,10:

Use cases are text documents not diagrams.

Use case modeling is an act of writing text, not drawing diagrams.

Unit 1.7.3 - Three kinds of actors(10 Min) Period No:10:

Primary actor has goals fulfilled through using services of the SUD

Example:the Cashier

Supporting actor provides service to the SUD.

Example:automated payment authorization service.

Offstage actor has an interest in the behavior of the use case,

Unit 1.7.4 - Three common usecase formats(10 Min) Period No:10:

Brief-one paragraph summary,usually of the main success scenario.

example:Process sale


15/65


Course Plan

Casual-Informal paragraph format.Multiple paragraphs that cover

various scenarios.

Example:Handle Returns

Fully dressed-All steps and variations

6 Title of the Lab.Practical/Assignment

Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson

UML Diagrams

7 Test Date & Time



of the lesson)

-

8 Dates forcommunicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -11 No. Of Students

above 50 %



16/65


Course PlanUNIT 1.8




2353



Sub Unit No 8 Sub Unit Name Relating usecases


Start Date End date




Sl.No Topic Details1 Lesson Title Unit 1.8 - Relating usecases

2 Sub Topic Unit 1.8.1 - Include relationships(10 Min) Period No:10

Unit 1.8.2 - Extend Relationships(15 Min) Period No:10,11

Unit 1.8.3 - Generalization(15 Min) Period No:11

Unit 1.8.4 - Terminology:Concrete,Abstract,Base,and Addition Use

Cases(10 Min) Period No:11

3 Lesson(Objectives) Relate use cases with include and external associations,in both text and

diagram formats.

4 Teaching Aids and

Teaching Methods



the class)

Unit 1.8.1 - Include relationships(10 Min) Period No:10:common to have some partial behavior that is common across several

use cases.

Example: Paying by credit includes process sale,Process

rental,Contribute to lay-away plan

Unit 1.8.2 - Extend Relationships(15 Min) Period No:10,11:

the idea to create an extending or addition use case, within it,describe

where and what condition it extends the behavior of some base use

case:

Example:Process sale

Unit 1.8.3 - Generalization(15 Min) Period No:11:

Generalization-Super class represents more general concepts.

Specialization-Sub class represents more specialized concepts

Unit 1.8.4 - Terminology:Concrete,Abstract,Base,and Addition Use

Cases(10 Min) Period No:11:

Concrete use case-initiated by actor and performs the entire behavior

desired by the actor.

Abstract use case -sub function use case that is part of another use

case.

Base use case- A use case that includes another usecase


17/65


Course Plan

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visitsrelevant to the

lesson

UML Diagrams

7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



18/65


Course PlanUNIT 2.1




2353


Unit No 2 Unit Name Elaboration

Sub Unit No 1 Sub Unit Name Elaboration


Start Date End date

Text/Reference books Craig Larman,"Applying UML and Patterns: An Introduction to object-oriented

Analysis and Design and iterative development.

Sl.No Topic Details

1 Lesson Title Unit 2.1 - Elaboration2 Sub Topic Unit 2.1.1 - Artifact in elaboration(10 Min) Period No:11,12

Unit 2.1.2 - Key ideas of elaboration(20 Min) Period No:12

Unit 2.1.3 - On to elaboration(10 Min) Period No:12

Unit 2.1.4 - Elaboration in one sentence(10 Min) Period No:12,13

3 Lesson(Objectives) Understand the concepts of elaboration phase

4 Teaching Aids and

Teaching Methods




the class)

Unit 2.1.1 - Artifact in elaboration(10 Min) Period No:11,12:

Domain model is prepared for modeling the domain concepts.

Design model is the collection of diagrams that represent the logical

design.Software architecture Document-key architectural issues are collected

in this document.

Data Model-Consist of

Unit 2.1.2 - Key ideas of elaboration(20 Min) Period No:12:

Each risk driven iteration must be time-boxed

Core and risky parts of the architecture must be designed step by step.

Test realistically

Get the feedback from users and developers and test the system

Develop most of the use cases

Unit 2.1.3 - On to elaboration(10 Min) Period No:12:

The core,risky architecture is progrmmed and tested.

The majority of requirements are discovered and stabilized

The major risks are mitigated or retired

Unit 2.1.4 - Elaboration in one sentence(10 Min) Period No:12,13:

Build the core architecture,resolve the high risk elements,define most

requirements,and estimate the overall schedule and resources.


19/65


Course Plan

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to thelesson

UML Activity Diagrams

7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



20/65


Course PlanUNIT 2.2




2353



Sub Unit No 2 Sub Unit Name Domain Models


Start Date End date



Sl.No Topic Details

1 Lesson Title Unit 2.2 - Domain Models2 Sub Topic Unit 2.2.1 - Creation of domain model(5 Min) Period No:13

Unit 2.2.2 - Why call a domain model a "Visual Dictionary"?(15 Min)

Period No:13

Unit 2.2.3 - Conceptual classes(5 Min) Period No:13

Unit 2.2.4 - Why create a domain moddel?(15 Min) Period No:13,14

Unit 2.2.5 - How to create a Domain model?(10 Min) Period No:14

3 Lesson(Objectives) Identify conceptual classes related to the current iteration

create an initial domain model

Model appropriate attributes and associations

4 Teaching Aids and

Teaching Methods




the class)

Unit 2.2.1 - Creation of domain model(5 Min) Period No:13:

Domain objects or conceptual classes.

Associations between conceptual classes

Attributes of conceptual classes.

Unit 2.2.2 - Why call a domain model a "Visual Dictionary"?(15 Min)

Period No:13:

Domain model is a visual dictionary of the abstractions,domain

vocabulary,and information content of the domain.

Unit 2.2.3 - Conceptual classes(5 Min) Period No:13:

Symbol- words or images representing a conceptual classes.

Intension-definition of a conceptual class.

Extension-set of examples to which the conceptual class applies.

Unit 2.2.4 - Why create a domain moddel?(15 Min) Period No:13,14:

Domain layer-Smalltalk objects representing business objects and logic.

Low representational gap-gap between our mental and software

objects.

Unit 2.2.5 - How to create a Domain model?(10 Min) Period No:14:

1.Find the conceptual classes.

2.Draw them as classes in a UML class diagram.


21/65


Course Plan

3.Add associations and attributes

6 Title of the Lab.


Topic /Seminars/


relevant to the

lesson


7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review


-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



22/65


Course PlanUNIT 2.3




2353



Sub Unit No 3 Sub Unit Name Finding conceptual

classes and description

classes


Start Date End date



Sl.No Topic Details

1 Lesson Title Unit 2.3 - Finding conceptual classes and description classes

2 Sub Topic Unit 2.3.1 - Finding conceptual classes(25 Min) Period No:14

Unit 2.3.2 - why use a Description classes?(20 Min) Period No:14,15

3 Lesson(Objectives)

Define conceptual class and description class

4 Teaching Aids and

Teaching Methods



details to Explain inthe class)

Unit 2.3.1 - Finding conceptual classes(25 Min) Period No:14:

Three strategies to find conceptual classes.1.Reuse or modify existing models.

2.Use a category list.

3.Identify noun phrases

Unit 2.3.2 - why use a Description classes?(20 Min) Period No:14,15:

A Description class contains information that describes something

For example ,a Product Description that records the price ,picture ,and

text descriptions of an item

A Product Description class records information about items

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson


7 Test Date & Time


-


23/65


Course Plan


of the lesson)

8 Dates for

communicating test

marks and review


-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



24/65


Course PlanUNIT 2.4




2353



Sub Unit No 4 Sub Unit Name Association and

attributes


Start Date End date



Sl.No Topic Details1 Lesson Title Unit 2.4 - Association and attributes

2 Sub Topic Unit 2.4.1 - Association(45 Min) Period No:15,16

Unit 2.4.2 - Attributes(50 Min) Period No:16,17

3 Lesson(Objectives) Understand relationship between classes

4 Teaching Aids and

Teaching Methods




the class)

Unit 2.4.1 - Association(45 Min) Period No:15,16:

Association-relationship between classes that indicates some

meaningful connections.

Multiplicity -how many instances of class A can be associated with one

instance of aclass

Unit 2.4.2 - Attributes(50 Min) Period No:16,17:

An attribute is a logical data value of an object.

Example

Sale needs a dateTime attribute

Store needs a name and address

Cahier needs an ID

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson


7 Test Date & Time



-


25/65


Course Plan

of the lesson)

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



26/65


Course PlanUNIT 2.5




2353



Sub Unit No 5 Sub Unit Name Domain model

refinement


Start Date End date



Sl.No Topic Details1 Lesson Title Unit 2.5 - Domain model refinement

2 Sub Topic Unit 2.5.1 - Domain model Refinement (45 Min) Period No:17,18

3 Lesson(Objectives) Analyze domain model

Understand domain model refinement

4 Teaching Aids and

Teaching Methods




the class)

Unit 2.5.1 - Domain model Refinement (45 Min) Period No:17,18:

The domain model is incrementally developed by considering concepts

in the requirements for this iteration.

Generalization is the activity of identifying commonality amongconcepts.

superclass(general concept) and subclass(specialized concept)

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson


7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review



-


27/65


Course Plan

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



28/65


Course PlanUNIT 2.6




2353



Sub Unit No 6 Sub Unit Name Finding conceptual class

hierarchies


Start Date End date



Sl.No Topic Details1 Lesson Title Unit 2.6 - Finding conceptual class hierarchies

2 Sub Topic Unit 2.6.1 - Conceptual class hierarchies(50 Min) Period No:18,19,20

3 Lesson(Objectives) Understand super class

And sub class

4 Teaching Aids and

Teaching Methods




the class)

Unit 2.6.1 - Conceptual class hierarchies(50 Min) Period No:18,19,20:

A conceptual superclass definition is more general or encompassing

than a subclass definition.

subclass has additonal attributes.subclass has additional associations of interest.

Superclass-commonality is identified among potential subclass.

Pay

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson


7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review


-


29/65


Course Plan


9 Follow up /

Remedies Including

revision classes ,


questions/answers,review etc.


10 Date -

11 No. Of Students

above 50 %



30/65


Course PlanUNIT 2.7




2353



Sub Unit No 7 Sub Unit Name Aggregation and

composition


Start Date End date



Sl.No Topic Details1 Lesson Title Unit 2.7 - Aggregation and composition

2 Sub Topic Unit 2.7.1 - Aggregation(20 Min) Period No:20

Unit 2.7.2 - Composition(30 Min) Period No:20,21

3 Lesson(Objectives) Understand aggregation and composition

4 Teaching Aids and

Teaching Methods




the class)

Unit 2.7.1 - Aggregation(20 Min) Period No:20:

Aggregation definition

- represents whole-part relationship.

Example:DVD Player

Unit 2.7.2 - Composition(30 Min) Period No:20,21:Compositions is also known as composite aggregation,is a strong kind

of whole-part aggregation and is useful to show in some models.

life time of the part is bound within the lifetime of the composite there

is a create-delete dependency of the part

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson


7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review

-


31/65


Course Plan



9 Follow up /

Remedies Including

revision classes ,


review etc.


10 Date -

11 No. Of Students

above 50 %



32/65


Course PlanUNIT 2.8




2353



Sub Unit No 8 Sub Unit Name Uml activity diagram

and modeling


Start Date End date



Sl.No Topic Details1 Lesson Title Unit 2.8 - Uml activity diagram and modeling

2 Sub Topic Unit 2.8.1 - Data flow modeling(30 Min) Period No:21,22

Unit 2.8.2 - Concurrent programming and parallel(20 Min) Period

No:22

3 Lesson(Objectives) Analyze Uml activity diagram and modeling

4 Teaching Aids and

Teaching Methods




the class)

Unit 2.8.1 - Data flow modeling(30 Min) Period No:21,22:

A UML Activity diagram shows sequential and parallel activities in a

process. They are useful for modeling business processes,work

flows,data flows,and complex algorithms.Initial state

Action state

Transition

Object

Fork

Join

End of activity

Unit 2.8.2 - Concurrent programming and parallel(20 Min) Period

No:22:

An activity diagram may have the following elements:

1. Activity states

2. Transitions

3. Decisions

6 Title of the Lab.


Topic /Seminars/



33/65


Course Plan

Guest Lectures

/Industrial visits

relevant to the

lesson

7 Test Date & Time


of the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,


review etc.


10 Date -

11 No. Of Students

above 50 %



34/65


Course PlanUNIT 3.1




2353


Unit No 3 Unit Name System sequence

diagrams

Sub Unit No 1 Sub Unit Name System Sequence

Diagrams


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 3.1 - System Sequence Diagrams

2 Sub Topic Unit 3.1.1 - System Sequence Diagrams (10 Min) Period No:22

Unit 3.1.2 - Need for Sequence diagrams(20 Min) Period No:22,23

Unit 3.1.3 - Elements of Sequence Diagrams(30 Min) Period No:23,24


agrams for use case scenarios.





the class)

Unit 3.1.1 - System Sequence Diagrams (10 Min) Period No:22:

System Sequence Diagrams

-SSD is a picture that shows, for one particular scenario of a use

case, the events that external actors generate, their order, and inter-

system events.

Unit 3.1.2 - Need for Sequence diagrams(20 Min) Period No:22,23:

Need for Sequence Diagram

-System events are an important part of analyzing system behavior.

-System behavior is a description of what a system does, without

explaining how it does it.

Unit 3.1.3 - Elements of Sequence Diagrams(30 Min) Period No:23,24:

Elements of Sequence Diagrams

-Time Line or Life Lin

-Message

-Box

-Activation Box


35/65


Course Plan

-Cross at bottom

6 Title of the Lab.


Topic /Seminars/Guest Lectures

/Industrial visits

relevant to the

lesson

Logical Architecture and UML Package Diagrams

7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review(ex:- within two days


-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



36/65


Course PlanUNIT 3.2




2353



diagrams

Sub Unit No 2 Sub Unit Name Relationship between

sequence diagrams and

use cas


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 3.2 - Relationship between sequence diagrams and use cas

2 Sub Topic Unit 3.2.1 - Relationship between sequence diagrams and use cases(45

Min) Period No:24,25


se scenarios.

identify the relationship b/w usecases and sequence diagrams.

4 Teaching Aids and

Teaching Methods

Blackboard and Chalk



the class)

Unit 3.2.1 - Relationship between sequence diagrams and use cases(45

Min) Period No:24,25:

Relationship between sequence diagrams and use cases:-

-SSD shows system events for one scenario of a use case.

-SSD is generated from inspection of a use case.

-SSDs are derived from use cases; they show one scenario.

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson


7 Test Date & Time


-


37/65


Course Plan


of the lesson)

8 Dates for

communicating test

marks and review


-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



38/65


Course PlanUNIT 3.3




2353



diagrams

Sub Unit No 3 Sub Unit Name Logical architecture and

UML package diagram


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 3.3 - Logical architecture and UML package diagram

2 Sub Topic Unit 3.3.1 - Logical architecture and Layers(50 Min) Period No:25,26

Unit 3.3.2 - Software architecture(5 Min) Period No:26

Unit 3.3.3 - Package diagrams(40 Min) Period No:26,27

Unit 3.3.4 - Design with layers(30 Min) Period No:27,28

Unit 3.3.5 - Model-View Separation principle(20 Min) Period No:28

Unit 3.3.6 - Connection between SSDs, System Operations and

Layers(10 Min) Period No:28,29


4 Teaching Aids and

Teaching Methods




the class)

Unit 3.3.1 - Logical architecture and Layers(50 Min) Period No:25,26:

Logical architecture and Layers

Logical architecture large-scale organization of the software classes

into packages, subsystems, and layers.

Layer - very coarse-grained grouping of classes, packages, or

subsystems.

User Interface

Application

Unit 3.3.2 - Software architecture(5 Min) Period No:26:

Software architecture

Set of significant decisions about organization of a software system.

The composition of structural and behavioral elements into larger

subsystems.


39/65


Course Plan

Unit 3.3.3 - Package diagrams(40 Min) Period No:26,27:

Package diagrams

Provides way to group elements

Dependency line-depended on package

Reverse-engineer package diagrams from code

UML approaches to show package nesting, using embedded packages,UML fully-qualified names, and circle-cross

Unit 3.3.4 - Design with layers(30 Min) Period No:27,28:

Design with layers

Benefits of using layers

Cohesive responsibilities

Mapping code organization to layers and UML packages

Domain layer Vs. Application logic layer; Domain objects

Relationship b/w Domain layer and Domain model

Tiers, Layers,

Unit 3.3.5 - Model-View Separation principle(20 Min) Period No:28:

Model-View Separation principle-Model is a synonym for the domain layer of objects

- View is a synonym for UI objects

Unit 3.3.6 - Connection between SSDs, System Operations and

Layers(10 Min) Period No:28,29:

Connection between SSDs, System Operations and Layers

-Identified input events from external actors into the system,

calling upon system operations.

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson


7 Test Date & Time



of the lesson)

-

8 Dates for

communicating testmarks and review



-

9 Follow up /

Remedies Including

revision classes ,




40/65


Course Plan

questions/answers,

review etc.

10 Date -

11 No. Of Students

above 50 %



41/65


Course PlanUNIT 3.4




2353



diagrams

Sub Unit No 4 Sub Unit Name Logical architecture

refinement


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 3.4 - Logical architecture refinement

2 Sub Topic Unit 3.4.1 - Collaborations with layers pattern(20 Min) Period No:29

Unit 3.4.2 - Information systems: three-tier architecture(15 Min) Period

No:29,30

Unit 3.4.3 - Model-View separation and upward communication(15

Min) Period No:30

3 Lesson(Objectives) ecture and layers patterns, including

inter-layer collaboration

architectural layers.

4 Teaching Aids and

Teaching Methods




the class)

Unit 3.4.1 - Collaborations with layers pattern(20 Min) Period No:29:

Collaborations with layers pattern

-Simple packages versus subsystem

-Facade

-Session Facades and the application layer

-Controller

-System operations and layer

Unit 3.4.2 - Information systems: three-tier architecture(15 Min) Period

No:29,30:

Information systems: three-tier architecture

Interface - windows, reports.

Application Logic task and rules

Storage persistent storage mechanism

Unit 3.4.3 - Model-View separation and upward communication(15


42/65


Course Plan

Min) Period No:30:

Model-View separation and upward communication

-Monitoring applications (telecommunication network

management)

-Simulation applications that requires visualization

(aerodynamics modeling)

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson


7 Test Date & Time(ex:- within two days


of the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,retest , assignments,

questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



43/65


Course PlanUNIT 3.5




2353



diagrams

Sub Unit No 5 Sub Unit Name UML class diagrams


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 3.5 - UML class diagrams

2 Sub Topic Unit 3.5.1 - Common class diagram notation/Design class diagram(10

Min) Period No:30

Unit 3.5.2 - Classifier/Attribute text and Association lines(15 Min)

Period No:30,31

Unit 3.5.3 - Notes, Comments, Constraints, and Method bodies(15

Min) Period No:31

Unit 3.5.4 - Stereotypes, Profiles, and Tags(10 Min) Period No:31

Unit 3.5.5 - UML Properties and Property Strings(10 Min) Period No:31

Unit 3.5.6 - Generalization, Abstract Classes, AbstractOperations/Dependency(10 Min) Period No:31,32

Unit 3.5.7 - Operations and Methods(15 Min) Period No:32

Unit 3.5.8 - Singleton classes/Template classes and

Interfaces/Template classes and Interfaces(15 Min) Period No:32


4 Teaching Aids and

Teaching Methods




the class)

Unit 3.5.1 - Common class diagram notation/Design class diagram(10

Min) Period No:30:

Common class diagram notation

Design class diagram

-Form part of the Design model

Unit 3.5.2 - Classifier/Attribute text and Association lines(15 Min)

Period No:30,31:

Classifier

Model element describes behavioral &structure features

Two classifiers

Classes and interfaces


44/65


Course Plan

Attribute text and Association lines

Attribute text notation

Association line notation

both

Unit 3.5.3 - Notes, Comments, Constraints, and Method bodies(15Min) Period No:31:

Notes, Comments, Constraints, and Method bodies

Note or comment- no semantic impact

Constraint- must be encased in braces {}

Method body- implementation of a UML operation

Unit 3.5.4 - Stereotypes, Profiles, and Tags(10 Min) Period No:31:

Stereotypes, Profiles, and Tags

Stereotypes- refinement of an existing modeling concept

Profile- collection of related stereotypes, tags, and constraints

Set of tags ,using attribute syntax

Unit 3.5.5 - UML Properties and Property Strings(10 Min) Period No:31:

UML Properties and Property Strings

Property- Characteristic of an element

Property string- {name1=value1,name2=value2}

{abstract, visibility=public}

Unit 3.5.6 - Generalization, Abstract Classes, Abstract

Operations/Dependency(10 Min) Period No:31,32:

Generalization, Abstract Classes, Abstract Operations

Generalization-taxonomic relationship b/w a more general

classifier and a more specific classifier

Abstract class & operations shown with an {abstract} tag

Dependency

Indicates a

Unit 3.5.7 - Operations and Methods(15 Min) Period No:32:

6.Operations and Methods

Operations

Methods in class diagrams

Operation issues

Create operation

Accessing operations

Unit 3.5.8 - Singleton classes/Template classes and

Interfaces/Template classes and Interfaces(15 Min) Period No:32:

Singleton classes

Only one instance of a class instantiated

Template classes and Interfaces

Templatized types

User-Defined Compartments


45/65


Course Plan

Added to class box

Active class

Class of an active object

Relationship b/w interaction

6 Title of the Lab.Practical/Assignment

Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson


7 Test Date & Time



of the lesson)

-

8 Dates forcommunicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -11 No. Of Students

above 50 %



46/65


Course PlanUNIT 3.6




2353



diagrams

Sub Unit No 6 Sub Unit Name UML interaction

diagrams


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 3.6 - UML interaction diagrams

2 Sub Topic Unit 3.6.1 - Sequence and communication diagram(10 Min) Period

No:32,33

Unit 3.6.2 - Common UML interaction diagram notation(10 Min) Period

No:33

Unit 3.6.3 - Basic sequence diagram notation(20 Min) Period No:33

Unit 3.6.4 - Basic communication diagram notation(20 Min) Period

No:33,34

3 Lesson(Objectives)notation-sequence & communication diagrams

4 Teaching Aids and

Teaching Methods




the class)

Unit 3.6.1 - Sequence and communication diagram(10 Min) Period

No:32,33:

1.Sequence and communication diagram

Strengths and weakness of sequence & communication

diagrams

Example: sequence diagram

Example: communication diagram

Unit 3.6.2 - Common UML interaction diagram notation(10 Min) Period

No:33:

2.Common UML interaction diagram notation

Participants with lifeline boxes

Basic message expression syntax

Singleton objects

Unit 3.6.3 - Basic sequence diagram notation(20 Min) Period No:33:


47/65


Course Plan

3.Basic sequence diagram notation

Lifeline boxes and lifelines

Messages

Focus of control and execution specification bars

Reply and returns

Messages to self or thisCreation of instances

Object lifelines and object destruction

Loo

Unit 3.6.4 - Basic communication diagram notation(20 Min) Period

No:33,34:

4.Basic communication diagram notation

Links

Messages

Messages to self or this

Creation of instances

Message number sequencingConditional messages

Mutually exclusive conditional paths

Iteration over a collection

Messages to cla

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson


7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Includingrevision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



48/65


Course Plan


49/65


Course PlanUNIT 4.1




2353


Unit No 4 Unit Name GRASP: Designing

Objects with

Responsibilities

Sub Unit No 1 Sub Unit Name GRASP: Designing

Objects with

Responsibilities


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 4.1 - GRASP: Designing Objects with Responsibilities

2 Sub Topic Unit 4.1.1 - Creator(45 Min) Period No:34,35

Unit 4.1.2 - Information expert(40 Min) Period No:35,36

Unit 4.1.3 - Low Coupling(45 Min) Period No:36,37

Unit 4.1.4 - Controller(45 Min) Period No:37,38

Unit 4.1.5 - High Cohesion(45 Min) Period No:38,39

3 Lesson(Objectives) Learn to apply five of the GRASP principles or patterns for OOD4 Teaching Aids and

Teaching Methods




the class)

Unit 4.1.1 - Creator(45 Min) Period No:34,35:

1.Creator

Name: Creator

Problem: Who creates an A?

Solution: Assign class B the responsibility to create an instance of class

A if one of these is true.

B contains or compositely aggregates A

B records A

B closely uses A

B has the initiali

Unit 4.1.2 - Information expert(40 Min) Period No:35,36:

2.Information expert

Name: Information expert

Problem: What is a basic principle by which to assign responsibilities to

objects?

Solution: Assign a responsibility to the class that has the information

needed to fulfill it.


50/65


Course Plan

Unit 4.1.3 - Low Coupling(45 Min) Period No:36,37:

3.Low Coupling

Name: Low Coupling

Problem: How to reduce the impact of change?

Solution: Assign responsibilities so that coupling remains low. use thisprinciple to evaluate alternatives.

Unit 4.1.4 - Controller(45 Min) Period No:37,38:

4.Controller

Name: Controller

Problem: what first object beyond the UI layer receives and

coordinates a system operation?

Solution: Assign responsibility to an object representing one of these

choices

Represents the overall system, a root

Unit 4.1.5 - High Cohesion(45 Min) Period No:38,39:5.High Cohesion

Name: High cohesion

Problem: How to keep objects focused, understandable, and

manageable, and as a side effect, support low coupling?

Solution: Assign responsibilities so that cohesion remains high. Use this

to evaluate alternative

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson

Applying GoF Design patterns

7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -


51/65


Course Plan

11 No. Of Students

above 50 %



52/65


Course PlanUNIT 4.2




2353



Objects with

Responsibilities

Sub Unit No 2 Sub Unit Name Designing for visibility


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 4.2 - Designing for visibility

2 Sub Topic Unit 4.2.1 - Visibility between Objects(20 Min) Period No:39,40

Unit 4.2.2 - What is visibility?(30 Min) Period No:40,41

3 Lesson(Objectives) Identify four kinds of visibility

Design to establish visibility

4 Teaching Aids and

Teaching Methods



the class)

Unit 4.2.1 - Visibility between Objects(20 Min) Period No:39,40:1.Visibility between Objects

-Sender object to send a message to a receiver

-Sender must be visible to the receiver

-Sender must have some kind of reference or pointer to the

receiver object.

Unit 4.2.2 - What is visibility?(30 Min) Period No:40,41:

2.What is visibility?

Attribute visibility B is an attribute of A

Parameter visibility- B is a parameter of a method of A

Local visibilityB is a local object in a method of A.

Global visibility-B is in some way globally visible

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits



53/65


Course Plan

relevant to the

lesson

7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



54/65


Course PlanUNIT 4.3




2353



Objects with

Responsibilities

Sub Unit No 3 Sub Unit Name Applying GoF Design

Patterns


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 4.3 - Applying GoF Design Patterns

2 Sub Topic Unit 4.3.1 - Adapter(50 Min) Period No:41,42

Unit 4.3.2 - Singleton(50 Min) Period No:42,43

Unit 4.3.3 - Factory(50 Min) Period No:43,44

Unit 4.3.4 - Observer pattern(50 Min) Period No:44,45,46

3 Lesson(Objectives) Introduce and apply some GoF design patterns

Show GRASP principle as a generalization of other design patterns

4 Teaching Aids and

Teaching Methods




the class)

Unit 4.3.1 - Adapter(50 Min) Period No:41,42:

1. Adapter(GoF)

Name: Adapter

Problem: How to resolve incompatible interfaces, or provide a stable

interface to similar components with different interfaces?

Solution: Convert the original interface of a component into another

interface, through

Unit 4.3.2 - Singleton(50 Min) Period No:42,43:

2.Singleton

Name: Singleton

Problem: Exactly one instance of a class is allowed- it is a singleton.

Objects need a global and single point of access.

Solution: Define a static method of the class that returns the singleton

Unit 4.3.3 - Factory(50 Min) Period No:43,44:

3.Factory


55/65


Course Plan

Advantages:

Separate the responsibility of complex creation into cohesive helper

objects

Hide potentially complex xreation logic

Unit 4.3.4 - Observer pattern(50 Min) Period No:44,45,46:4.Observer pattern

Name: Observer

Problem: Different kinds of subscriber objects are interested in the

state changes or events of a publisher object

Solution: Define a subscriber or listener interface.

6 Title of the Lab.


Topic /Seminars/


relevant to the

lesson


7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review


-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



56/65


Course PlanUNIT 5.1




2353


Unit No 5 Unit Name UML state diagrams

modeling

Sub Unit No 1 Sub Unit Name UML state diagrams

modeling


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 5.1 - UML state diagrams modeling

2 Sub Topic Unit 5.1.1 - Definition: Events, States, and Transitions(20 Min) Period

No:46

Unit 5.1.2 - Apply State Machine Diagrams(20 Min) Period No:46,47

Unit 5.1.3 - UML State Machine Diagram notation(10 Min) Period

No:47

3 Lesson(Objectives) machine diagram notation, with examples, and

various modeling applications





the class)

Unit 5.1.1 - Definition: Events, States, and Transitions(20 Min) Period

No:46:

1.Definition: Events, States, and Transitions

Event-Significant occurrence

State-condition of an object at a moment in time

Transition-relationship between two states

Unit 5.1.2 - Apply State Machine Diagrams(20 Min) Period No:46,47:

Apply State Machine Diagrams

State-Independent and State-Dependent Objects

Modeling State-dependent Objects

Complex Reactive Objects

Physical devices

Transactions

Role Mutators

Protocols and Legal Sequences

Communication protocols

UI page/window flow


57/65


Course Plan

UI flow controllers or sessions

Use case system operations

Individual UI window Event handling

Unit 5.1.3 - UML State Machine Diagram notation(10 Min) Period

No:47:UML State Machine Diagram notation

Transition Actions and Guards

Nested States

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson

UML State Diagrams

7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review



-

9 Follow up /

Remedies Includingrevision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



58/65


Course PlanUNIT 5.2




2353



modeling

Sub Unit No 2 Sub Unit Name Operation contracts


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 5.2 - Operation contracts

2 Sub Topic Unit 5.2.1 - Sections of a Contract(25 Min) Period No:47,48

Unit 5.2.2 - System Operation(25 Min) Period No:48

Unit 5.2.3 - Post conditions(15 Min) Period No:48,49

Unit 5.2.4 - How to create and write Contracts(35 Min) Period No:49

Unit 5.2.5 - Operations, Contracts, and the OCL(20 Min) Period

No:49,50

Unit 5.2.6 - Operation Contracts within the UP(25 Min) Period No:50,51

3 Lesson(Objectives) Define System Operations

Create contracts for system operations

4 Teaching Aids and

Teaching Methods




the class)

Unit 5.2.1 - Sections of a Contract(25 Min) Period No:47,48:

Sections of a Contract

Operation

Cross References

Preconditions

Post conditions

Unit 5.2.2 - System Operation(25 Min) Period No:48:

System Operation

System operations - system as a black box component

System events events or I/O messages relative to the system

Unit 5.2.3 - Post conditions(15 Min) Period No:48,49:

Post conditions

Instance creation and deletion

Attribute change of value


59/65


Course Plan

Associations formed and broken

Unit 5.2.4 - How to create and write Contracts(35 Min) Period No:49:

How to create and write Contracts

Identify system operations from SSDs

For system operations that are complex and perhaps subtle in theirresults, or which are not clear in the use case, construct a contract.

To describe post conditions, use following categories:

Instance creation and deletion

Attribute modification

Associations formed and broken

Unit 5.2.5 - Operations, Contracts, and the OCL(20 Min) Period

No:49,50:

Operations, Contracts, and the OCL

Operation contracts expressed with the OCL

OCL defines format for specifying pre-post conditions foroperations

Unit 5.2.6 - Operation Contracts within the UP(25 Min) Period

No:50,51:

Operation Contracts within the UP

Inception phase

Elaboration phase

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson

UML State Diagrams

7 Test Date & Time



of the lesson)

-

8 Dates for

communicating test

marks and review


-

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.



60/65


Course Plan

10 Date -

11 No. Of Students

above 50 %



61/65


Course PlanUNIT 5.3




2353



modeling

Sub Unit No 3 Sub Unit Name Mapping design to code


Start Date End date




Sl.No Topic Details

1 Lesson Title Unit 5.3 - Mapping design to code

2 Sub Topic Unit 5.3.1 - Programming and iterative , Evolutionary Development(10

Min) Period No:51

Unit 5.3.2 - Mapping Designs to code(10 Min) Period No:51

Unit 5.3.3 - Creating class Definitions from DCDs(10 Min) Period No:51

Unit 5.3.4 - Creating Methods from Interaction Diagrams(10 Min)

Period No:51,52

Unit 5.3.5 - Collection classes in code(10 Min) Period No:52

Unit 5.3.6 - Exceptions Error Handling(10 Min) Period No:52

Unit 5.3.7 - Defining the Sale.makeLineItem Method(10 Min) PeriodNo:52

Unit 5.3.8 - Order of Implementation(10 Min) Period No:52,53

Unit 5.3.9 - Test-Driven or Test-First Development(10 Min) Period

No:53

3 Lesson(Objectives) Map design artifacts to code in an object-oriented language.

4 Teaching Aids and

Teaching Methods




the class)

Unit 5.3.1 - Programming and iterative , Evolutionary Development(10

Min) Period No:51:

Programming and iterative , Evolutionary Development

Creativity and change during implementation

Unit 5.3.2 - Mapping Designs to code(10 Min) Period No:51:

Mapping Designs to code

Class and interface definitions

Method definitions

Unit 5.3.3 - Creating class Definitions from DCDs(10 Min) Period No:51:

Creating class Definitions from DCDs


62/65


Course Plan

Defining a class with method signatures and attributes

Unit 5.3.4 - Creating Methods from Interaction Diagrams(10 Min)

Period No:51,52:

Creating Methods from Interaction Diagrams

An interaction diagram translates to a series of statements inmethod definitions

Unit 5.3.5 - Collection classes in code(10 Min) Period No:52:

Collection classes in code

One-to-many relationships are common

Unit 5.3.6 - Exceptions Error Handling(10 Min) Period No:52:

Exceptions Error Handling

Exceptions can be indicated in property strings of messages and

operation declarations

Unit 5.3.7 - Defining the Sale.makeLineItem Method(10 Min) PeriodNo:52:

Defining the Sale.makeLineItem Method

Method of class sale

Unit 5.3.8 - Order of Implementation(10 Min) Period No:52,53:

Order of Implementation

Implemented from least coupled to most coupled

Unit 5.3.9 - Test-Driven or Test-First Development(10 Min) Period

No:53:

Test-Driven or Test-First Development

Unit testing code is written before the code to be tested

6 Title of the Lab.


Topic /Seminars/

Guest Lectures

/Industrial visits

relevant to the

lesson

UML State Diagrams

7 Test Date & Time


of the lesson)

-

8 Dates for

communicating test

marks and review



-


63/65


Course Plan

9 Follow up /

Remedies Including

revision classes ,


questions/answers,

review etc.


10 Date -

11 No. Of Students

above 50 %



64/65


Course PlanUNIT 5.4




2353



modeling

Sub Unit No 4 Sub Unit Name UML deployment and

component diagrams


Start Date End date

Text/Reference books Craig Larman "Applying UML and Patterns: An Introduction to

08Object Oriented Analysis and Design

Documents

Transcript of 08Object Oriented Analysis and Design