Chapter 10

Question 1

Benefits of object-oriented analysis and design

Answer 1

1. Reusability
   - Recycling of program parts can reduce the costs of development in
   computer based systems
2. Maintaining systems
   - Making a change in one object has a minimal impact on other objects

Question 2

Object oriented concepts: Objects

Answer 2

Persons/places/things that are relevant to the system being analyzed

Question 3

Object oriented concepts: Classes

Answer 3

• Set of shared attributes and behaviors found
  in each object in the class
• Should have a name which differentiates it
  from all other classes
• Instantiate is when an object is created from a
  class

o Method: Action that can be requested from
any object of the class

Question 4

Object oriented concepts: Attribute

Answer 4

describes some property that is

possessed by all objects of the class

Question 5

Object oriented concepts: Method

Answer 5

Action that can be requested from any object of the class

Question 6

Object oriented concepts: Inheritance

Answer 6

• When a derived class inherits all the attributes and behaviours of the base class
• Reduces programming labor by using common concepts easily
• Feature only found in object-oriented systems

Question 7

UML Concepts

Answer 7

1. things
2. relationships
3. diagrams

Question 8

UML things: things

Answer 8

• structural things
• Classes, interfaces, use cases and other elements that provide a way to create models
• Allow the user to describe relationships

Question 9

UML things: behavioural things

Answer 9

• describe how things work

- interactions and state machines

Question 10

UML things: group things

Answer 10

used to define boundaries

Question 11

UML things: annotations things

Answer 11

can add notes to diagram

Question 12

2 types of relationships in UML

Answer 12

1. Structural Diagrams
   - Used to describe the relations between classes
2. Behavioural Diagrams
   - Describes the interaction between actors and a use case

Question 13

3 types of UML Diagrams

Answer 13

1. use case diagram
2. use case scenario
3. activity diagram

Question 14

Use case diagram

Answer 14

• Describes how the system is used

- Starting point for UML modelling

Question 15

Use case scenario

Answer 15

Verbal articulation of exceptions of the main behavior described by the
primary use case

Question 16

Activity diagram

Answer 16

Illustrates overall flow of activities

Question 17

Use case modelling

Answer 17

• Describes what the system does without describing how a system does it
• Based on the interactions and relationships of individual use cases
• Similar to the context diagram

Question 18

Use case relations (behavioural)

Answer 18

1. Communicates
   - Connects an actor to a use case
2. Includes
   - Describes the situation in which a use case contains behavior that is
   common to more than one use case
3. Extends
   - Describes situation in which use case possesses the behaviour that allows the new case to handle a variation of exception from the basic use case
4. Generalizes
   - Implies one thing is more typical than another thing

Question 19

Activity diagrams

Answer 19

• Shows the sequence of activities in a process
• Includes sequential and parallel activities
• Decisions that are made

Question 20

Test Plans

Answer 20

• Activity diagrams can be used to construct test plans
• Each event must be tested to see if the system goes to the next state
• Each decision must be tested

Question 21

UML steps

Answer 21

1. Define use case model
2. Continue UML diagramming to model the system during the systems analysis
   phase
3. Develop the class diagrams
4. Draw statechart diagrams
5. Begin systems design by refining the UML diagrams
6. Document system design in detail