Lecture 3_ Software Architecture_1

0.0(0)
studied byStudied by 1 person
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/43

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

44 Terms

1
New cards

Architecture

The fundamental organization of a system embodied in its components, their relationships to each other and to the environment and the principles guiding its design and evolution.

2
New cards

Systems Architecture

The fundamental and unifying system structure defined in terms of system elements, interfaces, processes, constraints, and behaviors.

3
New cards

Components

The computational elements and data stores of the system, potentially with multiple interfaces, called ports.

4
New cards

Connectors

Models interactions among components, mediating communication and coordination activities.

5
New cards

Systems

Graphs of components and connectors that tend to be hierarchical, where components may represent subsystems.

6
New cards

Properties

Non-structural information about the parts of an architecture description, such as whether a connector is a function call.

7
New cards

Style

An architectural style represents a family of related systems, defining design vocabulary for components, connectors, roles, and properties.

8
New cards

System Architect

A team member responsible for designing and building a system, aware both of individual components and their interrelationships.

9
New cards

Systems Architecting

The process of creating complex, unprecedented systems in response to ill-defined market requirements and technology evolution.

10
New cards

Evolutionary Development

An approach to system development that allows for flexibility and adaptation to changing requirements and technology.

11
New cards

Functional Architecture

A set of activities or functions arranged to achieve specific requirements.

12
New cards

Physical Architecture

A representation of the physical resources expressed as nodes and links that constitute the system.

13
New cards

Technical Architecture

A minimal set of rules governing arrangement, interaction, and interdependence of parts ensuring a conformant system.

14
New cards

Operational Concept

A concise statement that describes how the system will operate and act in its operational environment.

15
New cards

Executable Model

A dynamic representation of the architecture required to analyze behavior and evaluate performance characteristics.

16
New cards

Architecture Development Process

Comprises three phases: Analysis, Synthesis, and Evaluation of the system's architecture.

17
New cards

MOP (Measures of Performance)

Measures used to assess the performance of an architecture.

18
New cards

MOE (Measures of Effectiveness)

Measures used to evaluate the effectiveness of an architecture.

19
New cards

Analysis Phase

Phase where static representatives of functional and physical architectures are obtained.

20
New cards

Synthesis Phase

Phase that uses static constructs alongside dynamic behavior descriptions to develop executable operational architectures.

21
New cards

Evaluation Phase

Phase where effectiveness and performance measures are obtained for the architecture.

22
New cards

Requirements

Specification of what the system needs to achieve, heavily influencing system architecture design.

23
New cards

Port

An interface that defines a point of interaction between a component and its environment.

24
New cards

Bindings

Mappings that connect interfaces of one level of a system to another.

25
New cards

Stakeholders

Individuals or groups affected by the operation and decisions of the system.

26
New cards

Scenarios

Collections of events that describe how stakeholders interact with the system throughout its lifecycle.

27
New cards

Design Vocabulary

The specific terms and guidelines used to define components, connectors, and other elements in an architectural style.

28
New cards

Level of Abstraction

Refers to how detailed or general a model or concept is within system architecture.

29
New cards

System Development Model

Traditional methodologies used to support system architecting, including requirement definition and design optimization.

30
New cards

Ill-defined Market Requirements

Unclear or changing specifications for what a system should accomplish, complicating system architecture.

31
New cards

Flexibility in Design

The ability to adapt system architecture as new information or technologies become available.

32
New cards

Prototype

An early sample or model built to test a concept or process.

33
New cards

Hierarchy

A system's organizational structure where components are arranged in layers of importance or control.

34
New cards

Interrelationships

The connections and dependencies between different components of a system.

35
New cards

Technology Alternatives

Various technological options available that can be selected for system development.

36
New cards

Dynamic Behavior

The change in behavior of a system as it processes data or responds to its environment.

37
New cards

Design Constraints

Limitations or restrictions that affect how a system can be designed and built.

38
New cards

User Interaction

How end-users engage and communicate with the system components during operation.

39
New cards

Lifecycle Scenarios

Different phases in which a system will function, be maintained, and eventually retired.

40
New cards

System Integration

The process of combining different subsystems into a single cohesive system.

41
New cards

Component Interface

The point at which different system components interact, facilitating communication and functionality.

42
New cards

Master Builder

An original meaning of the term ‘architecture’, referring to the one who designs and constructs systems.

43
New cards

Colocation of Nodes

Positioning of various system components in a specific way to facilitate connectivity.

44
New cards

Real-time Constraints

Requirements that dictate responses from the system must occur within a specific timeframe.