i. Component

ii. Connector

iii. Configuration

iv. Architectural style

v. Architectural patterns

vi. View and Viewpoints

Mumbai university > Computer engineering > Sem 7 > Software Architecture.

* Marks:- * 12 M

* Years :- * Dec14, May13, May12

i. Component

A software component is an architectural entity that

• Encapsulates a subset of the system’s functionality and/or data.
• Restricts access to that subset via an explicitly defined interface.
• Has explicitly defined dependencies on its required execution context.

General notation used for a component is:

ii. Connector

A software connector is an architectural element tasked with effecting and regulating interaction among components.

Simple connectors are usually restricted to enabling the interaction of pairs of components. However, as software system has become more complex, so have connectors, with their own separate identities, roles, and bodies of implantation-level code, as well as ability to simultaneously service many different components.

General notation used for a connector is:

iii. Configuration

An architectural configuration, or topology, is a set specific association between the components and connectors of software systems architecture.A configuration may be represented as a graph wherein nodes represent components and connectors, and whose edges represent their associations. General notation used for association is:

iv. Architectural style

An Architectural Style is a named collection of architectural design decisions that

• Are applicable in a given development context.
• constrain architectural design decisions that are specific to a particular system with in that context, and
• Elicit beneficial qualities in each resulting system.

Architectural style is a way of classifying architecture that gives emphasis to characteristic features of design.

v. Architectural patterns

An Architectural Pattern is a named collection of architectural design decisions that are applicable to a recurring design problem parameterized to account for different software development contexts in which that problem appears.

An architectural pattern provides a set of specific design decisions that have been identified as effective for organizing certain classes of software systems or, more typically, specific subsystems.

vi. View and Viewpoints

Architectural View is a representation of a particular system or part of a system from a particular perspective.

Architectural viewpoint is a template that describes how to create and use an architectural view. A viewpoint includes a name, stakeholders, concerns addressed by the viewpoint, and the modeling and analytic conventions.