Object oriented analysis and

design
1) What is Analysis and Design?
Analysis emphasizes an investigation of the problem and
requirements, rather than a solution. For example, if a new
computerized library information system is desired, how will it be
used?

Design emphasizes a conceptual solution that fulfills the

requirements, rather than its implementation. For example, a
description of a database schema and software objects. Ultimately,
designs can be implemented

2) What is OOAD?
During object-oriented analysis, there is an emphasis on
finding and describing the objects—or concepts—in the problem
domain and an emphasis on defining software objects and how they
collaborate to fulfill the requirements.

3) Define Use cases.

Use cases are not an object-oriented artifact—they
are simply written stories. However, they are a popular tool in
requirements analysis and are an important part of the Unified
Process.

4) Define Domain Model.

A decomposition of the domain involves an identification of the
concepts, attributes, and associations, which is illustrated in a set of
diagrams that show domain concepts or objects.

5) Define design class diagrams.

In addition to a dynamic view of collaborating objects shown in
interaction diagrams, a static view of the class definitions is usefully
shown with a design class diagram. This illustrates the attributes
and methods of the classes.

6) What is UML?
The Unified Modeling Language is a visual language for
specifying, constructing and documenting the artifacts of systems.

7) What are the three ways to apply UML?

• UML as sketch
• UML as blueprint
• UML as programming language

Gopi Krishna V 12808104008

8) What are the three perspectives of UML?
• Conceptual perspective
• Specification (software) perspective
• Implementation (software) perspective

9) Define Conceptual Classes.

Conceptual classes are real-world concept or thing. It’s a
conceptual or essential perspective. The UP Domain Model contains
conceptual classes.

10) Define software Classes.

Software class is a class representing a specification or
implementation perspective of a software component, regardless of
the process or method.

11) Define Implementation classes.

Implementation class is a class implemented in a specific OO
language such as Java.

12) Define Unified Process.

The Unified Process is a popular iterative software
development process for building object-oriented systems.

13) Give three reasons for the introduction of UP

1. The UP is an iterative process. Iterative development

influences how this book introduces OOA/D, and how it is best
practiced.
2. UP practices provide an example structure for how to do and
thus how to explain OOA/D. That structure shapes the book
structure.
3. The UP is flexible, and can be applied in a lightweight and agile
approach that includes practices from other agile methods
(such as XP or Scrum) more on this later.

14) What if I don’t care about UP?

The UP is used as an example process within which to explore
iterative and evolutionary requirements analysis and OOA/D, since
it's necessary to introduce the subject in the context of some
process.

15) What are the UP phases?

o Inception
o Elaboration
o Construction
o Transition
5
16) Draw the schedule oriented terms in UP.

Gopi Krishna V 12808104008

17) What are the UP disciplines?

• Business Modeling: The Domain Model artifact, to visualize

noteworthy concepts in the application domain.
• Requirements: The Use-Case Model and Supplementary
Specification artifacts to capture functional and non-functional
requirements.
• Design: The Design Model artifact, to design the software
objects.

18) What is the relationship between UP disciplines and phases?

The iterations tend to have a relatively high level of
requirements and design work, although definitely some
implementation as well. During construction, the emphasis is
heavier on implementation and lighter on requirements analysis.

19) What is the Development case?

5

Gopi Krishna V 12808104008

 The choice of practices and UP artifacts for a project may be
written up in a short document called the Development Case (an
artifact in the Environment discipline).

20) Define Inception.

Inception is the approximate vision, business case, scope,
vague estimates

21) Mention the arti-crafts in inception.

• Vision and Business Case
• Use-Case Model
• Supplementary Specification
• Glossary
• Risk List & Risk Management Plan
• Prototypes and proof-of-concepts
• Iteration Plan
• Phase Plan & Software Development Plan
• Development Case

22) Define requirements.

Requirements are capabilities and conditions to which the
system and more broadly, the project must conform.

23) What are the types and categories of requirements?

• Functional- features, capabilities, security.

• Usability- human factors, help, documentation.
• Reliability- frequency of failure, recoverability, predictability.
• Performance- response times, throughput, accuracy,
availability, resource usage.
• Supportability- adaptability, maintainability,
internationalization, configurability.

24) How requirements are organized in UP artifacts?

• Use-Case Model
• Supplementary Specification
• Glossary
• Vision
• Business Rules

25) What are actors, scenarios and usecase?

An actor is something with behavior, such as a person
(identified by role), computer system, or organization; for example,
a cashier.
5
A scenario is a specific sequence of actions and interactions
Gopi Krishna V 12808104008
between actors and the system; it is also called a use case instance.
A use case is a collection of related success and failure
scenarios that describe an actor using a system to support a goal.

26) Are Use Cases Functional Requirements?

Use cases are requirements, primarily functional or behavioral
requirements that indicate what the system will do, In terms of the
FURPS+ requirements types.
27) What are the types of Actors?

• Primary actor -To find user goals, which drive the use cases.
• Supporting actor- To clarify external interfaces and protocols.
• Offstage actor -To ensure that all necessary interests are identified and satisfied.
Offstage actor interests are sometimes subtle or easy to miss unless these actors are
explicitly named.

28) What are the three common usecase formats?

• Brief - one-paragraph summary, usually of the main success scenario. The prior
Process Sale example was brief.
• Casual - Informal paragraph format. Multiple paragraphs that cover various
scenarios. The prior Handle Returns example was casual.
• Fully dressed - All steps and variations are written in detail, and there are supporting
sections, such as preconditions and success guarantees

Gopi Krishna V 12808104008