Object Type Questions Roy Antony Arnold G Teaching Associate Dept. of Computer Science & Engg. Arunai Engineering College Tiruvannamalai

SSD is a picture that shows for a particular scenario of a use case the events that external actors generate, their order and inter-system events. SSDs are part of the Use-Case Model. SSDs can also be used to illustrate collaborations between systems. System events and their associated system operations can be expressed in terms of the physical input medium or interface widget level. An SSD should be done for the main success scenario of the use case and frequent or complex alternative scenarios. It is sometimes desirable to show at least fragments of the use case text for the scenario to enhance the two views

SSD is a picture that shows for a particular scenario of a use case the events that external actors generate, their order and inter-system events.

SSDs are part of the Use-Case Model.

SSDs can also be used to illustrate collaborations between systems.

System events and their associated system operations can be expressed in terms of the physical input medium or interface widget level.

An SSD should be done for the main success scenario of the use case and frequent or complex alternative scenarios.

It is sometimes desirable to show at least fragments of the use case text for the scenario to enhance the two views

Interaction Diagrams Activity Diagrams Use Cases State Diagrams Class Diagrams

Interaction Diagrams

Activity Diagrams

Use Cases

State Diagrams

Class Diagrams

Interaction Diagrams Activity Diagrams Package Diagrams State Diagrams Class Diagrams

Interaction Diagrams

Activity Diagrams

Package Diagrams

State Diagrams

Class Diagrams

Interaction Diagrams Activity Diagrams Package Diagrams State Diagrams Class Diagrams

Interaction Diagrams

Activity Diagrams

Package Diagrams

State Diagrams

Class Diagrams

Analyzing a use case Understanding workflow Describing a complicated sequential algorithm Dealing with multithreaded applications Procedural flow of control Representing complex conditional logic

Analyzing a use case

Understanding workflow

Describing a complicated sequential algorithm

Dealing with multithreaded applications

Procedural flow of control

Representing complex conditional logic

Sequence Diagrams Collaboration Diagrams Deployment Diagrams Package Diagrams

Sequence Diagrams

Collaboration Diagrams

Deployment Diagrams

Package Diagrams

Coincidental Cohesion Temporal Cohesion Procedural Cohesion Functional Cohesion

Coincidental Cohesion

Temporal Cohesion

Procedural Cohesion

Functional Cohesion

Interaction Diagrams Activity Diagrams Package Diagrams State Diagrams Class Diagrams

Interaction Diagrams

Activity Diagrams

Package Diagrams

State Diagrams

Class Diagrams

Activity Diagrams Package Diagrams State Diagrams Class Diagrams Sequence Diagrams

Activity Diagrams

Package Diagrams

State Diagrams

Class Diagrams

Sequence Diagrams

Activity Diagrams Package Diagrams State Diagrams Class Diagrams Sequence Diagrams

Activity Diagrams

Package Diagrams

State Diagrams

Class Diagrams

Sequence Diagrams

shows behavior with control structure can show many objects over many uses can show many objects in a single use case or implementation of method encourages parallel behavior All of the above "a", "b" and "d" only

shows behavior with control structure

can show many objects over many uses

can show many objects in a single use case or implementation of method

encourages parallel behavior

All of the above

"a", "b" and "d" only

Actions are associated with transition and are considered to be processes that occur quickly and are not interruptible. Actions are associated with transition and are considered to be processes that occur quickly and are interruptible. Activities are associated with states and can take longer. An activity may be interrupted by some event. Activities are associated with transition that occur quickly and are not interruptible. Activities are associated with states and can take longer. An activity cannot be interrupted by any event.

Actions are associated with transition and are considered to be processes that occur quickly and are not interruptible.

Actions are associated with transition and are considered to be processes that occur quickly and are interruptible.

Activities are associated with states and can take longer. An activity may be interrupted by some event.

Activities are associated with transition that occur quickly and are not interruptible.

Activities are associated with states and can take longer. An activity cannot be interrupted by any event.

From nouns in a text description Look for units of interaction Look for places where things or objects come to rest Interview Domain Experts. All of the above "a" , "b" and "c" only "a" and "c" only

From nouns in a text description

