Implemetacija Arhitektura

Implementation Architecture

• Implementation architecture focuses on how a system is built, identifying technological elements (software packages, libraries, frameworks, etc.) needed for the implementation process.
• It addresses non-runtime requirements and quality attributes like configurability, testability, and reusability.
• The architecture is comprised of components (application and infrastructure pieces) and connectors (describing how components interact).
• Components reflect software entities, and their relationships at the source and binary levels. The system may have several implementation models, focusing on individual concurrent subsystems (or processes).
• Application components are responsible for domain-level responsibilities defined in the conceptual architecture often implemented as binary, source, and files.
• Infrastructure components are needed for system running, unrelated to application functionality, such as an HTTP Connection Handler. Whether a component is application or infrastructure depends on the overall application.
• Infrastructure components can act as containers for application components, typically executing within a process and creating threads for individual application components (e.g., a Web application server for multiple applications).
• Connectors represent the "uses" relationship between components, with arrows depicting the direction, and styles representing the communication nature.
• API calls, callbacks, network protocols, and OS signals are the four types of connector styles.
• Ports are endpoints of the connectors, communicating between a component's internal and external sides.
• Interfaces are specifications of the communication method between components, acting as contracts for how they interact. They are commonly standardized.

Components

• Two main types of components: application and infrastructure.
• Application components implement domain-level responsibilities
• Infrastructure components support system operation but are separate from application functionality
• Infrastructure components often act as containers for application components, providing an execution environment and managing their lifecycle.

Connectors

• In implementation architecture, connectors represent the "uses" relation.
• The use of arrows in the diagrams denotes the direction of the relation.
• Communication between components is represented through connector styles (e.g., API call, callback, network protocol, OS signal).
• Several specialized tools and examples are used to illustrate how components interact (e.g., API calls, callbacks).

Interfaces

• Interfaces are an integral part of the implementation architecture, often depicted using lollipop notation while ports using little squares.
• Interfaces dictate how communication occurs between components.
• The responsibilities contained within an interface are typically stable even when components change
• Interfaces in many systems abstract out hardware-related complexity.
• Interfaces and ports are optional, only to be used when logically relevant to a given model.
• Examples of common interfaces: HTTP, SQL, File I/O

Sample Implementation Architecture

• An example outlines an implementation architecture diagram that includes Apache, HTTP, mod_php, Application components, MySQL, SQL Socket, Smarty, and Templates, amongst other components.

Requirements

• Implementation architecture addresses non-runtime requirements (maintainability, extensibility, reusability), alongside quality attributes; these are often represented through diagrams to identify and analyse any potential faults.
• Impact mapping, fault tree analysis, use of diagrams or maps help to investigate how the architecture changes in case of failures or updates in system components.
• This helps to ensure quality and stability in the software.

Prototypes

• Prototypes are used to show how a solution is feasible through implementation of each identified application component.
• Prototypes are deployed within pre-existing infrastructure.
• Testing phases help ensure functionality, correctness, and quality.
• There are two main categories of prototypes:
  • Technical prototypes, used to assess feasibility, quickly developed, and discarded. They assess if a specific technology (e.g. database, framework) is applicable for the project, or to check for the team's suitability.
  • Executable prototypes - a full skeleton of the system. They are implemented within an iterative process, not discarding code (and documentation); their purpose is for exploring flaws in architecture, testing overall system performance and integration with the infrastructure.
• Mock-ups, a particular instance of technical prototypes are frequently used in communication with stakeholders to illustrate user interfaces and system functionality.

Behavior Design

• Use-case models are too high-level, so detailed sequence diagrams are needed to explore the behavior at the operation level of implementation components.
• Use-case diagrams can be utilized for analyzing runtime characteristics within these scenarios.

Weighted Scoring Method

• The weighted scoring method is a procedure for selecting the best infrastructure.
• Alternatives and criteria are identified with individual scores and relative weighted importance (weights).
• Formulas for scoring alternatives (with or without equal weights) are given.

Practical Guidelines

• Mapping conceptual components to implementation components can be one-to-one, one-to-many or many-to-one depending on specific needs and characteristics. These guidelines are essential during the prototyping stage.

Interface Design

• Interface design is crucial for all application and infrastructure components.
• Components' responsibilities are clarified through interfaces.
• Interfaces can be standardized (e.g., HTTP, SQL, File I/O) and utilized within the system.
• Standardised interfaces help with component separation.

Sample Implementation

• Several examples of implementation architectures are provided, including visualizations of complex system integration where multiple components from different sources interact within the overall system.

Овој квиз се фокусира на имплементацијата на архитектурите на системот. Обработува важни аспекти како компоненти, конектори и квалитетни атрибути на софтверот. Пронајдете информации за како се реализираат и поврзуваат различни делови во системот.