Requirements, Architecture, and Building Software Flashcards

Comprehensive vocabulary flashcards covering software requirements, international quality standards, architectural patterns, design principles, testing methodologies, and operational concepts based on the lecture series.

-ilities

Desirable system attributes, also known as non-functional requirements, that represent quality-related aspects affecting long-term success and maintainability.

Evaluation: Good. Focusing on '-ilities' helps assess software quality and user satisfaction.

Usability

How user-friendly and intuitive the software is.

Evaluation: Good. High usability enhances user experience and can lead to better adoption rates.

Maintainability

How easily the software can be modified to correct faults, improve performance, or adapt to a changing environment.

Evaluation: Good. Maintainable software minimizes ongoing costs and effort required for updates.

Scalability

The ability of the software to handle growing amounts of work gracefully or its potential to be enlarged to accommodate growth.

Evaluation: Good. Scalable systems ensure long-term viability as demand increases.

Availability

The proportion of time the system is functional and working, often measured as a percentage.

Evaluation: Good. High availability is crucial for user trust and satisfaction in critical applications.

Reliability

The ability of the software to perform its required functions under stated conditions for a specified period.

Evaluation: Good. Reliable software reduces user frustration and operational risks.

Portability

The ease with which the software can be transferred from one environment to another.

Evaluation: Good. Greater portability allows flexible deployment options and wider usage scenarios.

Testability

How effectively the system can be tested for defects.

Evaluation: Good. Testable software leads to quicker identification of issues and improves overall quality.

Flexibility

How easily the software can be modified to accommodate changes in its environment or requirements.

Evaluation: Good. Flexible software can adapt to new needs without extensive rework.

Interoperability

The ability of the software to interact with other systems or components.

Evaluation: Good. High interoperability supports integration and enhances the software ecosystem.

Reusability

The degree to which components or parts of the software can be used in other systems or applications.

Evaluation: Good. Reusable components save development time and resources.

Security

The protection of the software against unauthorized access or modifications.

Evaluation: Good. Strong security measures protect user data and maintain trust.

Performance

How the system behaves in terms of speed, response time, and throughput under particular conditions.

Evaluation: Good. Optimal performance enhances user satisfaction and operational efficiency.

Stability

The software's ability to run without unexpected terminations or behavior.

Evaluation: Good. Stable software avoids frustration and enhances user confidence.

Accessibility

The software's ability to be used by end users with different technical, physical, and mental abilities.

Evaluation: Good. High accessibility ensures a wider user base and compliance with regulations.

Compatibility

The capability of the software to coexist with other systems, sharing resources without degrading functionality.

Evaluation: Good. Ensures smooth operation in diverse IT environments.

Configurability

The ease with which the software can be tailored to specific needs without modifying its source code.

Evaluation: Good. Configurable software can better meet specific user or business needs.

Modularity

The degree to which the software is composed of discrete components such that a change to one has minimal impact on others.

Evaluation: Good. Modular design supports easier updates and improves maintainability.