Web: Protocols, Languages, and Security

A structured approach to system design that emphasizes dividing a system into smaller, manageable modules or functions.

The degree to which the components within a module are related to each other.

The degree of interdependence between software modules. Low coupling indicates that modules are relatively independent.

A design principle where implementation details are hidden behind a well-defined interface.

A measure of the resources a program consumes (e.g., CPU time, memory) and its responsiveness.

The ability of a system to withstand errors, failures, or unexpected conditions without crashing or losing data.

The ease with which a system can be modified, adapted, or extended to meet new requirements.

The degree to which a system meets the specified needs of the users or stakeholders.

Process of assessing the system to identify potential security weaknesses or vulnerabilities. Includes threat modeling, code review, and penetration testing.

Safeguards put in place to protect system assets from potential threats, covering confidentiality, integrity, and availability.