1/15
These flashcards cover key vocabulary related to software architecture based on the lecture notes.
Name | Mastery | Learn | Test | Matching | Spaced | Call with Kai |
|---|
No analytics yet
Send a link to your students to track their progress
Software Architecture
The fundamental structure of a software system, defining its components and their relationships.
Quality Attributes
The non-functional requirements such as performance, security, usability, etc., that determine the characteristics of a software architecture.
Agile Methodology
A group of software development methodologies that emphasize iterative progress, collaboration, and adaptability.
Waterfall Model
A linear software development approach that progresses through clearly defined phases: requirements, design, implementation, testing, and maintenance.
Interoperability
The ability of different systems or components to work together and exchange information seamlessly.
Stakeholders
Individuals or groups with an interest in the success of a system, including customers, users, developers, and managers.
Architectural Tactics
Specific patterns or techniques that can be applied to achieve quality attribute goals within an architecture.
Technical Context
The environment and constraints under which a software architecture is developed, influenced by current technology and practices.
Business Goals
Objectives sought by organizations when investing in or developing a software system, often influencing architectural decisions.
Architectural Documentation
Records and specifications describing the architecture of a system, crucial for effective communication and implementation.
Model-Driven Development
An approach where software is designed using models and from which code is generated, minimizing manual coding.
Modifiability
The ease with which a software system can be changed to address new requirements or corrections.
Performance
The ability of a system to execute its tasks within specified response times and resource usage.
Availability
The degree to which a system is operational and accessible when needed, often emphasizing redundancy and fault tolerance.
Testability
The degree to which software can be tested to ensure it meets its requirements and functions correctly.
Functionality
The specific behaviors or capabilities of a software system, often defined by the requirements.