Look for units of interaction

Look for places where things or objects come to rest

Interview Domain Experts.

All of the above

"a" , "b" and "c" only

"a" and "c" only

Model A Model B Model A or Model B None of the above MODEL A DIAGRAM MODEL B

Model A

Model B

Model A or Model B

None of the above

Model P1 Model P2 Model P3 MODEL P1 MODEL P2 MODEL P3

Model P1

Model P2

Model P3

Female, Patient, Nurse Male, Physiotherapist Female, Patient Female, Doctor, Surgeon Patient, Doctor Male, Doctor, Nurse

Female, Patient, Nurse

Male, Physiotherapist

Female, Patient

Female, Doctor, Surgeon

Patient, Doctor

Male, Doctor, Nurse

Use case driven Data driven Responsibility driven All of the above "a" and "c" only "b" and "c" only

Use case driven

Data driven

Responsibility driven

All of the above

"a" and "c" only

"b" and "c" only

book, journal, copy (of book), library member, member of staff item, copy (of book), library member, member of staff item, library member, member of staff system, rule, week, item, member

book, journal, copy (of book), library member, member of staff

item, copy (of book), library member, member of staff

item, library member, member of staff

system, rule, week, item, member

a list of classes another Package diagram class diagram All of the above "b" and "c" only "a" and "b" only

a list of classes

another Package diagram

class diagram

All of the above

"b" and "c" only

"a" and "b" only

Use case diagrams fulfill a specific purpose : to document the actors (everything outside the system scope), the use cases (everything inside the system scope), and their relationships. Generalizations as well as other types of associations can be modelled between actors. Includes, Extends and other types of associations can be drawn directly between two use cases. Every use case must be initiated by an actor. The exception here is an includes or extends relationship.

Use case diagrams fulfill a specific purpose : to document the actors (everything outside the system scope), the use cases (everything inside the system scope), and their relationships.

Generalizations as well as other types of associations can be modelled between actors.

Includes, Extends and other types of associations can be drawn directly between two use cases.

Every use case must be initiated by an actor. The exception here is an includes or extends relationship.

Library, Library Member, Book, Video, Clerk, Checkout Transaction Library Card, Book, Video, Clerk Borrower, Member, Book, Video, Title Library, Library Member, Book, Video, System Library, Library Member, Book, Video, Author

Library, Library Member, Book, Video, Clerk, Checkout Transaction

Library Card, Book, Video, Clerk

Borrower, Member, Book, Video, Title

Library, Library Member, Book, Video, System

Library, Library Member, Book, Video, Author

This describes the System Dynamics of Bottom-Up Design approach. This describes the System Dynamics of Top-Down Design approach.

This describes the System Dynamics of Bottom-Up Design approach.

This describes the System Dynamics of Top-Down Design approach.

Pareto Diagrams Fishbone Diagrams Mind mapping Brainstorming Event Analysis Actor-Goal List

Pareto Diagrams

Fishbone Diagrams

Mind mapping

Brainstorming

Event Analysis

Actor-Goal List

In Object Oriented Analysis, the dimension of decomposition is fundamentally by things or entities in the domain. It is better to over-specify overspecify a domain model with lots of fine-grained conceptual classes, than to underspecify it. It is better to oversimplify a domain model with lots of coarse-grained conceptual classes, than to underspecify it. In Object Oriented Analysis, the dimension of decomposition is use cases.

In Object Oriented Analysis, the dimension of decomposition is fundamentally by things or entities in the domain.

It is better to over-specify overspecify a domain model with lots of fine-grained conceptual classes, than to underspecify it.

It is better to oversimplify a domain model with lots of coarse-grained conceptual classes, than to underspecify it.

In Object Oriented Analysis, the dimension of decomposition is use cases.

A subsystem is a package that has separate specification and realization parts. A subsystem is a discrete entity that has behavior and interfaces. A subsystem can be identified by the stereotype <<subsystem>> A subsystem is a package that has specification part only

A subsystem is a package that has separate specification and realization parts.

A subsystem is a discrete entity that has behavior and interfaces.

A subsystem can be identified by the stereotype <<subsystem>>

A subsystem is a package that has specification part only