You are on page 1of 7

UNIT- 3

1. What do you interpret from the term 4+1 view model?

The 4+1 view model is:

Logical view

Process view

Development view

Physical view

Scenario view

Logical view:

Represents functionality elements and it is a module view


category.

Encompasses different view types such as the class and


entity-relationship views.

Static structures are represented by object and class


diagrams

Dynamic behavior is represented by


interaction,state,activity,and deployment diagram

Process view:

Involes runtime elements,hence it is a component and


connector view category,includes
concurrency,synchronization and distribution aspects of a
systems design.

Views are represented by interaction,state,activity and


deployment diagrams.

Physical view:

It is an allocation view cAtegory that involves the mapping


of software elements to hardware units.
Represented by deployment diagrams.

Development view:

Shows how implementation elements are allocated to the


development environment.

It is an allocation view category which is represented by


component diagrams and packages.

Scenario or use case view :

The main role is

It is a driver which conducts design by discovering missing


architectural elements.

It is a tool to validate and illustrate the architecture design.

2. Define a Viewpoint

View point is a collection of patterns, templates and conventions for


constructing one type of view. It defines the perspective from which the view
is taken.

It describes how to construct and use a view, the information that


should appear in view, modeling techniques for expressing and analyzing the
information and describing the purpose and intended use.

3. Give example for Logical View.

4. Compare Physical view and Development view.

Physical view Development view

It shows the mapping of software It shows the layers and how


elements to hardware units. implementation elements are
allocated to deployment to
development environment.
It is represented by deployment
diagram It is represented by component
diagram and packages

Software engineer is the viewer Programmer and software manager is


the viewer

It considers non-functional It considers software module


requirements and network organization

5 .State few benefits and limitations of Viewpoints

BENEFITS: separation of concern

Communication with stake holders

Management of complexity

Improved developers focus

DRAWBACKS: It is inconsistent.fragmentation occurs

Selection of wrong set of views may occur

6. Differentiate view and viewpoint

View Viewpoint

It is a collection of coherent set of It is a collection of patterns,


architectural elements templates and conventions

View is defined as what one sees Viewpoint is defined as where one is


looking from (i.e.,) the perspective

It is always specific to the They are generic and can be stored in


architecture libraries for reuse

7. When will you say that the views are consistent?

Views are consistent if the design decisions they contain are


compatible.

Views are inconsistent if two views assert design decisions that cannot
simultaneously be true.
8. Classify the types of inconsistent views.

Direct inconsistencies

Refinement inconsistencies

Static vs. dynamic aspect inconsistencies

Dynamic vs. dynamic aspect inconsistencies

Functional vs. non-functional inconsistencies

9. Classify the critical roles played by Scenario view point in 4+1


view model.

The critical roles played by Scenario view point in 4+1 view model:

1. Scenario acts as a driver to help designers discover


architectural elements during the architecture design.

2. It validates and illustrates the architecture design, both on


paper and as the starting point for the tests of an architectural prototype.

10. Show the three step procedure to choose a view.

The procedure to choose a view is,

Step 1: produce a candidate view list.

Step 2: combine views

Step 3: prioritize the views

11 Illustrate the different kinds of views.

View is a representation of coherent set of architectural elements that


are written and read by the system stake holders.

Types:

module view

Component and connector view

Allocation view

Other categories:
Runtime view and non-runtime view

Business architecture view and application architecture view

12. What is a called a view packet?

A view packet is the smallest piece of information a stake holder


requires, which can be represented by one or more styles.

For instance, a single view packet could show a whole system at a high
level and a number of additional view packets could be used to show the
individual sub-system in greater detail.

13. Summarize the characteristics of the classes of logical


architecture.

The characteristics of the classes of logical architecture are,

Autonomy

Persistence

Sub-ordination

Distribution

14. What are the two strategies available to analyze the level of
concurrency in 4+1 view model?

The two strategies available are,

Inside-out: starting from logical structure

Outside-in: starting from physical structure

15. Summarize how to choose views.

The views are chosen based on,

How it is structured as a set of implementation units


(module view)

How it is structured as a set of elements that have runtime


behavior and interaction (component and connector view)
How it relates to non-software structures in an environment
(allocation)

16. Give the usage of operational view point.

The Operational Viewpoints can be used in a number of ways:


Including the development of user requirements
Capturing future concepts
Supporting operational planning processes

Operational view point describes how the system will be operated,


administered and supported when it is running in its production environment.

17 Mention the styles used for logical view and development view.

The styles used are for,

Logical view: object oriented style

Development view: layered style

18. How the 4+1 view is seen by the software industry? Generate
the scenarios that are considered difficult and easy.

System engineers approach it from the physical view, then the process
view.

End users, customers, data specialists from the logical view

Project managers, software configuration staff see it from the


development view

19. Define a component. Give example.

A component reperesents a modular part part of system that


encapsulates its content and whose manifestation is replaceable within its
environment. a component defines its behavior in terms of provided and
required interfaces.

Example: EJB containers hosting enterprise java beans,servlets,etc

20. Compose any two UML notations for module view type.

You might also like