lOMoARcPSD|21738369

CS8582 - VIVA VOCE Questions

computer science engg (Anna University)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by KARTIK GAIKWAD (kartikgaikwad2004@gmail.com)
 lOMoARcPSD|21738369

CS8582- OBJECT ORIENTED ANALYSIS AND DESIGN LABORATORY

VIVA VOCE QUESTIONS

1. What is an object?
An object is a combination of data and logic; the representation of some real-world entity.

2. What is the main advantage of object-oriented development?

 High level of abstraction
 Seamless transition among different phases of software development
 Encouragement of good programming techniques.
 Promotion of reusability.

3. What is Object Oriented System development methodology?

Object oriented system development methodology is a way to develop software by building self-
contained modules or objects that can be easily replaced, modified and reused.

4. Distinguish between method and message in object.

Method Message
Methods are similar to functions, procedures or subroutines in more traditional programming
languages. Message essentially are non-specific function calls.
Method is the implementation. Message is the instruction.
In an object oriented system, a method is invoked by sending an object a message. An object
understands a message when it can match the message to a method that has the same name as the
message.

5. 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.

6. What Is Object-Oriented Analysis and Design?

During object-oriented analysis, there is an emphasis on finding and describing the objects—or
concepts—in the problem domain. For example, in the case of the library information system, some
of the concepts include Book, Library, and Patron. During object-oriented design, there is an
emphasis on defining software objects and how they collaborate to fulfill the requirements.

7. What is UML?
Unified Modeling Language is a visual language for specifying, con- structing and documenting
the artifacts of system.
UML is the standard diagrammatic notation for drawing picture related to software.
UML defines UML profiles that specialize subsets of the notation for common subject areas.

8. What are the primary goals in the design of UML?

Provide users a ready – to use expressive visual modeling language so they can develop and
exchange meaningful models.
Provide extensibility and specialization mechanism to extend the core concepts.
Be independent of particular programming language and development process.
Provide a formal basis for understanding the modeling language.
Encourage the growth of the OO tools market.
Downloaded by KARTIK GAIKWAD (kartikgaikwad2004@gmail.com)
 lOMoARcPSD|21738369

Support higher – level development concepts.

Integrate best practices and methodologies.

9. Define Class Diagram.

The main static structure analysis diagram for the system, it represents the class structure of a
system including the relationships between class and the inheritance structure.

10. Define Activity Diagram.

A variation or special case of a state machine in which the states are activities representing the
performance of operations and the transitions are triggered by the completion of the operations.

11. What is interaction diagram? Mention the types of interaction diagram.

Interaction diagrams are diagrams that describe how groups of objects collaborate to get the job
done interaction diagrams capture the behavior of the single use case, showing the pattern of
interaction among objects.
There are two kinds of interaction models
Sequence Diagram
Collaboration Diagram.

12. What is Sequence Diagram?

Sequence diagram is an easy and intuitive way of describing the behaviors of a system by viewing
the interaction between the system and its environment.

13. What is Collaboration Diagram?

Collaboration diagram represents a collaboration, which is a set of objects related in a particular
context, and interaction, which is a set of messages exchanged among the objects with in
collaboration to achieve a desired outcome.

14. Define Start chart Diagram.

Start chart diagram shows a sequence of states that an object goes through during its life in
response to events. A state is represented as a round box, which may contain one or more
compartments. The compartments are all optional.

15. What is meant by implementation diagram?

Implementation Diagrams show the implementation phase of systems development such as the
source code structure and the run- time implementation structure.
There are two types of implementation diagrams:
Component Diagrams
Development Diagrams.

16. Define Component Diagram

A Component diagrams shows the organization and dependencies among a set of components. A
component diagrams are used to model the static implementation view of a system. This involves
modeling the physical things that reside on a mode, such as executable, libraries, tables, files and
documents.

17. Define Deployment Diagram.

Deployment Diagram shows the configuration of run-time processing elements and the software
components, processes, and objects that live in them.
Deployment diagrams are used to model the static deployment view of a system. A deployment
diagram is a graph of modes connected by communication association.
Downloaded by KARTIK GAIKWAD (kartikgaikwad2004@gmail.com)
 lOMoARcPSD|21738369

