Architectural views

Architectural views

1

Architectural views:

Architectural Models of a Software System can be used to focus discussion about the software requirements.

Architectures may be documented from several different perspectives or views.

A view describe the structure of a system and Architectural views may be used to document a design so that it can be used as a basis for more detailed design and implementation.

Concepts used in Architectural views

Two Concepts are used in Architectural views.

What views or perspectives are useful for when designing and documenting a systems architecture?(VIEWS)

What notations should be used for describing architectural model?(Structure)

4+1 view model

Krutchen (1995), in his well known 4+1 view model of software architecture suggest that there should be the four fundamental architecture views ,related using use cases or scenarios, as follows:

Logical views:

Shows key abstractions in the system as object or object classes

Relate the system requirements to entities.

Process view:

Shows how, at run-time, the system is composed of interacting processes.

This view is useful for making judgments about non functional system characteristics such as performance & availability.

Development View:

Shows how the software is decomposed for development

Show the breakdown of software into components that are implemented by a single developer or development team.

Useful for managers and programmers.

Physical View:

Shows the system hardware and how software components are distributed across the processors in the system.

Useful for system engineers planning a system deployment.

4+1 View Model

Logical View

Development View

Process View

Physical view

Scenarios