Scribd
Upload
150 views3 pages

Logical Architecture PDF

A software architecture involves significant design decisions about organizing a software system, including its structural elements, interfaces between elements, and composition of elements. These design decisions are captured using logical architecture models at a high level. A common approach is to organize a system into logical layers, with "higher" layers like the user interface calling upon "lower" layers like technical services. This logical architecture can then be modeled using UML package diagrams to show the packages and their dependencies without deciding on physical deployment.

Uploaded by

usama
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
Download as pdf or txt
150 views3 pages

Logical Architecture PDF

A software architecture involves significant design decisions about organizing a software system, including its structural elements, interfaces between elements, and composition of elements. These design decisions are captured using logical architecture models at a high level. A common approach is to organize a system into logical layers, with "higher" layers like the user interface calling upon "lower" layers like technical services. This logical architecture can then be modeled using UML package diagrams to show the packages and their dependencies without deciding on physical deployment.

Uploaded by

usama
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
Download as pdf or txt
Download as pdf or txt
You are on page 1/ 3

Software Architecture

• A set of significant decisions about:


– Organization of a software system
Logical Architecture and UML – Selection of structural elements
Package Diagrams – Interfaces between elements
– Behavioral collaboration between elements
– Composition of elements into subsystems
– Architectural “style” of organization

Logical Architecture and UML


Logical Architecture And Layers
Package Diagrams…
• High level, large scale Architecture Model. • Logical architecture is the large-scale organization of the
software classes into packages (or namespaces),
subsystems, and layers.
• At this level, the design of a typical OO system is
based on several architectural layers, such as a • Logical - because there's no decision about how these
UI layer, an application logic (or "domain") layer, elements are deployed across different operating system
and so forth. processes or across physical computers in a network
(deployment architecture).

• Goal is to design a logical architecture with


layers and partitions using UML package
diagrams

Layering Pattern Why use Layers


• Source code changes are rippling throughout the system many parts
• A layer is a very coarse-grained grouping of classes, packages, or of the systems are highly coupled.
subsystems that has cohesive responsibility for a major aspect of
the system. • Application logic intertwined with UI, neither reusable

• Also, layers are organized such that "higher" layers (such as the UI • Potentially general technical services or business logic is intertwined
layer) call upon services of "lower" layers, but not normally vice with more application-specific logic, so it cannot be reused,
versa. distributed to another node, or easily replaced with a different
implementation.
• Strict layered architecture VS Relaxed Layered Achitecture
• High coupling across different areas of concern. It is thus difficult to
• A logical architecture doesn't have to be organized in layers. But it's divide the work along clear boundaries for different developers.
very common, and hence, introduced at this time.
• The purpose and number of layers varies across applications and
application domains (information systems, operating systems, and
so forth).

1
Typical Layers Typically layers in an OO system
• User Interface.

• Application Logic and Domain Objects software objects


representing domain concepts (for example, a software
class Sale) that fulfill application requirements, such as
calculating a sale total.

• Technical Services general purpose objects and


subsystems that provide supporting technical services,
such as interfacing with a database or error logging.
These services are usually application-independent and
reusable across several systems.

NextGen
Example

Common
Layers

[Larman 2002]

[Larman 2002]

Package Package
Coupling Coupling [2]

• No classes, just
packages and
package dependencies
• Most common form

[Larman 2002] [Larman 2002]

2
Architectural
Interaction
Diagram

[Larman 2002]

You might also like