18. What is the UP and it’s Phases?

A software development process describes an approach to building, deploying, and possibly
maintaining software. The Unified Process has emerged as a popular iterative software
development process for building object-oriented systems.
4 Phases:
 Inception: Requirements capture and analysis
 Elaboration: System and class-level design
 Construction: Implementation and testing
 Transition: Deployment

19. What is Iterative and Evolutionary Development?

The iterative lifecycle is based on the successive enlargement and refinement of a system through
multiple iterations, with cyclic feedback and adaptation as core drivers to converge upon a suitable
system. The system grows incrementally over time, iteration by iteration, and thus this approach is
also known as iterative and incremental development. Because feedback and adaptation evolve the
specifications and design, it is also known as iterative and evolutionary development

20. What is Inception?

Inception is the initial short step to establish a common vision and basic scope for the project. It
will include analysis of perhaps 10% of the use cases, analysis of the critical non-functional
requirement, creation of a business case, and preparation of the development environment.

21. Define Use case modeling?

Use case modeling is a form of requirements engineering. How to create an SRS in what we might
call the ―traditional‖ way. Use case modeling is a different and complementary way of eliciting
and documenting requirements.

22. Define Use case generalization?

Use case generalization is used when you have one or more use cases that are really specializations
of a more general case.

23. List the Relationships used in Use cases.

 Generalization
 Extend
 Include

24. What is the purpose of extends and include relationship in use diagram.
Extend is used when a use case adds steps to another 昀椀rst class use case.
For example, imagine “Withdraw Cash” is a use case of an ATM machine. “Access Fee”
would extend Withdraw Cash and describe the conditional “extension point” that is
instantiated when the ATM user doesn’t bank at the ATM’s owning institution.
Include is used to extract use case fragments that are duplicated in multiple use cases.
The included use case cannot stand alone and the original use case is not complete
without the included one. This should be used sparingly and only in cases where the
duplication is signi昀椀cant and exists by design (rather than by coincidence).
For example, the 昀氀ow of events that occurs at the beginning of every ATM use case
(when the user puts in their ATM card, enters their PIN, and is shown the main menu)
would be a good candidate for an include..

25. Define a) Actors b) Scenario c) Use cases.

 An actor is something with behavior, such as a person (identified by role), computer
Downloaded by KARTIK GAIKWAD (kartikgaikwad2004@gmail.com)
 lOMoARcPSD|21738369

system, or organization; for example, a cashier.

 A scenario is a specific sequence of actions and interactions 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. Define Use-case Diagram.

 Use-Case Model is the set of all written use cases; it is a model of the system’s functionality
and environment.
 Use cases are text documents, not diagrams, and use-case modeling is primarily an act of
writing text, not drawing diagrams.
 The Use-Case Model is not the only requirement artifact in the UP.
 The Use-Case Model may optionally include a UML use case diagram to show the names
of use cases and actors, and their relationships.
 It also provides a quick way to list the use cases by name.

27. What are the three kinds of Actors and three common use case formats?
Three kinds of Actors Three common use case formats
 Primary actor  Brief
 Supporting actor  Casual
 Off stage actor  Fully dressed

28. What are the artifacts in inception phase?

i).Vision and business case ii).Supplementary specification iii).Glossary
iv).Risk list v).Prototypes vi).Iteration plan vii).Phase plan viii).Development case

29. What Tests Can Help Find Useful Use Cases?

 The Boss Test
 The EBP Test
 The Size Test

30. What are the three ways and perspectives to Apply UML?
3 Ways-
 UML as sketch,
 UML as blueprint,
 UML as programming language
Perspectives-
 Conceptual perspective,
 Specification (software) perspective,
 Implementation(Software) perspective

Downloaded by KARTIK GAIKWAD (kartikgaikwad2004@gmail.com)

 lOMoARcPSD|21738369

Downloaded by KARTIK GAIKWAD (kartikgaikwad2004@gmail.com)