1 Define UML

UML stands for Unified Modeling Language. The UML is a standard graphical

language for modeling object-oriented software.

UML can be defined as “UML is a language for visualizing, specifying,

constructing and documenting artifacts of a software intensive system”.

…….2 define the term object orientation:

An Object orientation is a technique for system modeling by considering object as a

basic building block. System modeling helps the analyst to understand the

functionality of the system.

• An Object is an instance of a class. All the instances/objects have same state and

behavior in a given class.

……3 what is polymorphism:

Polymorphism is a Greek term in which poly means "many" and morph means "form".

It means the ability to take more than one form.

• System behavior is performed when instances start to communicate with each other.

An instance may know the existence of another instance to which message has to be

sent.

………4 what is inheritance:

The process by which objects of one class acquire the properties of objects of another

class is called as Inheritance.

• Inheritance is the process of forming a new class from an existing class or base class.

The base class is also known as Parent Class or Super Class

………5 Object oriented system Development:

• Development refers to the software life cycle i.e. analysis, design and implementation.

• System development process is considered as a sequence of well defined activities

done throughout its life cycle.

•Object oriented development approach encourages software developers to work and

think in terms of the application throughout the software life cycle.

• OO development is a conceptual process independent of programming language until

the final stage.

….6 what is dependency:

• Dependency is a semantic relationship. Dependency is a relationship between two

things in which a change in one element also affects the other one.

• Dependency states that a change in specification of one thing (independent thing)

may affect another thing (depending thing) that uses it, but not the reverse.

……..7 define tagged value:

• A tagged value is a property of a stereotype, allowing us to create new information in

an element bearing that stereotype.

• We can define tags for existing elements of UML or we can define tags that apply to

separate stereotypes that have tagged value.

………8 define stereotype:

• Stereotypes are extensibility mechanisms in UML which allows designers to extend

the vocabulary of UML in order to create new model elements.

• By applying appropriate stereotypes in your model, you can make the specification

model comprehensible.

……….9 define forking:

• A fork represents the splitting of a single flow of control into two or more concurrent

flows of control.

• A fork may have one incoming transition and two or more outgoing transitions, each of which
represents an independent flow of control.

…………..10 system boundary:

• System boundary shows how user interacts with the system. System is class in which

use cases are executed.

• System boundary is a rectangle as shown and all use cases will be inserted

inside this. Anchors will be outside this rectangle.

…..11 Purpose of the Object Diagram:

• Forward and reverse engineering.• Object relationships of a system.

• Static view of an interaction.

….11 swim lane:

• We will find it useful when we are modeling workflows of business processes, to

partition the activity states on an activity diagram into groups, each group

representing the business organization responsible for those activities.

……12 what is inception:

Inception means start. Inception is the point where the project is proposed. The

outcome of inception is project plans, approximate vision, business case, scope,

indefinite estimates.

….13 Following are main goals of UML:

• Provide users with a ready-to-use, expensive visual modeling language so they can

develop and exchange meaningful models.

• Provide extensibility and specialization mechanisms to extend the central concepts.

• Be independent of particular programming languages and development processes.

• Provide a formal foundation for understanding the modeling language.

• Encourage the growth of the Object Orientation tools market.

• Support higher-level development concepts such as collaborations, frameworks,

patterns and components.• Integrate best practices.

…….14 explain UML architecture:

Any real-world system is used by different users like developers, testers, business

people, analysts and many more. So before designing a system the architecture is

made with different perspectives in mind. UML plays an important role in defining different
perspectives of a system. These

perspectives are Logical/Design, Implementation, Process and Deployment and Use

Case View.

CONCEPTUAL= Logical View- Class, Object, Package, Composite Structure, State Machine

Proces view- Sequence, Communication, Activity, Timing, Interaction Overview

PHYSICAL= Implementation View- component deployment View- Deployment.

….15 Various advantages of UML are listed below:

1. It is a formal language: Each element has a strongly defined meaning. When we

model a system, we can model with confidence that the designed model is

understood by everyone.2. It is concise: The entire language is made up of simple and

straightforward

notation. 3. It is comprehensive: It describes all important aspects of a system.

4. It is scalable: Wherever needed, the language is formal enough to handle massive

system modeling projects, but it also scales low to small projects, avoiding

overload. 5. It is built on lessons learned: UML is the result of best practices in object-oriented

communities over the past few years. 6. It is standard: UML is controlled by an open standard group
with active

contributions from a world-wide group of vendors and academics.

7. Mostly used: It is the most useful method of visualization and documenting

software system design.

16 explain the concept of aggression with example:

• Aggregation refers to the formation of a particular class as a result of one class being

aggregated or built as a collection.

• Aggregation is a special form of association. It is a simple concept which

distinguishes a “whole” from a “part”.

• This type of relationship is also called a “has-a” relationship, which means that an

object of whole has objects of parts.

….17 What is classifier? explain different classifiers.

• A classifier is a mechanism that has structural features (in the form of attributes), as

well as behavioral features (in the form of operations).

• The modeling elements that can have instances are called classifiers.

• A classifier has structural features i.e. in the form of attributes along with behavioral

features i.e. in the form of operations.

• Different classifiers are shown and explained

1. Class: It is a description of objects that share the same attributes, operations,

relationships and semantics.

2. Interface: A collection of operations that are used to specify a service of a class or

a component.

3. Data type: A type whose values have no identity, which includes basic built-in

types as well as enumeration types

4. Signal: The specification of an asynchronous stimulus communicated between

…..18 explain deployment diagram:

• A deployment diagram is a diagram that shows the configuration of run time

processing nodes and the artifacts that live on them.

• Graphically, a deployment diagram is a collection of vertices and arcs.

1. Visualize hardware topology of a system.

2. Describe the hardware components used to deploy software components.

3. Describe runtime processing nodes.

• Deployment diagrams commonly contain nodes, dependency, association

relationships etc.

• Like all other diagrams, deployment diagrams may contain notes and constraints.

Deployment diagrams may also contain artifacts.

…19 Describe UP phases with the help of diagram:

• The Unified Process is an iterative and incremental development process. The

Elaboration, Construction and Transition phases are divided into a series of time

boxed iterations.

1. Inception: • Inception means start. Inception is the point where the project is proposed. The

outcome of inception is project plans, approximate vision, business case, scope,

2. Elaboration: • Elaboration means refinement. The outcome of the elaboration is refined vision,

iterative implementation of the core architecture, resolution of high risks,

identification of most requirements and scope, more realistic estimates.

3. Construction: • Construction is a manufacturing process. Construction means to build. This phase

constitutes detailed design and construction of source code.

4. Transition: • Transition means delivery. Transition phase consists of development i.e. delivery of

the system to the user community. The outcome of this phase is beta testing deployment.

….20 Explain Jacobson method of object oriented design:

• The object oriented model of Jacobson describes the development of a sequence of

models from requirement to implementation.

• OOSE was developed by Ivar Jacobson in 1992. OOSE is the first object oriented design

methodology that employs use cases in software design.

• A brief outline of Jacobson's method is as follows:

o Consider adaptations to make the idealized analysis model fit the real world

environment.

o Create blocks as the primary design object.

o Create an interaction diagram that shows how stimuli are passed between blocks.

o Organize blocks into subsystems.

o Review the design work.

21 Explain design components:

• During subsystem design, it is necessary for the software engineer to define four

important design components:

1. Problem domain component: The subsystems, those are responsible for

implementing customer requirements directly.

2. Human interaction component: The subsystems that implement the user

interface (this included reusable GUI subsystems).

3. Task management component: The subsystems that are responsible for

controlling and coordinating concurrent tasks that may be packaged within a

subsystem or among different subsystems.

4. Data management component: The subsystem that is responsible for the storage

and retrieval of objects.

22 what do you mean by Task management components:

• The characteristics of a task are determined by understanding how the task is

initiated. Event-driven and clock-driven tasks are the most commonly encountered.

1. The characteristics of the task are determined.

2. A coordinator task and associated objects are defined.

3. The coordinator and other tasks1. Choose software or hardware implementation for subsystems.

4. Estimating the performance needs the resources needed to satisfy them.

……………23 explain types of SRS specification:

there are so many types of software requirement specification

functional, performance, interface, maintability, reliability, safety, quality, operational, resources.

mainly software requirement can be of three types

1 functional requirement= Functional requirements are statements or goals used to define system

Functional requirements define what a software system must do or not do.

2 Non-functional requirements: Non-functional requirements relate to software usability.

Non-functional software requirements define how the system must operate or perform.

3Domain requirements: Domain requirements are the requirements which are

characteristic of a particular category or domain of projects. Domain requirements can be functional

or nonfunctional
24 what is package explain different kinds of package:

• A package is a general purpose mechanism for organizing modeling elements into

groups: Use case, Actors, classes, Components.

Names

• Every package must have a name that distinguishes it from other packages.

• Package name is a textual string, consisting of any number of letters, numbers and

certain punctuation marks except colon.

Owned Elements

• A package may own different elements like classes, interfaces, components, nodes,

collaborations, use case diagrams and even other packages

Visibility

• The visibility of attributes and operations owned by class can be controlled in the

same way the visibility of packages can be controlled.

25 Object oriented system Development:

• Development refers to the software life cycle analysis, design and implementation.

• System development process is considered as a sequence of well defined activities

done throughout its life cycle.

•Object oriented development approach encourages software developers to work and

think in terms of the application throughout the software life cycle.

• OO development is a conceptual process independent of programming language until